A practical guide from people who have built these by hand.
How to make an on-call rota (without the chaos)
Every hospital department has one person who builds the rota — usually with no training, no handover, and a spreadsheet inherited from someone who left. This guide covers the method that actually works, the rules that can’t be skipped, and the mistakes that cause the Sunday-night rewrites.
Start with the fixed points, not the names
The commonest mistake is starting with people. Start with the shape of the week instead: which duties must be covered every day — on-call for each grade, ward cover, theatre, clinics — and which slots are immovable. Build the empty grid first: duties down the side, days across the top. Only when the shape is right do names go in.
If your department runs consultant firms or teams, block those in next: the registrar who operates with a given consultant should follow that consultant's theatre days. Team structure is a constraint, not a preference.
The rules that cannot be skipped
Post-call rest is the first rule and the one most often broken. Whoever is on call overnight cannot be first on for theatre or clinic the next day. Build the post-call day into the grid as its own row so it's impossible to miss — if it lives only in your head, it will be violated within a month.
Second: leave beats everything. Record approved leave in the grid before assigning a single on-call. A rota that schedules someone who is in Portugal is worse than no rota, because the team stops trusting it.
Third: weekends are a unit. Saturday and Sunday cover should be planned as blocks, not as two separate days — and whoever works the weekend needs the pattern around it (the Friday before, the Monday after) handled consistently. Decide the weekend pattern once and apply it everywhere.
Fairness is a number, not a feeling
Most rota arguments are really fairness arguments, and they persist because nobody is counting. Keep a running tally per person: weekday on-calls, weekend days, nights, and leave taken. Update it every single week. When someone says the rota is unfair, the tally is the answer — either it shows a genuine imbalance, which the next rota corrects, or it shows the spread is even, which ends the conversation.
Two people in the same grade should never differ by more than a couple of on-calls over a rotation.
If they do, fix it in the next block — silently absorbing the imbalance is how coordinators burn out.
Publish one version, not five
The moment a rota is emailed as an attachment, it starts going stale. Someone swaps, the file is re-sent, and within a fortnight there are four versions in circulation and nobody knows which is current. Whatever tool you use, the goal is a single source of truth: one place the whole team checks, updated the moment anything changes.
Swaps need a rule too: they go through the coordinator, or they don't count. A swap agreed in a corridor and never recorded is the commonest cause of an uncovered shift.
The handover nobody does
Rotas outlive their makers — you will rotate, and someone will inherit the spreadsheet. Write down the rules you've been holding in your head: the post-call pattern, the weekend logic, who can't do Tuesdays and why. Ten minutes of notes saves your successor a month of mistakes, and saves the team from re-learning fairness arguments that were already settled.
Tools
A spreadsheet can do all of the above for a small, stable team — if someone maintains it every week without fail. We keep a free Excel template with the grid, post-call row and fairness tally already set up.
When the maintenance itself becomes the job — the tally slips, the versions multiply, the checking-by-eye misses one weekend too many — that's the point of a dedicated tool. RotaOS generates months of rota with the post-call rules, leave and fairness handled automatically, and gives the team one live link that's always current. The demo takes two minutes and needs no signup.