Quick answer: An incident management procedure is the documented process a business follows when something goes wrong at work — from the immediate response through to investigation, corrective action, and review. It makes sure nothing is missed, records are complete, and the same incident is less likely to happen again.
Last reviewed: June 2026 by the BlueSafe Technical Team. Reflects current Model WHS Act and Model WHS Regulations as adopted across Australian jurisdictions.
When a workplace incident happens, people rarely have time to think through what comes next. A clear incident management procedure removes that uncertainty. It tells everyone — from the worker on site to the manager in the office — exactly what steps to follow, in what order, and why each step matters.
What is an incident management procedure?
An incident management procedure is a written document that defines how a business responds to workplace incidents. It covers every stage of the process: making the area safe, providing first aid, reporting the incident up the chain of command, recording it in the incident register, notifying the regulator if required, investigating the root cause, implementing corrective actions, and reviewing whether those actions worked.
The procedure applies to all types of workplace incidents — injuries, illnesses, near misses, dangerous occurrences, and property damage. Near misses deserve as much attention as actual injuries because they share the same causes. Investigating a near miss before someone is hurt is always better than investigating after.
A well-written procedure also defines what counts as an incident, who is responsible at each step, and what records need to be created and kept. Without that structure, steps are missed, records are incomplete, and the same incident is more likely to recur.
Why does a business need an incident management procedure?
The WHS laws impose a number of specific obligations that only make sense as part of a structured procedure. Under the Model WHS Act and Regulations, a PCBU must:
- ensure injured persons receive first aid and emergency services promptly;
- preserve the incident site after a notifiable incident until the regulator gives clearance or 24 hours have passed, whichever is earlier;
- notify the regulator immediately of a notifiable incident;
- keep records of incidents, investigations, and corrective actions;
- use incident information to improve risk controls.
Those obligations are impossible to meet consistently without a documented procedure. The procedure is also the clearest evidence a PCBU has that it takes due diligence seriously. If a regulator or court asks what the business does when an incident occurs, the procedure — and the records it generates — are the answer.
Beyond compliance, the procedure protects workers. Most repeat incidents share root causes with earlier incidents that were never properly investigated. A rigorous procedure interrupts that cycle.
The steps in an incident management procedure
A complete incident management procedure covers the following steps in sequence.
Step 1 — Respond and make safe
The first priority is the safety and welfare of anyone involved. This means:
- calling emergency services if required;
- providing first aid within the limits of the responder's training;
- securing the area to prevent further harm to workers, bystanders, or emergency responders;
- not disturbing the incident site any more than necessary to assist injured persons or prevent further injury.
The duty to preserve the site is a legal requirement for notifiable incidents. Workers should be trained not to clean up or move equipment until the supervisor confirms the site can be disturbed.
Step 2 — Report the incident internally
As soon as the immediate response is under control, the incident must be reported to a supervisor or manager. The business should define who must be notified and within what timeframe. For serious incidents this should happen immediately. For minor incidents and near misses, it should happen before the end of the shift.
Internal reporting starts the formal process. Without it, incidents are lost to memory, records are never created, and investigations never happen.
Step 3 — Record in the incident register
Every incident — including near misses — must be entered in the incident register. The register should capture:
- the date, time, and location;
- the name and role of the person involved;
- a factual description of what happened;
- the type and severity of any injury, illness, or property damage;
- the immediate actions taken;
- the name of the person completing the record;
- a unique reference number linking the entry to any subsequent investigation.
The incident register is a mandatory record under WHS regulations. It must be maintained and stored securely for the required retention period, which varies by jurisdiction but is typically five years.
Step 4 — Notify the regulator if the incident is notifiable
Not every incident requires regulator notification. But when an incident meets the definition of a notifiable incident — a death, serious injury or illness, or dangerous incident as defined in the Model WHS Act — the PCBU must notify the regulator immediately by phone or in person, and then follow up in writing within 48 hours.
A written notification must include: the business details, the date, time, and location of the incident, a description of what happened, the nature of any injury or illness, and the names of any persons involved.
The regulator may direct the business to preserve the incident site until an inspector attends. Failing to notify, or disturbing the site without authorisation, is a serious offence. See the related guide on reporting notifiable incidents for a detailed breakdown of what qualifies and how to notify each regulator.
Step 5 — Investigate the root cause
The investigation is the most important step for prevention. The goal is not to assign blame but to understand why the incident happened — what conditions, behaviours, system failures, or control gaps allowed it to occur.
A thorough investigation:
- interviews the people involved and any witnesses;
- inspects the physical environment and any equipment;
- reviews relevant procedures, risk assessments, and training records;
- identifies immediate causes (the unsafe act or condition directly linked to the incident) and root causes (the underlying system failures that allowed those conditions to exist);
- considers contributing factors such as workload, supervision, fatigue, or inadequate training.
The depth of the investigation should reflect the severity of the incident or the near miss potential. A minor cut from a slipping knife and a hand fracture from a machine nip point both deserve investigation, but the scope will differ. See the related guide on WHS incident investigation for a step-by-step approach.
Step 6 — Implement corrective actions
The investigation produces findings. Those findings should lead to specific, practical corrective actions that address the root causes — not just the immediate cause.
For example, if an investigation finds that a worker was injured because a guard had been removed and the procedure for checking guards before startup was not being followed, the corrective actions might include: replacing and securing the guard, revising the startup checklist, retraining the crew, and adding guard integrity to the supervisor's pre-start inspection.
Each corrective action should be assigned to a responsible person with a target completion date.
Step 7 — Record corrective actions and track completion
Every corrective action identified in an investigation must be entered in the corrective action register. This register is separate from the incident register. It tracks:
- the reference number linking the action to the incident investigation;
- a description of the action;
- the responsible person;
- the target completion date;
- the actual completion date;
- evidence that the action was implemented;
- a verification check confirming the action has been effective.
The corrective action register closes the loop. Without it, actions are agreed in meetings but never confirmed as done. The register makes accountability visible and creates a record that due diligence was followed through to the end.
Step 8 — Review and communicate learnings
After corrective actions are implemented, the business should review whether they have been effective. Did the control actually reduce the risk? Has the incident or a similar incident recurred?
Learnings from incidents should also be shared with workers, particularly those in similar roles or locations. This can happen through toolbox talks, updated procedures, or revised training. The goal is to prevent the same type of incident from happening elsewhere in the business.
How the incident register and corrective action register work together
The incident register and corrective action register are separate documents, but they must be linked. When an incident is recorded in the incident register, the reference number should be carried forward to the investigation report and then to any corrective actions in the corrective action register.
This creates a connected paper trail: incident → investigation → corrective action → verification. That trail is what a regulator or court examines when they want to know whether a business has genuinely acted on a safety problem.
Both registers should be reviewed regularly — not only when an incident triggers a new entry. Reviewing the incident register monthly can reveal patterns that would not be obvious from a single event. A cluster of near misses in one area, or a recurring type of injury, is a signal that a risk control needs attention before a serious incident occurs.
State and territory variations
The information on this page is based on the Model WHS Act and Model WHS Regulations as adopted across most Australian jurisdictions.
| Jurisdiction | Regulator | Key notes |
|---|---|---|
| NSW | SafeWork NSW | Follows Model WHS Act and Regulations. Notifiable incidents must be reported to SafeWork NSW immediately |
| VIC | WorkSafe Victoria | Uses the OHS Act 2004. Notifiable incidents are reported to WorkSafe Victoria. Definitions of notifiable incidents differ slightly from the Model Act |
| QLD | Workplace Health and Safety Queensland | Follows Model WHS Regulations |
| SA | SafeWork SA | Follows Model WHS Regulations |
| WA | WorkSafe Western Australia | Adopted Model WHS Act from March 2022. Notifiable incidents reported to WorkSafe WA |
| TAS | WorkSafe Tasmania | Follows Model WHS Regulations |
| ACT | WorkSafe ACT | Follows Model WHS Regulations |
| NT | NT WorkSafe | Follows Model WHS Regulations |
Always verify current notification requirements with your state or territory regulator, as thresholds and processes may differ from the model framework.
Related guides
Frequently asked questions
What is an incident management procedure?
An incident management procedure is the documented process a business follows when a workplace incident occurs — from the immediate response through to investigation, corrective action, and review.
What incidents must be reported to the regulator?
Deaths, serious injuries or illnesses, and dangerous incidents as defined in the Model WHS Act must be reported to the regulator immediately, and confirmed in writing within 48 hours.
What is an incident register?
An incident register is a log of every workplace incident and near miss. It records the details of each event and links to any investigation or corrective action taken.
How does a corrective action register link to incident management?
After an investigation identifies root causes, the corrective actions are recorded in the corrective action register, which tracks responsibility, completion dates, and verification that each action worked.
Get the right tools for incident management
A clear procedure only works when it is backed by the right templates and registers. BlueSafe's incident management tools give you the incident register, investigation forms, corrective action register, and written procedure your business needs to manage incidents consistently.
This article provides general WHS education information only. It is not legal advice. Requirements vary by jurisdiction and industry. Consult your state or territory regulator or a qualified WHS professional for advice specific to your circumstances.