Product
Operation types
Pricing
Compare
Resources
Log in See a 15-minute demo ESEN
Article · 8 min

The owner who wants to know without being there: the five numbers of the hotel restaurant that fit in one message

You do not need to stand in the hotel restaurant to know how the day went. You need five numbers, measured the same way every time, that reach the owner’s phone without anyone having to type them by hand.

Some hotel owners live half an hour from the restaurant, others live in another country. The same thing happens to both: they want to know how the day went without having to go, without having to call and without depending on someone remembering to send the number. The answer is not more reports. It is fewer, the right ones, and they should arrive on their own.

The owner who is not there but wants to know

The pattern repeats in almost every hotel with a restaurant that grows past the full-time owner-operator stage. At first the owner is there, sees the cash drawer, tastes the dish, greets the guest at table three. Once a second property opens, once daily operations get delegated, or simply once the owner wants a weekend off, that presence becomes impossible. And the question they used to answer with their own eyes now has to be answered by someone else, or by a system.

The problem is not the owner’s absence. It is that most hotels never defined what information someone who is not there needs to make decisions remotely. The manager sends what they can, when they can: a photo of the close, a voice message summarizing the night, a sales total that does not say where it came from. The owner reads that and does not know whether to ask more or just trust it.

Why sending photos of the close does not work

The photo of the cash close is the most common reflection of this problem. Someone photographs the close-out sheet and sends it by messaging to the owner’s group. It feels like transparency, and in the moment it is. The problem shows up later, when the owner wants to compare this week’s Thursday against last week’s and has to search through forty photos on their phone, each one in the handwriting of whoever closed that night.

  • The photo cannot be added up. If the owner wants the month’s total, someone has to pull out a calculator again.
  • The photo does not separate revenue centers. A mixed total of restaurant, bar and room service does not say where the problem is if something dropped.
  • The photo arrives whenever someone remembers. If the manager had a hard night, the report gets delayed on exactly the day it mattered most to see.
  • The photo does not explain the differences. A number crossed out and corrected by hand does not say who authorized it or why.

None of this is the manager’s fault. It is what happens when the report to the owner depends on a person writing it every night on top of everything else they have to close. The fix is not asking for more discipline. It is having the system send the numbers on its own, in the same format every time.

The five numbers that actually matter

An owner who wants to know without being there does not need forty reports. They need five numbers, the same ones every day, that together tell the full story of the hotel restaurant without requiring any interpretation.

NumberWhat it answers
Daily sales by revenue centerHow much did the restaurant, the bar, the coffee shop and room service each sell, separately?
Cash close resultDid expected cash match declared cash at every revenue center, and where did it not?
Guest room chargesHow much was charged to rooms, and how many of those charges were disputed at check-out?
Comps and discountsHow much was given away or discounted, and who authorized it?
Comparison against the same day the previous weekWas this Thursday better or worse than last Thursday, from the same starting point?
The five numbers an owner needs to know how the hotel restaurant did without being present.

Notice something: none of the five asks for anyone’s opinion. It does not say “good night” or “it felt calm”. They are figures the system already has, because the operation itself generates them: every sale, every close, every folio charge (Room charge) and every authorized comp gets recorded the moment it happens, not when someone sits down to write a report.

Why the comparison matters as much as the total

A total without a comparison is a loose fact. If the hotel restaurant sold 42,000 on Thursday, that number says nothing on its own. If last Thursday it sold 38,000, the owner knows something improved. If it sold 51,000, the owner knows something dropped and can ask what happened before it becomes a habit. The comparison turns a number into a signal.

How they reach the phone without anyone writing them

What makes all of this possible is that no human has to draft the message. The hotel restaurant’s point of sale already knows how much each revenue center sold, already knows the close result because it calculates it at cash close (Cash and shift close), already knows what was charged to each folio and already knows which comp had authorization and which did not. All that is missing is for that information to be assembled into a short message and sent on its own, every day, at the same time.

That is different from giving the owner access to a full reports dashboard, which also has its place (Reports) but requires someone to log in and check it. The daily message is the opposite: it arrives without the owner asking for it, it reads in the time it takes to check a notification, and if something does not add up, they can ask right there.

An illustrative example with numbers

The figures below are invented to show what the message would look like. They are not data from any hotel or any client.

ItemThis week’s ThursdayPrevious ThursdayDifference
Restaurant24,50022,000+2,500
Bar9,80010,600−800
Room service7,7006,200+1,500
Total sales for the day42,00038,800+3,200
Close variance (all revenue centers)−150−900+750
Guest room charges16,30013,100+3,200
Charges disputed at check-out1 for 3203 for 1,100−2 charges, −780
Comps and discounts1,200, all authorized1,600, one unauthorized−400
Illustrative example. Invented figures to show the content of the daily message to the owner.

With this table, the owner does not need to call anyone to understand Thursday. Total sales rose 3,200, and the detail explains where from: the restaurant rose 2,500 and room service 1,500, while the bar dropped 800. The close landed closer to zero than the previous week. Room charges rose in the same proportion as sales, which is consistent. And comps dropped and now all of them carry authorization, which is exactly the kind of improvement an owner wants confirmed without investigating it themselves.

Now picture the opposite message: total sales rise but the close gets worse, or comps grow without authorization while bar sales fall. That pattern, seen in time, is a conversation the owner can have Friday morning. Seen three months later in an audit, it is a problem that already cost money.

What to ask when something does not add up

The value of the five numbers is not just seeing them, it is knowing what to ask when one of them goes out of place. An owner who gets the message every day quickly learns their restaurant’s normal pattern, which lets them spot the unusual without needing to be present.

  • If the close does not balance two days in a row at the same revenue center, the question is who is on that shift and whether staff changed recently.
  • If disputed charges at check-out rise, the question is whether the server is verifying the folio before posting or only asking for a room number.
  • If comps grow without authorization, the question is who is applying them and whether the manager reviewed that night.
  • If sales at one revenue center drop several days in a row with no visible reason, the question is whether hours, the menu or a dish’s availability changed.

None of these questions requires the owner to be at the hotel restaurant. All of them can be asked by message, with the exact number in front of them, and all of them lead to a concrete answer in minutes instead of a suspicion that drags on for weeks.

Common mistakes when reporting to the owner

  • Sending the sales total without breaking it down by revenue center, which hides whether the problem is in just one of them.
  • Reporting sales without the close result, as if the two were not related.
  • Making the message depend on a person writing it every night, instead of having the system assemble it on its own.
  • Not comparing against the same day the previous week, which makes any number look normal.
  • Mixing daily operations with staffing or supplier topics in the same message, which deserve their own conversation.
In short

An owner who is not at the hotel restaurant does not need more reports, they need five numbers that arrive on their own and already compared: sales by revenue center, the close, room charges, comps and discounts. When the system assembles them without anyone typing them by hand, the owner can trust the numbers without needing to be present.

What to do this week

  1. Define the exact five numbers you want to receive every day, and in what order, without adding more than you will actually read.
  2. Check whether your point of sale can assemble those five numbers automatically at cash close, or whether they currently depend on someone typing them.
  3. Ask that the message always include the comparison against the same day the previous week, not just the day’s total.
  4. Agree with the manager on what questions you will ask when a number goes out of place, so it does not feel like a surprise.
  5. After two weeks of receiving the message, check whether you truly stop needing calls or loose photos, and adjust whatever is missing.

Inn Restaurant builds this daily message for the hotel owner from the same point of sale data: sales by revenue center, the close, room charges and comps, compared against the previous week without anyone having to type them. If you want to see what your own message would look like, book a 15-minute demo (contact).

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.

See a 15-minute demo
We use the minimum to make the site work and to know which pages are useful. You can reject the rest.