Four on the floor for twelve covers, three for ninety
The rota for next week is done on Thursday. It looks like this week's, because this week's worked, with two holidays swapped in. On Tuesday evening there are twelve covers booked and four front of house staff standing around. On Friday there is a private party of twenty on top of a full book, and the floor is one person short because Friday's rota was copied from a quiet Friday.
The information to avoid both was in the booking system when the rota was written. It just was not on the same screen.
Rota and bookings live in different places
Rotas are built in a rota tool, a spreadsheet or on paper. Bookings are in the reservations system. Walk-ins, which can be a big part of some sessions, are not in either. So the person writing the rota has to look up covers separately, and when they are busy, they do not.
- Rotas are written days ahead, before the book for the week has filled.
- Walk-in patterns are known by feel, not recorded.
- Large parties and private hire need extra staff but are not highlighted on the rota.
- Kitchen and floor staffing needs differ for the same number of covers.
A worked example: a Wednesday looks light in the book when the rota is written. By the weekend before, a local event has filled it. Nobody revisits the rota, because it is already published, and the team runs Wednesday short.
What a mismatched rota costs
Overstaffed quiet sessions are wages spent without the sales to cover them. Understaffed busy sessions mean slow service, stressed staff and guests who do not come back. Both happen in the same week in many restaurants, and the weekly labour cost looks fine on average while the sessions themselves are wrong.
Staff notice too. Being sent home early on quiet nights and run off their feet on busy ones is one of the things that makes hospitality jobs hard.
The kitchen feels it differently from the floor. A set-menu party of twenty needs more hands on the pass at one moment, while a steady run of two-tops needs a different shape of cover across the evening. A rota that only counts heads cannot show either.
How we build a covers-led rota view
- Booked covers for each session are read from your reservations system, updated as bookings come in.
- Expected walk-ins are estimated from your own past sessions, using till data for covers or bills, by day and time of year.
- Large parties, private hire and events are shown clearly on the session they affect.
- Your planned staff for each session are read from your rota tool, such as Deputy or RotaCloud, or from your spreadsheet.
- For each session, the view shows expected covers against staff planned, using simple staffing guides you set, such as covers per server.
- When the book changes after the rota is published, sessions that move out of line are flagged so you can adjust.
| Session | Shows | Flags when |
|---|---|---|
| Each lunch and dinner | Booked plus expected covers | Staffing guide is exceeded or unused |
| Large party nights | Party size and time | No extra staff planned |
| After publishing | Changes in the book | Session moves out of line |
| Kitchen | Covers and menu type | Set menu or events need different cover |
The view suggests where you are over or short. Who works when, and any change to staff hours, stays your decision within your own employment practices.
Writing the rota with the book in front of you
Whoever writes the rota sees the covers next to the shifts, and builds each session to fit. Changes in the book after publishing are flagged in time to ask for a volunteer or offer a shift. Large parties get the extra staff they need.
Over time, the walk-in estimates improve and the rota for a normal week needs fewer changes.
Signs your rota is not following covers
- Rotas are copied from last week and edited.
- Some sessions are overstaffed while others run short.
- Large parties are not reflected in the rota.
- Walk-in trends are known by feel only.
- The rota is rarely revisited once published.