Field notes › Compliance
What an expired ticket actually costs a labour hire firm
An expired ticket sounds like an admin problem. A date passed, a piece of paper needs renewing, someone will sort it. But when the worker holding that ticket is rostered onto a client site next week, the cost stops being administrative very quickly. It is worth walking through where the damage actually lands, because it is bigger than most firms assume.
The immediate cost: a worker who can't work
The moment a required licence or certificate expires, that worker cannot lawfully or contractually do that work. If the expiry is caught at the site gate, you now have a worker stood down on site. If it is a fly-in role, you have already paid for flights and accommodation to put a person somewhere they cannot work. The shift they were covering is now uncovered, and remote sites do not have a bench of spare qualified people sitting in the crib room.
So the first-order cost is a scramble: finding a replacement with the right tickets and inductions, getting them mobilised, and wearing whatever it costs to unwind the original arrangements. Anyone who has done this for a night shift at short notice knows how ugly it gets.
The slower cost: client trust
Labour hire is a trust business. The client is paying you to send people who are ready to work, and compliance is the least negotiable part of that promise. One expired ticket that reaches their gate tells the client your system has holes, and clients act on that. They audit you harder. They double-check your paperwork. They add their own verification steps, which slows every mobilisation. In the worst case they quietly shift the next contract to a competitor who has not embarrassed them.
None of that appears on an invoice, which is exactly why it is easy to underweight. The expiry that gets caught at the gate costs you a bad day. The pattern of them costs you the client.
The exposure cost: audits and incidents
Then there is the paper trail. If a worker performed high risk work while their licence was expired, that fact is now sitting in your records waiting to be found, by a client auditor, by the regulator, or worst of all in the aftermath of an incident. What the consequences look like depends on the circumstances and your state's laws, and that is a conversation for your lawyer and your state work health and safety regulator, not a blog. The general point stands on its own: an expired ticket discovered after the fact is a far worse conversation than one discovered before the shift.
Why expiries slip through
Almost never because nobody cared. They slip through because the information is scattered. Expiry dates live in a spreadsheet that was accurate the day it was built. The person who maintained it went on leave. The worker renewed their licence but the record was never updated, or did not renew it and assumed someone would remind them. Meanwhile the roster is being built in a different tool, or a different tab, with no connection to any of it. Every handover between those pieces is a place for an expiry to hide.
Catching it 60 days out instead
The fix is not more diligence, it is fewer gaps. Two things change the game. First, expiries need to surface early and automatically. In Mustr, expiring certificates surface up to 60 days ahead, with one-click reminder emails to the worker, and workers upload their renewed certificates themselves through the worker portal on their phone. Sixty days is enough to book a course around a swing. Two days is not.
Second, the roster has to enforce the rule. Every booking in Mustr is checked server-side against the worker's competencies and inductions before it is made, and a failed check blocks the booking outright. A worker whose ticket will not be valid on the day simply cannot be rostered onto that shift, which means the expensive version of this story, the one where the problem is discovered at the gate, does not get a chance to start.
If you would rather find expiries on your roster 60 days early than at a client's gate, book a demo and see it on your own roster.