48 Hour Deadline: Construction Incident Reporting for Supervisors

Supervisor and inspector at cordoned construction scene

Call 000 if anyone’s life is at risk, secure the scene, and give first aid. Notify your WHS regulator immediately by phone if the incident is notifiable, then follow up with a written report within 48 hours. Everything else, including the investigation and paperwork, comes after those steps are locked in.

TL;DR:

  • Immediate notification by phone is mandatory within hours for all notifiable incidents, followed by a written report within 48 hours to ensure compliance.
  • Accurate incident documentation requires precise timestamps, labeled photos, and witness details to support investigation and regulatory review.
  • Root cause analysis must extend beyond worker error by questioning systemic factors like scheduling, maintenance, and supervision to prevent recurrence.
  • Preserving the scene until inspector approval is essential, with documented reasons and directions needed if disturbance becomes necessary for safety or health reasons.
  • Maintaining a centralized incident register with all reports, photos, and corrective actions over at least five years helps demonstrate a pattern of proper incident management during audits.

Table of Contents

Immediate actions: your on-site incident checklist

The first ten minutes decide whether your report holds up later. Work through these steps in order, not all at once.

  1. Call 000 if there’s any threat to life, then render first aid.
  2. Isolate the hazard so nobody else gets hurt (cut power, cordon the area, stop plant movement).
  3. Assign a notifier to contact the regulator, an investigator to start gathering facts, and a communications lead to handle site enquiries.
  4. Secure the scene without blocking emergency access.
  5. Capture evidence: photos from multiple angles, timestamps, and the names of anyone who witnessed what happened.

Splitting roles matters because one person trying to do all three jobs at once usually does none of them well.

  • Photograph before anything gets moved or cleaned up.
  • Record exact times: when the incident happened, when it was noticed, when help arrived.
  • Write down witness names and contact details on the spot, not from memory later.

Pro Tip: Keep a laminated card in the site office with the regulator’s phone number and your company’s internal notifier chain. In the panic of a real incident, nobody wants to hunt for a number.

Which incidents count as notifiable, and who you call

A notifiable incident is a death, a serious injury or illness, or a dangerous incident that exposes someone to a serious risk, even if nobody got hurt. On a construction site, that covers a structural collapse, a failure of earth-moving plant or a crane, a fall from height, an electric shock, or an uncontrolled chemical or fuel spill. Safe Work Australia confirms that as a person conducting a business or undertaking, you must notify your relevant WHS regulator the moment you become aware of one.

From 1 July 2024, some jurisdictions expanded the list of plant types that automatically trigger notification, so it pays to check your state’s current schedule rather than assume last year’s list still applies.

The timeline that matters: notify by phone immediately (the fastest means available), then lodge the written report within 48 hours. WorkSafe Victoria and Comcare both apply this same two-step rule for state and Commonwealth workplaces respectively.

  • State and territory regulators handle most private construction sites.
  • Comcare covers Commonwealth employers and licensees.
  • Record the reference number given during the phone call, it’s your proof of timely notification.

Filling out the written incident report correctly

Regulators reject vague reports, not honest ones. Fill in what you know, mark the rest “unknown” rather than guessing, and let the investigation catch up later.

Your written report needs these fields, at minimum:

  • Reporter name, role, and contact details
  • Site address and location within the site
  • Date and exact time of the incident
  • Names and roles of anyone affected
  • Nature and extent of any injury
  • Plant or equipment involved, including make and model if relevant
  • Immediate actions taken (first aid, isolation, evacuation)
  • Witness names and statements, written in their own words rather than paraphrased
  • Photos and diagrams, labelled with date, time, and a brief description
Field Why it matters Common mistake
Time of incident vs time reported Regulators check the gap for notification compliance Estimating instead of checking logs or timestamps
Witness statements Provides independent corroboration Summarising in the investigator’s own words
Photo labelling Links evidence to the written record Generic filenames like “IMG_XXXX”
Plant/equipment ID Needed if a defect contributed Leaving the make/model blank

Name your photo files with the date, site, and a short description (2026-03-14_SiteA_CraneBoom01.jpg) so they line up with the written report without extra explanation. Every entry should also feed into your master incident register, which links the written notification to whatever corrective actions come out of the investigation.

Investigating with root cause analysis, not blame

Stopping at “the worker made a mistake” is the single most common investigative failure. It closes the file without fixing anything, and the same incident happens again in six months. The OHSBOK investigations chapter sets out a four-step model that avoids this trap:

  1. Secure the scene and confirm first aid has been given.
  2. Gather evidence: photos, statements, equipment logs, maintenance records.
  3. Analyse with root cause analysis, asking “why” repeatedly until you reach a systemic cause, not just the last action before the incident.
  4. Act and record: assign corrective actions to named owners with due dates, then log them.

Push your questioning past the individual and into the system: was the task properly scheduled, was the equipment maintained on time, was supervision adequate for the crew size? Near-misses deserve the same four steps as an actual injury, since they’re often the only warning you get before something worse happens.

Pro Tip: If your RCA keeps landing on “worker error” as the final answer, you haven’t finished the analysis. Keep asking why until you hit a process, not a person.

Iterative root cause analysis process illustration

Preserving the scene and dealing with inspectors

You’re required to preserve an incident site, including the immediate surroundings and any plant or equipment involved, until an inspector arrives or gives other directions. That duty holds even when work pressure makes it tempting to clear the area and get moving again.

There are narrow exceptions. WorkSafe Victoria’s guidance permits disturbing the scene to protect someone’s health or safety, to assist an injured person, or to make the area safe from further harm.

  • Contact the regulator’s hotline if you need to disturb the scene for a reason beyond those exceptions.
  • Record any verbal direction given by an inspector, along with their name and the reference number.
  • Photograph the scene before making any changes, even when the disturbance is justified.
  • Log the time and reason for every change made to the site.

Building a master incident register that holds up

A single written report proves compliance for one incident. A properly kept register proves your business has a pattern of doing this properly, which matters at audit time and when a regulator asks for history.

Store the written notification, all photos, investigation notes, corrective actions, and the regulator’s reference number together for each entry. WorkSafe Victoria requires copies of written notifications to be kept for at least five years, and that’s a sensible floor even where your own state’s rule differs slightly.

  • Structure your register with columns for date, site, incident type, injury severity, notifiable status, corrective action owner, and closure date.
  • Restrict access to sensitive medical or personal details to the people who genuinely need them.
  • Review the register quarterly to spot repeat incident types across sites, not just within one project.

A ready-to-use incident report template

Copy this structure straight onto your site tablet or a printed pad. It splits into what goes to the regulator and what stays in your internal register.

  • Fields marked “Yes” for the regulator match what your state’s notification form asks for.
  • Digital capture through a tablet or phone means photos and GPS location attach automatically, cutting down the gap between the incident and a complete record.

Practitioner perspective: speed versus thoroughness

The tension in every incident report is between getting the notification out fast and getting it right. Stick to facts, skip speculation about blame, and let the corrective action process do the heavy lifting. Digital capture tools close that gap without sacrificing accuracy.

— Mike

Report incidents faster without losing the paper trail

There’s a real cost to chasing paper forms and photo files across separate folders while a regulator’s 48 hour clock is running. Supervisors can capture an incident record on-site in minutes: photos, GPS location through the OBD port, and the key details land straight into a master register instead of scattered text messages and half-filled forms.

Dirtchamp

Because the record ties back to the same platform tracking trucks, machinery, and project records, there’s no separate system to maintain for compliance. Corrective actions get logged against the same entry, so nothing falls through when the file gets reviewed later. If your current process for incident reporting construction still runs on paper dockets and a filing cabinet, it’s worth seeing how Dirtchamp handles it instead. Explore software options that help incidents move quickly from the field into a compliant record.

Sources