Field notes › Rostering
No-shows: reducing them and recovering fast
A no-show costs more than one empty spot on a roster. The client's supervisor rearranges their morning around the gap, the coordinator drops everything to fill it, and a little of the client's confidence in your firm goes with it. Labour hire lives and dies on turning up, so no-shows deserve more analysis than the usual response, which is a sigh and a note in someone's head about who is unreliable.
Where no-shows actually come from
Genuine flakiness exists, but it explains fewer no-shows than coordinators assume. Look closely at each one and you keep finding the same upstream causes.
- Booked against reality. The worker told someone weeks ago they could not do Wednesdays. The note died in a text thread, the booking went ahead, and the no-show was scheduled the day it was booked.
- Never saw the change. The shift moved sites or start times, the update went out in a group text, and the worker turned up to the old shift or not at all.
- Double-booked. Casual workers juggle more than one employer. If your roster cannot see their other commitments, some conflicts only surface as an empty seat at pre-start.
- Not fit for the shift. Sometimes the honest options are a fit-for-work declaration they cannot truthfully make or a quiet disappearance, and the quiet disappearance feels easier.
Reduce them before they happen
Each cause has a specific fix, and most of the fixes are structural rather than motivational. Availability maintained by workers themselves in the worker portal stays current in a way office-collected notes never do, and in Mustr a booking that falls outside a worker's availability is blocked server-side before it lands, along with anything that clashes with an existing booking. That deletes the booked-against-reality category and the double-up category at the source.
The never-saw-the-change category shrinks when workers have one place that always shows their current shifts. The portal works on any phone with nothing to install, so the roster in the worker's pocket is the roster, not a screenshot of last week's. And fit-for-work declarations give workers a legitimate, low-drama way to flag a problem before the shift instead of vanishing on the morning of it.
Recover fast when one lands anyway
No system gets no-shows to zero, so the recovery path matters as much as prevention. Two things make it fast. First, publish the gap as an open shift so the whole eligible crew sees it on their phones and registers interest, instead of the coordinator ringing down a list. Second, keep the guardrails on while you hurry: the same server-side checks on competencies, inductions, availability and double-bookings apply to a panic booking at 6am as to a planned one, and a failed check blocks the booking outright. Speed without those checks is how one no-show becomes two problems.
Keep the client informed while you work. A site watching the gap get filled in its own portal experiences a hiccup being handled. A site discovering the gap on its own experiences something worse.
Learn from the pattern
Individual no-shows are noise. Patterns are signal, and patterns need records. With every booking and change in an audit trail, you can see whether one worker keeps dropping short-notice, whether one site generates more no-shows than the others, or whether the no-shows cluster on a particular shift pattern. Those are three different problems with three different fixes, and without records they all look like bad luck.
Some patterns point back at the roster itself. A shift that keeps getting no-showed might be a shift nobody can actually work, and the fix is the pattern, not the people.
If your no-show plan is currently a sigh and a phone list, see it on your own roster.