The hidden cost of Excel duty rosters (and a checklist for evaluating alternatives)
· 3 min read
Excel is free, familiar, and already installed on every computer in the building. It's also, for a hospital duty roster, one of the more expensive tools a department can choose — the cost just doesn't show up on an invoice. It shows up as hours, as chaos, and as trust that erodes one unfair-seeming schedule at a time.
The time cost nobody budgets for
Building a duty roster in a spreadsheet isn't just data entry. It's cross-referencing time-off requests against a mental model of who worked what last month, manually checking that nobody's scheduled for a night shift followed by an early morning, and then doing it all again when someone requests a change after the roster is "final." Coordinators routinely spend hours on a task that has almost no room for reuse — next month, you start nearly from scratch, because a spreadsheet doesn't remember last month's balance for you.
That time is real cost, even though nobody puts it on a budget line. It's time a clinical coordinator isn't spending on clinical work.
Version chaos
Ask any coordinator managing a roster by spreadsheet how many files are named something like "roster_final.xlsx," "roster_final_v2.xlsx," and "roster_ACTUAL_final.xlsx," and you'll get a rueful laugh. Once a spreadsheet is shared across a team chat, email, and a printed copy on a break-room wall, there is no single source of truth — there are several, and they drift out of sync the moment one person requests a swap and someone updates only their local copy.
Swap tracking that doesn't exist
Shift swaps are a normal, healthy part of any roster — people get sick, have family emergencies, need a specific day off. But in a spreadsheet, a swap is usually two names typed over each other in a cell, with no record of who approved it, whether it violated a rest rule, or whether it quietly gave one person another weekend off while someone else absorbed the difference. Multiply that by a year of swaps and the roster's fairness becomes untraceable — nobody, including the coordinator, can actually reconstruct who has worked what.
No fairness memory
This is the deepest problem, and the hardest to see month to month: a spreadsheet has no memory beyond what's on the current tab. If someone worked extra holidays in the spring, nothing carries that forward into how autumn's roster gets built, unless a coordinator personally remembers and manually compensates — which is a lot to ask of anyone across dozens of staff and a full year. Fairness disputes are rarely about a single month; they're about a pattern that built up quietly because nothing was tracking it.
A checklist for evaluating scheduling tools
If you're weighing whether to move off spreadsheets, these are the questions worth asking about any alternative, RosterShift included:
- Does it track weighted fairness (nights, weekends, holidays) as a running balance across months, not just within one period?
- Does it enforce rest rules as hard constraints, not just flag them after the fact?
- Is there a single published version of the roster, with swaps recorded and auditable?
- Can staff see their own balance and history without asking the coordinator?
- Does it reduce the coordinator's manual work, or just move the spreadsheet into a different-looking interface?
If a tool can't answer "yes" to the fairness-memory and hard-rest-constraint questions, it's solving the display problem, not the actual problem. That gap — between a nicer-looking spreadsheet and a system that actually remembers and enforces fairness — is exactly what RosterShift was built to close.
None of this means spreadsheets are a bad tool in general — they're excellent for a huge range of jobs. A duty roster with fairness rules, rest constraints, and swap history just isn't one of them, in the same way a spreadsheet isn't the right place to track a patient's medication schedule. The job needs a system that remembers, not a grid that has to be remembered for.