The reports a hotel general manager actually reads at nine in the morning

By nine in the morning the general manager of a hotel has already checked occupancy, the day’s arrivals and last night’s complaints. The restaurant gets, at best, two minutes of their attention. If you hand them a twenty-page report in those two minutes, they will not read it. If you hand them four numbers with one question each, they will act.

Why most restaurant reports go unread

The point of sale in almost any restaurant produces dozens of reports: sales by item, sales by server, sales by hour, menu mix, theoretical cost, tips, payment methods. Each is useful to someone at some point. None of them is useful to the hotel general manager at nine in the morning, because none answers the question they actually have: did the restaurant in my hotel do what it was supposed to do yesterday with the guests who were sleeping here?

The problem is not a lack of data. It is a lack of hierarchy. When everything is reported with the same weight, nothing gets read. The manager ends up asking the captain how the night went, and the answer is always the same: good, busy. You cannot run anything on that.

What works is the opposite: a few numbers, always the same ones, always in the same order, always compared against something. A number without a comparison is a data point. A compared number is a signal. And a signal with an action attached is a report that actually gets used.

The first number: net sales by revenue center against the same day last week

The first number is yesterday’s net sales, split by revenue center: restaurant, bar, room service, pool bar, whatever you have. Net means without tax, without tips, and with discounts and comps already deducted. It is compared against the same day of the previous week, not against yesterday, because a Tuesday does not look like a Saturday and comparing them only produces noise.

Reading it takes twenty seconds: which center went up, which went down, and by how much. The question it answers is simple: did any revenue center step outside its normal range? If the restaurant dropped by a third on a Tuesday with similar occupancy, something happened. It closed early, staff were short, the menu changed, there was an event outside. The number does not say what, but it says where to look.

The action it triggers is a targeted question, not a meeting. The manager asks the person responsible for the center that stepped out of range, and only that person. The centers that are in range do not need a conversation that morning.

The second number: food and beverage revenue per occupied room

The second number is the one that connects the restaurant to the hotel: yesterday’s total net food and beverage revenue divided by the rooms occupied last night. That metric has a place in the hospitality accounting standard, it is explained in detail in another article (How food and beverage revenue per occupied room is calculated, and what a good number looks like), and it is what separates a restaurant that sells from a restaurant that captures its own guest.

The reading is quick as well: yesterday’s number against the average of the last thirty days. If occupancy went up and revenue per room went down, the restaurant sold to the street and let the guest walk past. If occupancy went down and revenue per room went up, the few guests who were there did eat. Two different scenarios with two different answers.

The action lives in the relationship between the front desk and the restaurant. If the number falls with high occupancy, the question is which segment arrived last night and why they did not come down for dinner: a group with dinner elsewhere, a corporate agreement without meals, a wave of late arrivals. The hotel general manager is the only person who holds both halves of the answer, which is why this number belongs to them and not to the chef.

The third number: the day’s leakage, in one figure

The third number adds up three things that most hotels report separately or not at all: comps, discounts and voids after the order was sent to the kitchen. It is expressed as a percentage of the day’s gross sales. It does not matter that each one has a valid reason; what matters is the total and whether it moves.

The reading is against a fixed threshold the hotel decides, not against the previous day. Below the threshold, nobody asks anything. Above it, the manager pulls the detail: who authorized, in which center, with what reason, at what time. A single high day can be an event with agreed comps. Three high days in a row are a pattern, and a pattern has a first and last name.

The action is to open the detail, not to scold. A discount without a captured reason is not fraud; it is a system that does not require a reason. When the system requires one, the number reads itself and the manager no longer needs interrogations.

The fourth number: unreconciled room charges and cash variance

The fourth number has two parts that are read together because they tell the same story: money that left the restaurant and has not yet arrived at the hotel. The first part is the amount of consumption charged to guest folios that does not yet appear on the front desk statement. The second is the cash variance at close: what should have been in the drawer against what was counted.

If room charge is tied to the guest folio, the first part should be zero every morning: what was charged last night is already on the folio before the guest comes down for breakfast. If it is not zero, there are charges that will be disputed at check-out or never collected. The second part, the cash variance, has its own article on the close by revenue center (A guide to the shift close by revenue center in a hotel), but for the manager one rule is enough: any variance, in either direction, gets explained that same morning.

This action is the most urgent of the four, because time works against you. An unreconciled charge for a guest checking out at noon today gets collected today or never. That is why this number is read before departures, not after.

An illustrative example of the full reading

The figures below are invented to show how the four numbers are read in two minutes. They are not data from any hotel or from the industry. Assume a sixty-room hotel with a restaurant, a bar and room service, with forty-two rooms occupied last night.

In the example, the full reading takes under two minutes and produces three actions: a question to the restaurant captain about the drop, a review of the leakage detail and a reconciliation of 1,800 before guests leave. The bar and room service need no attention that morning. That is managing with numbers: knowing where not to look.

What the report looks like in practice

Format matters as much as content. A report you have to go looking for does not get read; a report that arrives on its own does. The minimum conditions for the four numbers to be used every single day are few, but not negotiable:

• It arrives before nine without anyone having to generate it. If it depends on the night cashier exporting something, one day it will not arrive.
• It fits on a phone screen. Four numbers, four comparisons, four colors. No tables with twenty columns.
• Each number has its reference next to it: the same day last week, the thirty-day average, the threshold or zero. Without a reference the number cannot be read.
• Each number opens its detail with one tap. The manager should not have to ask anyone for the breakdown; they open it themselves if they need it.
• It uses the same revenue center names the front desk and the controller use. If the restaurant calls it "terrace" and the controller calls it "center 3", nobody will reconcile anything.

All of this is only possible if the restaurant point of sale knows it lives inside a hotel: it knows last night’s occupancy, ties every charge to a folio and separates sales by revenue center from the source. The reports page (Reports) shows how a dashboard is built under these conditions, and the page for the general manager (General manager) explains what each role sees.

What the manager should not read at nine

Just as important as the four numbers is the list of what stays out of the morning report. Not because it does not matter, but because it has another moment and another owner.

• Sales by server. That belongs to the captain and the weekly report; read daily it becomes an unfair ranking.
• Menu mix. That belongs to the chef and the monthly menu review.
• Food cost. That belongs to the controller and depends on inventories that are not taken daily.
• Tips. They belong to the servers and are shared under their own rule; they tell the manager nothing about the operation.
• The detail of every check. It only gets opened when one of the four numbers asks for it.

When the manager respects this list, something curious happens: they start trusting the four numbers because they are always the same, and they start delegating the rest because they know someone else reviews it. The morning report stops being an obligation and becomes a two-minute habit.

What to do this week

1. Write the four numbers with their references on one sheet and ask the restaurant to send them to you tomorrow at nine, even by hand. You will discover which data point does not exist yet.
2. Define your hotel’s leakage threshold with the controller. One percentage, written down, that does not change every week.
3. Ask for room charge to be tied to the guest folio rather than a typed number. Without that, the fourth number will always be an estimate.
4. Unify revenue center names across restaurant, front desk and accounting. One list, one name per center.
5. For five days, read only those four numbers and note what action you took with each. By the end of the week you will know which of the four changed a decision.

Inn Restaurant builds this morning report with the four numbers tied to the hotel: last night’s occupancy, real folios and revenue centers separated from the source. If you want to see how it reads on a general manager’s phone, the fifteen-minute demo is booked from the contact page (contact).