Staff Rotas for Small Food Businesses: A UK Guide for 2026

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:

1. Two weeks firm. The next fortnight is published and treated as committed. Changes after publication happen by agreement, not by announcement.
2. Weeks three and four provisional. The shape is visible — who is likely to be on, where the busy days are — but not yet fixed.
3. 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:

• GOV.UK: maximum weekly working hours
• GOV.UK: rest breaks at work
• ACAS: working hours guidance

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 inc. VAT (£650 a year). Core also includes food safety records, menus and the allergen matrix, meal planning, Business Insights, card payment links, Shopify and WooCommerce sync, and teams and multi-site support.

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. No app 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:

1. Availability in by Wednesday. One channel, one deadline, no exceptions that are not genuine emergencies.
2. 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.
3. Publish Thursday evening, two weeks out. Same day, every week, so the team knows when to look.
4. Changes only on the rota. If it is not on the rota it did not happen, and the calendar feeds carry the correction automatically.
5. 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

Start a 7-day free trial — no card required →

Further resources

• GOV.UK: maximum weekly working hours
• ACAS: working hours and rest breaks
• Managing a kitchen team with software
• Kitchen staff permissions and access control
• Production scheduling for small food businesses
• FoodCore kitchen management software
• FoodCore product overview