Field notes › Compliance
Who's responsible when a non-compliant worker gets on site?
A worker walks onto a client site without a current ticket for the task they are doing. Nobody noticed until something prompted a check. Now everyone is asking the same question: whose fault is this? The labour hire firm that supplied them, or the host that let them through the gate?
The uncomfortable answer: more than one party
Under Australian work health and safety law, duties are shared. The labour hire provider has duties to the workers it supplies. The host business has duties to everyone working under its direction, including labour hire workers. Those duties overlap, they generally cannot be contracted away, and pointing at the other party has a poor track record as a strategy. The specifics vary by state and by circumstance, so treat this as orientation, not advice, and check with your state's work health and safety regulator for how the duties apply to your arrangement.
The practical takeaway is blunt. If you supply the worker, "the host should have checked" is not a position you want to be defending. If you are the host, "the agency said they were fine" is not either. Both parties need their own basis for believing the worker was compliant.
Where the gap actually opens
Almost never at induction day, and almost never through bad intent. The gap opens quietly, in the ordinary run of business. A ticket that was current when the worker was onboarded expires eight months later. A worker cleared for one client site gets booked onto another with different induction requirements. A last-minute swap gets made by phone on a Sunday night and the paperwork is left to catch up. In every case there was a moment, the moment of booking, where the problem was checkable. It just was not checked, because checking relied on a person having time and the right spreadsheet open.
Close the gap where it opens
If the failure point is the booking, that is where the control belongs. Mustr checks every booking server-side before it is confirmed: the worker's competencies, their inductions, their availability, and whether they are already booked elsewhere. If the check fails, the booking is blocked outright. Nobody has to remember to check, be senior enough to push back, or be awake enough at 9pm on a Sunday to catch it. The non-compliant booking simply cannot be made. How it works shows the flow from booking to confirmation.
This changes the conversation with hosts too. Instead of assuring a client that your people are checked, you can describe a control: every worker we send has passed a server-side competency and induction check for your site, at booking time, every time. That is a stronger sentence, and safety managers know the difference.
Be able to prove what you knew
When an incident or an audit lands, the question shifts from "was the worker compliant" to "show us". What did the worker's certifications look like when they were booked? Who made the booking and when? A firm running on spreadsheets and texts reconstructs that story from fragments. A firm with an audit trail produces it. Mustr keeps the trail as a side effect of normal rostering, along with expiring certs surfaced up to 60 days out so renewals happen before they become findings. The compliance page has the detail.
Responsibility you can carry
Shared duties are not going anywhere, and no software changes what the law expects of you. What you can change is whether your side of the chain has gaps. A hard check at the moment of booking, plus a record you can produce on demand, covers the two questions that decide how these situations go: could it have been prevented, and can you show what you did.
If you would rather block the bad booking than explain it later, book a demo.