Incident Report vs Incident Register: What Is the Difference?

Quick answer: An incident report is the detailed record of a single incident — what happened, the investigation, and the corrective actions. An incident register is the ongoing log that lists every incident over time, enabling trend analysis and demonstrating compliance. Both documents are required. They serve different purposes and work together.

Last reviewed: June 2026 by the BlueSafe Technical Team. Reflects current Model WHS Regulations.

Why This Difference Matters

Walk into almost any SafeWork audit or WHS inspection and the auditor will ask for two things: your incident reports and your incident register. Many businesses have one but not the other — or they confuse the two entirely.

An incident report and an incident register are related but distinct documents. Mixing them up, or treating one as a substitute for the other, can leave significant gaps in your WHS system — gaps that become obvious the moment something goes wrong or a regulator comes knocking.

This guide explains what each document is, what it must contain, and how the two work together to support a compliant and functional incident management system.

What Is an Incident Report?

An incident report is a formal, detailed record of a single workplace incident. It is completed at the time of the incident — or as soon as practicable afterwards — and captures everything relevant to understanding what happened and preventing a recurrence.

A well-completed incident report typically includes:

• Incident details — date, time, location, and type of incident (injury, near miss, dangerous incident, property damage, illness).
• Persons involved — names and roles of injured persons, witnesses, and supervisors present.
• Description of the incident — a factual account of what happened, in sequence.
• Injury or damage details — the nature and extent of any injury, illness, or property damage.
• Immediate actions taken — first aid given, area made safe, notifications made.
• Investigation findings — root causes, contributing factors, and hazards identified.
• Corrective and preventive actions — what will be done to prevent a recurrence, by whom, and by when.
• Sign-off — signatures from the supervisor, health and safety representative, and/or manager.

The incident report is a living investigation record. It may be updated as the investigation progresses and as corrective actions are completed.

When is an incident report required?

An incident report should be completed for every workplace incident, including:

• Injuries — any work-related injury that requires medical treatment, results in time off work, or affects the worker's capacity.
• Near misses — events that did not cause harm but could have.
• Dangerous incidents — events defined under WHS legislation that must be reported to the regulator (e.g. an uncontrolled escape of a hazardous substance, a collapse of a structure).
• Property damage — damage to plant, equipment, or property resulting from a workplace event.
• Occupational illnesses — work-related health conditions.

For notifiable incidents — which include deaths, serious injuries or illnesses, and dangerous incidents — you must also notify your state or territory WHS regulator immediately.

What Is an Incident Register?

An incident register is an ongoing, summarised log of all workplace incidents recorded over time. Where the incident report gives you the depth — the full story of a single event — the register gives you the breadth: a bird's-eye view of everything that has happened across your workplace.

The register is typically maintained as a table or spreadsheet, with a new row added each time an incident occurs.

A standard incident register entry includes:

• Date and time of the incident.
• Incident reference number (linked to the full incident report).
• Type of incident (injury, near miss, dangerous incident, property damage, illness).
• Location where the incident occurred.
• Person(s) involved — name or identifier.
• Brief description — a one or two sentence summary.
• Outcome — lost time, medical treatment, first aid only, nil injury.
• Notifiable? — whether the regulator was notified and on what date.
• Status — open, under investigation, closed.

For more detail on what an incident register should contain and how to set one up, see our guide: What Is an Incident Register?

Why regulators and auditors want to see it

The incident register demonstrates to a regulator, auditor, or insurer that your business:

• Consistently records all incidents — not just the serious ones.
• Monitors trends in hazard types, locations, and contributing factors.
• Takes a systematic approach to incident management rather than reacting to each event in isolation.
• Meets its record-keeping obligations under WHS legislation.

A business that produces a thick folder of individual incident reports but has no register is harder for an auditor to assess quickly. A business that maintains a well-kept register alongside its reports demonstrates a mature WHS system.

How They Work Together

The incident report and the incident register are two halves of the same system.

Think of it this way:

• The incident report is the file.
• The incident register is the filing index.

Each time an incident occurs, you complete a report (the full investigation record) and add a summary entry to your register (so the event is captured in your overall log). The register entry links back to the report — usually via a reference number — so you can pull the full detail when you need it.

This two-document approach gives you:

1. Accountability at the individual incident level — every event has a thorough, documented investigation.
2. Visibility at the organisational level — patterns become apparent when you can see all incidents in one view.
3. Compliance evidence — both documents together satisfy record-keeping and investigation obligations under WHS legislation.

Using the register to identify trends

One of the most valuable uses of an incident register is spotting patterns that no single report would reveal. For example:

• Multiple near misses in the same location may indicate a persistent environmental hazard.
• A cluster of manual handling injuries across a short period may indicate a process change has introduced new risks.
• A rising number of first-aid-only incidents may be an early warning sign before a serious injury occurs.

These patterns are invisible if you only ever look at individual reports. The register is what makes them visible. For more on using data from your register to drive preventive action, see our guide: Incident Reporting Best Practices

Common Mistakes to Avoid

Keeping a register but skipping detailed reports

Some businesses maintain a register with brief entries but do not complete full investigation reports. This means the root cause is never properly documented, corrective actions may not be assigned or tracked, and if a similar incident recurs, there is no investigation record to draw on. Insurers and regulators will also expect to see the full report, not just a register entry.

Completing reports but never entering them in the register

Other businesses produce thorough reports but keep them in a drawer without summarising them in a register. Without the register, trend analysis is impossible and there is no quick way to demonstrate the volume and nature of incidents to an auditor.

Only recording notifiable incidents

The legal obligation to notify the regulator applies to notifiable incidents — but your own internal record-keeping should capture everything, including near misses and first-aid-only incidents. Near misses in particular are one of the best early-warning signals available to a WHS system.

Closing records before corrective actions are verified

An incident report should not be marked as closed until all corrective actions have been completed and verified. Leaving actions open in the register until they are done — rather than closing the record the day after the incident — keeps the system honest and drives follow-through.

State and Territory Variations

The information on this page is based on the Model WHS Regulations published by Safe Work Australia, which have been adopted (with minor variations) by most states and territories.

Always verify requirements with your state or territory regulator. Local codes of practice and guidance may impose additional obligations.

Related guides

• What Is an Incident Register?
• Incident Reporting Best Practices

Frequently asked questions

What is the difference between an incident report and an incident register?

An incident report is a detailed document about a single workplace incident — it captures what happened, the investigation findings, and the corrective actions taken. An incident register is a running log that records a summary of every incident over time. You need both: the report captures the detail; the register captures the pattern.

Is an incident register a legal requirement in Australia?

Yes. Under the Model WHS Regulations and equivalent state legislation, PCBUs are required to keep records of notifiable incidents and workplace injuries. Most regulators and auditors expect a maintained incident register as evidence that incidents are being tracked and reviewed systematically.

Who is responsible for completing an incident report?

The PCBU holds the primary duty, but in practice the task is usually delegated to the supervisor or health and safety representative at the time of the incident. The injured person, witnesses, and the investigating officer may all contribute to completing the report.

How long do I need to keep incident records in Australia?

Under the Model WHS Regulations, records of notifiable incidents must be kept for at least five years from the date the incident occurred. Many businesses keep all incident records for this minimum period as a matter of policy. Check your state or territory regulator for any additional requirements.

How BlueSafe Helps

Building incident reporting and register systems from scratch is time-consuming, and many businesses either delay the work or implement something that does not hold up under scrutiny.

BlueSafe provides ready-to-use incident management tools that you can deploy across your business immediately. Our platform is designed to:

• Align with Australian WHS legislation and regulator expectations.
• Use plain-language forms that workers and supervisors can complete without WHS expertise.
• Automatically feed incident summaries into a centralised register.
• Flag notifiable incidents and prompt the correct notifications.
• Give management a real-time view of open actions and emerging trends.

Understanding the difference between an incident report and an incident register — and implementing both — is one of the clearest signs of a WHS system that actually works.

This article provides general information about WHS documentation practices in Australia. It does not constitute legal advice. Requirements vary by jurisdiction and industry. Always consult your state or territory WHS regulator or a qualified WHS professional for advice specific to your situation.