Incident Report for a Construction Site: What to Record and When to Notify

Two incidents happen on the same day. A subcontractor trips on a cable run and sprains their wrist. An excavator swings and nearly strikes a worker standing in the exclusion zone. One of these is almost certainly notifiable to WorkSafe. The other needs to be documented internally but probably doesn't trigger a statutory notification. The problem is, plenty of site managers aren't clear on which is which — and some don't know they're two separate duties in the first place.

Getting your incident report construction site process right means understanding that internal recording and external notification are different obligations, governed by different sections of the Health and Safety at Work Act 2015 (HSWA). You need to do both correctly, in the right order, on the right timelines.

What Belongs in a Construction Incident Report

Right after the scene is made safe and any injured person is receiving first aid — that's when the incident report starts. Not at the end of the shift. Not tomorrow morning. The reason is simple: scenes get disturbed, memories fade, and an incident report written two days later is nearly useless for investigation and likely to fail any audit.

HSWA 2015 doesn't prescribe a specific format for internal incident records, but the record needs to support investigation and satisfy the five-year retention duty under s57. In practice, a compliant record contains the following, in order:

Use this template:

INCIDENT RECORD — CONSTRUCTION SITE Date: Time: Location (area/chainage): Reporter name and role: Person(s) involved (name, employer, trade): Witnesses (name, contact): Plant, equipment or substances involved: Factual sequence of events (no blame, no inference): Injury/illness detail OR near-miss description: Treatment given and by whom: Immediate make-safe actions taken: Notifiability decision: YES / NO — reasoning: Photos taken: YES / NO — reference: Root cause and contributing factors: Corrective actions | Owner | Due date | Close-out date: Investigator name: Sign-off: Date:

Every one of those fields matters. The notifiability decision field is the one most templates leave out entirely — which is exactly how a notifiable event slips through unnotified, an offence in itself under HSWA s56.

how to structure your H&S incident register

Near Miss Report: Why These Matter as Much as Injuries

At the morning toolbox talk, someone mentions the crane load swung wide yesterday afternoon and nearly clipped the form workers below. Nothing hit anyone. No injury. A lot of sites would log that nowhere.

That's a significant gap. A near miss report captures events where harm didn't occur but easily could have — and under HSWA's risk-management framework, failing to investigate near-misses means you're missing the leading indicators before something serious happens. The hierarchy is straightforward: near-misses are the bottom of the iceberg; fatalities and serious injuries sit above the waterline.

In Australia, Safe Work Australia's approach to the model WHS legislation is consistent on this point: near-misses should be recorded internally even when they're not externally notifiable. The 2025 Model WHS Legislation Amendment also extended the categories of notifiable incidents — but note those changes only take effect once each jurisdiction adopts them into its own WHS laws, so check with your local regulator before assuming they apply to you.

For your incident register, near-misses should be recorded with the same rigour as injuries: factual sequence, plant or equipment involved, witnesses, root cause, corrective actions. What changes is the notifiability assessment — most near-misses won't clear the threshold, but you still need to record that you assessed it.

The most common failure auditors find isn't that a near-miss was assessed and found non-notifiable. It's that no one wrote anything down at all.

Recording vs Notifying: How to Tell Which Duty You're Dealing With

During a busy concrete pour, a penetration in the deck fails and a worker falls into the level below. The foreman's first instinct is to fill in the incident form. That's correct — but it's not the only thing that needs to happen in the next few minutes.

Under HSWA ss23–25, a notifiable event is a death, a notifiable injury or illness, or a notifiable incident (which includes unplanned or uncontrolled events with serious potential). The duty under s56 is to notify WorkSafe "as soon as possible after becoming aware" — in practice that means immediately, not at the end of the day. The 24/7 notification line is 0800 030 040.

Alongside notification, there's a separate duty to preserve the site. You cannot disturb the scene (other than to assist injured persons, make the area safe, or comply with a WorkSafe direction) until an inspector clears you to do so.

Here's the decision logic that should sit inside every notifiability field on your incident form:

NOTIFIABILITY DECISION TREE — HSWA 2015

Incident occurs
  │
  ├─ Death of any person? ──────────────────────────────► NOTIFIABLE (s23)
  │
  ├─ Serious injury or illness to a worker?
  │    (amputation, serious head injury, serious eye injury,
  │     serious burns, spinal injury, loss of bodily function,
  │     serious laceration, requires immediate in-patient
  │     treatment, acute illness from hazardous substance)
  │                  │
  │                  └─ YES ─────────────────────────────► NOTIFIABLE (s23)
  │
  ├─ Unplanned/uncontrolled event with potential to cause
  │  death or serious injury?
  │  (collapse of structure, plant, excavation;
  │   unintended explosion, fire, escape of substance)
  │                  │
  │                  └─ YES ─────────────────────────────► NOTIFIABLE (s24)
  │
  └─ None of the above
               │
               └─ Record internally only ──────────────► NOT notifiable
                  Include reasoning in notifiability field

If you're uncertain, notify. The cost of an unnecessary call to WorkSafe is zero. The cost of failing to notify is a criminal offence carrying financial penalties.

WorkSafe notification obligations explained

Why Incident Reports Fail Audits — and How to Fix Yours

When a principal's H&S representative reviews your SSSP or your incident register ahead of a prequalification audit — SiteWise or otherwise — incident records are one of the first things they scrutinise. The failures that come up repeatedly are predictable and entirely avoidable.

Here's what auditors actually find:

Failure	What's missing	Consequence
Notifiability not assessed	No field in the report; no reasoning recorded	Notifiable event goes unreported — offence under s56
Root cause = "worker wasn't careful"	No contributing factor analysis	Same incident recurs; demonstrates no learning
Corrective actions without owners or dates	Actions list has no accountability	Actions never closed out; audit finding
Report written days after the event	Scene disturbed, memory degraded	Report can't support investigation or defence
Near-misses not captured	Register shows only injuries	Leading indicators invisible; no preventive action
Blame-oriented language	Report attributes fault to individuals	Discourages future reporting across the team

The fix for most of these is structural: build a form that forces each field. If the notifiability field is mandatory, no one can submit the report without making a decision. If corrective actions require an owner name and a due date, they can't be left as a vague intention.

Corrective action close-out is where a lot of incident registers break down. Logging the action is step one. Verifying it's done and signing it off is what completes the cycle — and what a prequalification auditor will look for.

Step-by-Step: What to Do in the First Hour After an Incident

Whether you're a site manager or a foreman, the sequence below is what a compliant first-hour response looks like on a NZ construction site.

Step 1: Make the area safe and attend to any injured person — call an ambulance if needed, administer first aid, prevent access to the scene. This always comes first.

Step 2: Preserve the scene — if there's any chance this is a notifiable event, don't let anyone disturb the area beyond what's needed for safety and first aid. Take photos immediately, before anything is moved.

Step 3: Make your notifiability assessment — run through the decision logic above. If it meets any criterion under ss23–25, call WorkSafe on 0800 030 040 now. Don't wait to finish the paperwork.

Step 4: Collect information while it's fresh — names and contacts of witnesses, plant and equipment involved, exact location (chainage or area reference), what was happening immediately before the incident.

Step 5: Complete the incident report — use a form that includes every required field. Write the sequence of events factually and without blame. Record the notifiability decision and your reasoning regardless of the outcome.

Step 6: Begin root cause analysis — "worker wasn't paying attention" is not a root cause. Ask what conditions allowed this to occur: task planning, supervision, SWMS adequacy, plant condition, environmental factors.

Step 7: Assign corrective actions with owners and close-out dates — log these in the incident register and track them to completion. Sign off when each one is verified closed.

Frequently Asked Questions

Is a near-miss the same as an incident?

For recording purposes, yes — treat them the same. A near-miss is an unplanned event where harm didn't occur but could have. Internal recording obligations under HSWA's risk-management framework apply regardless of whether anyone was hurt. What differs is the notifiability assessment: most near-misses won't meet the ss23–25 threshold, but you still need to record that you assessed it and why you concluded it wasn't notifiable.

How soon do I have to write up an incident report?

As soon as possible after the scene is made safe. There's no specific statutory deadline for the internal record, but the practical rule is: if you haven't started before the end of the shift, you're already losing accuracy. For notifiable events, WorkSafe notification must happen as soon as you become aware — that's a statutory obligation under s56, not a paperwork exercise you can defer.

What's the difference between an incident and a notifiable event?

Every notifiable event is an incident, but not every incident is notifiable. All incidents should be recorded internally. Notifiable events — deaths, notifiable injuries or illnesses, and notifiable incidents as defined at ss23–25 — also trigger the external duty to notify WorkSafe under s56, and a separate duty to preserve the scene. Failing to notify a notifiable event is an offence carrying financial penalties.

How long do I need to keep incident records?

Under HSWA s57, records of notifiable events must be kept for at least five years from the date WorkSafe was notified. Best practice is to apply that same five-year retention period to your full incident register, including near-miss records. In Australia, the model WHS legislation has the same five-year retention period, running from the day notification was made.

Key Takeaways

Three things that will immediately improve your incident reporting process:

Separate the two duties in your head — internal recording applies to everything; notification to WorkSafe applies to the subset defined at ss23–25. Both are obligations. Neither replaces the other.
Put a notifiability decision field on every incident form — mandatory, with space for reasoning. If the field isn't there, the assessment doesn't get made.
Assign corrective actions with a named owner and a close-out date — an action without an owner is a wish. Your incident register needs to show completed close-outs, not open lists.

For the related obligations around what your SSSP needs to say about incident management and investigation, see SSSP incident management requirements NZ.

Incident Report Construction Site: What to Record and When to Notify