Staff scheduling in hospitality: rotas that match your rush
A restaurant rota is never really finished, because last week's rush doesn't tell you everything about next week. Scheduling too many staff wastes money on wages, scheduling too few costs you tables, waiting time and frustrated guests. In this article you'll read how to build a weekly rota that matches your expected rush, how to handle a staff member calling in sick on a busy night, and how to stop scheduling turning into improvising all over again every week.
Why a fixed rota doesn't work
A restaurant doesn't have fixed levels of business, even though it can look that way at first glance. An ordinary Tuesday in January draws a different number of guests than a Friday night in June, and a terrace changes the maths entirely. A rota you build once and then keep repeating structurally overstaffs quiet shifts and understaffs busy ones. Both cost money: the first in unnecessary wages, the second in slow service and guests who don't come back.
Build your rota on expected rush, not on habit
Before building a rota, look at what you already know: how many covers did you have last week on the same day, is there an event nearby, is it school holidays, does a bank holiday fall in the week. Bookings already in hand give you a hard floor; the rest is an estimate based on patterns you'll be able to read well after a few months.
- Schedule your core team first: the people you need on every shift, whatever the rush.
- Add flexible hours on top for the shifts you expect to be busy.
- Keep one fixed moment each week when you finalise the rota for the week ahead, so it doesn't turn into a daily recalculation.
What to do when someone calls in sick
A sick call on a busy night can't be prevented, but it can be absorbed if you've thought about it in advance. Know in advance who's available on call and for which shifts, instead of having to work out who's reachable at the moment someone calls in sick. A short list of who normally covers which shift and who gets called first in case of a no-show saves a lot of panic in the moment itself.
Weighing wage costs against expected revenue
Scheduling staff by feel almost always leads to too many hours on quiet shifts, because nobody wants to be the one saying afterwards that someone could have gone home early. Work out roughly, per shift, what the expected revenue is against the planned wage cost: if that ratio is consistently off on certain days, that's a signal to adjust the rota on those days, not to leave it as it is just because it's always been that way.
A rota that matches your rush isn't about planning harder, it's about planning based on what you already know instead of on habit. With a core team, flexible hours for busy shifts and a clear plan for no-shows, you'll have to improvise less each week.
Frequently asked questions
How far in advance should I build a staff rota?
Most restaurants plan roughly a week ahead, with a core team that's already fixed further out and flexible hours you adjust as bookings and expected rush become clearer.
How do I stop scheduling too many staff?
Schedule based on expected rush per day instead of a fixed pattern, and periodically check whether the wage cost per shift is in proportion to the revenue that shift usually brings in.
What do I do if someone calls in sick on a busy night?
Keep a list of who's available on call and for which shifts, so that when someone calls in sick you know straight away who to call first, instead of having to work it out yourself.
Is scheduling for a restaurant different from a catering event?
Yes. For an event, you schedule staff once for one fixed headcount. For a restaurant, you build a new rota every week to match changing levels of rush, with a core team and flexible hours around it.
Want to match your rota to your rush more easily? That's what Catermonkey is for.
Start free