Restaurant shift planning is the process of building, publishing, and maintaining a staff schedule that matches your team to customer demand across every service. Done well, it keeps your operation staffed, your labour costs in check, and your team informed. Done poorly, it becomes a daily fire you manage by phone.
This guide walks through the full process: from understanding shift types to building the schedule step by step, handling what happens after you publish, and the common mistakes that quietly cost restaurants time and money every week.
Why restaurant shift planning is harder than it looks
Most managers underestimate how much time goes into the schedule, and even more into keeping it running after it's published.
The schedule is just the start
Building the rota takes time. But the real cost is what comes after. A schedule published on Thursday is already outdated by Saturday morning. Sick calls arrive by text. Swap requests come in by WhatsApp. Someone approved leave that nobody recorded. Every change routes back to the manager's phone, and the version of the schedule in the system no longer reflects what's actually happening on the floor.
This post-publish chaos is where most scheduling time goes, and it's the part most guides skip entirely.
The labour cost gap
Most restaurant managers build their schedule based on experience and availability, not on what the shift will actually cost. Labour costs typically account for 25 to 40% of gross revenue in the restaurant sector, depending on service style. That is the single biggest controllable cost in most operations. When schedules are built without that target in mind, overspend only surfaces at month-end, by which point the shifts have already been worked and the money is gone.
The shift types you'll be managing
Before you can plan effectively, it helps to know what you're working with. Most restaurants use a mix of the following shift patterns, and the right combination depends on your service hours, team size, and peak periods.
| Shift type | When it's used | Watch out for |
|---|---|---|
| Morning / opening | Pre-service prep, mise en place, breakfast or brunch cover | Back-to-back scheduling with late closers — minimum 11-hour rest required |
| Lunch / midday | Peak service cover during the midday rush | Overstaffing during the slow mid-afternoon lull between covers |
| Evening / closing | Dinner service through to end of service | Check the 11-hour rest gap before the next morning opener starts |
| Split shift | Covers both lunch and dinner with a break in between | Long unpaid gaps can affect staff wellbeing; total hours still trigger break entitlements |
| Weekend / holiday | High-demand periods requiring full cover | Requires advanced planning; popular with part-timers but creates fairness issues if not rotated |
⚠️ A note on split shifts: split shifts can maximise staffing flexibility across lunch and dinner, but they need careful handling. Employees working both lunch and dinner covers are putting in a long day. Make sure the total hours worked trigger appropriate rest break entitlements, and consider whether the unpaid gap between shifts is reasonable for staff who may have long commutes.
How to build a restaurant shift plan step by step
Good shift planning starts before you open a spreadsheet or scheduling tool. The steps below follow the order that produces the fewest problems downstream.
Step 1: start with demand, not availability
The most common scheduling mistake is building a rota around who's available rather than when you actually need people. Start with your demand picture instead.
Use historical sales data, reservation volumes, and known local events to identify your peak and slow periods by day and by hour. Predictive scheduling techniques help you turn this data into concrete staffing plans. Most scheduling software connects to your point of sale to pull this data automatically. If you're still working manually, look back at the last four weeks of covers and flag your consistently busy periods. Then set a labour cost target before you start assigning shifts: keeping labour between 25% and 40% of expected revenue is the right ballpark for most UK restaurants, though quick-service operations typically run leaner than full-service dining.
Step 2: collect availability before you plan
Aim to have staff submit their availability two to three weeks in advance. Building a schedule without knowing who's on holiday, who has a commitment on Saturday, or who's unavailable for opening shifts means you'll be unpicking it once that information surfaces. Collect availability through a system rather than by message, so you have a single, up-to-date record rather than a thread of texts to cross-reference.
Step 3: build from your busiest day outward
Start with your highest-demand day and assign your strongest team first. You have more control over who works the busiest shift than the quieter ones, so use it. From your peak day, work backward through the week in order of demand. This approach means the days that need the most staffing never get left until you're short of options.
Use shift templates wherever possible. If your Friday dinner service runs the same pattern every week, there's no reason to build it from scratch each time. Templates save significant time and reduce the chance of errors creeping in.
Step 4: cross-train and mix skill levels
A restaurant that can only function when specific people are in specific roles is fragile. Cross-training staff to cover multiple positions gives you scheduling flexibility when gaps appear and reduces the panic when someone calls in sick. When building the rota, mix experienced and newer team members during busy shifts deliberately so that each shift supervisor has the right blend of experience on the floor. This maintains service quality and creates on-the-job training opportunities without additional cost.
Step 5: stagger start times and avoid back-to-back shifts
Staggered shifts across a service period avoid a surge of labour at the beginning of a shift and a gap at the end. It also smooths the wage cost curve across the day. More importantly: avoid scheduling the same employee for a late closing shift followed by an early opening shift. Under the Working Time Regulations 1998, workers are entitled to a minimum of 11 hours' uninterrupted rest between shifts. A closer finishing at 11pm cannot legally be scheduled to start before 10am the following morning. Catching this during the build is far easier than dealing with it after.
Step 6: build compliance into the schedule from the start
Compliance is not a box-tick you do after building the rota. It's easiest when it's built in from the beginning.
Key rules for restaurant managers under the Working Time Regulations 1998 are grounded in UK working hours and break laws and the specific rest break requirements that apply to your team:
- 20-minute rest break: any worker over 18 who works more than 6 hours in a shift is entitled to a minimum 20-minute uninterrupted break. This applies to all your restaurant staff, including kitchen and front-of-house, and automated scheduling tools can help you build these entitlements into every rota by default.
- 11 hours between shifts: the minimum rest period between the end of one shift and the start of the next.
- 48-hour working week: average weekly working time cannot exceed 48 hours, though workers can sign a written opt-out.
- Young workers (under 18): stricter rules apply. They are entitled to a 30-minute break after 4.5 hours of work and 12 hours' rest between shifts. Do not apply adult rotas to under-18s without adjustment.
The full guidance is available on Acas and GOV.UK.
Step 7: publish with enough notice
Aim to publish the completed schedule two to three weeks in advance. This gives staff enough time to manage personal commitments, reduces no-shows, and means any errors or availability clashes surface before the week starts rather than on the morning of the shift. Last-minute schedule publication is one of the most consistent drivers of staff dissatisfaction in the restaurant sector, and one of the easiest to fix.
What happens after you publish (and how to handle it)
This is the part most scheduling guides skip, but it's where the real time goes. A well-built schedule can still fall apart in the days after it's published if there's no system for managing changes.
Shift swaps
Staff swapping shifts with each other is inevitable. The problem is not the swap itself; it's when swaps happen without manager visibility and approval. A swap that creates an all-new-starters shift on a busy Friday, or moves your only trained barista off the Saturday morning, can only be caught if there's an approval step in place.
Set a clear policy: all shift swaps require manager approval before they take effect. The manager checks whether the swap creates a skills gap or compliance issue, then confirms or declines. In practice, most swaps are straightforward and approval takes seconds. Digital tools make this easy: staff request the swap in the app, the manager approves with one tap, and the schedule updates automatically.
Sick calls and open shifts
A sick call at 6am doesn't have to mean an uncovered shift at 8am. The key is having a system that makes the gap visible immediately and gives available staff a way to claim it without every notification going through the manager's phone.
Open Shifts let you publish an uncovered shift to eligible team members, who can claim it themselves. Managers approve the claim rather than making individual calls down a list. This is how absence management and scheduling should connect: when someone logs a sick call, the schedule gap appears instantly and the open shift goes out automatically. Businesses using this approach consistently report that the time between a sick call and a confirmed cover is significantly shorter than the old phone-around method.
Absence and time-off requests
Absence planning is not a separate HR task. It directly affects your schedule, and tracking your overall absence rate helps you spot patterns before they turn into chronic understaffing. Approving a holiday request without checking how it affects that week's rota creates a gap nobody spots until the shift is undermanned.
The fix is straightforward: absence and scheduling need to live in the same system, ideally supported by a robust shift booking system. When a manager approves a leave request, the schedule should update in real time, the gap should become visible, and any coverage shortfall should surface before the week starts. This is the difference between reactive and proactive shift planning.
Common restaurant shift planning mistakes
Most of these are invisible until they cause a problem, which is why practical restaurant scheduling tips that focus on communication, fairness, and data can be so valuable.
| Mistake | Why it matters |
|---|---|
| Scheduling by gut feel instead of demand data | Labour costs drift over target without any feedback loop until month-end |
| Ignoring the 11-hour rest rule between shifts | A closer finishing at 11pm cannot start before 10am — catching this during build prevents compliance issues |
| Building the schedule without collecting availability first | Staff submit availability you haven't seen yet, leading to swaps and last-minute scrambles |
| Approving leave without checking staffing impact | A Sunday suddenly has two people off that you only notice when the shift starts |
| Publishing too late for staff to plan around | Less than a week's notice increases no-shows and reduces morale |
| Managing swaps and sick calls through WhatsApp | No audit trail, no approval process, no visibility — and the schedule in the tool becomes fiction |
How restaurant scheduling software changes the process
The biggest shift isn't in the schedule itself. It's in what you stop doing manually.
What to look for in restaurant scheduling software
Not all scheduling tools are built for shift-based restaurants. A generic HR tool that includes scheduling as a feature will usually lack the operational depth you need. When evaluating options, look for:
- Availability built in, not separate: the tool should know who is available before you start building, not require you to cross-reference a separate spreadsheet.
- Absence visible during build: approved leave should appear in the schedule automatically so you never build a rota and then discover someone is on holiday.
- Shift swap approval flow: staff request swaps in the app, manager approves, schedule updates. No WhatsApp group required.
- Open Shifts for sick cover: eligible staff are notified of uncovered shifts and can claim them, reducing the time between a sick call and a confirmed cover.
- Compliance flags during build: the tool should surface rest period violations and contract limit issues before you publish, not after payroll.
- Connection to time tracking and payroll: hours worked should flow from the schedule to the timesheet to payroll without manual re-entry, supported by accurate employee timekeeping and integrated time and attendance software.
Shiftbase is built around this connected model, offering online shift planning designed specifically for complex, shift-based teams. Employee scheduling, time tracking, and absence management are part of the same platform, not separate modules that need reconciling. The schedule already knows who is on leave, what the contract hours are, and what it will cost before you publish it, making it easier to follow best practices for an effective restaurant schedule. Managers at businesses using this approach consistently report spending 50 to 70% less time on scheduling and post-publish coordination.
Try Shiftbase free for 14 days
Shiftbase gives restaurant managers a connected schedule that knows your team before you start building. Availability, absence, and contracts are already loaded in. Try Shiftbase free for 14 days, no credit card required. Or explore the employee scheduling feature to see exactly how it works.
