Comps, discounts and voids in one report: the leakage dashboard of the hotel restaurant
Each one looks small and justified on its own. Added together in one dashboard, the comps, discounts and voids of the hotel restaurant tell a story nobody sees when they are reported separately. Here is how to build that dashboard, how often to review it and which thresholds force a closer look.
In a hotel restaurant there are three legitimate ways for a sale to be worth less than the menu says: a comp, a discount and a void. All three have valid reasons. All three are authorized by different people, at different moments, on different reports. And precisely because of that, the three of them together are where the most revenue leaves without anyone noticing.
Why they are reported separately, and why that is a problem
The comp is authorized by the hotel general manager for an upset guest or for the director of a company with an agreement. The discount is applied by the captain with the employee card or the promotion of the day. The void is done by the cashier when the server keyed the wrong table. Three people, three reasons, three moments. The point of sale stores them in three reports, each with its own total, and each total looks reasonable.
The problem is that the revenue that left does not know which of the three doors it went through. The hotel controller does not care whether a two-hundred dish was given away, discounted at one hundred percent or voided after it was served: in all three cases the hotel bought the ingredients, paid the cook and did not collect. Added together, those three doors are one leak, and the leak is only visible when it is looked at as one.
There is a second, more uncomfortable problem. When the three are reported separately, anyone who wants to take consumption out of the restaurant without paying quickly learns which of the three is reviewed least, and uses that one. A single dashboard removes that option: whichever the door, the total shows.
What goes into the dashboard and what does not
The leakage dashboard adds three concepts and only three. Defining them precisely avoids the monthly argument about what was counted and what was not.
- Comps: consumption that was delivered and recorded at zero value, or closed with the "comp" payment method. This includes items charged to a guest folio and later adjusted to zero at the front desk, because they also left your kitchen.
- Discounts: the difference between menu price and price collected, for any reason: corporate agreement, employee, promotion, adjustment after a complaint. Count the discounted amount, not the whole check.
- Voids after sending to the kitchen: items that were fired to the kitchen or bar and then removed from the check. Voids before sending, which are keying errors, do not count: they cost no ingredients.
What does not go in: staff meals, if they have their own account and their own budget; breakfast included in the rate, which is recorded with an allocation value and is not a comp; and consumption at an event that was already agreed as part of the group contract. All of that is planned expense. The dashboard measures what was not planned.
The columns that make the dashboard useful
A total is not enough. For the dashboard to trigger actions rather than just worry, every line needs the same set of columns, captured at the moment and not rebuilt afterwards. If the point of sale does not ask for any of these when the comp, discount or void is applied, the dashboard is born incomplete.
| Column | What it is for | Who captures it |
|---|---|---|
| Type (comp, discount, void) | Separate the three doors when needed | The system, on application |
| Amount at menu price | Add the leak into one figure | The system |
| Reason from a closed list | Group by cause and spot the reason that grows | Whoever applies it, mandatory |
| Authorized by | Know who holds the key and how often they use it | The system, with a personal code |
| Revenue center and table | See whether the leak lives in the bar, the terrace or room service | The system |
| Server and cashier | Cross with the sales-by-person report | The system |
| Time | Find the hour when nobody is watching | The system |
| Guest folio or corporate account, if any | Verify the comp reached who it was meant for | The system, from the room charge |
The reason column deserves its own rule: the list is closed and short. Ten reasons at most, with one that says "other" and requires free text. If "other" exceeds a fifth of the lines, the list is badly built or someone is using it to avoid explaining.
How often it is reviewed
The dashboard has three readers and three rhythms. Mixing them up is what gets a report abandoned: if the hotel general manager has to read every line every day, they stop reading it within two weeks.
Daily: one figure
The hotel general manager sees a single figure each morning: total leakage for the day as a percentage of gross sales, next to the other numbers of the morning report (Reports). If it is below the threshold, they open nothing. If it is above, they open the day’s detail and look for the largest line.
Weekly: reasons and people
The food and beverage manager, or the captain if there is no manager, reviews the week grouped by reason and by who authorized. This is where patterns a single day cannot show appear: the same reason three times a week, the same authorization code used at the same hour, the same server with voids after sending.
Monthly: trend and cross-check with the front desk
The hotel controller compares the month against the previous three and crosses the comps charged to folios against the adjustments made at the front desk. This is the review that closes the loop: a restaurant comp the front desk did not adjust was charged to the guest by mistake; a front desk adjustment with no comp recorded in the restaurant is a sale that vanished after being collected. The page for the controller (Controller) describes that cross-check.
The thresholds that trigger a review
A threshold is a promise: below it, nobody asks; above it, someone looks. Without a threshold, the dashboard becomes a source of anxiety that produces no action. Each hotel sets its own thresholds according to its operation, but the structure is the same for everyone.
- Daily threshold on the total: a percentage of the day’s gross sales. Above it, the manager opens the detail that same morning.
- Per-line threshold: an absolute amount above which a single comp or discount needs a second authorization before it is applied, not after.
- Weekly threshold per person: a number of voids after sending per server or per cashier. Above it, a conversation with the person, not a sanction.
- Concentration threshold: if one authorization code accumulates more than half the comps of the month, the code gets reviewed, not the person.
- "Other" threshold: if the free-text reason exceeds a fifth of the lines, the reason list gets rebuilt.
What matters about thresholds is not the exact number but that they are written down, that everyone knows them and that they do not change every week. A threshold that moves so the report looks good is not a threshold.
An illustrative example with numbers
The figures below are invented to show the calculation and the reading. They are not data from any hotel. Assume the hotel restaurant sold 210,000 at menu price in one week, with a weekly leakage threshold of 5 %.
| Item | Amount | Lines | Reading |
|---|---|---|---|
| Comps | 6,300 | 21 | Twelve authorized by the same code |
| Discounts | 5,600 | 48 | Corporate agreement: 4,200; employee: 1,400 |
| Voids after sending | 2,800 | 19 | Eleven between eleven at night and one in the morning |
| Total leakage | 14,700 | 88 | 14,700 ÷ 210,000 = 7 % |
The reading is not "the restaurant gives away too much". It is finer than that. The corporate agreement discounts are planned expense: 4,200 that were already in the contract. Subtracting them, unplanned leakage is 10,500, which is exactly 5 %: at the threshold, not above it. But the two concentrations do call for action: one code with twelve comps out of twenty-one, and eleven voids out of nineteen in the last hour of the night. Without the authorized-by and time columns, those two signals would not exist; there would only be a 7 % that scares and explains nothing.
What to do with what the dashboard shows
The dashboard accuses no one. It shows concentrations, and every concentration has an explanation that may be perfectly valid. The rule is that the explanation is always asked for, calmly, and written down. Three unconvincing explanations in a row are something else.
The most frequent actions are about the system, not about people: require a second authorization above a certain amount, remove the comp code from whoever does not need it, require a reason on every void after sending, and put the manager on duty physically in the bar during the hour when voids concentrate. Another article walks through the eight places where consumption gets lost in a hotel (The eight places where a hotel loses food and beverage revenue); the leakage dashboard covers three of them with a single report.
Comps, discounts and voids after sending are one leak with three doors, and it only shows when added into a dashboard with reason, authorized by, revenue center, time and folio. It is read as a daily figure against a threshold, as weekly patterns by person and as a monthly trend crossed with the front desk.
What to do this week
- Pull last week’s three reports, comps, discounts and voids, and add them by hand on one sheet. Divide by gross sales. That percentage is your starting point.
- Write the closed list of reasons, ten options at most, and ask the system to require it when any of the three is applied.
- Review who holds a code to authorize comps. If it is more than three people, decide which ones keep it.
- Set the daily threshold and the per-line threshold with the controller, write them down and share them with the restaurant team.
- Ask for last month’s comps charged to folios to be crossed against the front desk adjustments. You will find at least one difference.
Inn Restaurant builds the leakage dashboard with those columns captured on application, with closed reasons, a personal code per authorization and the guest folio tied to every comp. If you want to see how a week reads on a single dashboard, the fifteen-minute demo is booked from the contact page (contact).
More articles
The reports a hotel general manager actually reads at nine in the morning
A hotel general manager does not need thirty restaurant reports. They need four numbers, read in two minutes, each with a clear action behind it. Here they are, with an illustrative example and the question each one answers.
The hotel lobby bar: why it is the revenue center with the most open tabs and the least control
The hotel restaurant opens and closes checks by table, with a server per section and a captain watching. The lobby bar opens tabs by seat, moves them between rounds, charges them to rooms and closes after the manager has gone home. This article explains why that revenue center is different and where control slips away.
The report the hotel controller wants on the first of the month, and why it arrives on the eighth
The hotel controller asks for the food and beverage close on the first day of the month. It arrives a week later, with manual adjustments and room charges nobody can attribute to a guest. Here is the anatomy of those eight days and how they become one.
Your hotel’s restaurant already sells well. Now the hotel needs to know it.
Fifteen minutes, with your menu and your tables. Nothing to install.