Field notes › Rostering
Filling open shifts without the ring-around
You know the ring-around. A shift needs filling, so the coordinator starts at the top of the phone list and works down. Voicemail. Voicemail. A no. A maybe who wants to check with his wife. A yes, finally, and then twenty minutes later a better-suited worker calls back and you have to decide whether to unwind the whole thing. It works, in the sense that shifts mostly get filled. It is also one of the most expensive habits in a labour hire office.
What the ring-around actually costs
The obvious cost is time. A single gap can absorb a coordinator's whole morning, and mornings are exactly when the office has the least of it. The less obvious costs are worse. The shift goes to the first person who answers, not the best person for it. Workers learn that a call from the office at 6am means pressure, so some stop picking up. And nothing about the process is recorded, so when someone asks why a particular worker got the shift, the honest answer is that he answered his phone.
Flip it: publish the shift
The alternative is to stop chasing individuals and publish the gap. In Mustr, an open shift sits on the roster like any other shift, except no one is booked on it yet. Workers see open shifts in the worker portal on whatever phone they already own, no app to install, and register their interest with a tap. Instead of one coordinator hunting one worker at a time, the shift is in front of the whole eligible crew at once, including the night shift worker who is asleep right now and will check his phone at 2pm.
The office's job changes from chasing to choosing. You open the shift, wait for hands to go up, and pick.
Interest is not qualification
The catch with any first-in-best-dressed system is that keen and qualified are different things. The worker who responds fastest might be missing the site induction, or carrying a ticket that expired last month, or already booked on nights somewhere else. Under ring-around pressure those details get skipped, and that is how the wrong person ends up at the gate.
This is where the server-side checks matter. When you book a worker onto the shift, Mustr checks their competencies, inductions, availability and existing bookings before the booking lands, and a failed check blocks it outright. Not a warning to click past. Blocked. So the pool of interested workers can only ever turn into valid bookings, no matter how rushed the morning is. There is more on how those checks work on the compliance page.
What changes for the office
A few things, and they compound. Shifts get filled by people who actually wanted them, which does no harm to reliability. The coordinator's morning comes back, because publishing a shift takes a minute and the interest arrives on its own. The decision is recorded in the audit trail, so the answer to why a worker got a shift is written down rather than remembered. And the client sees the filled roster in their own portal instead of ringing to ask whether the gap is sorted.
None of this requires workers to change much. They already carry phones. They already want more shifts, or at least the good ones. Giving them a place to put their hand up asks less of them than screening calls from the office does.
Keep a little judgement in it
Open shifts do not have to mean first come first served. You still choose who gets the booking, and you should. The point of publishing the gap is not to remove the coordinator's judgement, it is to stop spending that judgement on phone tag and spend it on the actual decision instead.
If your mornings still start with a phone list and a biro, see it on your own roster.