Contractor vs Subcontractor: WHS Liability in Australia

A subcontractor has just turned up on site with the right tools, the wrong SWMS, and an expired insurance certificate. Work is booked, the client is pushing, and your supervisor wants to let them start anyway. That decision sits right at the centre of the contractor vs subcontractor problem in Australia. It isn't mainly about labels. It's about who carries the WHS duty, who controls the work, and who gets blamed when the regulator asks for records.

For H&S managers and operations leads, this isn't an admin issue. It's a live exposure sitting in every prestart, mobilisation, permit, and contractor file. If you engage subcontractors across construction, manufacturing, or industrial services, your legal position depends less on what the contract calls them and more on how the work is organised, monitored, and documented.

Table of Contents

• The On-Site Reality of Subcontractor Risk
  • The scale changes the control model
• Defining the Legal and Financial Differences
  • A practical comparison
  • What managers should actually check
• WHS Responsibility and the PCBU Duty of Care
  • What the duty looks like in practice
  • Where the principal contractor gets caught
• The Pitfall of Liability Dumping
  • Why contract wording won't save you
  • The WA pattern that should concern directors
• Best Practices for Contracts and On-Site Oversight
  • Contract clauses that actually matter
  • Site controls that prove due diligence
• Using Digital Systems for Subcontractor Management
  • Why paper systems fail
  • What a usable digital process includes
• Actionable Onboarding and Site Management Checklist
  • Pre-commencement
  • On-site mobilisation

The On-Site Reality of Subcontractor Risk

On many sites, most of the people exposed to risk don't work directly for the principal contractor. In Western Australia, subcontractors perform approximately 70% to 90% of all construction work by volume, yet the main contractor remains responsible for the whole site under the WA WHS framework. That changes how a sensible PCBU should set up supervision, consultation, and verification.

If your exposure is mostly created by external labour, your control system has to be built around external labour. Too many businesses still run subcontractor management as a procurement task first and a WHS task second. That approach fails as soon as there's a fall, plant interaction, electrical event, or uncontrolled change to method.

The scale changes the control model

A direct workforce model assumes you can rely on line management, internal systems, and familiar workers. A subcontractor-heavy model is different. You are dealing with separate businesses, variable supervision standards, mixed documentation quality, and competing production pressures.

That means the contractor vs subcontractor question has to be tested on site, not just in the contract file. Ask simple questions:

• Who is directing the work day to day: If your foreman is setting the sequence, method, and timing, your WHS exposure is high even if the worker is engaged through another entity.
• Who verifies competence: If nobody checks licences, inductions, or task-specific capability before mobilisation, the paperwork is already behind the risk.
• Who stops unsafe work: If the answer is vague, the system is weak.

Practical rule: If the principal contractor controls access, sequencing, interfaces, and site rules, they also need a robust subcontractor oversight process. The risk sits with the party controlling the environment.

A lot of incidents don't start with reckless behaviour. They start with poor coordination between trades, unclear boundaries, or assumptions that a subcontractor is “managing themselves”. That assumption is where WHS systems break.

Defining the Legal and Financial Differences

The cleanest way to deal with contractor vs subcontractor risk is to classify people properly from the start. Titles don't decide status. Working arrangements do. If you get that wrong, you create payroll, super, insurance, tax, and WHS problems at the same time.

General contractors also carry a different financial burden. The average base salary for general contractors in Australia is approximately $121,492 per year, reflecting project execution responsibility and overall liability. That gap matters because it points to function. Contractors carry coordination and risk. Subcontractors are usually engaged to deliver a defined part of the work.

A practical comparison

The table is a practical screen, not legal advice. Real situations often sit in the grey zone. Labour-only arrangements are a common trap. A worker may invoice like a contractor but function like an employee in every meaningful sense.

What managers should actually check

The fastest test is operational, not theoretical. Review what happens on an ordinary day:

1. Look at control. Who sets the method, roster, breaks, and supervision?
2. Look at financial structure. Is the person quoting a scope, or just billing hours under your direction?
3. Look at business independence. Do they carry their own business identity, insurances, and trading risk?
4. Look at substitution. Can they send another competent worker, or does the arrangement depend on one person turning up each day?

If you're engaging small operators and want a clearer starting point for documentation, an AI-powered contractor agreement for SMEs can help structure the commercial terms. It won't fix bad practice on its own, but it can force useful decisions about scope, control, insurances, and reporting obligations before work starts.

The contract should reflect the real arrangement. It should never be used to disguise one.

Misclassification usually shows up later through a workers' compensation issue, a super dispute, or a regulator asking why a “subcontractor” was being supervised like a direct employee with none of the supporting controls.

WHS Responsibility and the PCBU Duty of Care

If you're the PCBU or principal contractor, you can't contract out of your WHS duties. You can share activity. You can assign tasks. You can require subcontractors to meet site rules and provide SWMS, insurances, and competencies. What you can't do is hand over the primary duty and hope the paperwork protects you.

Under the WHS Act, primary contractors bear 100% of the legal liability to the client for the project's safety compliance, including subcontractor failures. Australian industry benchmarks also indicate that 78% of safety incidents on multi-site projects are attributed to subcontractor misalignment, while the primary contractor still faces the statutory penalty. In practical terms, that's the core risk in contractor vs subcontractor management.

A plain explanation of PCBU obligations is set out in WHS duties of a Person Conducting a Business or Undertaking.

What the duty looks like in practice

The duty is easiest to understand through activities, not legal theory. A principal contractor should be able to show evidence of all of the following:

• Consultation and coordination: Trades affect each other. High-risk construction work, traffic movement, lifts, isolations, and temporary works all require coordination between duty holders.
• Verification before mobilisation: Don't wait until the gate. Review licences, competencies, insurances, SWMS, and plant records before the first day on site.
• Site-specific induction: Generic company induction isn't enough. People need to understand local hazards, emergency arrangements, interfaces, exclusions, and escalation lines.
• Monitoring: A SWMS in a folder proves very little if the actual method changes once production pressure hits.
• Intervention: Supervisors must have authority to stop work, correct non-conformance, and escalate repeated failures.

The WHS Act expects due diligence. That means officers and managers need to know how subcontractor risk is being managed, not just assume the project team has it under control.

Where the principal contractor gets caught

The weak points are predictable. A subcontractor submits a compliant-looking SWMS that doesn't match the plant on site. A supervisor gives verbal approval to vary the work sequence. Another trade enters the same area. No one updates the risk controls. Then an incident occurs and the record trail doesn't match the work as done.

A subcontractor can own their safe work practices. They do not absorb your PCBU duty.

Insurance matters here too, but not as a substitute for control. Proof of public liability and workers' compensation should be current, checked, and tied to mobilisation approval. If your business is reviewing cover arrangements as part of a broader contractor risk program, this guide on how to secure your contractor business is a useful prompt for the insurance side of the equation.

The mistake I see most often is overreliance on prequalification and underinvestment in field verification. Documents matter. Supervision matters more.

The Pitfall of Liability Dumping

Some contractors still try to push WHS responsibility down the chain with clauses that say the subcontractor is fully responsible for its workers, methods, and compliance. Those clauses have a place, but they do not erase the duties of the engaging business.

That practice becomes dangerous when management starts to believe its own contract wording. Once that happens, oversight drops off. Supervisors stop checking what they should check. Procurement treats subcontractors as self-contained risk packages. Then the principal contractor is exposed on both fronts. The work was not properly monitored, and the contract creates false comfort.

Why contract wording won't save you

A subcontractor can be required to follow site rules, provide SWMS, train workers, maintain plant, and report incidents. All of that is proper. The problem starts when the head contractor acts as though those obligations remove the need to verify and coordinate.

Paper compliance is not site control. A signed subcontract, a current certificate of currency, and a generic risk assessment don't prove that the task was managed safely on the day. Regulators and courts look at conduct, not just clauses.

The WA pattern that should concern directors

Recent WA data shows 42% of construction safety incidents involved subcontractors where the General Contractor failed to provide adequate safety oversight, while 68% of GCs claimed “subcontractor self-managed compliance”. That gap says a lot. Businesses are asserting separation while the facts show dependency and poor oversight.

WA's WHS settings also hold procurers accountable even when subcontractors are self-employed. That point is often missed in simple contractor vs subcontractor guides. If you engage the party, control the workplace, and benefit from the work, you need to assume the regulator will examine your oversight first.

When a business says “the subcontractor was responsible”, the next question is usually “show me how you monitored them”.

Directors should treat liability dumping as a governance failure, not a drafting issue. If the board or leadership team sees subcontractor reliance increasing, the control framework has to tighten with it.

Best Practices for Contracts and On-Site Oversight

A good subcontractor arrangement does two things at once. It sets clear legal expectations, and it creates a field process people can follow under production pressure. Most failures happen because one of those parts is missing.

The contract can't be generic. It needs WHS clauses that match the risks of the work, the interfaces on site, and the level of verification you'll require before and during mobilisation.

A structured process for subcontractor safety management is useful here because it forces consistency across prequalification, approvals, and field checks.

Contract clauses that actually matter

These are the clauses I'd insist on for high-risk work:

• Defined scope of work. Spell out what the subcontractor will do, what they won't do, and where interfaces with other trades sit. Ambiguity creates unsafe assumptions.
• WHS compliance obligation. Require compliance with the WHS Act, site rules, permit conditions, SWMS, and lawful directions from authorised site representatives.
• Right to verify and audit. Reserve the right to inspect documents, observe work, review training records, and audit implementation, not just possession, of controls.
• Stop-work power. Give the principal contractor explicit authority to suspend work for non-compliance, changed conditions, or immediate risk without argument over contractual interference.
• Incident and hazard reporting. Set reporting expectations for incidents, near misses, hazards, and changes to method. If you don't specify the trigger and path, reporting becomes discretionary.
• Insurance and competency evidence. Require current proof of relevant insurances, licences, high-risk work tickets, and other competencies before mobilisation and on renewal.

Site controls that prove due diligence

Contracts set the rules. Supervisors prove the system works.

Use a field routine that leaves an auditable trail:

1. Prestart verification
   Check that the approved worker list matches the people who arrived. Verify plant, licences, and any task-specific controls before work starts.

2. Review the SWMS against the live job
   Don't ask whether a SWMS exists. Ask whether it matches the actual location, sequence, plant, and adjacent trades.

3. Inspect interfaces, not just tasks
   Many events occur between work packages. Focus on access routes, overhead work, mobile plant, temporary power, isolations, and housekeeping boundaries.

4. Record corrective action quickly
   If you identify a gap, assign it to a person, set the response expectation, and verify closure. A verbal direction with no record usually disappears.

5. Escalate repeat non-conformance
   Some subcontractors need education. Others need removal. If the same issue keeps returning, treat it as a contractor management problem, not a worker behaviour issue.

Site advice: The strongest evidence of due diligence is not the binder in the ute. It's a record showing what the supervisor checked, what changed, and what action followed.

Using Digital Systems for Subcontractor Management

Paper files and spreadsheets break down fast once you have multiple subcontractors, multiple sites, and changing work fronts. The issue isn't convenience. It's visibility. If the latest SWMS is in one inbox, the induction record is on paper, and the insurance renewal sits in a spreadsheet nobody trusts, the system is already late.

That's why the digital oversight gap matters. It isn't only a tech problem. It's a control problem. Managers can't coordinate what they can't see, and supervisors can't verify what they can't access in the field.

Why paper systems fail

Projects using centralised, AI-driven subcontractor management platforms reduce administrative safety burden by 45% and incident response time by 60%. Subcontractors in high-risk industries are also 3.5 times more likely to fail safety audits if they are not integrated into the primary contractor's real-time monitoring system.

Those figures line up with what many site teams already know. Manual systems create delays in approvals, poor version control, patchy evidence, and weak escalation. A spreadsheet can list expiry dates. It can't tell a supervisor at the point of work whether the worker in front of them is approved for that task under current site conditions.

What a usable digital process includes

A proper contractor management platform should cover the full lifecycle, not just document storage. Look for these functions:

• Prequalification controls that hold mobilisation until required insurances, licences, and other records are current.
• Induction tracking that links workers to site-specific requirements, not just a one-time generic induction.
• SWMS and form workflows that support review, approval, revision control, and field access.
• Incident and hazard reporting available to both internal teams and subcontractors.
• Audit trail visibility so managers can show what was submitted, who approved it, what changed, and when.

A system should also reduce double handling. If supervisors have to re-enter data from email, WhatsApp, or paper forms, the process is still fragmented.

For businesses trying to tighten due diligence across sites, a contractor management system is most useful when it becomes the single place for approvals, worker records, SWMS, and corrective actions. The point isn't software for its own sake. The point is control you can demonstrate.

Actionable Onboarding and Site Management Checklist

Use this as the minimum standard before a subcontractor starts work.

Pre-commencement

• Confirm business status. Check that the entity engaged matches the contract, invoice details, and insurance documents.
• Review scope boundaries. Make sure the subcontracted scope is defined clearly enough to avoid interface confusion with other trades.
• Verify WHS documents. Collect and review licences, competencies, plant records, insurances, and relevant SWMS before mobilisation approval.
• Set communication lines. Nominate who can issue directions, receive hazard reports, approve variations, and stop work.
• Check supervision arrangements. Confirm who the subcontractor's supervisor is and how they'll coordinate with your site team.

On-site mobilisation

• Induct the actual workers. Don't rely on company-level approval. Confirm the people on site have completed the correct induction.
• Match the SWMS to the task. Review the job location, sequence, plant, and interaction risks before work starts.
• Walk the work area. Check access, exclusions, overhead hazards, traffic paths, and emergency arrangements.
• Test reporting behaviour early. Ask how hazards, near misses, and changes to method will be reported during the shift.
• Inspect and record. Document what you checked, what was corrected, and who signed off.

If any of those steps are missing, don't tell yourself you'll fix it later. Later is usually after something has gone wrong.

If your team is juggling subcontractor approvals, inductions, SWMS, audits, and corrective actions across multiple sites, Safety Space gives you one place to manage the whole process. It helps PCBUs and site leaders replace paper and spreadsheets with a clear, auditable system for subcontractor oversight, so you can spot gaps earlier and show due diligence when it counts.