How to build a restaurant rota that survives a busy week

Start with the service, not the names

Split each day into the periods that actually change your staffing needs: preparation, opening, lunch, the afternoon lull, dinner and closing. Record reservations, events and any unusual work. A full dining room and a large delivery order can demand different kitchen coverage, even when the sales forecast looks similar.

For each period, identify the essential roles and the person responsible for running the shift. Headcount alone is misleading: five people who cannot lead a section do not replace a section leader. Include the time needed to prepare and hand over rather than assuming it will happen around service.

Collect constraints before filling shifts

Review approved leave, current availability, agreed working arrangements and the skills each shift needs. Keep preferences separate from confirmed constraints. Someone preferring early shifts is different from someone who has already been approved for leave.

Set a regular deadline for availability changes and explain how urgent exceptions should be raised. The deadline is a planning habit, not a reason to ignore a genuine problem. Where an assignment conflicts with a known constraint, speak to the employee before publishing.

• Confirm the location, date and timezone.
• Check who is trained to open, close and supervise.
• Review consecutive shifts and realistic handover time.
• Check relevant working-time requirements and employment arrangements separately.

Build the difficult shifts first

Place the roles with the fewest suitable people first, such as the closing supervisor or specialist kitchen station. Fill supporting roles after that. This avoids discovering at the end that everyone qualified to close has already been assigned elsewhere.

Review the distribution of weekends, early starts and late finishes across several weeks. A rota can look balanced on one Friday while repeatedly giving the same person every difficult close. Ask managers to explain exceptions so fairness is a visible decision rather than an assumption.

Publish one version and make changes traceable

Before publication, read the rota as an employee would. Can they tell where to go, when to arrive, what role they are covering and who to contact? Publish the plan in one agreed place. A screenshot sent to a chat group becomes unreliable as soon as a shift changes.

For a late change, confirm the replacement, update the authoritative rota and notify the affected people. Do not treat a message saying “I might be able to do it” as confirmed cover. Keep the original issue visible until the replacement has accepted and the manager has approved the arrangement.

Review the week using exceptions

After service, compare where the rota struggled with what you expected. Record one cause: demand changed, a skill was missing, availability was outdated or preparation took longer. Change the next template only when you understand the cause. Adding an extra person to every shift may hide a process problem without fixing it.

Staff Wing brings published schedules, availability, leave and cover workflows into the same workspace. Use that shared record to keep the plan current; managers still decide whether the coverage is suitable.