---
title: "“Equivalent or Higher” Is Now an Evidence Test for NSW Mines"
description: "What NSW’s section 26A code-of-practice duty means for mines, how to demonstrate equivalent or higher controls, and where evidence-anchored SHMS assurance can help."
url: https://mineguard-ai.com/blog/equivalent-or-higher-evidence-test-nsw-mines
author: "MineGuard AI"
published: 2026-10-17T20:33:31.103Z
updated: 2026-10-17T20:34:08.054Z
tags: ["Best Practices", "AI Safety", "Industry Insights", "Mining"]
publisher: MineGuard AI
---

# “Equivalent or Higher” Is Now an Evidence Test for NSW Mines

Since 1 July 2026, New South Wales PCBUs have faced a sharper choice on approved codes of practice: comply with the code, or manage the hazard another way that provides an equivalent or higher standard of health and safety.

For mining leaders, this is more than a legal wording change. It turns local departures, alternative engineering solutions and inherited site practices into an assurance question: **what evidence shows that the alternative is at least as protective as the code, and who remains accountable for that conclusion?**

The practical response is not to force every site into identical paperwork. It is to make the basis for every material difference explicit, current and reviewable.

## What changed on 1 July

[SafeWork NSW says section 26A of the *Work Health and Safety Act 2011* commenced on 1 July 2026](https://www.safework.nsw.gov.au/resource-library/codes-of-practice). Its guidance describes approved codes as minimum performance standards: a PCBU must comply with a relevant code or use a different method that provides an equivalent or higher standard of work health and safety.

That is a stronger footing than treating a code only as persuasive guidance. Codes also remain admissible in court proceedings, and inspectors may refer to them when issuing improvement or prohibition notices. SafeWork advises PCBUs to identify the codes relevant to their hazards, review existing practices and controls, consult workers on changes, address training needs, and maintain clear records of risk assessments, reviews and actions.

The mining regulator is signalling the same direction. [NSW Resources lists codes of practice as an FY27 mine-safety compliance priority](https://www.resources.nsw.gov.au/resources-regulator/our-role/regulatory-approach/compliance/compliance-priorities-fy27). It says eight codes have received editorial updates and the remaining eight are undergoing comprehensive review, with consultation intended to keep them contemporary, risk-based and focused on controls in practice.

The [NSW Resources mining code library](https://www.resources.nsw.gov.au/resources-regulator/safety/advice-and-resources/codes-of-practice) includes mine-specific codes covering safety management systems, electrical and mechanical engineering control plans, emergency planning, inundation and inrush, roadway dust analysis, shafts and winding systems, and underground strata control. General WHS codes may also be relevant to mine work. Applicability should be assessed against the operation, hazard and current law.

This article is operational commentary, not legal advice. Sites should confirm their obligations for the codes and circumstances that apply to them.

## Equivalence is a case to be demonstrated

An alternative may be entirely legitimate. A newer engineering control, a site-specific design or another recognised standard may outperform the method described in a code. But “different” is not self-validating, and “we have always done it this way” is not an equivalence test.

A defensible equivalence case should connect at least six elements:

1. **The applicable requirement.** Identify the relevant code provision and the hazard or risk it addresses.
2. **The alternative method.** Describe the actual control as implemented, not merely its policy name.
3. **The comparison basis.** Explain how the alternative achieves an equivalent or higher safety standard, including assumptions, limits and credible failure modes.
4. **The evidence.** Link design records, risk assessments, technical references, verification results, worker consultation and competence requirements.
5. **The accountable decision.** Record competent review, approval, ownership and any conditions attached to continued use.
6. **The maintenance trigger.** Define when the case must be reconsidered, including code revisions, plant or process change, incidents, failed verification and new technical information.

This is not about producing a legal brief for every routine task. It is about applying assurance effort in proportion to consequence and uncertainty. A material departure affecting a principal hazard or critical control deserves a stronger evidence chain than a minor administrative variation.

## The hidden risk is system drift

The first assessment of equivalence may be sound while the surrounding system slowly changes.

A code is revised. A procedure is updated without its linked risk assessment. A contractor uses a different work method. A form still references a superseded standard. A control described in a principal hazard management plan no longer matches the verification checklist used in the field.

Each document may look reasonable in isolation. The weakness sits in the relationships between them.

That creates three executive risks:

- **False assurance:** the organisation can show documents, but not that the alternative control still meets the code’s safety standard.
- **Unowned exceptions:** local variations accumulate without a named decision-maker or expiry and review logic.
- **Late discovery:** contradictions surface during an inspection, an audit or an incident, when remediation is most disruptive and the decision trail matters most.

The leadership question therefore changes from “Have we reviewed the code?” to “Can we trace each material requirement through our chosen control, field evidence, approval and current operating documents?”

## A practical 90-day response

Executives do not need to launch a document rewrite across the whole business. A risk-based program can begin with four moves.

### 1. Establish the code register

Confirm which approved codes apply to the operation and who owns each one. Record the current version, affected plans and procedures, and the business process for monitoring change.

### 2. Find the departures

Map relevant code provisions to the SHMS, principal hazard plans, control plans, procedures and task documents. Prioritise gaps, partial matches and places where the site intentionally uses another method.

### 3. Build equivalence records for material alternatives

For high-consequence departures, capture the comparison, evidence, competent review, worker consultation, approval and review triggers in a consistent form. Do not let the rationale live only in meeting minutes or personal knowledge.

### 4. Test the operating system

Sample whether field documents, verification activities and worker understanding reflect the approved arrangement. An equivalence record is not assurance if the control it describes is absent, degraded or contradicted at the job.

Board and executive reporting should focus on exposure, not document volume: applicable codes not yet mapped, material departures without an approved equivalence case, overdue reviews, unresolved contradictions, and alternatives whose verification evidence is weak or deteriorating.

## Where MineGuard AI fits

The workload is highly structured but judgement-heavy: identify requirements, compare many linked documents, surface contradictions, preserve citations, and route findings to competent people. That is a natural place for AI assistance, but not for delegated legal or safety accountability.

[MineGuard AI’s SHMS AI](https://mineguard-ai.com/solutions/shms-ai) is designed to ingest safety management systems, procedures, risk assessments, principal hazard management plans and standards; compare them with legislation and internal requirements; and return clause-level findings with citations. Its published capabilities include cross-document consistency checks, change-impact analysis, version comparison, evidence prompts and action-ready remediation outputs.

For section 26A readiness, that can support a controlled workflow: build the applicable requirement set, locate where each requirement is addressed, flag missing or contradictory material, identify documents affected by a code change, and assemble reviewable findings. MineGuard explicitly states that risk-assessment content is always human-reviewed and that the customer’s team remains the decision-maker.

That boundary matters. AI can widen review coverage and make evidence easier to trace. It cannot determine legal applicability for the organisation, certify equivalence, approve a critical control or replace competent consultation and field verification.

MineGuard’s [trust model](https://mineguard-ai.com/trust) states that outputs are presented for human inspection and require named approval before reaching the field, with an audit trail of approval. The commercially useful outcome is not an automated declaration of compliance. It is a faster, more consistent way for accountable people to find the gaps, examine the evidence and maintain the decision record.

## Make the alternative visible

Section 26A does not remove room for better or site-specific controls. It raises the discipline required to use them.

Mining leaders should expect the strongest organisations to know which code provisions apply, where their systems meet them, where they deliberately differ, why the alternative is at least as protective, and what current evidence supports that position.

The immediate next step is simple: choose one high-consequence code and one linked document set, then test whether every material departure has a current, owned and evidence-backed equivalence case.

[Request a MineGuard AI SHMS sample assessment](https://mineguard-ai.com/solutions/shms-ai) to see how clause-level mapping, contradiction detection and change-impact review can support that work while keeping approval with your competent people.

## Key sources

- [SafeWork NSW: Codes of practice and the section 26A duty](https://www.safework.nsw.gov.au/resource-library/codes-of-practice)
- [SafeWork NSW: Australian Standards and other Standards](https://www.safework.nsw.gov.au/resource-library/WHS/australian-and-other-standards)
- [NSW Resources: July 2026 to June 2027 compliance priorities](https://www.resources.nsw.gov.au/resources-regulator/our-role/regulatory-approach/compliance/compliance-priorities-fy27)
- [NSW Resources: Codes of practice for mines](https://www.resources.nsw.gov.au/resources-regulator/safety/advice-and-resources/codes-of-practice)
- [MineGuard AI: SHMS AI](https://mineguard-ai.com/solutions/shms-ai)
- [MineGuard AI: Trust & Security](https://mineguard-ai.com/trust)