Staff Rotas for Small Food Businesses: A UK Guide for 2026
A bakery rota with the right number of people on it can still fail badly — because a rota is not a headcount exercise, it is a skills exercise. This guide covers what a good kitchen rota actually contains, how far ahead to publish it, how to catch clashes before they become Saturday-morning problems, and where UK working time rules fit in. It includes a sample weekly rota for a small bakery. It is general operational guidance, not employment-law advice.
What a good kitchen rota actually does
The most common rota mistake in a small food business is treating the problem as arithmetic: we are open eight hours, we need three people, three names go in the box. That produces rotas which are technically full and operationally broken.
A rota's real job is to guarantee that the capabilities the shift requires are present, not just the bodies. In a bakery that usually means asking four questions of every shift:
- Who can run the oven? If the only person who can judge a bake is on the counter, you have three people and no baker.
- Who can answer an allergen question correctly? This is not optional cover. If a customer asks what is in something and the only person qualified to answer is off, the shift has a compliance gap, not a staffing gap.
- Who is the responsible person? Somebody has to be able to decide — to refuse an order, to bin a batch, to call you. If that is ambiguous, the decision gets deferred and the problem gets bigger.
- Who is learning? A rota that never pairs an experienced person with a newer one produces a business with exactly one person who can do each job, which is the single most expensive staffing structure there is.
Once you frame it this way, the rota stops being a grid of names and becomes a coverage map. The practical version is simple: write the skills each shift needs first, then fill them.
See FoodCore kitchen management software →
Publish far enough ahead to be useful
A rota published on Friday for a week starting Monday is not really a rota. It is a notification. Staff in small food businesses very often have caring responsibilities, second jobs, studies or long commutes, and short notice is the thing they will leave over — long before pay becomes the issue.
There is no single UK-wide notice period that applies to every worker, so this is an operational standard you set rather than a rule to look up. A pattern that works well for small bakeries and kitchens:
- Two weeks firm. The next fortnight is published and treated as committed. Changes after publication happen by agreement, not by announcement.
- Weeks three and four provisional. The shape is visible — who is likely to be on, where the busy days are — but not yet fixed.
- One cut-off, clearly communicated. Availability and time-off requests are submitted before the cut-off. After it, they are swap requests instead, which is a different and slower process on purpose.
Predictability compounds. A team that trusts the rota stops holding back availability defensively, which in turn makes the rota easier to build.
Handling double-bookings and clashes
Clashes almost never come from a single dramatic error. They come from three quiet, structural ones:
- More than one rota exists. A printed copy on the wall, a version in a spreadsheet, and a WhatsApp message that amended both. Every additional copy is another chance to be wrong.
- Changes are agreed verbally. A swap arranged at the end of a shift, agreed by everyone present, and written down by nobody. It will hold until the day it doesn't.
- Someone is scheduled into two places at once. Assigned to a delivery run and to the counter over the same hours, or booked on the rota while already on approved leave. In a busy week this is genuinely easy to do and genuinely hard to spot by eye.
The remedies map straight onto the causes. Keep exactly one rota and make it the only source anyone consults. Make it a rule that a change is not a change until it is on the rota — a swap agreed but unrecorded is not agreed. And use a rota that checks itself for overlaps rather than relying on you noticing while tired.
A sample weekly rota for a small bakery
Here is a worked example for a small bakery with a counter, a small wholesale round and weekend celebration cakes. Note that the entries name a role as well as a person, and that a responsible person is identified for every trading day.
Two things are worth noticing. Ash appears on Wednesday as "bench, training" alongside Priya — that is deliberate skills-building, not padding. And there is never a trading day without a named responsible person and without at least one allergen-trained person on the counter.
UK working time basics — stated carefully
Rotas sit close to employment law without being employment law, and it is important to be precise about the boundary. The general position is that the UK has working time rules covering matters such as limits on average weekly working hours, daily and weekly rest, rest breaks during the working day, and record-keeping relating to working time. There are separate and stricter rules for workers under 18 — which is directly relevant to food businesses, where young workers are common. Whether and how each of these applies depends on the worker's age, contract, role and circumstances.
This article does not attempt to tell you what the rules are for your specific team, and nothing here should be treated as employment-law advice. The authoritative and current sources are:
What a rota can reasonably do is make the underlying facts visible: what hours you actually scheduled, who was on which shift, and when. That visibility is useful when you or your adviser need to check something. It is not a substitute for taking advice, and no scheduling tool — FoodCore included — can tell you whether your arrangements are compliant.
Rotas belong where staff can actually see them
A rota that exists only on a wall in the back of the kitchen is invisible on the two days a week it matters most — the days someone is not in the building and is trying to work out whether they are due in tomorrow. A photo of that rota in a group chat is worse, because it is a snapshot that goes out of date the moment anything changes, and nobody can tell by looking whether the version they are scrolling past is the current one.
The reliable answer is to publish the rota to the calendar your staff already have on their phone.
How the FoodCore staff rota works
The staff rota is part of the FoodCore Core plan, £65/month (£650 a year). On Essentials or Growth you can add it as a £6 a month bolt-on.
Add staff by name, with no email or login
Not everyone on the rota needs to sign in to anything. On the Staff tab you can add a person by name only, with an optional phone number, position and colour on the rota. No email, no password, no login. They go on shifts, timesheets, leave and payroll exports like anyone else.
If you later want them to see the rota themselves, use Give them a login. They get an invite email, and every shift, hour and holiday they already have stays theirs. Logins for staff need Team logins, which is included in Core or £10 a month on Essentials and Growth. Staff rota and Team logins together are £16 a month.
Kitchen PINs are part of Core: a manager sets one for each person, for clocking in on the kitchen tablet. The tablet clock screen is coming next in the FoodCore app. Until then, and on Essentials and Growth, a manager adds hours for staff without logins on Timesheets.
Clocking in, leave and timesheets
Staff with a login clock in and out from the rota or dashboard, or you can let FoodCore assume each shift happened. Holidays and leave are booked against allowances, and managers can add leave for someone. Timesheets let you approve and lock each pay period, then export the hours as a CSV or for Xero, Sage or BrightPay. Overtime is paid at its own rate and carried into every export.
Weekly rota with conflict detection
You build the week in a single weekly view, assigning people to shifts. Conflict detection flags double-bookings — when someone has been scheduled into two overlapping shifts, the rota tells you while you are building it, rather than leaving you to discover it at half past four on a Saturday morning when one of the two shifts has no one in it.
Publish to Google Calendar or any ICS calendar
Once the rota is published, it can be subscribed to from Google Calendar or any calendar app that supports ICS subscriptions — which in practice means Apple Calendar, Outlook and effectively everything else. Each member of staff subscribes once. Their shifts then appear alongside everything else in their own calendar, and update when the rota changes. Nothing extra for staff to install, no login to remember, no screenshot to misread.
A deliberate privacy decision worth understanding
There is a design choice in these calendar feeds that is worth spelling out, because it is unusual and it is on purpose.
The calendar feeds carry no phone numbers and no addresses. And a member of staff's personal feed shows only their own shifts — never a colleague's name, contact details or whereabouts.
The reasoning is straightforward once you think about where those calendar entries end up. A subscribed feed lands in a personal Google or Apple account. That account is outside your business's control entirely: you cannot see it, you cannot audit it, and you certainly cannot delete anything from it when someone leaves. It may be synced to a shared family tablet, backed up to a personal cloud, or still sitting on a phone belonging to someone who stopped working for you two years ago. Putting a colleague's mobile number or home address into that feed means publishing another person's personal data into an account you have no authority over and no way of retrieving it from. So FoodCore does not put it there. Staff get exactly what they need — when am I in, and doing what — and nothing that belongs to anyone else.
This sits alongside FoodCore's wider approach to team access, where people see the parts of the system their role requires and not the rest. Our guide to kitchen staff permissions and access control covers that in detail.
Explore everything FoodCore does →
Getting a rota habit to stick
The rota that works is the one that gets built at the same time every week. A workable routine for a small bakery:
- Availability in by Wednesday. One channel, one deadline, no exceptions that are not genuine emergencies.
- Build Thursday, against the production plan. Staffing follows production, not the other way round — if Friday is decorating day, Friday needs a decorator. Planning the two together is why they belong in the same system.
- Publish Thursday evening, two weeks out. Same day, every week, so the team knows when to look.
- Changes only on the rota. If it is not on the rota it did not happen, and the calendar feeds carry the correction automatically.
- Review monthly. Which shifts were consistently short? Which skills only ever have one person? Fix those in the next month's rota rather than absorbing them.
Staff rotas: frequently asked questions
What should a kitchen rota include?
A kitchen rota needs more than names against days. At minimum it should show who is working, the start and finish time of each shift, and the role that person is covering on that shift — bench, oven, counter, decorating, deliveries. It should also make clear who is the responsible person on each shift, so there is never ambiguity about who makes a call when something goes wrong. Break arrangements should be visible rather than assumed. Finally, it should state clearly whether the rota is a draft or published, because a draft that staff mistake for a published rota causes more trouble than no rota at all.
How far in advance should I publish a staff rota?
There is no single legally fixed notice period that applies to every worker in the UK, so treat this as an operational standard you set rather than a rule you can look up. In practice, small food businesses that publish two to four weeks ahead have noticeably fewer swap requests and no-shows than those publishing a few days ahead, because staff can plan childcare, second jobs and travel around it. A reasonable approach is to publish a firm rota two weeks out, hold a provisional shape for weeks three and four, and commit to a fixed cut-off after which changes are by agreement rather than by announcement. If your workers are on particular contract types, check current GOV.UK and ACAS guidance for any notice or predictability requirements that apply to them.
What are the UK rules on working hours and rest breaks?
UK working time rules cover things like limits on average weekly working hours, daily and weekly rest, and rest breaks during the working day, and employers are expected to keep adequate records relating to working time. There are also separate and stricter rules for workers under 18, which matter in food businesses because young workers are common in bakeries and cafés. The detail depends on the worker's age, contract and role, and on whether any opt-out or exemption applies, so this article does not attempt to state the rules for your situation. Read the current guidance on GOV.UK and ACAS, and take proper advice if anything is unclear. This article is general information about rota practice and is not employment-law advice.
How do I stop double-booking staff on a rota?
Double-bookings usually happen for one of three reasons: the rota is built in more than one place, a change is made verbally and never written down, or someone is assigned to two roles in the same time window without anyone noticing. The fixes are to keep exactly one rota, to require that every change is made on that rota rather than agreed in a corridor, and to have the rota itself check for overlaps. FoodCore's weekly rota includes conflict detection that flags a double-booking when a person is scheduled into two overlapping shifts, so the clash is caught while you are still building the rota rather than at six on a Saturday morning.
Can staff see their shifts on their own phone?
Yes. FoodCore's rota can be published to Google Calendar or to any calendar application that supports ICS subscriptions, which covers Apple Calendar, Outlook and most others. Each member of staff subscribes once and their shifts then appear in the calendar they already use, updating when the rota changes. This is generally far more reliable than a photo of a printed rota in a group chat, because the calendar is always the current version rather than whichever screenshot someone last scrolled past.
Does FoodCore work out pay, holidays or overtime?
FoodCore prepares your hours for payroll, but it is not a payroll system. Timesheets add up the hours each person worked, split out overtime over their contracted hours and price it at its own rate, and track holiday against the allowance you set. You approve and lock the hours, then export them as a CSV or for Xero, Sage or BrightPay. FoodCore does not work out tax, National Insurance, pensions or statutory pay, and it makes no judgement on whether your arrangements meet employment law. That belongs in your payroll software or with your accountant. Use GOV.UK and ACAS as the reference points for your employment obligations.
Which FoodCore plan includes the staff rota?
The staff rota is part of the FoodCore Core plan, which is £65/month (£650 a year). On Essentials (£25/month) or Growth (£40/month) you can add it as a bolt-on for £6 a month. On its own it works for staff without logins. To let staff sign in, add Team logins (£10 a month). Both together: £16 a month. All plans come with a 7-day free trial and no card is required to start it.
Do my staff need an account to be on the rota?
No. Add them by name, and give them a login later (needs Team logins).
Start a 7-day free trial — no card required →
Further resources
FoodCore is kitchen management software built for small UK food businesses. We handle recipe costing, Natasha's Law labels, allergen matrices, production planning, staff rotas and order tracking. We are not an HR, payroll or employment-law provider.
Start free trial →