Method · K.L. Kropf, Founding Partner · October 2026

Hotel F&B staff rostering: staff to forecast covers per hour

Hotel F&B staff rostering fails on the same assumption as every other department: that occupancy sets the workload. In a hotel restaurant, who is in the house sets it. A 250-room city hotel at the same occupancy serves 190 breakfast covers on a corporate Tuesday and 420 on a tour-group Saturday. The low-hanging fruit is to roster the servers and cooks you already have to the forecast covers per hour. Ordering kiosks, buffet-only service and outlet closures come after, for the gap the roster cannot close.

−9.8%F&B labor at a 250-room Bangkok hotel, breakfast satisfaction unchangedHotelCadence client results, baseline-verified

190–420daily breakfast-cover swing at that hotel on similar occupancyHotelCadence client data, anonymized

−14%low-season F&B labor-to-revenue at a Bali resort, high season untouchedHotelCadence client results

HotelCadence is workforce software for hotels. It reads the bookings already in your property system, forecasts how busy each department will be hour by hour, builds the roster to match, records worked hours and prepares payroll. Department heads approve every roster. From US$6 per scheduled employee per month.

Hotel F&B staff rostering is the planning of restaurant, bar and banquet shifts so that the servers and cooks on duty each hour match the covers the outlet will serve in that hour, within the working-hour and rest rules of the market.

The flat breakfast team, and what it costs

The breakfast roster at that Bangkok hotel said eleven staff, every day. On the 190-cover Tuesday four of them polished cutlery. On the 420-cover Saturday eleven could not clear tables fast enough and the queue at the omelette station became the review headline. Required staff swung between seven and thirteen; the roster never moved. Idle hours on one side, overtime and complaints on the other, and a fixed 11-person cost sitting on a demand curve that halves and doubles inside one week.

Step 1: identify the F&B workload drivers

In-house guests by segment. Tour groups eat breakfast at close to double the rate of corporate guests, and they arrive together at 07:00.
Breakfast inclusion and package codes. A rate with breakfast included changes the capture rate.
Group meal plans and the banquet calendar. A 200-pax plated lunch is its own roster.
Outlet mix. Pool bar, lobby lounge, all-day dining and the signature restaurant peak at different hours.
Day of week and weather. Terrace covers on a dry evening; room service on a monsoon night.
Season. Bali's occupancy swings about 38 points between the monsoon low and the August peak.
Local walk-in demand. City restaurants with a street entrance follow the neighbourhood before they follow the rooms.

Step 2: get data on the drivers

Your property system holds tomorrow's in-house count, segment codes, package codes and group blocks. Your restaurant tills hold covers by outlet by hour for the last two years. Together they are the forecast. The manual start is a weekly spreadsheet that applies capture rates by segment to the in-house forecast. The step up is AI demand forecasting that reads both systems daily, learns the capture rate per segment per outlet, blends events and weather, and forecasts covers per hour two weeks out. Forecasting per outlet per hour →

Step 3: set the labour standard

For F&B it is covers per server, covers per cook, and the minimum floor presence an open outlet needs. Example, figures indicative: 20 covers per server at breakfast, one cook per 50 covers, two servers and one cook minimum while the outlet is open. A forecast of 300 covers between 07:00 and 09:00 means eight servers and three cooks at peak; by 10:30 the same standard says three and one. Agree the ratios with the F&B manager and the chef, by outlet and service style, so the standard and the service promise are the same number.

Step 4: design shifts around the meal peaks

F&B work comes in meal peaks, so the shifts split. Design staggered starts so the floor is set before the first wave, a cut order so staff leave as service slows, and a separate banquet roster driven by the event calendar. Keep every shift inside working-hour limits, rest rules, split-shift rules and overtime caps for the market. An optimizer treats those as constraints and drafts the lowest-cost roster that still meets the standard. AI shift design →

Step 5: fill the shifts

Assign by outlet skill, language and cost. Put the bartender who knows the wine list on the signature restaurant Saturday. Honour contract hours and requested days off. Schedule daily-wage casuals and agency pools from the same roster with their own constraints, so the cost per outlet is visible. The F&B manager sees the covers behind every shift, edits, and approves.

When kiosks and consolidation make sense

After the roster follows covers, look at the hours where the minimum presence exceeds what the forecast justifies. That is where consolidating outlets on quiet days, moving to buffet-only in the trough or adding an ordering kiosk pays. A Bali resort did this for the monsoon months, consolidating outlets on quiet days and leaving high season untouched, and cut low-season F&B labor-to-revenue 14%. Bali low-season F&B case study →

The result, measured

The Bangkok hotel forecast breakfast covers from Cloudbeds reservation data, converted them to staff through the F&B manager's own standard, and let the roster flex between seven and thirteen. F&B labor fell 9.8% in a quarter with breakfast satisfaction unchanged. Bangkok breakfast roster case study →

Questions F&B managers ask

How many servers does a hotel restaurant need per shift?

Divide forecast covers in the peak hour by covers per server. Common rules of thumb are 16 to 25 covers per server for full-service and one cook per 40 to 60 covers at peak. A breakfast expecting 300 covers between 07:00 and 09:00 at 20 covers per server needs about eight servers at peak, then four by 10:00.

What drives F&B workload in a hotel?

In-house guests and their segment above all: tour groups eat breakfast at close to double the rate of corporate guests. Then breakfast inclusion in the rate, group meal plans, the banquet calendar, outlet mix, day of week, weather for terraces and pools, and local walk-in demand. Occupancy alone misses the segment effect.

Is covers per occupied room enough to forecast?

It is the usual starting point and it misses the two things that move hotel covers most: segment mix and in-house groups. A 250-room hotel can swing from 190 to 420 breakfast covers on the same occupancy depending on who is in the house. Forecast from the reservation mix in your property system; a single multiplier misses it.

Should we add ordering kiosks or cut outlets before fixing the roster?

Roster to forecast covers first. Most outlets run a fixed breakfast team every day while covers swing by half. Matching servers to the forecast peak and cutting as service slows removes idle hours without touching the menu. Consolidate outlets or add kiosks afterwards, for the quiet periods the roster cannot staff below minimum presence.

See next Saturday's breakfast covers forecast from your own booking data

30 minutes, your data, written estimate of your labor-cost gap either way.