Incident Report Template for Construction Sites

Safe Work Australia's annual worker fatality statistics consistently show construction as the industry with the highest volume of workplace deaths, driven by falls from height, contact with mobile plant, electrocution, and struck-by incidents involving falling objects or materials. Behind each of these fatalities is a sequence of failures that were usually preventable if earlier near-misses had been reported, investigated, and used to improve the control measures in place on the site. Incident reporting is the feedback loop that converts an event into a lesson.

The statutory framework for incident reporting sits in Part 3 of the WHS Act 2011 in the model jurisdictions and Part 5 of the Victorian OHS Act 2004. Section 35 of the WHS Act requires the PCBU to ensure that the regulator is notified immediately after becoming aware that a notifiable incident has occurred, and that the notification is confirmed in writing within 48 hours where the regulator requires it. Section 38 requires the PCBU to preserve the incident site until an inspector arrives or the regulator gives permission for it to be disturbed, subject to limited exceptions for saving life, preventing further injury, or making the site safe.

Failure to notify is an offence under section 38 carrying a maximum penalty of $10,000 for an individual and $50,000 for a body corporate for the immediate notification failure, with higher penalties if the notification failure is combined with other offences or if the incident involves a fatality. Failure to preserve the site carries equivalent penalties. These provisions exist because delayed or suppressed notifications allow evidence to be lost, injured workers to be moved before medical assessment, and site conditions to be altered before investigators can document them.

The connection to SWMS is direct. WHS Regulation 2025 section 300 requires the SWMS to be reviewed, and if necessary revised, after any incident or near-miss relating to the HRCW. The review asks whether the SWMS was being followed, whether the controls in the SWMS were adequate, and whether the document needs to be amended to address any gap revealed by the incident. Workers must then be re-briefed on the amended document before the work resumes. This ongoing review obligation is one of the reasons that SWMS are not static documents — they evolve through the life of the work in response to the events that occur on site.

Not every workplace incident is notifiable, and confusing minor events with notifiable ones wastes regulator time while missing notifiable ones exposes the PCBU to enforcement action. Section 35 of the WHS Act defines a notifiable incident as the death of a person, a serious injury or illness of a person, or a dangerous incident. Each of these categories has a specific definition and triggers the immediate notification obligation.

Death is the simplest category. Any death at a workplace, or any death caused by a workplace event even if the death occurs later in hospital, is notifiable. This includes deaths of workers, visitors, members of the public, and anyone else affected by the work. The reporting obligation is not limited to workers — a member of the public struck by falling debris from a construction site, or a passer-by injured by an uncontrolled excavator movement, is a notifiable death if the incident is caused by the workplace activity.

Serious injury or illness is defined in section 36 of the Act and includes amputation of any part of the body, serious head injury, serious eye injury, serious burn, separation of skin from underlying tissue (degloving or scalping), spinal injury, loss of a bodily function, and serious lacerations. It also includes any injury or illness requiring the person to be admitted to hospital as an inpatient (not just treated in the emergency department), and medical treatment within 48 hours of exposure to a substance. The hospital-admission criterion is a useful shortcut for field decisions — if the injured worker is admitted, the incident is notifiable, and the regulator must be called.

Dangerous incidents are defined in section 37 and cover events that exposed a person to a serious risk even if no one was actually injured. The list includes uncontrolled escape, spillage, or leakage of a substance; uncontrolled implosion, explosion, or fire; electric shock (other than from a working extra-low voltage supply); the fall or release from height of any plant, substance, or thing; damage to or collapse of a structure; the collapse or failure of an excavation or shoring; the inrush of water, mud, or gas in workings of an underground excavation or tunnel; and the interruption of the main system of ventilation in an underground excavation or tunnel. The common thread is serious risk: if the incident could reasonably have caused a death or serious injury, it is notifiable regardless of whether any person was harmed.

Victoria operates under OHS Act 2004 sections 37 to 39 and uses slightly different terminology (incident requiring notification rather than notifiable incident), but the substance is similar. Employers must notify WorkSafe Victoria immediately after a workplace incident that causes death, serious injury, or a range of specified dangerous occurrences. The notification number is 13 23 60, and written confirmation is required within 48 hours.

Immediate notification means as soon as the PCBU becomes aware of the incident — not at the end of the shift, not the next morning, and not after the internal investigation. The notification hotlines for each Australian jurisdiction are SafeWork NSW on 13 10 50, WorkSafe Victoria on 13 23 60, Workplace Health and Safety Queensland on 1300 362 128, WorkSafe WA on 1300 307 877, SafeWork SA on 1300 365 255, WorkSafe Tasmania on 1300 366 322, WorkSafe ACT on 13 22 81, and NT WorkSafe on 1800 019 115. The Commonwealth regulator Comcare is on 1300 366 979 for Commonwealth workplaces.

The person making the notification should be a senior site representative — typically the site supervisor, the WHS manager, or the principal contractor's nominated emergency contact. The call should be made from a location where the caller can speak clearly and take notes; the regulator will ask for the time, location, and nature of the incident, the names and conditions of any injured persons, the work activity being performed, and the PCBU's contact details. Have this information ready before the call so the notification does not become a conversation the caller struggles to navigate.

Site preservation starts immediately. The WHS Act section 38 requires the site to remain undisturbed until the inspector arrives or gives permission to resume work, with exceptions limited to saving life, preventing further injury, protecting the environment, or making the site safe. In practice this means cordoning off the incident area with barricades or tape, excluding non-essential personnel, preventing any movement of plant or materials involved in the incident, and not cleaning up debris or blood. Any modification of the site should be photographed before and after, with the reason documented.

First aid to injured persons is obviously permitted and takes priority over site preservation. Trained first aiders should apply immediate treatment, call 000 for ambulance support if needed, and stabilise the injured person until medical services arrive. The injured person's PPE, clothing, and any equipment they were using at the time should be preserved if possible, because investigators may want to examine these items as part of the investigation. Clothing and PPE should not be cleaned or washed until the investigator has had the opportunity to inspect them.

Other workers on site should be spoken to briefly to capture their immediate impressions while the event is fresh. Formal witness interviews come later as part of the investigation, but early notes about what workers saw and heard are valuable evidence. Workers should not discuss the incident in ways that could contaminate each other's recollections, and the site supervisor should manage the communication to prevent speculation and rumour.

A thorough incident report captures all the information needed to investigate the event, satisfy the regulator, support any insurance claim, and feed the SWMS review process. The template below sets out the essential sections and should be completed as soon as practicable after the incident — ideally while the first-hand recollections are still fresh. Leaving sections blank or deferring completion until the next day introduces gaps that investigators will find.

Header section: the date, time, and exact location of the incident, including building, level, grid reference, or GPS coordinates. Project name, address, and principal contractor. Weather conditions including temperature, wind, rain, and visibility. Start time of the shift and the elapsed time from shift start to incident. These fields establish the context of the event.

Persons involved: names, roles, and employers of anyone injured, involved, or witnessing the incident. Record their condition immediately after the event, any first aid or medical treatment provided, the name of the treating first aider or paramedic, and the destination if the person was transported to hospital. Include contact details so investigators can follow up.

Description of the incident: a factual narrative of what happened, written in plain language without blame or speculation. Start with the activity being performed before the incident, then describe the sequence of events leading up to the incident, the incident itself, and the immediate aftermath. Avoid interpretation at this stage — report what was seen, heard, and done, not why it happened. That analysis comes later in the investigation.

SWMS reference: which SWMS was in effect for the work being performed. Version number, issue date, and the date the current version was issued. Whether the involved workers had signed on to the current version. Whether the controls described in the SWMS were in place and being followed at the time of the incident. These questions drive the SWMS review process and are the hinge between the incident and the corrective action.

Immediate actions taken: the response in the first minutes and hours. First aid applied, emergency services called, site preservation steps, notifications made to the principal contractor and the regulator, isolation of plant or energy sources, and any work stoppage imposed. Record the time of each action to establish a timeline.

Photographic evidence: photos of the incident scene from multiple angles, close-ups of any equipment involved, the work area, any signage or barriers, and the immediate surroundings. Photos should be taken before anything is moved where it is safe to do so, with timestamp and device metadata preserved. Hand-drawn sketches of the site layout can supplement photos where the three-dimensional geometry is not obvious.

Witness statements: short written statements from every person who saw or heard the event, collected separately so witnesses do not influence each other's recollections. The statements should include the witness's location at the time, their view of the incident, what they did in response, and any comments they heard from others. Statements are typically written by the witness in their own words and signed.

Root cause analysis: the underlying causes of the incident, developed through techniques such as the five whys or a cause-and-effect diagram. Do not stop at worker error — human action is almost always preceded by a system failure (inadequate training, unclear procedures, missing controls, time pressure). A root cause analysis that concludes the worker was careless is usually a sign that the investigation did not go deep enough.

Corrective actions: specific, measurable actions to prevent recurrence. Each action should have a named person responsible, a deadline, and a verification step. Be more careful is not a corrective action; install physical barriers around fragile roof areas and update the pre-access checklist to identify fragile sheeting before work commences is.

SWMS amendment: the specific changes required to the SWMS based on the investigation findings. Reference the section 299 content elements affected (hazard identification, control measures, implementation arrangements, review triggers) and describe the amendment. Record the version number of the amended SWMS and the date workers will be re-briefed.

Root cause analysis is the most important and most frequently botched part of an incident investigation. The goal is to identify the underlying system failures that made the incident possible, not to assign blame to the worker at the sharp end. An investigation that concludes the worker was careless or failed to follow procedure has almost always missed the real causes, because human behaviour is shaped by the system around it — training, supervision, equipment, time pressure, and procedural clarity all influence what workers actually do on site.

The five whys technique is a simple and effective starting point. Ask why the incident occurred, then ask why the answer to that question occurred, and repeat until the chain of causation reaches a systemic issue. For example: why did the worker fall through the fragile roof sheeting? Because they stepped on an unmarked area. Why was the area unmarked? Because the pre-access survey missed it. Why did the survey miss it? Because the surveyor did not have the original building plans. Why didn't they have the plans? Because the principal contractor did not include plan access in the subcontractor onboarding pack. Why not? Because the onboarding process does not specify what documents must be provided for work on existing buildings. The root cause is the gap in the onboarding process, not the worker's foot placement.

Cause-and-effect diagrams (sometimes called fishbone or Ishikawa diagrams) support more complex investigations. The incident is placed at the head of the diagram, and branches represent the categories of contributing factors — people, methods, materials, equipment, environment, and management. Each branch is populated with the specific factors identified during the investigation, and the diagram helps the investigator see the full picture rather than focusing on one category.

The investigation should consider all six of these categories. People factors include training, competency, experience, fatigue, and individual actions. Method factors include the procedures, the SWMS, the JSA, and the pre-start briefings. Material factors include the equipment in use, the materials being handled, and any consumables. Equipment factors include the plant, the tools, the PPE, and the inspection records. Environment factors include weather, lighting, noise, and adjacent work. Management factors include supervision, planning, communication, and the principal contractor's WHS Management Plan.

The deliverable of the analysis is a short list of causal factors with supporting evidence, and a prioritised list of corrective actions that address each factor. The actions should be specific enough that their implementation can be verified, and the verification step should be assigned to a named person with a deadline. A corrective action without verification is almost never implemented, and the lesson from the incident is lost.

WHS Regulation 2025 section 300 requires the SWMS to be reviewed, and if necessary revised, after any incident or near-miss relating to the HRCW. This obligation is automatic and does not depend on the outcome of the investigation — the review must be conducted even if the investigation has not yet concluded. In practice, the SWMS review happens in parallel with the incident investigation and feeds into it.

The review asks one critical question: was the work being done in accordance with the SWMS at the time of the incident? If yes, then the controls specified in the SWMS were inadequate, because they were in place and an incident still occurred. The SWMS must be revised with additional or stronger controls. For example, the SWMS might have specified the use of a fall-arrest harness when working at heights, and an incident occurred because the anchor point failed. The control (harness) was in place, but the control specification was incomplete — it did not address the strength of the anchor point. The revised SWMS adds a specific anchor point verification requirement referencing AS/NZS 1891.4.

If the answer is no — the SWMS was not being followed — then the investigation focuses on why not. Was the control impractical on site? Was it unclear in the document? Was the worker trained on the control? Was the supervisor enforcing it? A SWMS that specifies a control that cannot be implemented in practice is not a useful document, and the revision may involve changing the control to something that works in the field rather than forcing workers to comply with an unworkable instruction. Retraining, supervision changes, or additional signage may also be needed.

The amendment process itself is straightforward on a platform that supports quick-amend workflows. The supervisor opens the SWMS on a phone or tablet, navigates to the section affected by the incident findings, adds or modifies the hazard or control, saves a new version, and triggers a notification to all affected workers to re-acknowledge the updated document. The amendment log records the change with a timestamp, the identity of the person who made the change, and the reason for the change. Workers scan a QR code to re-sign on to the amended version, and the sign-on count is updated in real time.

On a paper workflow, the same amendment takes hours. The supervisor returns to the site office, opens the SWMS in Word, makes the change, prints the new version, circulates a new sign-on sheet at the next toolbox talk, and files the updated document in the project folder. During the gap between the amendment and the re-briefing, workers may continue HRCW against the outdated document, and the audit trail for the change is often incomplete or missing. The platform-based workflow is not just faster — it is measurably more complete and more defensible in enforcement action.

The SWMS amendment must be communicated to the principal contractor as well as the workers. On managed sites, the principal contractor maintains the project SWMS register and must be aware of every revision. A subcontractor who amends a SWMS silently, without notifying the principal contractor, has violated the principal contractor's control of the project and is likely to face consequences under the subcontract. The notification should include the amended version, the reason for the amendment, and confirmation that workers have re-signed on.

WHS Regulation 2025 requires the SWMS to be kept and available at the workplace until the HRCW is completed, and for at least 2 years from the date of a notifiable incident to which it relates. These minimum retention periods are the floor rather than the ceiling, and best practice is to keep SWMS, incident reports, investigation findings, and corrective action records for significantly longer. The reasons are practical: coronial inquiries, civil claims, workers compensation disputes, and industrial manslaughter prosecutions can all require documentation years after the event.

Coronial inquiries into workplace deaths can take several years from the incident to the coroner's findings, and the coroner may request the SWMS, the incident report, and the investigation records at any stage during the inquiry. Industrial manslaughter prosecutions have a statute of limitations that varies by jurisdiction but is typically several years from the date the offence is alleged to have occurred. Civil claims by injured workers or their families may not be filed for years after the incident, and the defence will rely heavily on the contemporaneous documentation of what the employer did and did not know.

The practical best practice is 7 years of retention for all SWMS and related records as a minimum, and permanent retention for any record associated with a notifiable incident, a fatality, or an asbestos-related exposure. Permanent retention is the norm on digital platforms because the marginal cost of storage is trivial compared to the risk of losing records that may be required. A paper-based retention system is expensive to maintain and increasingly unreliable over long timescales — documents fade, filing systems are lost during office moves, and the people who know where the records are stored leave the business.

Digital retention also supports retrieval. An incident record that is filed in a paper folder in a warehouse is technically retained but may be effectively inaccessible when needed. A digital record in a searchable system can be retrieved in minutes, with the full context of the SWMS, the amendment history, the sign-on records, and the related documents. This is the difference between a retention obligation that is met on paper and a retention system that actually delivers evidence when it matters.

On platforms that support permanent retention regardless of subscription status, the contractor's records remain accessible after any cancellation of the active subscription. This matters because the retention obligation outlasts any commercial relationship — a contractor who closes their business, changes platforms, or cancels their subscription still has legal obligations to produce records if a regulator, coroner, or court requests them. A platform that deletes records on cancellation creates a compliance gap that the contractor cannot close.