The food and beverage manager who runs the hotel restaurant from a phone: what to watch and what to leave alone

The food and beverage manager of a hotel does not live in the restaurant. They live between the restaurant, the bar, the kitchen, the meeting with the general manager and the call from the controller. The phone promises to show them everything without being anywhere, and that is where the trouble starts: seeing everything is not leading, and a phone full of numbers can turn you into the boss who interrupts every five minutes.

The phone extends the floor, it does not replace it

There are two ways to use a phone as a food and beverage manager. The first is as a window: you glance in, confirm service is running, and go back to what you were doing. The second is as a remote control panel, where every number invites you to call the captain and ask why. The first gives you time; the second takes it from you and from the team.

The difference is not in the app but in what you decide to look at. A hotel restaurant produces dozens of possible indicators, and almost all of them are noise when you watch them in real time. What you need on the small screen is the handful of numbers that change a decision today, plus alerts that only fire when something leaves the range you defined yourself.

Everything else belongs to the next morning’s report, read calmly, with coffee, and with the controller beside you if needed. That separation between what is watched live and what is analyzed the next day is the first decision of a manager who leads well from a distance.

The five numbers that fit on one screen

If you had to reduce the day to a screen that can be read in thirty seconds, these are the indicators a hotel food and beverage manager needs to see, in this order.

• Sales for the day by revenue center, compared with the same day last week. Restaurant, bar, pool bar, room service and coffee shop, each on its own line. A single total hides that the bar went up while the restaurant went down.
• Room charges posted today and how many are tied to a verified folio. If the count of charges without a folio rises, something is wrong in the link with the front desk, and you will pay for it at check-out.
• Tables and tickets open longer than a set time. A ticket open for forty minutes at breakfast is either a table waiting for the check or a server who forgot to close it. Both cost you.
• Discounts, comps and voids for the shift, with the name of whoever authorized them. Not to scold anyone, but because the sum of small courtesies is where margin dissolves fastest.
• Status of the shift close by revenue center: which one has closed, which is still open, and whether there is a variance against what was expected. The controller will ask tomorrow; better to know today.

Notice what they have in common: each one answers a concrete decision you can make today. Trend indicators such as revenue per occupied room or the month’s food cost are extremely valuable, but they do not move in an hour and they do not belong on the phone. How that full dashboard is built is explained on the reports page (Reports).

What you should not watch from the phone

Some information does harm on a phone, not because it is false but because it invites you to step in where you should not. Three examples that repeat in almost every hotel.

Ticket by ticket

Watching every order that leaves the kitchen from your phone is the fastest way to become a second captain at a distance. Knowing that table twelve ordered two mains and a starter does you no good. Knowing that the average check per cover for the shift is running low does, and you see that in one number, not in forty orders.

The dining room camera

Some managers connect the restaurant camera to their phone and open it constantly. The team knows, and what it produces is not discipline but performance. A server who works for the camera does not work for the guest. If you need to see the room, go to the room; physical presence sends a message the camera never will.

Live inventory

Stock changes with every plate and every delivery to the storeroom. Watching it minute by minute from the phone leads you to call the chef about a shortage he already knows about and has already solved. Inventory is reviewed at close, against the day’s sales, with the report in hand, not with a thumb.

Alerts: few, actionable and owned

A good alert has three parts: a threshold you defined, a person who receives it, and a clear action when it arrives. If you cannot say what you would do on receiving it, it is not an alert, it is noise. And alerts that fire all the time end up muted, so be stingy with them.

Notice that the only alert that goes to the captain and not to the manager is the open ticket. That is on purpose: the captain is in the dining room and can walk to the table. From the phone, all you could do is call to tell them what their own screen already said.

An illustrative example with numbers

The figures below are made up to show the calculation; they are not data from any hotel or from the industry. Picture the restaurant of a 60-room hotel. The dinner shift sells 24,000 in total. You decided that comps and discounts should not exceed 5 % of shift sales, that is, 24,000 × 0.05 = 1,200.

At ten at night the app shows shift discounts at 1,800. That is 600 above the cap and equals 7.5 % of sales (1,800 ÷ 24,000 = 0.075). With a well-placed alert, you knew at nine thirty, when they stood at 1,300, and you sent the captain one question: what happened. The answer was that a group of twelve with a corporate agreement received a discount that was already built into their rate, and it was applied twice.

Without the alert, that same fact shows up in the next day’s report, after the group has checked out and the charge has already gone to the folio with the error in it. Fixing it means a credit note, a conversation with the controller and a call to the company. With the alert, it was a two-line message at nine thirty.

Now the other side: if instead of an alert you had been watching every ticket, you would have called the captain at the first discount, at eight, when everything was fine. And at nine. And at nine fifteen. The captain would have stopped answering you by nine thirty, exactly when it mattered.

The temptation to micromanage

The phone does something dangerous: it removes the cost of asking. Before, to know how service was going you had to walk to the restaurant or call the extension, and that small friction forced you to decide whether the question mattered. Today asking costs one message, and a manager who sends twenty messages per shift is not leading; they are interrupting.

The rule that works best is simple: if the number you are looking at is inside the range you defined, you do not write. Not to congratulate, not to ask, not to suggest. The team has to be able to work a full shift without knowing you are watching, because what you are watching is the result, not the people.

And when you do write, write a question, not an order. The captain is in the dining room with the full context; you have a number on a screen. Most likely they already know what happened and are already handling it. Your message is there to confirm someone owns it, not for you to solve it from the parking lot.

A manager who trusts the team shows it on the phone: few alerts, few messages, and a serious review the next day. What that role looks like in the daily operation of a hotel is developed on the page for managers (General manager).

A day well run from the phone

In the morning

Before breakfast opens, a one-minute look: how last night’s dinner closed by revenue center, whether every close is done, and whether there are room charges pending verification for guests leaving today. With that, if something is wrong, you talk to the front desk before the guest reaches the counter with a suitcase.

Mid-afternoon

Between lunch and dinner service, another look: breakfast and lunch sales against the same day last week, plus whatever alerts came in. This is where you decide whether it is worth stopping by the restaurant or whether the team has it under control.

At night

When the bar is still open and the restaurant closes, the restaurant close is what matters. If it closed and balanced, you go to sleep. If it did not close, that is a message worth sending, because a variance investigated tonight takes five minutes and tomorrow takes an hour.

What the system needs for this to be possible

None of this works if the restaurant’s point of sale keeps its data on a server inside the hotel that your phone cannot reach, or if the room charge is a text field where the server types a number and moves on. For the indicator of charges without a folio to exist, the charge has to be born tied to the guest’s real folio the moment the server captures it, as explained on the room charge page (Room charge).

You also need revenue centers separated in the system from the start. If the pool bar and the restaurant share a single register, the phone will show you a total that is useless for any decision. And you need alerts configured by threshold and by person, not a stream of identical notifications for everyone.

• Data in the cloud, so the phone can see it from wherever you are, without connecting to the hotel’s internal network.
• Separate revenue centers, each with its own close and its own sales line.
• Room charge tied to the guest folio, not to a typed number.
• Alerts configurable by threshold and recipient, with the option to silence them by schedule.
• A next-morning report that does carry all the detail, so the phone does not have to.

What to do this week

1. Write on one sheet the five numbers you want on your phone and cross out any that do not change a decision today.
2. Define three alerts at most, each with threshold, recipient and action. If you cannot write the action, delete the alert.
3. Count how many messages you sent the captain during the last dinner shift. If it was more than three, cut it in half next week.
4. Check with the front desk how many room charges this month arrived without a verified folio. That number is the first one you want on your screen.
5. Block fifteen minutes every morning for the previous day’s detailed report, and stop looking for it on the phone during service.

Inn Restaurant was designed so the food and beverage manager of a hotel sees from a phone what actually changes a decision, with revenue centers kept separate and every charge tied to the guest folio. If you want to see how those alerts are configured, a fifteen-minute demo (contact) sets them up with you.