A Staff Rota That Survives a Busy Week
- Build the rota from your busy hours, not from your team's names. The week has a shape — when it fills and when it empties — and the shifts should be poured into that shape.
- Cover roles before headcount: till, bar, floor and the pass are four different jobs, and a shift with three people all of whom can only do one of them is still a gap.
- Core cover plus shoulders beats flat cover — full strength for the morning peak, deliberately thin for the quiet afternoon, instead of two people on all day who are neither enough nor necessary.
- Publish early and change through rules: swaps exist, but they are not real until approved and written into the rota.
- The sick call is a scenario, not an emergency. Who is phoned, in what order, and who takes the floor is decided in writing before the morning it happens.
- In the worked example here, one café covers the same peaks with 54 shifts instead of 62 — by moving cover out of quiet hours, not by thinning the rush.
Ask a café owner where their rota came from and the honest answer is usually an accident — a shape inherited from whoever worked there three years ago, patched each week around holidays, hunches and whoever threatened to leave. The result is a document nobody trusts: over-covered on Tuesday afternoons, thin on Saturday at eleven, and renegotiated by text message at midnight. A rota that survives a busy week is not harder work than that. It is the same effort pointed at the week's actual shape instead of at its history.
Start From the Busy Hours, Not the Names
The first draft of a rota contains no people at all. It contains hours: when does this café fill, when does it empty, and by how much. Most coffee-led cafés find a double peak — a sharp morning on weekdays and a longer, later one at weekends — but yours may have a lunch bump from the offices nearby or a dead August. Whatever the shape is, the shifts are built to fit it: strong cover where the curve is high, deliberate thinness where it is low, and nothing at all pretending the two need the same team.
Roles Before Headcount
| Role | Owns | Thin when |
|---|---|---|
| Till | Orders in, payments, takeaway queue | Off-peak hours, when bar can absorb it |
| Bar | Drinks production, machine and grinder | Never during peak — this is the bottleneck role |
| Floor | Tables, delivery, clearing, the room's mood | Quiet hours, counter service only |
| Pass / kitchen | Food readiness, plating, handover | Outside food hours |
Count these roles across the peak before you count people. Four staff who can all only work the till is, at the morning rush, a rota with one barista and no floor — whatever the headcount says. Cross-training is what converts headcount into cover: everyone's second skill is the rota's shock absorber.
A Shape That Bends
The pattern that fits most cafés is core plus shoulders. The core is the peak window at full strength — for a weekday morning rush, roughly opening until early afternoon. The shoulders are the hours either side, covered by one or two people who hold the fort, prep, clean and stock. This is the shape that lets a small team be genuinely enough at 08:00 without being paid to stand still at 15:00.
| Core cover | Shoulder cover | |
|---|---|---|
| Weekdays | 07:30–10:30, three on — bar, till, floor | 10:30–15:00, two; 15:00–17:00, one |
| Saturday | 09:00–14:00, three on | 08:00–09:00 and 14:00–16:00, two |
| Sunday | 10:00–14:00, three on | 09:00–10:00 and 14:00–15:00, one |
Publish Early, Change Through Rules
A rota is a promise, and promises work when they are made early and changed openly. Publish the coming fortnight before the current one ends, so childcare and second jobs can be arranged around it rather than against it. Then give changes a single route: a swap is proposed by the two staff involved, approved by a manager, and written into the rota before the shift date. The version in the system is the only version. Leave requests land in one place too — not in a conversation at the end of a shift that nobody remembers on Monday.
When Someone Calls In Sick
- The call order, written down. Who is phoned first, second and third — usually the part-timers who want hours, then the cross-trained closer, then whoever owes a favour from last month.
- The fallback is you. If the call order comes up empty, the manager takes the role that cannot be skipped: the bar at peak, the till at lunch. A rota whose last line of cover is nobody is not a rota.
- Cover the roles, not the hours. One missing person means one missing role. Decide which role they had, and cover that; a sick floor person on a quiet Tuesday is a different problem from a sick barista on a sunny Saturday.
- Afterwards, look at the pattern. Absences that cluster on the same shift or the same day are telling you something about that shift — its length, its staffing, or who it always lands on.
Fairness the Team Can See
Rotas do not fail because they are unfair; they fail because the unfairness is invisible. Weekend work, closing shifts, the Monday-after-a-festival open — all of it costs whoever always gets it. Rotate the costly shifts on a published pattern, split consecutive closes so nobody does four in a row, and spread the quiet weekday hours among the people who actually want them. The test is simple: could any member of the team look at the rota and see why it is shaped the way it is? If yes, complaints become requests. If no, every change is a negotiation.
Worked example
A café with six staff — four full-time, two part-timers — runs weekday peaks at 07:30–10:30 and weekend peaks at 10:00–14:00. Its old rota was six people on fixed five-shift weeks: 62 shift-slots a fortnight, and still only two people on the floor at the Saturday peak, because the fixed shifts were shaped by seniority, not by the week. The rebuild started with the hours: three-on cover for every peak window, two in the mid-afternoon, one late. Fitting the six people into that shape — part-timers on the shoulder hours they wanted, full-timers owning the cores, the weekend rotation published alongside — produced 54 slots a fortnight. Peak cover went up, total shifts went down, and the two part-timers stopped being asked to invent hours they had never agreed to. The next problem was not cover but what to do with the quiet hour nobody needed to stand through any more.
Where the Shape Comes From
The busy hours the rota is built on are a fact, not a feeling, and the till is where the fact lives. In Kafe360, the hourly sales report shows the day curve for the last month, and table analytics adds a heatmap of how busy the room is hour by hour across the week — which is the weekday-versus-weekend question answered directly. The staff section holds the plan itself: shift plans and leave tracking, so the rota everyone argues about is at least the same document everyone is reading.
Kafe360 does not do payroll, working-hour checks or contract rules, and a rota is where those questions get close. Maximum hours, rest between shifts, holiday and sick-pay treatment — all of these differ by country and by contract, and none of them are the software's job. Check the rules where you trade and put the pay-related decisions in front of whoever does your payroll, not in front of a scheduling screen.
Before the Fortnight Starts
- Read the sales curve for the last four weeks and mark the true peaks — weekday and weekend separately.
- Draft the role grid first, people second; check every peak window has bar, till and floor covered.
- Publish the fortnight before the previous one ends, with the weekend rotation visible.
- Confirm the swap rule and the sick-call order with the team out loud, once, together.
- Book the quiet hours honestly thin, and give the saved hours to the people who asked for them.
A rota is working when Saturday feels busy but not brittle — when the sick call is annoying rather than catastrophic, and when the team's complaints are about the weather and the espresso machine, not about whose weekend it is.
Pull your hourly curve for a month and build the core-plus-shoulders shape on your real peaks. Kafe360 is $249 a year, with a 30-day free trial and no card to start.
Start your 30-day free trialFrequently asked questions
How far in advance should the rota be published?
How should shift swaps work?
Someone calls in sick on our busiest morning. What now?
Should part-time staff work weekends too?
Can Kafe360 build the rota for me?
How do I know how many people the rush actually needs?
Opening a venue? Start with a free QR menu, move to the full system when you are ready.