This guide is for independent restaurants, cafés and pubs. It is written with UK kitchens in mind, but the method is the same elsewhere. It is practical advice on how to build a week that still holds up on Saturday night. It is not legal advice, and it is not a substitute for your contracts or for the official working-time pages. For UK hours, rest and pay records, see our staff hours briefing and the official GOV.UK and Acas pages linked there.
What a rota is really doing
A rota is a promise to the people who will work the week, and a plan for the work the kitchen and the floor actually have to do. If the two do not match, the week unravels in the same places: a pass with no chef who can run it, a quiet lunch overstaffed, a Friday night short on the wash-up, or a closer who is down to open the next morning.
Start from the services, not from a blank spreadsheet of names. Fix the constraints that cannot move — rest days, a late-to-early clash, a holiday already agreed — and only then put people into the remaining shifts. Publishing comes last, and it only works if the team can see the result and ask for a swap without a group-chat hunt.
Start from the work, not the names
Write the week as a set of services, not a list of staff. For each service, note the expected covers or usual trade, the stations that must be filled, and the skill you cannot do without. A 40-cover Saturday dinner does not need the same board as a quiet Tuesday lunch, and a chef who can run the pass is not interchangeable with a commis still learning the grill. A simple one-page “service map” you reuse every week is enough:
- Days and services (for example Tuesday lunch, Tuesday dinner, through to Sunday lunch)
- Expected covers, even if that is only a realistic range from the last few weeks
- Stations or roles that must be present: pass, grill, garnish, pastry if you run it, floor, bar, wash-up
- The minimum number of people who can actually do each role, and who those people are
- Known absences: holidays, medical appointments, already-agreed time off
If you skip this and start with everyone’s “usual shifts”, you will fill the quiet days first and discover on Thursday that Saturday’s pass is uncovered.
Fix rest days and late-to-early clashes first
Before you place a single shift, mark the days people cannot or should not work. Holidays already agreed are not a surprise. Regular days off should be visible, not squeezed out because a Saturday was short. If someone closed on Friday night, think carefully before you put them on an early Saturday — not only because it is hard, but because rest rules and a decent night’s sleep are part of running a kitchen safely.
Look at the hand-over between days, not only at each day in isolation. The classic failure is a closer who finishes after a late sitting and is written down to open the next morning. Even where the hours look legal, the person arrives tired and the opening checks are rushed. If you need an early shift after a late finish, put it on someone who was off or who finished earlier, and say so on the rota. For each busy service, confirm that someone on the board can run the pass, and that you are not leaving a junior member of the team as the only person in the kitchen. If only two people can do a job, their rest days cannot fall on the same Saturday.
Build the week in a set order
Once the work and the constraints are on the page, fill the board in the same order every week. It is slower the first time and faster after that, because you stop renegotiating the same arguments.
- Place the busiest services first — usually Friday dinner, Saturday dinner, and Sunday lunch if you serve it.
- Put a named person on the pass, or the equivalent lead role on the floor, for each of those services.
- Fill the remaining stations on those days, including wash-up. It is easy to forget, and expensive when you remember at 18:00.
- Fill the midweek services from the people who still have hours and rest days to give, matching the lighter trade.
- Check each person’s week as a whole: total hours, rest days, late-to-early pairs, and whether they are being asked to cover a station they have not been trained for.
- Only then deal with leftover gaps: a split shift if you genuinely need one, an on-call name for a booking that may not arrive, or a request to a trusted extra.
If midweek trade does not need three people, give the third a rest day or a later start, and keep the hours for the service that will actually use them. Unused hours on Tuesday are often why Saturday runs short.
A worked example: Harbour Kitchen, a quiet midweek and a busy Saturday
The figures below are illustrative, not from a real site. Imagine a neighbourhood restaurant, Harbour Kitchen, open Tuesday to Sunday, around 40 covers on a busy night and 20 at midweek lunch. The kitchen team is six people: a head chef, a sous, two chefs de partie, a commis, and a kitchen porter. The floor is planned separately; the same method applies.
The service map for Saturday dinner says: 40 covers, a pass, a grill, a garnish, and a porter. Only the head chef and the sous can run the pass. The sous has Sunday off, already agreed. The head chef closed on Friday. That single fact decides Saturday: the sous should take the pass on Saturday dinner, and the head chef should not be asked to open Saturday lunch after a late Friday. The commis can work Saturday lunch with one chef de partie; the other chef de partie works Saturday dinner with the sous. The porter is on both peak services, with a later start on Saturday lunch if the morning prep is already covered.
Tuesday lunch, at around 20 covers, needs two people in the kitchen, not four. The remaining two take a rest day or a late start, which is how Saturday stays staffed. None of this requires software, but the constraints have to be written down before the names are placed. A late booking of 12 on Thursday does not automatically need another chef; changing the whole week because one table moved is how a published rota loses the team’s trust.
Hand the rota over so people can actually use it
A rota that lives in one person’s notebook is not published. People need to see their own shifts, the whole week, and how to ask for a change — on a printed sheet, a shared file, or a phone. The test is the same: can a chef check tomorrow’s start time at the end of tonight’s service, without waking the owner? Publish with enough time for a genuine swap. A rota that appears on Sunday night for a Monday start is a notice, not a plan. Record swaps on the same board, and if you allow them only between people who can do the same station, say so.
Planned hours and actual hours will not match perfectly — a late sitting, a sick call, a trial shift. That is expected. You still need to see the difference, so the next rota is built from what happened, not from last month’s optimism. Timesheets and clock-in close that loop; the legal side is covered in the staff hours briefing.
When the week changes
It will change: a sick call at 08:00, a late booking, a delivery that overruns prep. The aim is not to prevent every change. It is to make the first version solid enough that a change is a small move, not a rewrite.
Keep a short list of who can step in for the pass, who can take an extra midweek lunch, and who should not be asked because they closed the night before. Update the published rota whenever you change it. If the same gap appears every week, fix the template, not a Saturday morning message. A spreadsheet is enough when the trade is stable and the team is small. Software starts to help when people need to see the rota on a phone, when clock-in has to match the plan, or when you compare hours across more than one site.
How Hosmere Rota can help
Hosmere Rota is built for this sequence: plan the week from the people and sites you already have, publish it so the team can see it, and let people clock in and out against the site with GPS, on their own phone or on a shared kitchen tablet with a PIN. Timesheets then compare the planned shifts with the hours that were actually worked, which is the starting point for the next week and for a payroll CSV export.
It will not invent a good skill mix for you, and it will not make a late-to-early clash legal or kind. It will show the clash, the gap on the pass, and the hours before you publish. Hosmere is not a substitute for advice on contracts or working time.
If you want to see the layout before you commit, you can open the demo without creating an account:
You can also start a 14-day trial from the Rota product page — no card is required for that trial. Device-only use on one device, without an account, is free forever.