A weekly rota for a 6-person cafe should take 15 minutes. If yours takes 3 hours, the problem isn't you. It's the spreadsheet.
Most independent cafe owners we speak to have the same Sunday-night ritual. A laptop on the kitchen table. A paper diary. A team chat with 47 unread messages from baristas asking about next week. A spreadsheet that started clean three months ago and now has merged cells, colour-coded chaos, and a tab called FINAL_v3_real_USE_THIS.
This guide is the fix. Nine practical steps to compress your weekly rota from 3 hours to 15 minutes. No software pitch. No magic. Just a sequence that works because it stops you doing the slow things by hand.
Why cafe rotas eat so much time
Before the steps, it helps to name the four things that actually make rotas slow:
- Re-asking availability every week. If you message each barista every Sunday, you've already spent an hour before you've drawn a single shift.
- Doing maths in your head. Hours per person, hours per week, contracted minimums, cost against tomorrow's forecast revenue. Doing this in a spreadsheet means re-doing it every time you move a shift.
- Not having a template. Most cafes have the same shifts every week (open, mid, close, weekend AM, weekend PM). Building from scratch each Sunday is the single biggest time sink.
- Distributing the rota by hand. Screenshot, message, email, repeat. Then field five sorry can you swap me Thursday messages.
Fix these four and the other small frustrations disappear with them.
The 9-step weekly rota method
Step 1 — Build a one-time shift skeleton
Before your first fast rota, spend 30 minutes building a skeleton week. A skeleton has the shifts your cafe always needs, without names attached. For a typical small cafe that's roughly:
- Mon-Fri opening shift (06:30-13:00) — 1 barista
- Mon-Fri mid shift (10:00-15:00) — 1 barista on busy days
- Mon-Fri closing shift (12:30-18:30) — 1 barista
- Saturday AM (07:00-13:00) — 2 baristas
- Saturday PM (13:00-18:00) — 2 baristas
- Sunday brunch (08:30-15:30) — 2 baristas
This is your starting grid every single week. You will never build a rota from a blank page again.
Step 2 — Collect availability once, not every week
Ask each staff member to give you their standing availability — the days and hours they can normally work — plus a way to flag exceptions. Not weekly messages. A single source.
A shared form takes ten minutes to set up. A scheduling tool with self-service availability takes about the same. Either way, the principle is identical: stop interviewing your staff once a week.
Step 3 — Draft against forecast revenue, not gut feel
Before assigning names, look at the same week last year (or last month) and roughly map your busiest 3-hour windows. Most independent cafes find:
- Weekday morning rush: 07:30-10:00
- Weekend brunch: 09:30-13:30
- Friday afternoon: 14:00-17:00
You want your most experienced barista on bar during these windows. Everything else can flex. This single decision often saves around 20% on labour cost without losing service quality.
Step 4 — Drop names into the skeleton in priority order
Start with the constraints, not the convenience. In this order:
- People with fixed days (e.g. parents, students)
- Senior baristas on peak windows
- Contracted minimum hours that must be hit
- Everyone else
If you do it in this order, the rota almost builds itself. If you start with who wants what, you'll end up reshuffling six times.
Step 5 — Hold one float shift open
Do not fill every slot. Leave one mid-week shift unassigned and labelled float. When someone calls in sick on Wednesday morning, you have a slot to offer rather than a panicked group chat. This is the single biggest stress-reducer most cafe owners miss.
Step 6 — Run the cost check before publishing
A quick maths step. Total scheduled hours × average wage = labour cost for the week. If it's above 30% of forecast revenue, you've overscheduled. Below 22%, you've probably under-scheduled and Saturday will burn.
This is a 60-second check. Most cafe owners skip it and find out on payroll day.
Step 7 — Publish in one click, not ten messages
A published rota should be visible to your whole team the moment it's done. Not in your camera roll. Not as a screenshot. Not in a chat thread where it scrolls off in two days.
A shared link, a calendar, or a scheduling app that pushes notifications — any of these is fine. The goal is that nobody has to ask am I working Tuesday? ever again.
Step 8 — Make swaps a self-service problem
The second-biggest time sink after building the rota is fielding swap requests. Decide once: staff arrange their own swaps, you approve. Don't be the broker. A cafe of 6 baristas should generate maybe two swap approvals a week, not twelve.
Step 9 — Save this week as next week's starting point
Never start from blank again. Whatever you publish this week becomes the duplicate base for next week. You'll only need to adjust:
- Holiday requests
- One-off events (a wedding cake order, a public holiday)
- New starters or leavers
Everything else carries over. This is the single biggest time-saver of all nine steps.
What this looks like in practice
A cafe owner doing this manually in a spreadsheet, with a saved skeleton template and standing availability, can hit 15-20 minutes per week. With a scheduling tool that handles availability, costing, and notifications, it drops to under 10.
The pattern that doesn't work — and the one that costs three hours every Sunday — is this:
- Open a blank spreadsheet
- Re-ask everyone's availability
- Draft from scratch
- Calculate hours by hand
- Screenshot it
- Send to the team chat
- Field swap requests for 3 days
That's the loop to kill.
When a spreadsheet stops being enough
For a 4-person cafe with stable shifts, a spreadsheet plus a saved template can absolutely work. The break point usually arrives around 6-8 staff or when you add a second site. At that point you're juggling:
- Multiple availability windows
- Holiday requests
- Variable revenue between sites
- Fair-scheduling rules and rest-period requirements that vary by region
This is when a flat-rate scheduling tool starts paying for itself in pure time saved. We built rota for exactly this kind of small cafe — $29/month for up to 30 staff (or $23/month on annual billing), no per-user fees, no per-location fees. It's the price of a couple of bags of speciality beans, and it gives you back your Sunday evenings.
If a spreadsheet is still better for you, no hard feelings. The point of this guide isn't to sell software — it's to stop you losing 12 hours a month to a job that should take one.
Quick checklist
Before your next Sunday-night rota session, make sure you have:
- A shift skeleton saved and reusable
- Standing availability collected once, not weekly
- A view of last week's busy windows
- A single source of truth for the published rota
- A swap policy your staff can run themselves
- Last week's rota saved as next week's starting point
If you have all six, your rota will take minutes. If you're missing three or more, that's where the three hours are going.
Try rota free trial →
$29/month for up to 30 staff. $23/month on annual billing. No credit card. Setup takes 5 minutes.
