HSE Incident Reporting: Legal Requirements in Australia
Incident reporting is time-critical. Before a team debates root cause or starts cleaning up, it may need to make people safe, decide whether the event is notifiable, contact the correct regulator and preserve the site.
The difficult part is that Australia does not have one identical rulebook. Most jurisdictions use the model WHS framework with local variations; Victoria has its own OHS legislation, and industry-specific laws can add further duties.
This article provides general information, not legal advice. Confirm the current requirements with the WHS regulator for the jurisdiction and industry in which the incident occurred.
Industrial Manslaughter Is Now Nationwide — but the Offences Differ
Every state and territory, as well as the Commonwealth WHS jurisdiction, now has a specific industrial or workplace manslaughter offence. That does not mean every workplace death automatically amounts to industrial manslaughter. The prosecution must prove the elements of the offence, and those elements differ by jurisdiction — including who can be charged, the required level of negligence or recklessness, and whose death is covered.
The current specific offences commenced as follows:
| Jurisdiction | Current specific offence in force since |
|---|---|
| Queensland | 23 October 2017 |
| Northern Territory | 1 February 2020 |
| Victoria (workplace manslaughter) | 1 July 2020 |
| ACT | 11 November 2021 under the WHS Act; an earlier offence existed under the Crimes Act from 2004 |
| Western Australia | 31 March 2022 |
| South Australia | 1 July 2024 |
| Commonwealth | 1 July 2024 |
| New South Wales | 16 September 2024 |
| Tasmania | 2 October 2024 |
Maximum penalties are severe, but a single national penalty figure would be misleading. Depending on the jurisdiction and defendant, the maximum may include lengthy imprisonment for an individual or a multi-million-dollar fine for a body corporate. Penalty units and statutory amounts can also change.
For construction leaders, the practical lesson is broader than the offence itself: officers need current knowledge of WHS matters and must ensure that the business has processes for receiving incident and hazard information, responding to it, complying with notification duties and verifying that those processes are used. The Commonwealth WHS Act's due-diligence provisions are a useful statement of that model, but local law must be checked.
Start With the Local Notifiable-Incident Test
Under the established model WHS framework, a notifiable incident arising from the conduct of a business or undertaking generally falls into one of three categories:
- the death of a person
- a serious injury or illness
- a dangerous incident that exposes a person to a serious risk, even if no one is injured.
The words arising from the conduct of the business or undertaking matter. It is not accurate to say that every death or injury occurring near a workplace is automatically notifiable.
There is also an important current-law warning. In December 2025, Safe Work Australia published amendments to the model incident-notification provisions, including additional categories and clarifications. Model amendments do not change a local duty until the relevant jurisdiction adopts them, and adoption is not uniform. For example, ACT notification amendments commenced on 19 November 2025. Check the local regulator before changing a notification procedure.
Serious injury or illness
The established model provisions include an injury or illness requiring, or that would reasonably be considered to require:
- immediate treatment as an in-patient in a hospital
- immediate treatment for an amputation, serious head or eye injury, serious burn, degloving or scalping, spinal injury, loss of bodily function or serious laceration
- medical treatment within 48 hours of exposure to a substance.
The legal test is not simply whether the person was eventually admitted or treated. Avoid making a notification decision from an informal injury label alone; gather the treatment facts and apply the regulator's current test.
Dangerous incidents
The established model list includes incidents involving:
- an uncontrolled escape, spillage or leakage of a substance
- an uncontrolled implosion, explosion or fire
- an uncontrolled escape of gas, steam or a pressurised substance
- electric shock
- the fall or release from height of plant, a substance or another thing
- the collapse or partial collapse of a structure or excavation
- an inrush of water, mud or gas in an underground excavation
- an interruption to the main ventilation system in an underground excavation.
A dangerous incident can be notifiable without an injury. An excavation collapse that exposes someone to a serious risk should not be dismissed as “only a near miss”.
What to Do When an Incident May Be Notifiable
1. Make the situation safe
Provide assistance, call emergency services when required, prevent further harm and escalate internally. Immediate safety comes before record administration.
2. Notify the regulator without delay
Under the model approach, the PCBU must notify the regulator immediately after becoming aware of a notifiable incident, using the fastest possible method. Follow the regulator's published channel; for an urgent or uncertain event, calling the regulator is the prudent course.
| Jurisdiction | WHS regulator |
|---|---|
| Queensland | Workplace Health and Safety Queensland |
| New South Wales | SafeWork NSW |
| Victoria | WorkSafe Victoria |
| Western Australia | WorkSafe WA |
| South Australia | SafeWork SA |
| Tasmania | WorkSafe Tasmania |
| Northern Territory | NT WorkSafe |
| ACT | WorkSafe ACT |
| Commonwealth scheme | Comcare |
Do not assume that recording an incident in an internal system notifies the regulator. Unless the regulator confirms receipt through its accepted channel, the external notification remains a separate action.
3. Preserve the site
The model duty is to preserve the incident site, so far as reasonably practicable, until an inspector arrives or directs otherwise. The site includes associated plant, substances, structures and other things.
The recognised reasons for disturbing a site include:
- assisting an injured person
- removing a deceased person
- making the site safe or minimising the risk of another notifiable incident
- facilitating a police investigation
- acting with an inspector's permission.
Where the site must change, record what changed, why, when and by whom. Photographs, video, measurements and contemporaneous notes can help preserve the factual record, provided it is safe and appropriate to collect them.
4. Supply written notice if required
A regulator may require written notice after an initial telephone notification. Under the model provision, that written notice must be supplied within 48 hours of the request. The 48-hour period is not a general extension for making the initial notification.
Capture the incident time and location, activity underway, people involved, injuries or treatment, immediate actions, scene changes, witnesses and the regulator notification details. Keep fact and opinion distinct; preliminary theories should not be presented as established causes.
5. Retain the required record
Under the established model provision, the PCBU must keep a record of each notifiable incident for at least five years from the date of notification. Local and industry-specific requirements may require more.
Keep the notification record connected to the supporting material: incident report, investigation, relevant risk assessment and work method documents, corrective actions, close-out evidence, training or competency records, and regulator correspondence.
Build an Evidence Chain, Not Just an Incident Form
A credible incident record lets a reviewer follow the response from report to close-out. The exact audit criteria depend on the contract, management system and regulator, but a useful evidence chain normally answers:
- What happened, when and where?
- Who reported it and who was affected or witnessed it?
- What immediate actions made the situation safe?
- Was notifiability assessed by an accountable person?
- If notification was required, when and how was the regulator contacted, and what reference was issued?
- What evidence was preserved?
- What investigation method was used, and what did it find?
- Which corrective actions were assigned, to whom and by when?
- What shows that each action was completed?
- Who reviewed the result and authorised close-out?
Independent verification and later effectiveness review are strong controls, particularly for significant incidents, but do not describe them as universal statutory requirements unless the applicable law, contract or management-system procedure says so.
The Weak Point Is Fragmentation
A spreadsheet is not automatically non-compliant, and modern file platforms may retain version history. The risk arises when the incident register, emails, photographs, witness information, investigation and action list are split across different locations with unclear ownership.
Typical failure modes include:
- the regulator call is made but its time and reference are not recorded
- the incident is updated without a clear record of who changed the status
- an action has no accountable owner or due date
- close-out evidence is stored in a separate folder and cannot be matched to the action
- similar incidents cannot be grouped for trend review
- sensitive personal information is copied more widely than necessary.
The control objective is not “buy software”. It is to maintain one governed process with defined responsibility, reliable records, appropriate access and a close-out path the team actually follows.
How TaskRox Supports the Process
TaskRox's shipped HSE module keeps incident records, investigations and corrective actions in the project workspace. It supports the process; it does not decide whether an event is legally notifiable and it does not notify a regulator on the user's behalf.
Structured incident records
An incident can record:
- an auto-generated incident number and the date the event occurred
- description, immediate actions, location, area and contractor
- involved and linked project personnel
- classification, including near miss, FAI, MTI, RWI, LTI, fatality and non-injury event types
- actual and potential consequence on a 1–5 scale, plus an HPI flag
- structured injury details, including treatment notes and days lost or restricted
- regulator status: Not Notifiable → Under Review → Notifiable → Notified, with notification detail and date
- incident attachments and linked project photos.
The register can be searched, filtered through its columns and exported to CSV. The status lifecycle is Reported → Triage → Investigation → Actions Open → Awaiting Verification → Closed.
Linked investigations
Separate investigation records can be linked to an incident. The available levels are Quick Review, 5 Whys, ICAM Lite and Full ICAM, with fields for chronology, direct causes, contributing factors, failed controls, human and organisational factors, lessons learned, approval and close-out.
Using a named method does not make an investigation adequate by itself. The method should match the event's potential severity, contractual requirements and the competence of the people leading it.
Corrective actions
Each incident can carry multiple corrective actions with a title, description, assignee, due date and status of Open, In Progress or Closed. The incident detail shows open-action counts, while project HSE reporting brings incident and action information together.
TaskRox records key HSE events such as incident creation and updates, corrective-action creation, investigation changes and attachment uploads in the organisation audit log. That logging supports traceability, but teams still need a sound review procedure and meaningful evidence.
Reporting without invented rates
The HSE analytics layer separates injury classification, actual and potential consequence, HPI status and regulator-notification status. Recordable classifications feed LTIFR/TRIFR-style reporting only when the required exposure hours exist; if hours are missing or zero, the rate remains unavailable rather than being guessed.
A Practical Close-Out Standard
Before closing a significant incident, confirm that immediate risk controls remain in place, the notifiability decision and any regulator communication are recorded, the investigation is complete, corrective actions have owners and evidence, and the person approving close-out has enough information to test the result.
Good records do not replace safe work, competent investigation or legal advice. They make the organisation's actions visible and reviewable — which is exactly what a serious incident response needs.
If your current process is fragmented, try TaskRox free for 14 days and test the HSE workflow against a real project scenario. No credit card is required.