Most pre-service meetings are a mixture of yesterday’s complaints, today’s absences and a pep talk. The team leaves knowing to “have a good one” but not what the shift needs to achieve.
Give the manager three numbers instead: booked or expected covers, rostered hours and product constraints or priorities. These are not targets to chant at the team. They are the facts that shape the shift.
1. Expected covers
Expected covers tell the team where demand sits. A single number is useful, but the arrival pattern makes it actionable. A service with 86 covers arriving evenly needs a different plan from 86 covers concentrated between 7:00 and 7:30.
Ask the host, floor and kitchen to identify the pressure point before doors open. The purpose is not to create anxiety. It is to decide how the door, bar, pass and sections will move through the busy window.
2. Rostered hours
Rostered hours make the labour plan visible. The manager needs to know where experience sits, where the gaps are and what can change if the service runs differently from forecast.
Use the number to start a practical conversation: who owns the door at the rush, who can support the pass, which break can move, and who has authority to make the call. A roster is not a plan until people understand how it works on the floor.
3. Product constraints and priorities
Product constraints stop the floor selling something the kitchen cannot deliver. That might mean a supplier shortfall, a slow-moving item to use carefully, a batch that needs checking, or a dish the team should explain differently.
Be precise. “The seafood special is limited to twelve serves, so confirm availability before promising it” is clearer than “watch the specials”.
Photo: Unsplash
Before-service decision card
| Number | Ask before doors open | Operational response |
|---|---|---|
| Expected covers | When do arrivals cluster? | Set door, bar and pass coverage for the pressure window |
| Rostered hours | Where does experience sit? | Name support, break and escalation decisions |
| Product constraints | What cannot be promised? | Brief the floor with a clear guest-facing response |
Illustrative operating checklist. Use verified venue inputs for each shift.
Further reading
Add one sentence of context
The three numbers become useful when paired with one sentence that changes behaviour: “Most bookings arrive between 7:00 and 7:30, so the host paces arrivals and the bar runs water early.”
That is a briefing people can act on. It gives the team a shared picture of the service rather than a vague instruction to work harder.
Close the loop after service
At close, compare the plan with what occurred. Not to punish the team, but to make tomorrow’s briefing less of a guess. Did arrivals bunch as expected? Did staffing cover the pressure point? Was a constraint handled cleanly?
The best pre-service briefing is short, specific and repeatable. It should help the team make a better decision before the first guest asks for one.
