Friday's gala dinner went from 180 to 260
The banqueting manager built next week's rota on Thursday from the printed function sheets. On Monday, the gala dinner grew by eighty covers and a breakfast meeting was added for Wednesday. The manager hears about the dinner in passing from the events coordinator and starts texting casual waiting staff one by one. By Wednesday, a few have replied, one has said yes to two different venues, and the rota spreadsheet is on its fourth version.
On the night, service is stretched. On another night that week, a cancelled lunch leaves several people rostered with little to do.
Rotas are built from snapshots
Event numbers change right up to the day, but rotas are built once and patched. The link between an event's type and size and the staff it needs is in the banqueting manager's head. Casual staff availability lives in text messages.
- Staffing ratios differ for plated dinners, buffets, conference breaks and receptions.
- Number changes are not passed to the rota automatically.
- Casual staff are contacted individually, with no single view of who confirmed.
- Setup and breakdown shifts are guessed rather than calculated from the room changes.
- Planned hours are only compared with revenue after the payroll run.
Too thin or too thick
Understaffed events show in slow service and tired teams, which clients notice. Overstaffed shifts cost wages the event cannot justify. The banqueting manager spends hours each week on messages and spreadsheets instead of running service. Casual staff who get last-minute requests or cancellations tend to prioritise other venues.
We do not advise on employment terms or working time rules. Your HR adviser owns those. We make the plan reflect the diary.
How we build staffing plans from the diary
- We record your staffing ratios with the banqueting manager: covers per server for each service style, supervisors per event size, setup and breakdown time per room change.
- Each day's events are read from your booking system, and required staff by role and hour are calculated.
- When numbers or events change, the requirement is recalculated and the manager sees the difference: two more servers needed on Friday, one fewer on Tuesday lunch.
- Shifts are offered to casual staff through a simple app or text link, and they accept or decline. The rota fills as they do.
- Double bookings are avoided because each person has one set of confirmed shifts.
- Planned hours are shown alongside event revenue for the week, before the week happens.
| Service style | Your ratio held as | Recalculated when |
|---|---|---|
| Plated dinner | Covers per server, plus supervisors | Covers change |
| Buffet | Covers per server, station staff | Covers or format change |
| Conference breaks | Staff per delegate range | Numbers or break times change |
| Reception | Staff per guest range | Guest numbers change |
If you already use a rota tool, such as Deputy or Rotaready, we feed the requirement into it rather than replacing it.
What the banqueting manager's week looks like
The rota starts from the diary and moves with it. The manager fills gaps rather than rebuilding the plan, and casual staff confirm shifts in one place. Finance sees planned labour against event revenue in advance.
Casual staff get clearer notice and fewer last-minute cancellations, which tends to make them more willing to say yes to your venue first. When a big event grows late, the manager sees exactly how many extra people are needed and who has already been asked.
Is this your venue?
- Rotas are built from printed function sheets.
- You find out about number changes after the rota is done.
- Casual staff are booked by individual text messages.
- Staffing ratios live in one person's head.
- You only see labour against revenue after payroll.