Field notes › Running the business
The spreadsheet breaking point: what changes between 10 staff and 40
Why the spreadsheet worked in the first place
At ten staff, a rostering spreadsheet is genuinely fine. One person owns it, usually the person who built it. They know every worker by name, they know who holds a forklift ticket and who is away next month, and they can spot a clash by eye because the whole roster fits on one screen.
The spreadsheet is not really the system at that size. The person is the system. The spreadsheet is just where they write things down.
What changes on the way to 40
There is no single day when it breaks. It erodes. Somewhere between ten staff and forty, a few things start to compound.
- A second client site arrives. Now there are two rosters, or one roster with a column that keeps getting misread. Sooner or later a worker is pencilled in at both sites on the same day, and nobody notices until one site calls asking where he is.
- Night shift and swing patterns arrive. A grid built for Monday to Friday day work starts sprouting colour codes and footnotes that only the author understands. Handover between shifts becomes guesswork.
- Certificates multiply. Ten workers might mean a few dozen tickets and inductions to track. Forty workers doing mine site work can mean hundreds, each with its own expiry date. That volume does not fit in anyone's head, and the expiry column nobody sorts by is where it goes to die.
- A second person starts editing. Now there are versions. The copy on the shared drive, the copy someone emailed a client on Tuesday, and the copy open on a laptop at home. They disagree, and nobody knows which one is right.
The failure is silent until it isn't
The dangerous thing about a spreadsheet is that it never says no. It will happily let you roster someone whose site induction lapsed last week. It will let you book the same rigger on two sites at once. Every cell accepts whatever you type into it.
So the error does not surface when it is made. It surfaces at the gate, when a worker is turned away in front of your client. Or it surfaces in an audit, when someone asks you to prove a person was compliant on a given day and the honest answer is a shrug and some scrolling.
What a real system does differently
The difference is not tidier formatting. It is that the checking happens before the booking exists. Mustr checks every booking server-side against the worker's competencies, inductions, availability and existing shifts before it goes on the roster. If a check fails, the booking is blocked outright. Not flagged with a warning someone can click past at nine on a Sunday night. Blocked.
Expiring certificates surface up to 60 days before they lapse, with one-click reminder emails to the worker. And there is one roster timeline across every client site, day shift and night shift, so a double-booking is impossible rather than merely unlikely. There is more on how the checks work at compliance and rostering.
Move before it bites
The best time to get off the spreadsheet is before the second client site, not after the first incident report. Waiting feels cheaper because the spreadsheet is free, but the spreadsheet was never the cost. The cost is the senior person spending half their week nursing it, and the client relationship riding on nothing going wrong.
The move is also smaller than it looks. Mustr imports your workers and clients by CSV, so the spreadsheet you have becomes your starting data rather than wasted work. You are not rebuilding anything, you are handing the checking to something that does not get tired.
If your roster has outgrown the person holding it together, book a demo and see it on your own roster.