Field notes › Rostering
Roster templates vs a live roster
Templates are how most rosters grow up. The spreadsheet gets a "master" tab, someone copies it each week, fixes the differences, and the whole operation runs on copy-and-adjust. It works well enough at one site that it feels like the natural way to scale. It is not, and the reasons show up at the exact moment labour hire gets complicated.
A template is a photo of a roster that no longer exists
The moment you copy last swing's roster, you have copied a set of assumptions: that everyone on it is still available, still holds the same tickets, still works for you, and is not already committed somewhere else. Every one of those assumptions decays. A certificate that was current at the last copy has had weeks to expire. A worker who was free has picked up shifts elsewhere. In a single-site business the decay is slow enough to manage by eye. In labour hire, with a casual pool spread across multiple client sites, it happens every day, and a template has no way of noticing any of it.
Patterns are real, templates are the wrong way to run them
None of this means repetition is bad. Remote work runs on swing patterns, and plenty of client sites need the same shape of crew week after week. The question is where the repetition lives. A template repeats the people and hopes they still fit. A live roster repeats the pattern, the shape of shifts across days and nights, and treats each placement of a person into that pattern as a fresh decision that gets checked. You keep the efficiency of repetition and drop the risk of it. The two even, two off swing still takes seconds to lay out. What changes is that the person dropped into each slot has to actually qualify for it, today, not at some point in the past when the template was first built.
Copy-paste errors compound quietly
The nastiest property of template rostering is that mistakes replicate. Book someone in error once on a live roster and it is one bad shift. Bake the error into the template and it comes back every week until someone notices, and the person who eventually notices is often the client. Double-bookings are the classic case. Two client-site templates each "own" the same worker, both get copied forward on Sunday night, and nothing in a spreadsheet will ever object, because each tab looks perfectly fine on its own.
What a live roster does differently
A live roster is one timeline, not a stack of copies. Mustr runs one roster timeline across every client site, day and night shifts, swing patterns included, so the same worker cannot quietly exist in two places at once. Every booking, whether typed in fresh or part of a repeating pattern, is checked server-side against the worker's competencies, inductions, availability and existing shifts before it is created, and a failed check blocks the booking outright. The expiry problem that quietly rides along inside every copied template gets handled ahead of time instead, with expiring certificates surfacing up to 60 days out and one-click reminder emails to the worker. Gaps you cannot fill from the usual crew can go up as open shifts for qualified workers to register interest in, which beats pre-filling a template with hopeful names and finding out later.
The practical difference is where your effort goes. Template rostering spends it on reconciliation, hunting down what has changed since the last copy. Live rostering spends it on decisions, because the system already knows what changed and refuses to let the stale version through.
If your Sunday nights currently involve copying tabs and crossing fingers, see it on your own roster.