Field notes › Rostering
Rostering around leave, training and medicals
A worker is unavailable for three quite different reasons in the same month. Two weeks of leave they booked in March. A day off for a renewal course. Half a day for a medical the client site insists on. To the roster they all look the same: a gap where this person cannot work. To your operation they are nothing alike.
Leave is a decision, training is an investment, a medical is a requirement
Leave is the simple one. Someone asked, someone approved, the days are gone. Nothing about it needs chasing.
Training is different because it has a deadline attached to something else. A renewal course is not just a day off, it is the day that keeps a ticket alive. Miss it and you have lost a day and gained an expiry problem in six weeks. That means training days want scheduling backwards from the expiry, not forwards from whenever there is a gap.
Medicals are different again, because they are usually a condition of being on a particular site, they can have their own validity period, and booking one depends on somebody else's calendar. A worker cannot always take the first available slot, which is exactly why any deadline attached to a medical needs a realistic window rather than a same-week demand.
Record the reason, not just the absence
Most rosters record unavailability as a blocked-out range and stop there. That is enough to stop a booking and not enough to run an operation.
If the reason is stored, useful things follow. You can see, in one place, how much of next month's capacity is going into renewals, which is the number that tells you whether your training is a plan or a scramble. You can spot the site whose medical requirement is quietly eating two days per worker per year. And when a client asks why you are short in week three, you have an answer better than everyone seems to be off.
Plan renewals against the expiry dashboard
The practical routine is short and does not need a system to start with, though it is much easier with one.
Once a month, look at everything expiring in the next 60 to 90 days. Group it by ticket type rather than by person, because renewal courses are usually cheaper and easier to book in a group. Then place those training days into the roster as unavailability with the reason recorded, before the client asks for those weeks rather than after.
Doing it in that order is the whole trick. Renewals booked after the roster is built are always an interruption. Renewals booked before it are just capacity that was never there.
Mustr surfaces expiries up to 60 days out on the dashboard, with one-click reminders to the worker, which is the input to that monthly routine. The certificates guide covers the states a certificate moves through on the way.
Do not let unavailability be a memory
The failure mode here is the same one as everywhere else in labour hire: it is in somebody's head, or an email, or a note on a whiteboard. Then that person is on leave themselves, and a worker gets rostered onto a swing that clashes with the course that keeps their ticket alive.
Whatever the reason, it belongs in the same place the roster reads from. In Mustr, a worker's own availability calendar is where they mark the days they cannot work, and the booking check refuses a shift that lands on one. The office can see it while building, rather than discovering it at save time.
Watch the return-from-leave edge
One specific thing worth a check in any system: what happens to someone the day they get back. A worker returning from four weeks off may have had a ticket expire while they were away, and the roster is often built during their absence, which means the shift was created when the ticket was still current.
The check that matters is the one at booking time, so a shift created in advance for a worker whose ticket expires before the shift starts is a gap worth looking for deliberately. Running the expiry view against the published roster once a week catches it.
The short version
Record why, not just when. Book renewals from the expiry list rather than from spare capacity. Keep unavailability in the same system the roster reads. And check the people coming back from leave before they walk through a gate with a lapsed card and a valid-looking roster entry.
More on how availability feeds the roster is on the worker portal page.