Skip to content
PIAGO
All guides

Duty of care

Duty of care, and what "reasonably practicable" really means

Duty of care is not an unlimited obligation to prevent all harm. It is a duty to do what is reasonably practicable — and that phrase has a legal definition with five parts, weighed in a fixed order, with cost last.

Written for anyone who has had a control knocked back on cost and needs to know whether that was a defensible answer.

The test

Five factors, in order

Likelihood, degree of harm, knowledge, availability of controls — and only then cost.

Cost

Considered last

And only excuses inaction where it is grossly disproportionate to the risk.

The standard moves

With what you ought to know

A control that becomes normal industry practice becomes reasonably practicable for you.

5 min read · Legislation and figures checked 19 August 2026

"Duty of care" is one of those phrases that everybody uses and almost nobody defines. In an Australian workplace it has a precise meaning, and the precision is in the qualifier rather than the duty.

The duty is to ensure health and safety so far as is reasonably practicable. Not absolutely. Not as far as possible. Not as far as is affordable. Reasonably practicable — which section 18 of the Work Health and Safety Act defines in five parts.

The five-part test

To work out what is reasonably practicable, you weigh, at the relevant time:

  1. The likelihood of the hazard or the risk occurring.
  2. The degree of harm that might result if it does.
  3. What the person concerned knows, or ought reasonably to know, about the hazard or risk, and about ways of eliminating or minimising it.
  4. The availability and suitability of ways to eliminate or minimise the risk.
  5. After assessing the extent of the risk and the available ways of eliminating or minimising it, whether the cost of doing so is grossly disproportionate to the risk.

Read the fifth one again, because the drafting is doing something specific. Cost is not one of five equal considerations. It is explicitly sequenced after the risk and the available controls have been assessed, and the threshold is not "expensive" — it is grossly disproportionate.

That is a very high bar. A control that costs a lot but is proportionate to a risk of death is reasonably practicable. A control that costs a modest amount and addresses a trivial risk may not be. The comparison is always to the risk, never to the budget.

Why the order matters more than the list

Most organisations can recite the five factors. Far fewer apply them in order, and the order is where enforcement action tends to land.

The common failure looks like this: somebody proposes a control, somebody else asks what it costs, and the number ends the conversation. No assessment of likelihood was written down. No assessment of the degree of harm. No survey of what else was available. The risk was never quantified, so there is nothing for the cost to be disproportionate to.

When that sequence is reconstructed in an investigation, it reads as a business decision dressed as a safety decision. The record that would have helped — a written consideration of the risk, the options and why one was chosen — was never made.

The inverse is surprisingly strong evidence. An organisation that assessed a risk properly, considered three controls, adopted the second because the first was genuinely unsuitable, and wrote that down at the time is in a good position even if the outcome was bad. Reasonably practicable is judged at the relevant time, on what was knowable then.

"Ought reasonably to know" is the factor that moves

The third factor is the one that changes underneath you.

You are held to what you know and what you ought reasonably to know. That second half tracks the state of industry practice. When a control is novel and unproven, not using it is defensible. When it appears in a code of practice, is sold by several suppliers, is discussed at every industry conference and is used by your competitors, the position has moved — whether or not anyone wrote to tell you.

For contractor management specifically, this is not theoretical. Verifying a worker's competency against the task and the site, rather than accepting a declaration, has moved from a leading practice to an expected one over the last decade. So has holding equipment to the same standard as people. An operator arguing in 2026 that checking was impractical is arguing against an industry that plainly finds it practical.

What it looks like on a site with contracting companies

Where the duty is shared — and on a contracting company site it always is — reasonably practicable is measured against your capacity to influence and control the matter.

A principal that controls site access has enormous capacity to influence who comes through the gate. That makes verification at the gate reasonably practicable almost by definition, and "the contracting company told us they were current" a weak answer, because checking was available and suitable and not remotely disproportionate.

A contracting company that controls who it rosters has the same capacity in its own domain. It cannot argue that its client's portal was responsible for knowing whether its people were current, because the contracting company is the one who decided who to send.

There is a version of this that appears repeatedly in investigations, and it is worth naming because it is so avoidable. A credential lapses. Nobody notices, because the system that would have noticed is a spreadsheet somebody maintains between other duties. The person works for weeks in that state. Nothing happens — until something does, and the question becomes: what would it have cost to know?

The answer, in 2026, is very little. Which is exactly the problem, because the fifth factor cuts both ways.

Where this sits in Queensland resources

If your work is on a Queensland mine or quarry, the wording that binds you is not section 18 of the WHS Act. The Coal Mining Safety and Health Act 1999 and the Mining and Quarrying Safety and Health Act 1999 use their own formulation: risk must be reduced to an acceptable level, and the Acts define that as within acceptable limits and as low as reasonably achievable.

It reaches much the same place by a different route, and it puts an extra obligation on the way: since 1 June 2026, Queensland operators have had to demonstrate a systematic, verifiable approach to the critical controls standing between a worker and a fatal event. That is a shift from "we assessed the risk" to "we can show this specific control was in place and working on this specific day", and it is much harder to satisfy from memory.

The practical version

Strip out the law and the duty resolves to four questions you should be able to answer on any given day:

  • What could seriously hurt someone here?
  • What are we relying on to stop that?
  • How do we know that thing is actually in place right now?
  • When did we last check, and what happened when it was not?

Organisations that can answer all four have a duty of care position. Organisations that can answer the first two have a risk register. The gap between them is where nearly every enforcement action lives.

What we do about it

Two products, one on each side of the gate.

You run the site

GO! Site Approved

Verification is the reasonably practicable step that gets skipped most often, because doing it by hand across every worker on site is genuinely hard. GO! Site Approved makes checking the default rather than the exception.

See how it works

You go onto someone else’s

GO! Site Ready

Your duty to your own workers is measured the same way. GO! Site Ready gives you the dated record of what each person and machine held, and when you checked it — the evidence "reasonably practicable" is actually assessed on.

See how it works

Questions people ask about this

Does duty of care mean we have to eliminate every risk?
No. The duty is to eliminate risk so far as is reasonably practicable, and where that is not reasonably practicable, to minimise it so far as is reasonably practicable. Elimination is preferred and has to be genuinely considered first, but the qualifier applies to both limbs. What the law does not allow is skipping the consideration — deciding a hazard cannot be eliminated without ever asking the question is where most enforcement action starts.
Can we argue a control was too expensive?
Only if the cost is grossly disproportionate to the risk, and only after you have worked through likelihood, degree of harm, what you knew or ought to have known, and what controls were available and suitable. Cost is the last of the five factors deliberately. A regulator that finds cost was the first thing considered will treat that as evidence the duty was not taken seriously, not as a defence.
What does "ought reasonably to know" mean in practice?
It means the standard rises with industry practice. If a control is published in a code of practice, sold by multiple suppliers, discussed at industry conferences and used by your competitors, you ought to know about it — whether or not anyone told you. This is why "we have always done it this way" tends to be an aggravating factor rather than a mitigating one.
Is a signed contracting company declaration enough to discharge our duty?
Almost never on its own. A declaration is information, and the duty asks what you did with it. Where you have the capacity to influence and control a matter — and a principal engaging a contracting company almost always does — a reasonable step is to verify rather than accept. The test is not whether you asked. It is whether it was reasonably practicable for you to check, and it usually is.
Who decides what was reasonably practicable — us or the regulator?
You decide at the time, and a court decides afterwards, on the facts as they stood at the time. That matters both ways. You are not judged with hindsight about the specific incident, but you are judged against what was knowable and available then. Which makes contemporaneous records of what you considered and why far more valuable than a reconstruction written after something has gone wrong.

Where this comes from

This is a plain-English explainer written for people who have to act on the law, not legal advice. Where a decision turns on it, read the instrument itself or take advice — and if you find something here that is out of date, tell us at [email protected] and we will fix it.

Talk to people who know mining, not a sales team.

PIAGO is Australian owned and operated, out of Brisbane. Book a time and we will walk through your operation and tell you honestly whether we are the right fit.

Talk to Carl