There is a sentence in the Coal Mining Safety and Health Act that changes how contractor management works in Queensland, and it is easy to read past.
The site senior executive must ensure that people at the mine are competent to perform the work they are asked to do.
Not employees. Not the operator's workforce. People at the mine.
On a site where two thirds of the people through the gate on a given morning work for somebody else, that is a personal obligation about other companies' employees — held by one named individual, who did not hire them, does not pay them, and cannot see their training records.
The obligation does not distribute
The instinct, reasonably, is that this is what the contract is for. The contracting company warrants that its people are competent. The warranty is in writing. The risk has moved.
It has not moved, and the reason is structural rather than legal drafting. The SSE role exists in the Act precisely so that a single accountable person holds the whole picture of safety and health at the mine. Splitting that across engagement boundaries would defeat the purpose of naming the role at all.
Which means the SSE's position on a contracting company's competency is not did we obtain an assurance but did we know.
Those are different questions and they produce different evidence. The first produces a signed document. The second produces a record of what was actually checked, when, against what standard.
Verification, not attestation
The distinction has been sharpened considerably since 1 June 2026, when Queensland's critical control management obligations took full effect under the Resources Safety and Health Legislation Amendment Act 2024.
Operators now have to demonstrate a systematic and verifiable approach to the controls standing between a worker and a fatal event. Verifiable is the operative word.
Work through what that means on a contracting company-heavy site. A critical control is performed by a person, usually using plant. The control is only genuinely in place if:
- the person performing it is competent to perform it; and
- the plant involved is fit for the task.
If the person is a contracting company's employee and the machine is a contracting company's asset, then verifying the control means verifying a contracting company's worker and a contracting company's plant. There is no version of this obligation that stops at the fence.
An attestation is a contracting company telling you everyone is current. A verification is a record showing that this named person held this named competency, assessed on this date, and this named machine was serviced on that date. Only one of those is evidence.
What this looks like when it goes wrong
The pattern in investigations is consistent and it is rarely dramatic.
Nobody ignored a warning. Nobody accepted an obviously unqualified person. What happened is that the system for knowing was a set of documents collected at onboarding, filed, and never revisited — so the mine's picture of a contracting company's workforce was accurate on the day it was assembled and progressively less accurate every day afterwards.
Someone's ticket lapsed. The renewal was arranged eventually. In the gap, they worked. Nobody at the mine knew, because nothing at the mine was watching.
When that is reconstructed afterwards, the SSE's position is not that they made a bad decision. It is that they had no mechanism for making the decision at all. Which is worse, because it is systemic rather than an error of judgement.
The three questions worth being able to answer
For any contracting company, on any day, an SSE should be able to answer:
Who is on site under this engagement, and what is each of them authorised to do? Not who is registered. Who is here.
What evidence did we hold for that authorisation, and on what date did we last verify it? Not "they provided certificates at onboarding" — the date of the last verification.
What plant did they bring, and is it fit for the task it was brought for, against our requirements? This is the half that is usually answered from a different system, or from memory.
If those three answers require somebody to go and find out, the honest position is that the mine does not currently know, and would discover the gap only when something forced it to.
Why this lands harder on some sites than others
Two operators with identical obligations can be in very different positions, and it usually comes down to whether contractor compliance was treated as a records problem or as a gate problem.
Treated as a gate problem, the check happens at entry, once, against whatever the person is carrying. It is a real control and it catches the obvious cases.
Treated as a records problem, the mine holds a live view of every contracting company workforce against its own requirements, and a lapse surfaces before the person travels rather than when they arrive. The gate then becomes a confirmation rather than a discovery.
The second is more work to set up and dramatically less work to run, because the alternative to a system is a person — and a person who holds the whole picture in their head is a single point of failure whose leave is always taken in the week something happens.
The uncomfortable part
An SSE cannot delegate this obligation, but they also cannot personally verify several hundred contracting company workers.
What they can do is be able to show that the mine had a mechanism, that the mechanism ran, and that when it found something the mine acted. That is a defensible position, and it is available to any operator willing to treat contracting company competency as something the site knows rather than something the site was told.
The requirement did not change on 1 June 2026. What changed is that the operator now has to be able to demonstrate it, on request, for the controls that matter most.
