Hospitality rota planning — templates and best practices that actually work

The rota is your single biggest weekly decision. It's the document that decides whether you make money, whether your staff stay, and whether Sunday lunch runs smoothly. And in most hospitality businesses, it's still being built on a spreadsheet on a Tuesday afternoon by someone who's already tired.

Here's how to do it properly — and the templates that make it ten times faster.

Start with revenue, not headcount

Rotas built by guessing how many people you need are rotas that lose money. Build the other way round:

1. Take your last four weeks of revenue, broken down by day-part.
2. Calculate your target labour cost percentage (28–32% for cafés and casual restaurants, 22–28% for premium operators).
3. Multiply forecast revenue by target % to get a daily labour budget.
4. Then decide how many people you can roster.

This single change shifts the rota from a wish list to a budget. Most operators find they were over-staffing two shifts and under-staffing one without realising it.

Templates are the highest-leverage thing you can do

If you sit down with a blank rota every week, you're rebuilding the same shape over and over. Stop.

A rota template captures the structure of a typical week — three openers Tuesday, four floor staff Friday dinner, one duty manager every shift — without the names. Each week, you load the template and just slot people in. What used to take 90 minutes takes 10.

Minimum templates to build:

• A standard mid-week template.
• A weekend template (different volume, different skill mix).
• A bank holiday template.
• A summer / Christmas variant if your trade is seasonal.

Four templates cover 90% of the year.

The rules that cut overtime by 30%

Overtime is almost never strategic. It's the thing that happens when the rota was wrong on Monday and you didn't notice until Saturday. These rules catch it earlier:

• Hard cap on weekly hours per contract. A 25-hour contract should trigger an alert at 24 hours.
• No back-to-back closes and opens. A closer leaving at 11pm cannot open at 7am. It's bad for the staff and bad for the food.
• Mandatory break tracking. Unpaid 30-minute breaks for shifts over 6 hours, by law.
• Single approver for last-minute changes. Otherwise three managers add three extra hours on Saturday and nobody knows until payroll.

Codify these and your overtime drops without any negotiation.

Publish two weeks ahead

The single biggest predictor of staff retention in hospitality is rota notice. A team that knows their hours two weeks out can plan their lives. A team that finds out on Sunday evening starts looking for a new job by Wednesday.

Two-week-ahead publishing also forces you to template, because you can't improvise that far in advance. The discipline pays off twice.

Build for swaps, not against them

Swaps will happen. The question is whether they happen on WhatsApp at 11pm on a Friday with you in the middle, or in an app where staff propose, swap, and you approve in one tap.

A good swap process needs three things:

1. Visibility — both staff agree before it lands on your desk.
2. Skill matching — a bar-trained closer can't swap with an untrained floor runner.
3. Audit — you need to know who actually worked, for payroll and for compliance.

If your current process has any of these missing, you're losing money on payroll errors and time on Sunday admin.

Skill and section coverage

A rota with the right number of people but the wrong skills is still a broken rota. Tag each shift with required skills — barista, allergen-trained, fire marshal, supervisor — and the rota tool refuses to leave a gap. This is the difference between "five people on" and "five people who can actually run service."

Real-time clock-in matters

A rostered shift is a plan. A clocked-in shift is reality. If you can't see the gap between the two in real time, you're paying for shifts that nobody worked and missing late starts that compound into bad service.

Modern rota tools handle this in one app: rota → publish → clock-in → timesheet → payroll export. The fewer hand-offs, the fewer payroll disputes.

A simple weekly rhythm

Most operators we work with land on this cycle:

• Monday morning: review last week's labour cost vs. revenue.
• Monday afternoon: load next-next week's template, adjust for holiday/events.
• Tuesday: publish to staff. Open a 24-hour swap window.
• Wednesday: approve swaps, lock the rota.
• Following week: real-time monitoring, last-minute changes via the app only.

Forty minutes total, instead of three to four hours of constant firefighting.

The tool that does all of this

Spreadsheets get you to 80% of this. The last 20% — automatic overtime alerts, skill matching, real-time clock-in, swap approvals, payroll export — needs software built for hospitality. That's exactly what Dilagee does, and the reason most teams that switch save around 20 hours a week on rota admin alone.

Your rota is the lever. Use it.