Field notes › Running the business
One source of truth for the roster
How many rosters do you have right now?
Not how many you should have. How many exist. There is the master spreadsheet, and the copy exported for a client on Thursday, and the version printed for the crib room, and the screenshot texted to a worker, and the amended copy on the coordinator's laptop that has not made it back to the shared drive yet.
Each copy was made for a sensible reason. Someone needed the information and copying was the only way to hand it over. But every copy is a fork, correct at the moment it was made and decaying from then on. The question is never whether the copies disagree. It is which disagreement bites first.
What version drift actually costs
Drift stays invisible until two people act on different versions of the truth. A worker turns up at the old start time because his screenshot predates the change. A site expects a fitter who was swapped out on a version they never received. A client makes a plan around a roster email that was superseded the same afternoon.
Then comes the second cost, the sorting out. Reconstructing who was told what, from which copy, when. Those conversations run on memory and end without a winner, and they burn exactly the goodwill with clients and workers that the roster exists to protect, and they always happen at the worst moment, mid-shift, mid-scramble. The blame lands on whoever sent the copy, when the real fault is that copies were the distribution method at all.
One timeline, not one file
A single source of truth is not a tidier master file, because a master file still gets copied the moment someone outside the office needs it. It only works as a live system that everyone reads directly.
Mustr runs the whole operation on one roster timeline: every client site, day and night shifts, swing patterns, and open shifts workers can register interest in, all in the same view. There is no per-site spreadsheet to reconcile against a master, because the site view and the master are the same data. What that looks like in practice is at rostering.
Access instead of copies
The copies exist because people without access still need answers. So the fix is giving them access, scoped to what they should see.
- Workers see their own shifts through a portal on any phone, no app to install. When a shift changes, the portal shows the change. Nobody is acting on a screenshot from Tuesday.
- Clients get a login per site and see only that site's roster, live. The exported-copy-for-the-client, the most drift-prone document in the business, stops being produced.
- The office reads the same timeline as everyone else, so what the coordinator sees and what the site sees cannot diverge.
Truth needs a memory
One live roster answers what is happening now. Just as often the argument is about what happened before: who changed the Saturday shift and when. A shared file has no memory, and blame fills the gap.
Mustr keeps an audit trail of changes, so the history is a record rather than a recollection. And because every booking on that single timeline is checked server-side against competencies, inductions, availability and double-bookings before it is confirmed, the single source of truth is also a checked source of truth. A spreadsheet can only tell you what someone typed. This tells you it was valid when it went in.
Count the copies of your roster in circulation this week, and if the answer worries you, book a demo and see what one live roster looks like with your crew on it.