Incident Reporting Procedure: A Practical WHS Guide

A worker is caught in a mobile plant exclusion zone. Production stops, the supervisor calls for first aid, and three people reach for their phones. One starts an internal form. Another calls the project manager. Nobody has yet decided whether the PCBU must notify the WHS regulator.

That decision can't wait for a complete investigation. The first part of an effective incident reporting procedure separates emergency care from statutory triage, protects the scene, and gets the right people involved before evidence disappears. In Australian construction, manufacturing and industrial services, the difference between an internal log and a notifiable incident is often decided with incomplete information.

Table of Contents

• The First 30 Minutes After a Workplace Incident
  • A role-based opening response
• Internal Log or Notifiable Incident
  • Step one, classify the event
  • Step two, separate uncertainty from inaction
• Statutory Notification and Site Preservation Steps
  • The notification sequence
  • Where local rules affect the workflow
• Why Incidents Go Unreported and How to Fix It
  • Design for the behaviour you need
• Documentation, Registers and Record Retention
  • A defensible record structure
• Turning Reports into Prevention Actions

The First 30 Minutes After a Workplace Incident

At a construction site, a worker falls near an open penetration. The foreman stops nearby work, a trained first aider attends, and the site manager begins asking what happened. The worker is conscious, but the extent of the injury isn't clear. The temptation is to move equipment, clean the area and restart unaffected work.

That response creates risk. The immediate priorities are 救助, scene control and notification triage, not fault-finding. The PCBU must make the area safe and assist the injured person, but must avoid disturbing the incident site unless an exception applies under the WHS framework.

A role-based opening response

The first supervisor on scene should give clear directions rather than start an informal investigation.

1. Stop the immediate danger. Isolate plant, stop work and establish a controlled area. Don't allow well-meaning staff to move tools, materials or guards unless necessary to prevent further harm.

2. Arrange medical assistance. Call emergency services where required, provide first aid and account for people in the area. Record who attended and when.

3. Escalate internally. The supervisor should contact the site manager or operations manager, who alerts the H&S lead and the responsible PCBU representative. A contractor incident also needs prompt escalation through the principal contractor's agreed pathway.

4. Start the notification test. Ask whether there has been a death, serious work-related injury or illness, or dangerous incident. The model WHS framework requires the PCBU to notify the relevant regulator immediately after becoming aware of a notifiable incident. Safe Work Australia's incident notification guidance sets out the national framework and the separate regulators operating in each jurisdiction.

5. Preserve early evidence. Note the time, location, people present, plant identification, work activity, weather or lighting conditions, and the state of controls. Take photographs only if that can be done without disturbing the site.

Practical rule: Treat the first account as perishable evidence. Capture who saw what, where each person was standing and what changed before memory fills the gaps.

Vehicle and fleet events need the same discipline. A useful comparison is this logistics fleet incident reporting guide, particularly for assigning driver, supervisor and fleet-management responsibilities. Your emergency response plan should also define the call tree before an event occurs. A workplace emergency response plan template can help formalise those roles.

Internal Log or Notifiable Incident

The wrong question is, “Can we prove the injury is serious?” The right question is, “Based on what we know now, could this fall within a notifiable category?”

Under the model WHS framework, the PCBU must notify the relevant WHS regulator immediately after becoming aware of a workplace death, serious work-related injury or illness, or dangerous incident. Safe Work Australia's incident notification materials also identify newer categories and practical edge cases that operations teams need to consider.

Use this decision sequence at the point of escalation.

Step one, classify the event

Start with the event, not the form.

• Death or suspected fatality: Treat it as notifiable immediately. Keep the site controlled and notify the regulator.
• Serious injury or illness: Escalate where the event may meet the serious injury or illness threshold. Don't wait for a final diagnosis if the circumstances indicate a potentially serious outcome.
• Dangerous incident: Consider the potential for serious harm even where nobody is injured. Mobile plant contact, a major fall event, structural failure, uncontrolled release or electrical event may require regulator notification because of the danger created.
• Other event: Log it internally, investigate it and apply corrective action where it doesn't meet the notifiable threshold.

Falls from height and mobile plant events deserve early H&S review because the absence of immediate visible injury doesn't remove the potential significance of the event. Violent incidents, including sexual assault, also require careful escalation. An extended absence exceeding 15 calendar days is among the categories addressed in updated model duties, so your triage tool must reflect current jurisdictional requirements rather than rely on an old form.

Step two, separate uncertainty from inaction

If the facts are incomplete, record what is known and escalate for a regulator decision. Internal logging doesn't replace statutory notification. A report can be updated as more information becomes available, but a missed immediate notification can't be repaired by completing a better form later.

Keep the internal form focused on triage: event type, harm or potential harm, location, regulator jurisdiction, time of awareness and the person responsible for calling. A WHS incident report form can support that workflow, but it must sit inside a defined escalation process.

For comparison, organisations operating across borders may encounter different reporting tests. A guide by Scher, Bassett & Hames provides California-focused context, but Australian PCBUs should not transplant overseas thresholds or terminology into an Australian WHS decision tree.

Statutory Notification and Site Preservation Steps

Once an incident may be notifiable, the PCBU must shift from internal logging to a controlled statutory response. The first decision is who has authority to notify, who controls the site and who records each action.

The relevant state, territory or Commonwealth WHS regulator must be contacted immediately. Safe Work Australia identifies the national regulator network, including SafeWork NSW, WorkSafe Victoria, WorkSafe Queensland, SafeWork SA, WorkSafe WA, WorkSafe ACT, WorkSafe Tasmania, NT WorkSafe and Comcare. The correct contact depends on where the work occurred and which regulatory scheme applies.

The notification sequence

1. Control the area. Stop work that could change the scene or expose people to further harm. Establish a boundary, nominate an access controller and keep non-essential personnel out.

2. Make the immediate call. Notify the regulator as soon as the PCBU becomes aware of the notifiable incident. Record the time, contact method, regulator contact, information provided and the internal person who made the call.

3. Preserve the site. Leave the incident site undisturbed until an inspector arrives or gives direction. The model duty permits disturbance to assist an injured person, remove a deceased person, make the site safe, prevent further harm or enable police action. Safe Work Australia's incident notification fact sheet explains these limited exceptions.

4. Provide written information when required. If the regulator requests written notification, the PCBU must provide it within 48 hours. State requirements may impose separate lodgement rules. South Australia requires written lodgement as soon as reasonably practicable and within 48 hours, while life-threatening events or fatalities must be reported by phone immediately, as described in Safe Work Australia's regulator guidance.

Where local rules affect the workflow

SafeWork NSW directs employers to call immediately for a serious injury, illness, dangerous incident or death, and recommends keeping a register of issues and incidents. NSW and Victorian practices also require rapid internal escalation and written follow-up within 48 hours in relevant circumstances. Victoria requires records to be retained for at least five years.

Set the jurisdiction in the incident system, keep regulator contacts current and name the notification owner on the roster or emergency plan. Site managers can preserve evidence, but the nominated PCBU representative should confirm the threshold and complete the regulator contact.

Why Incidents Go Unreported and How to Fix It

A legally correct procedure can still fail if workers don't use it. Australian survey findings summarised by ClockOn's workplace incident reporting analysis report that 31% of incidents were unreported in the Australian data, compared with 25% unreported overall. Those figures are survey findings, not a complete measure of every Australian workplace, but they expose a practical weakness in many systems.

The reasons are familiar on a busy site. Workers fear blame, supervisors are under production pressure, minor injuries seem unimportant, and subcontractors aren't sure whether a near miss belongs in the principal contractor's system. A form that asks for fault before facts makes each of those barriers worse.

Design for the behaviour you need

Use a short initial capture process. The worker should be able to report the location, event, immediate harm and required assistance without writing an investigation report at the point of disruption. The supervisor then owns escalation and adds the operational detail.

• Remove blame language: Ask what happened, what task was underway and what controls were present. Don't begin with who caused the event.
• Define near misses: Give supervisors examples relevant to the site, such as a dropped load that misses a person or a reversing vehicle that enters a pedestrian path.
• Accept subcontractor reports: Use one route for employees, labour hire, visitors and contractors, then allocate ownership internally.
• Close the loop: Tell the person who reported the issue what action followed. Silence teaches workers that reporting has no value.
• Measure supervisor behaviour: Review delayed escalation, incomplete fields and unclosed actions at operational meetings.

The objective isn't to maximise form counts. It's to surface weak controls early, distinguish a genuine notifiable incident from an internal event, and make corrective action visible. The national harm context is substantial, with 188 workers dying from traumatic injuries in 2024 and 146,700 serious workers' compensation claims involving at least one week of working time lost in 2023–24, according to Safe Work Australia's latest key WHS statistics. A reporting culture can't prevent every event, but it gives management earlier information to act.

Documentation, Registers and Record Retention

The incident report is not the investigation. It is the controlled record of what was known, when it was known and what the organisation did next.

Capture the basics first: date and time, exact location, task, people involved, witnesses, injury or potential harm, plant and equipment, relevant SWMS, immediate controls, regulator contact and photographs. Add witness statements separately where possible. A witness should describe observations in their own words, with the statement dated and linked to the event.

A defensible record structure

Use a unique incident reference and keep the record in one controlled register. The register should allow authorised users to locate the original notification, attachments, regulator correspondence, investigation findings, corrective actions and close-out approval without relying on an individual manager's inbox.

Common failures include missing timestamps, overwritten statements, photographs without locations, and corrective actions that have no owner. Digital systems can reduce those failures by routing reports, preserving attachments and showing overdue actions, but automation doesn't replace judgement about notification.

Your document retention policy should address access control, version history, privacy and disposal approval. Keep health information restricted, separate factual records from opinions, and preserve the original submission when a later investigation adds detail.

Turning Reports into Prevention Actions

A report only earns its place when it changes work. After the immediate response, the H&S manager should identify the failed or missing control, assign an accountable owner and set a verification method. “Retrain the team” is rarely enough if the actual issue is poor guarding, an unrealistic SWMS or a contractor interface nobody owns.

Review events across sites by task, plant type, contractor, shift pattern and control failure. Look for repeated weak signals, such as the same isolation problem appearing in near misses, first-aid cases and formal incidents. Use that pattern to prioritise engineering controls, procurement changes, SWMS reviews and contractor performance discussions.

Close-out standard: An action isn't complete because someone uploaded a photograph. It's complete when a responsible manager verifies that the control works in the task where the failure occurred.

Present leadership with a short view of open actions, repeat events, overdue investigations and unresolved high-potential hazards. Link each decision to a named budget or operational owner. Tools such as Safety Space can provide digital incident forms, photo uploads, workflow routing and multi-site oversight, including workflows designed to identify potentially notifiable incidents for escalation.

Make the incident reporting procedure part of the broader WHS system. Connect it to hazard registers, SWMS review triggers, contractor onboarding and management inspections. That is how a single event becomes a prevention control rather than a closed file.

Safety Space provides digital tools for capturing, investigating and tracking incidents, near misses and hazards across sites and subcontractor teams. Visit Safety Space to review the platform and arrange a practical H&S consultation for your organisation.