Field notes › Rostering
Availability: the quiet foundation of a good roster
Nobody gets excited about availability. It is not the part of rostering anyone demos first, and no coordinator ever came back from site raving about it. But almost every late-notice drama in a labour hire office traces back to it. The worker who was booked on a day he said months ago he could never do. The gap that took all morning to fill because half the phone list was never going to say yes. A roster is only ever as good as the availability data underneath it.
How availability goes stale
In most crews, availability lives in fragments. A text to one coordinator. A comment made in the ute. A note in a spreadsheet column that was accurate in March. The knowledge is real, but it is stored in one person's head, and it decays the moment that person goes on leave or the worker's life changes.
There is also a quieter problem. When telling the office you are unavailable means an awkward phone call, some workers just do not make it. They take the booking, intend to sort it out later, and later becomes a no-show. The system taught them that honesty is friction, so honesty stopped.
Make it the worker's job, and make it easy
The fix is to stop treating availability as something the office collects and start treating it as something the worker maintains. In the Mustr worker portal, workers set and update their own availability from any phone, with nothing to install. School holidays, a mate's wedding, a second commitment on Tuesdays, whatever it is, they mark it themselves the moment they know.
This only works if it is genuinely easy, which is why the no-app part matters. A portal that opens in the browser on whatever handset the worker already owns gets updated. An app that needs a download, a password reset and 200 megabytes of spare storage does not.
Enforce it at booking time
Collected availability is only half the job. The other half is making the roster respect it. In Mustr, every booking is checked server-side against the worker's availability before it lands, along with their competencies, inductions and existing bookings. If the shift falls on a day the worker marked out, the booking is blocked outright. Not flagged for someone to review later. Blocked.
That one behaviour changes the relationship between workers and the roster. When workers see that marking a day unavailable actually prevents bookings on that day, they start keeping their availability current, because it works. When availability is a suggestion the office sometimes overrides, they stop bothering, and you are back to fragments and texts.
What good availability quietly fixes
- Fewer knock-backs. The coordinator stops offering shifts to people who were never going to take them, so filling a gap takes minutes instead of a morning.
- Honest open shifts. When workers register interest in open shifts, the interest means something, because their availability already says they are free.
- Fewer quiet no-shows. A worker booked against their stated availability is a no-show waiting to happen. Remove those bookings and you remove a slice of no-shows with them.
- Planning further out. With availability visible weeks ahead, next month's roster stops being guesswork about who might be around.
Start unglamorous, stay unglamorous
Availability never becomes exciting. It just sits underneath everything else, and when it is current, the rest of the roster gets easier in ways that are hard to attribute to any single feature. The coordinators feel it before anyone can explain it.
If your availability lives in text threads and one coordinator's memory, see it on your own roster.