How to build restaurant rotas without losing your mind

Most rotas are built by inertia: copy last week, patch the absences. It works while the venue is predictable, then it becomes the main source of wasted hours and uncovered sections.

1. Start from demand, not from people

Before assigning names, define how many people each time band needs. Expected covers, transactions per hour and service times show where coverage is real and where you are paying for presence.

2. Cover peaks with short or split shifts

A two-peak service cannot be covered with uniform shifts. Short peak shifts cut labour cost without cutting quality, as long as they are predictable and announced early.

3. Constraints before preferences

• Minimum rest between shifts
• Weekly hour caps and consecutive days
• Required skills per band (who can run the kitchen alone)
• Declared availability and approved leave

4. Publish early and in one place

Two weeks of notice reduces last-minute swaps more than anything else. Publishing needs a single source: if the rota also lives in a chat, the chat wins and planning loses.

5. Close the month with data you already have

When worked hours, overtime and absences are captured as they happen, month end becomes a check rather than a reconstruction.