WHS Incident Report Form: A 2026 Guide

A supervisor has an hour to document a serious event, preserve the scene, brief management, and work out whether the regulator must be notified. The form on the shared drive asks for a description, injury details, and corrective action. It looks complete until someone asks for the exact treatment, the PCBU contact details, the notification pathway, or the evidence supporting the account.

A WHS incident report form must do more than record an internal H&S note. It must help the PCBU make a sound notification decision, capture the information a regulator will request, and preserve an auditable record for investigation and follow-up.

Table of Contents

• What a Regulator-Ready WHS Incident Report Form Actually Does
  • Why generic templates fail
• Required Fields on a WHS Incident Report Form
  • Start with the event and the people
  • Record treatment and the PCBU
  • Worked example
• Notifiable Incident Categories and Reporting Timeframes
  • State and territory notification channels and timeframes
• Preserving the Scene and Collecting Evidence
  • What to collect
  • Managing a necessary restart
• Digital Tools and How They Change Incident Reporting
  • The operational difference
• Investigation, Corrective Actions, and Regulator Follow-Up
  • Turn findings into owned actions
• Checklist for Auditing Your Current Incident Report Form

What a Regulator-Ready WHS Incident Report Form Actually Does

A construction supervisor in Western Australia is told that a worker has fallen from scaffolding. While the worker receives medical attention, the supervisor isolates the area, contacts the site manager, and opens the incident form. The template contains three boxes: what happened, who was injured, and what action was taken.

Those boxes leave the supervisor without the information needed for a defensible notification decision. The record must identify the precise location and time, everyone involved, treatment provided, the condition of the site, and the incident category. It should also guide the PCBU toward direct notification to the relevant regulator before a statutory deadline passes.

Under the model WHS framework, a PCBU must notify the regulator immediately after becoming aware of a notifiable incident. If the regulator requests written notice, the PCBU must provide it within 48 hours and keep a record of each notifiable incident for at least 5 years. These duties appear in section 38 of the model WHS Act.

Practical rule: Treat the form as the first controlled record in a regulator notification, not as a narrative written for internal filing.

Why generic templates fail

Generic forms depend heavily on free text. They may not prompt the reporter to classify a dangerous incident, record an extended absence, capture hospital details, or distinguish a near miss from an injury event. Combining immediate containment with later corrective action also obscures what happened at the scene and what the business decided afterward.

A regulator-ready form applies conditional logic. The questions change when the event involves a death, serious injury or illness, dangerous incident, violent incident, work-related suicide or attempted suicide, or extended absence. The form should then point the reporter to the applicable state or territory notification process, because the pathway and required details depend on jurisdiction.

The form is also a decision record. It should show the facts considered, the notification decision, who made it, when it was made, and what evidence supports the account. That structure reduces the need to reconstruct events from emails, text messages, and memory.

Could the record withstand questions from SafeWork WA, WorkSafe Victoria, or SafeWork NSW? The workplace incident report form should help answer that question by keeping facts, decisions, evidence, and follow-up in one controlled record.

Required Fields on a WHS Incident Report Form

A regulator-aligned form starts with the operational facts, not the theory about why the event occurred. SafeWork NSW identifies the information the regulator will ask for, including the date, time and location, the injured person's details, injury and treatment information, PCBU details, and the immediate and follow-up actions taken to make the site safe and prevent recurrence. See the SafeWork NSW notifiable incident guidance for that data set.

Start with the event and the people

Capture the date, time, location, work area, task, and equipment involved. “Forklift near miss in production” isn't sufficient. A useful entry identifies the aisle, the loading activity, the forklift, the pedestrian route, and the point at which the two paths conflicted.

The injured or exposed person's record should include their name, date of birth, contact details, and relationship to the business. That relationship matters where the person is a worker, contractor, labour-hire worker, visitor, or another person affected by the undertaking. Record witnesses separately, with their names, roles, and contact details, so the investigation team can distinguish direct observations from later assumptions.

The description should remain factual and chronological. Record what each person was doing, what was observed, what happened, and what occurred immediately afterwards. Don't turn the initial report into a root-cause conclusion.

Record treatment and the PCBU

The injury section needs the nature of the injury, first aid or other treatment, whether the person attended hospital, and the hospital details where relevant. If there was no injury, the form should still record the potential consequence and classify the event as a near miss or dangerous incident where appropriate.

The PCBU section should identify the business, workplace, contact person, telephone and email details, and the person making the notification. A regulator must be able to identify the duty holder and contact the person who can answer questions.

Worked example

A forklift reverses from a loading area while a pedestrian enters the marked route. The pedestrian steps back before contact. No injury occurs.

A strong form would record:

• Incident details: The date, time, loading-area location, aisle, task, and forklift identification.
• People involved: The pedestrian's name, role and business relationship, plus the operator's details.
• Witnesses: Names, roles and contact details of people who saw the movement.
• Description: A factual account of the vehicle movement, pedestrian position, warning systems and separation controls.
• Treatment and impact: No treatment, no injury, and the potential for a vehicle-person collision.
• PCBU details: The manufacturing business and responsible contact.
• Immediate action: Stop the task, isolate the route, check the forklift and review the traffic arrangement.
• Follow-up action: Assign an owner to review the traffic management plan, operator controls, pedestrian segregation and verification of completion.

Conditional questions should then determine whether the event involves a dangerous incident, a violent incident, work-related suicide or attempted suicide, or an absence from work of 15 or more calendar days. Safe Work Australia's incident notification guidance explains why the form must capture more than physical injuries.

Notifiable Incident Categories and Reporting Timeframes

Triage must occur before the form is closed. Under the model WHS framework, the core categories are death, serious injury or illness, and a dangerous incident that exposes a person to serious risk, even when nobody is injured. The notification scope can also include violent incidents such as sexual assault, work-related suicide and attempted suicide, and worker absences of 15 or more calendar days. The incident reporting guidance for workers confirms that a dangerous incident may be notifiable without an injury.

A regulator-ready form should use conditional questions to test each category, rather than relying on the person completing the form to recognise the legal threshold. If a response indicates a possible notifiable event, the form should identify who must notify, which regulator applies, and whether the notification has been completed.

Notification must be made immediately by the fastest available method to the relevant state, territory or Commonwealth WHS regulator. Written lodgement may also be required through the local approved form or system. The PCBU must retain the record for at least 5 years, as required by section 38 of the WHS Act.

State and territory notification channels and timeframes

SafeWork SA states that non-life-threatening injuries or issues can be reported by phone, form or email, with written lodgement as soon as reasonably practicable and within 48 hours. SafeWork NSW provides WHS Form 10 for incident and injury reporting. WorkSafe Victoria requires an Incident Notification ID before the incident notification form is completed.

The notification channel is local. There isn't one national submission portal that replaces each state or territory process.

Safe Work Australia states that notifications must go directly to the relevant regulator, and employers should check with the local regulator before changing notification systems or reporting practices. A national company can standardise its internal form, but it should retain a state-specific submission prompt and a recorded confirmation of lodgement.

Preserving the Scene and Collecting Evidence

After a notifiable incident, the PCBU must preserve the incident site until an inspector arrives or directs otherwise. That duty doesn't prevent the business from helping an injured person, removing a deceased person, making the site safe, or assisting with a police investigation. The practical balance is described in Safe Work Australia's incident reporting guidance.

A manufacturing line illustrates the conflict. A guard fails and a worker suffers a crush injury. First aid and emergency response take priority. The line is then isolated, access is controlled, and the equipment position is left undisturbed unless movement is necessary to protect people or prevent further harm.

What to collect

In the first response period, preserve and log:

• Equipment position: Photograph the guard, controls, product, tools and surrounding area if it is safe to do so.
• Time records: Capture CCTV footage and its timestamps before routine recording overwrites it.
• Witness accounts: Take separate statements while recollections are fresh, without directing people towards a preferred explanation.
• Work instructions: Secure the relevant SWMS, task instructions, risk assessment and permits.
• Pre-start records: Retain the day's equipment checks, pre-start safety checks and defect reports.
• Access records: Record who entered the area, who isolated the line and who authorised any change.

Don't edit the original photograph or overwrite the first witness statement. Store the original file, identify the person who collected it, and record when and where it was captured.

Managing a necessary restart

Production may need to restart for reasons unrelated to the incident. That decision creates scrutiny if the scene changes. Document who made the decision, why the restart was necessary, what areas or equipment remained isolated, what evidence was collected first, and what temporary controls were put in place.

A regulator will usually be more interested in the decision trail than in a polished retrospective explanation. If the line moved, say so. If a component was removed to make the machine safe, record who removed it, where it went, and whether photographs were taken before removal.

Digital Tools and How They Change Incident Reporting

Paper and spreadsheet processes can record an event, but they often separate the report from the response. A supervisor completes a paper near-miss form on a residential build, takes photographs on a phone, emails a scan to the H&S manager, and waits for someone to decide whether the event needs regulator notification. The evidence, classification and escalation trail sit in different places.

A digital form can ask the next question based on the incident class. It can require injury and treatment fields for an injury event, prompt for potential consequence on a dangerous incident, attach timestamped photographs, and route the record to the people responsible for notification and corrective action. Those controls reduce omission risk, but they don't replace the PCBU's judgement or the obligation to notify the correct regulator.

The operational difference

The trade-off is governance. A digital platform needs sensible permissions, offline access where sites have poor connectivity, a clear approval process, and a way to preserve the original report. Automation that sends the wrong notification or locks incomplete information can create a new failure mode.

Safety Space is one example of a platform that combines customisable forms, AI-assisted completion, multi-site visibility and subcontractor oversight. Its incident management software selection guidance is useful when comparing these controls against the needs of construction, manufacturing and industrial service operations.

Investigation, Corrective Actions, and Regulator Follow-Up

A submitted form is only the investigation's starting point. Investigators should test the initial account against photographs, CCTV, witness statements, SWMS documents, pre-start records, training and authorisation records, and the physical work area. The record must show what happened, while the investigation establishes why it happened.

Consider a dangerous incident involving work outside the controls described in the SWMS. The form should capture the event, people involved, immediate isolation and exposed risk. Investigators then examine why the SWMS was not followed, whether it matched the actual task, how supervisors checked the control, and whether production pressure or a design change influenced the work.

Turn findings into owned actions

Separate immediate corrective actions from preventive actions. Immediate actions may isolate equipment, repair a guard, change the work area or suspend a task. Preventive actions may involve reviewing the SWMS, consulting workers, verifying competency, changing the design, controlling procurement or revising supervision.

Every action needs an owner, due date, completion evidence and an effectiveness check. A closed status without evidence is not reliable close-out. During a visit, an inspector may compare the listed actions with site conditions, records and workers' understanding.

Choose an investigation method that fits the event. Five-whys analysis may suit a focused equipment failure. Fishbone analysis can help examine plant, people, process, environment and management factors. Both methods still require evidence, rather than assumptions.

A director or senior operational leader should review the final action set when the incident exposes a system weakness. The ICAM investigation template provides a structured way to connect evidence, contributing conditions and corrective actions.

Keep the complete record for at least 5 years under the model WHS requirement. A well-organised file also supports tender pre-qualification by showing how the business reports events, assigns actions and verifies that controls changed. For regulator readiness, retain the submitted notification, investigation record, action evidence and any follow-up correspondence together. This makes it easier to demonstrate that the business responded to the event and addressed the underlying risk.

Checklist for Auditing Your Current Incident Report Form

Test the form against a realistic handover. A supervisor completes it after an event, a manager decides whether notification is required, and an investigator later reconstructs what happened. The form should support each decision without relying on memory or a separate instruction sheet.

Score every item 0, 1 or 2: zero means absent, one means unclear or manual, and two means the field, rule and evidence are built into the workflow.

• Jurisdiction: Does the incident class route to the correct state or territory notification pathway, with the responsible decision-maker recorded?
• Conditional logic: Do follow-up questions appear when the event may involve regulator notification, scene preservation or serious harm?
• Decision trail: Does the form record who assessed the event, what information they relied on and when the decision was made?
• Evidence integrity: Can attachments retain timestamps, source details and links to the relevant person, plant or location?
• Handover: Can another manager identify outstanding actions, owners, due dates and verification evidence without contacting the original reporter?
• Retrieval: Can the business export a regulator-ready file containing the report, attachments, decisions and correspondence?

A low score in routing, conditional logic or decision traceability indicates a process risk, not merely a poor layout. Test the form with a recent near miss and a serious event, then compare the output with what a regulator would request.

Safety Space offers customisable digital H&S forms, AI-assisted completion, incident workflows and visibility across sites and subcontractors. Its workflow can connect regulator-relevant information with follow-up actions, while the business remains responsible for jurisdiction-specific review.