The Tuesday corporate traveler and the Saturday family: two different ways of consuming in the same restaurant

On a Tuesday at nine in the evening, your hotel restaurant has six tables for one, each with a closed laptop and a main course with no starter. On a Saturday at ten in the morning it has four tables of five, with children, with juice refills and nobody in a hurry. It is the same restaurant, the same menu and the same server. But if your report adds both days into a single average, you are reading a guest who does not exist.

Two guests who never cross paths

Almost every city hotel lives on two segments that take turns in the building. Monday through Thursday the corporate traveler arrives: the company books, the traveler comes alone, sleeps two or three nights and consumes with the clock running. Friday through Sunday the family or the couple arrives: booked directly or through an agency, coming as a group, staying one or two nights and consuming as part of the plan, not as a necessity.

The restaurant sees both go by, but it sees them very differently. The corporate guest fills the evening tables and the bar; the family fills breakfast, the pool and mid-afternoon room service. The corporate guest posts to the room because the company pays; the family pays at the table because it wants to know the running total. Each segment has its own hours, its own average check and its own way of paying, and the average of the two describes neither.

This is not a marketing problem. It is a reading problem: if the weekly report says revenue per occupied room was such a figure, the manager does not know whether it went up because corporate guests had more dinners or because there were more families. And without knowing that, the manager does not know what to move.

How the Tuesday corporate guest consumes

The corporate traveler has three consumption moments, and all three carry friction. Breakfast is early, quick and almost always included in the rate or the agreement, so its value depends on how you record it. Lunch is almost never at the hotel: it happens in offices, with clients, or not at all. Dinner is the moment that matters: the guest arrives late, alone, hungry and with no desire to think.

At that dinner, the corporate guest chooses fast, orders a main course, maybe a glass of wine, and wants to sign without waiting. If the room charge is a procedure, the guest orders something to the room by message or walks out to the street. If the charge is verified in seconds with the stay on screen, the guest dines with you tonight and tomorrow. The check is moderate but the frequency is high: three nights, three dinners, three opportunities.

The way this guest pays also defines how you read them. Almost all of their consumption goes to the folio and from there to the company account, under the agreement’s rules: a cap per dinner, food yes, alcohol maybe not. That means the corporate guest, in the restaurant’s shift close, barely appears as cash or card: they appear as room charge, as described on the corporate traveler page (Corporate traveler).

How the Saturday family consumes

The family does not have three moments: it has the whole day. It has a late, long breakfast with more drinks than plates. It goes down to the pool and consumes from the lounger, with no wallet, for hours. It eats mid-afternoon, sometimes in the restaurant and sometimes through room service because the children have fallen asleep. It has an early dinner as a group, with a high check per table and a low one per person.

Its relationship with the room charge is different. Many families prefer to pay at the table to control spending, or charge to the room only what they had at the pool because there is no alternative there. Their consumption is a single stay, with no agreement and no credit, so the restaurant’s Saturday close looks much more like a street restaurant: card, some cash and a share of room charges that almost always comes from the pool bar.

The family also has a schedule pattern the corporate guest lacks: it consumes where it is, not where the restaurant wants it to be. If the pool bar opens at one and the family has been there since eleven, two hours of thirst went to the corner store. If room service closes at ten and the children eat at seven, that does not matter. If the breakfast menu is the same as on weekdays, built for one hurried person, the family orders little.

The two segments side by side

The table does not say which segment is worth more. It says they are measured differently. The corporate guest is read by room night and by dinner frequency; the family is read by day and by revenue center. A single weekly metric flattens both stories.

An illustrative example with numbers

The figures below are invented to show how the reading changes when you separate by day of the week. They are not from any hotel; they only serve to follow the calculation of food and beverage revenue per occupied room on two different days.

An example hotel with 50 rooms has, on a Tuesday, 30 occupied rooms, almost all by corporate travelers. That day the restaurant sells 4,500 in dinners and the bar 3,000, net of tax and tips. On Saturday it has 38 occupied rooms, almost all by families. That day the restaurant sells 8,000 between breakfast and dinner, the pool bar 4,200 and room service 3,000.

Add the two days together and you get 22,700 over 68 occupied rooms: revenue per room of 334 that happened on neither day. Worse: if the following Tuesday the bar sells 2,000 instead of 3,000, Tuesday’s metric drops from 250 to 217, but the weekly average barely moves because Saturday hides it. Read by day, the corporate bar problem jumps out. Read as an average, it disappears. The article on how revenue per occupied room is calculated (How food and beverage revenue per occupied room is calculated, and what a good number looks like) explains the full formula.

Where the segment comes from: the folio, not the server

To read by segment you need to know which segment each consumption belongs to, and that information should not be captured by the server. The front desk has had it since the booking was made: whether it was direct, corporate or through an agency; whether the room is in a group block; whether the guest has an agreement. When the room charge is tied to the folio, the consumption inherits the segment without anyone typing it.

What is lost when the point of sale is not tied to the folio is exactly that. The check says "room 214", but it does not say whether room 214 holds an engineer from a company with an agreement or a family of four who came through an agency. And without that data, the only way to read by segment is by day of the week, which is a useful but coarse approximation: there are Saturday corporate guests and Tuesday families, and the season mixes them.

Walk-in sales are a third segment

Everything that is not posted to a room and does not come from an identified guest is walk-in revenue. That is not bad: it is another segment, with its own pattern, which in many city hotels keeps the bar alive on weekdays and breakfast full on Sundays. But it must not be mixed with guest consumption, because it inflates the per-occupied-room metric with money that did not come from the rooms. Separating it is the first step; reading it by day, the second.

What decisions come out of the reading

Reading by segment and by day is not a reporting exercise. It is what lets you move concrete things in the hotel restaurant without guessing. These are the ones that usually come out first.

• Hours by day: the pool bar opens earlier on Saturday and the lobby bar closes later on Tuesday. A single schedule for the whole week loses at both ends.
• Menus by moment: a weekend breakfast with dishes to share and a weekday one for a single person with twenty minutes. Same kitchen; what is offered first changes.
• Staff by shift: Tuesday night needs servers who close checks fast; Saturday morning needs servers who can hold long tables. Assigning by weekly average leaves one shift short and the other overstaffed.
• Agreements with dinner: if the corporate guest dines three times per stay, negotiating for the agreement to cover dinner up to a cap raises their revenue per room without touching the rate.
• Room service by messaging: the family orders from the lounger or from the room with the children asleep. A channel that does not require a phone call changes the Saturday pattern.
• What to review every week: Tuesday’s revenue per occupied room against the previous Tuesday’s, and Saturday’s against the previous Saturday’s. Never the week against the week.

The monthly reading that actually helps

Once you separate by segment and by day, the monthly report changes shape. Instead of one revenue-per-occupied-room figure, you have two or three: the corporate one, the family one and the walk-in one. And instead of comparing them against an industry average that does not describe your hotel, you compare them against your own Tuesdays and Saturdays from a month ago and a year ago.

That is what the controller needs to explain to the owner why the restaurant went up or down. "Revenue per room fell" says nothing. "Weekday corporate revenue fell because the bar sold less, while weekend family revenue rose thanks to the pool" says exactly what to do on Monday. The reports page (Reports) shows how that reading is built from the revenue center up.

What to do this week

1. Pull net food and beverage revenue for every day of the last four weeks, by revenue center, along with each day’s occupied rooms. Calculate revenue per occupied room day by day.
2. Group Tuesdays with Tuesdays and Saturdays with Saturdays. Note how much they differ from each other and how far they sit from the weekly average you report today.
3. Ask the front desk which segment it records on each booking and check whether that data reaches the restaurant check. If it does not, that is the first fix.
4. Separate walk-in sales from guest consumption in every revenue center’s close, even if it starts as a manual flag.
5. Review the pool bar and lobby bar hours against each segment’s peak moments, and adjust at least one this week.
6. Set, in the weekly meeting, a comparison of Tuesday against Tuesday and Saturday against Saturday, instead of week against week.

Inn Restaurant inherits the guest’s segment from the folio on every room charge and calculates revenue per occupied room by day, by revenue center and by segment, so Tuesday and Saturday are read separately. If you want to see what your two guests look like in a single report, the fifteen-minute demo is scheduled on the contact page (contact).