12 May 2026
How to build a staff rota that actually works
A practical guide to publishing rotas your team turns up for — written for cafés, restaurants and pubs running on tight margins.
The rota is the most-checked, most-ignored, most-rewritten document in your business. It is also the single biggest lever you have on labour cost. Get it right and you'll see the impact in your margin within four weeks. Get it wrong and you'll spend Friday answering swap requests on WhatsApp.
This is how to build one that works.
The four mistakes that cost you money
1. Building it on the wrong number. Most rotas are built on "how many hours can I afford to roster?" The right starting point is "how much do I expect to take at the till each day, and what labour cost % keeps that healthy?" For most UK cafés and restaurants, a healthy labour ratio is 25-32% of revenue. If you don't know yours, work it out from last month before you do anything else.
2. Building it once a week. A weekly rota in hospitality is a snapshot. Within 48 hours of publishing, somebody's swapped a shift, someone's called in sick, and your floor is uneven. A rota you can update from your phone in 30 seconds is a different tool entirely from a rota that lives in Excel.
3. Treating part-time staff like full-time staff. A 16-hour-a-week barista has half the slack of a 40-hour-a-week chef. They can't absorb a no-show. They can't extend a shift. The rota has to account for which staff are flexible and which aren't.
4. Publishing without confirmation. Most no-shows aren't from staff who can't be bothered — they're from staff who didn't realise they were on. If your rota lives on a corkboard, half your team never reads it. If it sends a push to their phone with a confirm button, you find out who's coming on Wednesday, not on Friday at opening time.
The hour you save by templating
If your business has any pattern at all — same days of the week busy, same shift lengths, same skill mix — you're rebuilding the same rota every week. Stop.
A template captures the shape of a week. Three openers Tuesday morning, four floor staff Friday dinner, one duty manager every shift. You publish the template, then nudge it for the specifics: holiday, mid-week event, bank holiday. What used to take 90 minutes takes 10.
This is the single highest-leverage thing you can do with your rota process. Even on Excel, ten templates can shave 50 hours a year off rota-building. On a proper tool, it's effectively zero.
What "good" looks like on the day
The Saturday morning test:
- 100% of staff know they're on (because they pressed Confirm or got a reminder push)
- 100% of staff know their start time
- 100% of staff know the role they're playing
- The duty manager knows the labour cost of the day before service starts
- Anyone needing to swap a shift can do it without you
Live labour cost as a planning tool
Almost everyone treats labour cost as a backward-looking report — what we spent last week. The better use is forward-looking: see the cost as you build the rota, and adjust before you publish. If Tuesday's labour is forecast at £820 against a £600 expected revenue, you've over-rostered. Move a shift. Cut a 4-hour to 3.
Doing this once a week is worth, conservatively, 2-3% off labour cost. On a £100k/month venue, that's £30k a year.
The mobile question
If your staff aren't seeing the rota on their phones, you are running a 2010 system. Push notifications, shift swap buttons, confirm-receipt — these aren't nice-to-haves. They're how your team actually interacts with the schedule today.
If the rota lives on a wall and only on a wall, your team won't see it until they walk in. That's how shifts get missed.
How Dilagee does it
Drag-and-drop builder, recurring templates, live labour cost, mobile push to every staff phone with one-tap confirm, shift-swap workflow, time-off requests, and a labour vs revenue dashboard that updates as you go.
Free for teams of 5 or fewer. £49/month for up to 20 staff. Start a free trial →
Got a question about something rota-shaped? Drop us a line — we read everything.