Back to blog
Compliance · 4 May 2026 · 6 min read

Your Duty of Care Doesn't Stop at the Gate

A PCBU's WHS duty for on-site contractors is non-delegable — and a folder of certificates collected at procurement doesn't discharge it. Why contractor compliance has to be verified at the gate, on the day.

Quynh Do
Quynh Do
Business Analyst

A crew arrives at 6:40am to replace a switchboard. The procurement file says the company was vetted eleven weeks ago: prequalification approved, public liability sighted, the lead electrician’s licence on record. So the boom gate lifts. What nobody at the gate can actually see is that the company’s public liability policy lapsed nine days ago, the licensed electrician on file is on another job, and the person about to open the switchboard is a second-year apprentice the site has never inducted.

Every line of that file was true the day it was filed. None of it describes the people on site this morning. That gap — between “we vetted them” and “the person here right now is current” — is where contractor compliance actually lives, and it’s the gap a folder cannot close.

The duty you can’t hand over

Under Australia’s model WHS laws, a Person Conducting a Business or Undertaking (PCBU) owes a primary duty of care to workers who carry out work for the business. When more than one PCBU shares a duty — your organisation and the contractor’s employer both do — each must discharge it to the extent of its own influence and control. Critically, that duty is non-delegable. You cannot sign it away in a contract, and you cannot assume the contractor’s own employer has it handled.

In plain terms: if a contractor works on your site, the obligation to verify, monitor and document their WHS compliance is yours, independently, and it does not transfer because you collected paperwork from their company. The procurement folder is evidence that you asked. It is not evidence that the duty was met on the day work happened.

This is the part that surprises people. A signed subcontract, a current ABN, a stack of certificates — those are necessary, but they describe a relationship and a moment, not an ongoing state. The duty is continuous. The verification has to be too.

Why paper vetting fails

Vetting at procurement time fails for a structural reason, not a diligence one. Even a thorough vetting process captures a snapshot, and the things it captures keep moving after the snapshot is taken.

  • Certificates expire between award and arrival. A High Risk Work Licence (HRWL) or a trade qualification that was current when the tender was awarded can lapse before the crew sets foot on site weeks or months later. The file still shows green.
  • Company insurance lapses mid-contract. Public Liability and Professional Indemnity policies renew on their own cycle, not yours. A policy sighted at onboarding can quietly fall out of currency halfway through a twelve-month maintenance contract, and nothing in a static folder will tell you.
  • The worker who turns up isn’t always the worker you vetted. You filed one person’s white card and HRWL. Subcontracting, labour hire and last-minute crew changes mean the individual signing in today may never have been assessed against anything — yours or their employer’s.

A folder is a record of the past tense. A duty of care operates in the present tense. The mismatch is the whole problem.

What “good” looks like: continuous and gated

Discharging a non-delegable duty for a moving workforce means two things at once: the checks have to be continuous (state that updates as licences, insurances and inductions change) and they have to be gated (enforced at the moment a person tries to start work, not just filed somewhere).

Concretely, “good” verifies all of the following — and re-verifies them at sign-in, on the day:

  1. Company prequalification — the contracting company is approved to work on your site.
  2. Insurance currency — Public Liability, Professional Indemnity and the rest are current today, not on the day they were sighted.
  3. Worker licence and certification currency — HRWL, white card (general construction induction), trade qualifications, each tracked for currency rather than mere presence.
  4. Induction completion — the specific person has completed your site’s induction, mapped to the competencies the work actually requires.
  5. A right-to-work check at the moment of sign-in — the gate makes a decision when the person presents, not when the contract was signed.

The difference between a folder and a gate is the difference between we believe they were compliant and this person is cleared to work, here, now, and we can show exactly why. One of those discharges a duty of care. The other is a hope with a paper trail.

Assessed against your own standard

There’s a subtler point inside induction. A document store can confirm a contractor electrician holds an electrician’s qualification. It can’t confirm that qualification meets your requirements for the work. Good contractor management assesses an external contractor against the organisation’s own position-to-competency matrix — the same matrix used for staff — so a contractor electrician is held to the same competency requirements as an employee electrician. Compliance becomes a question of fitness for your work, not just the presence of a generic ticket. We go deeper on this in One matrix, two workforces.

The gate, in practice

Lattice Look Contractor Management implements exactly this as a six-check right-to-work gate at sign-in. When a person checks in, the gate evaluates company prequalification, insurance currency, worker status, certification currency, induction completion and geofenced presence on site, then returns a PASS, BLOCK or WARN with an explainable reason — not a silent yes or a mystery no. And the checks cascade: if a company’s insurance lapses, its prequalification suspends and every linked worker is automatically blocked, without anyone manually chasing it down. We walk through all six checks and the cascade logic in The six-check right-to-work gate.

Everything the gate decides is written to an immutable, tamper-evident audit trail, so when a regulator or your own board asks how do you know this person was compliant on the morning of the works, the answer is a sealed record rather than a reconstruction. You can read more about the platform on the Contractor Management page, the underlying security and data-sovereignty posture on our trust centre, and the broader platform overview.

The folder at procurement was never the problem. Treating it as the finish line was. Your duty of care doesn’t stop at the gate — which is exactly why the gate is where it has to be enforced.

contractors whs compliance

Ready to see Lattice Look in action?

Five minutes to sign up. Free onboarding.