An excavator clips a service, or a worker falls, or a trench face slumps while nobody is in it. In the minutes that follow, a small number of decisions get made by whoever is standing there — usually a supervisor with no training in any of this — and those decisions shape the regulatory outcome, the insurance outcome and the contractual outcome for the next two years.
Most civil contractors have a safety system covering how to prevent incidents and almost nothing covering what to do once one has happened. This guide covers the second half: notification, site preservation, evidence, investigation and the consequences that follow, including the ones that reach your next tender. What happens in the minutes before any of that — rescue, access and getting help to the right place — is covered in our guide to emergency preparedness and site rescue, and testing after an incident sits inside your drug, alcohol and fitness for work policy.
The first two hours
In order. The order matters, because two of these have legal deadlines and one of them is irreversible.
| # | Action | Note |
|---|---|---|
| 1 | Care for the injured and make the area safe | Always first. Nothing in this guide displaces it, and the law permits disturbing a site to do it |
| 2 | Stop related work | If one trench failed, the others are suspect. If one machine contacted a service, the method is suspect |
| 3 | Secure the scene | Fence or tape it, and stop people tidying up. Tidying up is the instinct, and it destroys the evidence |
| 4 | Notify the regulator if the incident is notifiable | Immediately, by the fastest means. This is a legal duty with a criminal penalty for failure |
| 5 | Notify the principal or head contractor | Contractual, usually with a short deadline |
| 6 | Photograph and record everything before it changes | Weather, ground, plant positions, the whole area, not just the point of failure |
| 7 | Take contact details for everyone present | Including subcontractors, deliveries and visitors, who will otherwise be gone |
| 8 | Notify your insurer and get advice | Policy conditions require prompt notification, and on a serious incident legal advice should be early |
Step 3 is the one that goes wrong. A crew’s natural response to a serious event is to clear up, move the machine, backfill the hole and restore order. Every one of those actions removes evidence that would otherwise have shown what happened — and where the site had to be disturbed, the fact and the reason should be recorded at the time.
What counts as notifiable
Australian work health and safety law requires notification of three categories: the death of a person, a serious injury or illness, and a dangerous incident. The definitions are set out in the legislation, and the third category is the one contractors consistently under-recognise.
A dangerous incident is notifiable whether or not anyone was hurt. The legislation lists categories that map closely onto ordinary civil work — uncontrolled escape or release of substances, an uncontrolled implosion, explosion or fire, electric shock, the fall or release from height of plant or a substance, the collapse or partial collapse of a structure, the collapse or failure of an excavation or of any shoring supporting it, damage to or contact with overhead or underground electrical lines, and the collapse or malfunction of plant required to be authorised. In civil terms: a trench that slumps overnight with nobody in it, a machine that contacts a powerline without injuring anyone, and a struck electrical service are all capable of being notifiable events.
Three practical points:
- The categories and thresholds differ between jurisdictions, because each enacts its own version of the law. Confirm with the regulator where you are working; do not carry an interstate understanding across a border.
- “No one was hurt” is not the test. Treating injury as the trigger is the single commonest reason a notifiable incident goes unnotified.
- If in doubt, ring the regulator. Regulators would rather field a call about a non-notifiable event than investigate a failure to notify, and the call itself is evidence of a diligent approach.
Notification is generally required immediately after becoming aware, by the fastest available means, with written notice to follow if the regulator requires it. The obligation sits on the business, and failing to notify is an offence in its own right — separate from, and additional to, whatever the incident itself gives rise to.
Who you must tell, and in what order
| Who | When | Why it is separate |
|---|---|---|
| Work health and safety regulator | Immediately, if notifiable | Statutory duty on the business |
| Electrical safety regulator | Immediately, for electrical incidents in jurisdictions with a separate regime | A separate statutory duty — see working near overhead powerlines |
| Environmental regulator | Immediately, for pollution incidents meeting the jurisdiction’s threshold | A separate duty with its own definition of what triggers it |
| Asset owner or network | Immediately, for a struck service | They must make it safe, and they will investigate separately |
| Principal or head contractor | Per the contract, usually immediately or within hours | Contractual, and often a condition of remaining on site |
| Workers compensation insurer | Within the scheme’s timeframe | Late notification delays support and can attract penalties — see workers compensation and injury management |
| Liability or plant insurer | Promptly, per the policy | Policy condition; late notification can prejudice cover — see making an insurance claim on a civil job |
| Your lawyer | Early, on anything serious | For the reasons in §08, this is more time-critical than it appears |
| Health and safety representative and workers | Promptly | Consultation duties continue after an incident, and rumour fills a silence |
The point of the table is that these are separate duties with separate triggers and separate deadlines, and satisfying one does not satisfy another. Telling the head contractor is not telling the regulator. Telling the regulator is not telling your insurer. The commonest failure is assuming a single phone call has discharged everything.
Preserving the site
Where an incident is notifiable, the law requires the site to be preserved until an inspector arrives or the regulator directs otherwise. There are exceptions — to assist an injured person, to remove a deceased person, to make the site safe or minimise further risk, and where a police officer or inspector directs.
What preservation means in practice on a civil site:
- Leave plant where it stopped, isolated and secured, rather than driving it out of the way.
- Do not backfill, even where an open excavation is inconvenient — fence it instead.
- Do not repair the damaged thing, unless making safe requires it, in which case photograph first.
- Preserve the surrounding area, not only the immediate point. Approach routes, ground conditions, spoil positions and sight lines are all part of what an investigator needs.
- Record every disturbance: what was moved, by whom, when and why. That record is what distinguishes lawful making-safe from interference.
- Keep the rest of the job going where it is safe and separate, but be prepared for a prohibition notice on part or all of the work.
The commercial consequence is real: a preserved site is a stopped site, and a stopped site has programme and cost consequences. Whether those are compensable depends on the contract and on the cause, and it is a question for later — but the records made now are what any later claim will rest on, as our guide to contract administration for civil SMEs sets out.
Evidence is mostly made before the incident
The uncomfortable truth about incident response is that the most important evidence was created weeks earlier, or was not created at all.
| Record | What it establishes |
|---|---|
| SWMS for the activity, signed by the crew | That the hazard was identified and controls were set and communicated |
| Pre-start inspections and plant maintenance records | That the plant was fit, and when it was last checked |
| Competency records, licences and tickets | That the person was qualified for the task |
| Induction and toolbox records | That the person was informed of site-specific hazards |
| Service location records and proving results | On a strike, the single most important document — see utility and telecommunications civil works |
| Excavation inspections by a competent person | On a collapse, likewise — see temporary works and excavation support |
| Temporary works design and certification | That the support system was engineered rather than improvised |
| Site diary, weather and hold points | Conditions and sequence on the day |
| Hazard reports and previous near misses | Cuts both ways: evidence of a functioning system, or evidence of a known and unaddressed risk |
That last row deserves emphasis. A near miss reported and closed out is powerful evidence of a working system. The same near miss reported and ignored is the strongest evidence against you that exists, because it establishes you knew. The practical lesson is not to discourage reporting — it is to close out what gets reported, and to record the closure.
Everything in that table already belongs in the systems described in our guides to WHS management plans and SWMS and quality management plans and ITPs. The point here is that those records have a second audience nobody designs them for.
Running an investigation that finds the actual cause
Structured investigation methods used across Australian construction and resources share a common shape, and an SME can apply the shape without the branded methodology.
- 1. Establish the sequence of events before analysing anything. Who was where, doing what, when. Build a timeline from records and statements, and note where they conflict rather than resolving the conflict prematurely.
- 2. Identify the absent or failed defences. What was supposed to prevent this, and what happened to it? A control that existed on paper but not on site is an absent defence, not a present one.
- 3. Identify the individual actions and conditions immediately involved — what was done, and what state things were in.
- 4. Identify the task and environmental conditions that shaped those actions — time pressure, weather, lighting, plant availability, crew experience, supervision ratio, the sequence imposed by the programme.
- 5. Identify the organisational factors that produced those conditions — how the job was resourced, how the work was priced, how the programme was set, how competency was assured, how the subcontract was written.
- 6. Set corrective actions against each level, with an owner and a date.
Step 5 is where most SME investigations stop short, and it is the level where the durable fixes live. If a crew was working without the shoring because the shoring was on another site, the finding is not that the crew took a shortcut — it is that the resourcing made the shortcut the only way to meet the programme. That is a fixable organisational condition, and it is also, in a regulator’s hands, exactly the reasoning that leads back to the officers of the business.
“Operator error” and why it ends the learning
The commonest finding in a poor investigation is that somebody did something wrong. It is usually accurate and almost always useless.
Three reasons to push past it:
- It generates no useful corrective action. “Counselled the operator” and “reminded the crew” do not change the conditions, so the same event remains available to the next person.
- It will not survive scrutiny. A regulator, a client or an insurer reading an investigation that stops at operator error will ask the next question, and you will answer it under less favourable circumstances than if you had asked it yourself.
- It destroys reporting. A workforce that sees investigations end in blame stops reporting hazards and near misses, which removes the information that prevents the serious event — the same dynamic described in our guide to workers compensation and injury management.
This is not an argument against accountability. Deliberate and reckless conduct exists and should be dealt with. It is an argument that the question “why did that seem like the reasonable thing to do at the time?” produces better findings than “who failed to follow the procedure?” — and that the answer is usually about pressure, availability and design rather than character.
Advice, privilege and the two-document problem
A genuine tension, and one that catches contractors who are trying to do the right thing.
You want a frank internal investigation that finds real causes so you can fix them. You are also potentially exposed to prosecution, and a frank internal document identifying organisational failures can be obtained and used. Those two objectives pull in opposite directions.
Legal professional privilege can protect material created for the dominant purpose of obtaining legal advice. Whether it applies in any particular case depends on the circumstances, how the investigation was commissioned and what it was actually for — it is not conferred by putting a lawyer’s name on the front of a report you were going to write anyway. This is genuinely a matter for advice, and the reason to get that advice early is that the decision about how to structure the investigation has to be made before it is run, not after.
What a civil SME can sensibly do without a legal department:
- Call a lawyer on the day for anything serious — a fatality, a serious injury, a regulator attendance, or any incident likely to lead to a notice or prosecution.
- Separate the immediate safety response from the causal investigation. Making things safe and identifying immediate hazards should happen straight away regardless; the deeper analysis can be structured on advice.
- Never delay a statutory notification while taking advice. Notification is a duty with its own penalty and it is not a strategic decision.
- Do not create speculative documents. Emails theorising about fault, drafted in the first hours by people without the facts, are discoverable and unhelpful.
- Record facts as facts, and keep opinions and conclusions to the investigation itself.
Interviews and what workers are entitled to
Both your interviews and the regulator’s.
Your own. Talk to people early, because memory degrades quickly, but do it carefully: individually rather than in a group, focused on what they saw and did rather than on what they think caused it, without leading, and with a written record they have the chance to confirm. Someone who has just been through a traumatic event may not be in a state to give a useful account, and pressing them is both unkind and counterproductive.
The regulator’s. Inspectors have statutory powers to require information and to interview. Workers generally have rights in that process — including, commonly, the right to have a support person or legal representative present, and protections around self-incrimination that differ by jurisdiction and by whether the person is an individual or a business. Contractors should tell their workers that these rights exist, and should not attempt to coach, script or discourage them. Interfering with a regulator’s investigation is a serious offence and converts a defensible incident into an indefensible one.
Inspectors, notices and what follows
| Outcome | What it is | Practical effect |
|---|---|---|
| Improvement notice | A direction to remedy a contravention within a stated period | Compliance required by the date; usually manageable |
| Prohibition notice | A direction to stop an activity presenting an immediate or imminent risk | Work stops until the risk is remedied. Immediate programme consequence |
| Non-disturbance notice | A direction to preserve a site for a period | Extends the preservation obligation in §04 |
| Infringement or penalty notice | An on-the-spot penalty | Financial, and it appears in your compliance history |
| Enforceable undertaking | A binding commitment to remedial activity, accepted by the regulator as an alternative to prosecution in some cases | Substantial and public. A matter for legal advice |
| Prosecution | Court proceedings against the business and potentially its officers | The most serious outcome, with penalties and disclosure consequences |
Two things worth knowing in advance. Notices generally carry review or appeal rights with short time limits, so a notice you believe is wrong needs advice quickly rather than eventually. And most notices are recorded and many are published — which connects directly to §13, because a compliance history is what prequalification schemes ask about.
How you deal with an inspector on the day matters more than contractors expect. Be cooperative, provide what is required, do not obstruct, do not speculate, and have one person nominated to interface rather than several offering competing accounts. If you do not know something, say so rather than guessing.
Insurance, client and contract notifications
The obligations that run in parallel with the regulatory ones and are easiest to overlook while the regulatory ones are consuming attention.
- Insurance. Policies require notification of events likely to give rise to a claim, promptly, and prejudice from late notification is a real basis for reduced or refused cover. Notify on the event, not on the claim — and notify all potentially responding policies, since one incident can touch liability, plant, motor and workers compensation at once.
- Contract. Most contracts require immediate notification of incidents, and many give the principal rights to suspend, to direct removal of a person from site, or to require an investigation report. Read the clause before you need it.
- Subcontractors and hired plant. Where the incident involves a subcontractor’s worker or a hired machine, their insurers and their principals have their own notification chains — see our guides to subcontracting to Tier 1 civil contractors and plant hire agreements.
- Environmental incidents carry their own duty, threshold and clean-up obligations, and the regulator involved may not be the safety one — see our guide to environmental approvals and permits.
A practical device: a one-page notification matrix for each project, prepared at mobilisation, listing every party to be notified, the trigger, the deadline, the method and the phone number. It takes twenty minutes, it lives in the site office, and it means the decisions in §01 are made by reference to a list rather than from memory during the worst hour of someone’s career.
Corrective actions that actually close
An investigation that produces no change is an expense. Four tests separate a real corrective action from a recorded one.
- Does it sit high enough on the hierarchy? Eliminating or engineering out the hazard is a corrective action. Re-training and reminding are rarely more than a supplement.
- Is it assigned to a named person with a date? Actions owned by “the team” do not happen.
- Does it change something outside the individual? A method, a piece of equipment, a resourcing decision, a specification, a subcontract term.
- Has its effectiveness been checked afterwards? Closing an action is not the same as verifying it worked, and the verification is what a client audit asks for.
Actions should also propagate. A finding on one site almost always applies to the others, and the mechanism for that is a simple corrective action register reviewed at the same rhythm as everything else — the management review structure described in our guide to the ISO prequalification trifecta, if you hold certified systems, and a monthly agenda item if you do not.
What tenders ask about your incident history
The reason this belongs in a tendering library rather than only a safety one.
Prequalification schemes and tender schedules routinely ask for notifiable incidents over a period, improvement and prohibition notices received, infringements, enforceable undertakings and prosecutions — and increasingly for the corrective actions taken. Our guide to civil contractor prequalification in Australia covers how the schemes assess.
How to answer:
- Answer truthfully and completely. Much of this is on public record or discoverable, and a discovered omission is treated as a probity matter rather than a safety one — which is far worse.
- Describe the incident factually and briefly, then spend the space on the investigation and what changed.
- Show the organisational-level fix. A response that identifies a resourcing or method change reads as competence; one that says the worker was counselled reads as an unlearned lesson.
- Do not minimise. Evaluators have read many of these and can tell.
- A clean history with no explanation invites the same scepticism as an unqualified zero injury rate from a small contractor. If you have had nothing notifiable, say so and support it with your leading indicators.
The general drafting approach is in our guide to addressing selection criteria. The specific point for this subject is that a well-managed incident, honestly described, with a real organisational fix, frequently scores better than silence — because it is the only direct evidence an evaluator will ever see that your system works when it is tested.
Checklist
- Does every project have a one-page notification matrix in the site office?
- Do your supervisors know that a dangerous incident is notifiable even if nobody was hurt?
- Do they know a trench collapse with nobody in it, and a powerline contact with no injury, can both be notifiable?
- Is there a clear instruction not to tidy up, move plant or backfill after an incident?
- Does everyone know the exceptions — assisting an injured person and making safe — and to record any disturbance?
- Is there a rule to photograph the wider area, not just the point of failure?
- Are contact details taken for everyone present, including visitors and delivery drivers?
- Do you notify the regulator without waiting for legal advice?
- Do you call a lawyer on the day for anything serious?
- Do you notify every potentially responding insurer, not just one?
- Have you read the incident notification clause in your current contracts?
- Does your investigation method reach organisational factors, not just the individual?
- Have you banned “operator error” as a final finding?
- Are near misses reported, closed out and the closure recorded?
- Do workers know they may have a support person present in a regulator interview?
- Is one person nominated to interface with an inspector?
- Do you know the review and appeal time limits for notices?
- Are corrective actions assigned to a named person with a date, and verified afterwards?
- Do findings from one site propagate to the others?
- Is your incident history recorded accurately and ready to answer in a prequalification?
The short version
- The first two hours set the regulatory, insurance and contractual outcome. Care for people, stop related work, secure the scene, notify, record.
- Tidying up is the instinct and it destroys the evidence. Do not move plant or backfill unless making safe requires it — and record any disturbance.
- Dangerous incidents are notifiable whether or not anyone was hurt. A trench that slumps empty and a powerline contact with no injury both qualify.
- Notification duties are separate and parallel. Telling the head contractor is not telling the regulator; telling the regulator is not telling your insurer.
- Never delay a statutory notification to take advice. It is a duty with its own penalty, not a strategic decision.
- Most of the evidence was created before the incident — SWMS, pre-starts, competencies, service proving, excavation inspections.
- A near miss reported and closed out is strong evidence for you. The same one ignored is the strongest evidence against you.
- Push the investigation to organisational factors. If the shoring was on another site, the finding is about resourcing, not the crew.
- “Operator error” generates no useful fix, will not survive scrutiny, and stops people reporting.
- Get legal advice on the day for serious incidents — how the investigation is structured has to be decided before it is run.
- Never coach or discourage workers in a regulator interview. Interference converts a defensible incident into an indefensible one.
- A well-managed incident honestly described, with a real organisational fix, often scores better in a tender than silence.
Sources and further reading
This guide is general information for Australian civil construction businesses and is not legal, safety or insurance advice. Notification obligations, the definitions of serious injury, illness and dangerous incident, site preservation duties, inspector powers, notice types, review rights, penalties and the protections available to individuals in regulator interviews are set by the work health and safety, electrical safety and environmental legislation of each state and territory and differ between them. No notification deadline, threshold, penalty or definition is stated here as applicable to your jurisdiction and none should be inferred. Whether legal professional privilege attaches to an investigation depends on the circumstances and requires legal advice obtained before the investigation is commissioned. Insurance notification obligations are set by your policy. On any serious incident, contact the regulator for your jurisdiction, your insurer and a lawyer immediately.
- The model Work Health and Safety Act and Regulations and the versions enacted in each Australian state and territory, which establish the categories of notifiable incident described in §02 — death, serious injury or illness, and dangerous incident — together with the duty to notify the regulator immediately by the fastest available means, the duty to preserve the incident site and its exceptions described in §04, and the inspector powers and notice types in §10. Definitions, thresholds and procedures differ between jurisdictions and are amended; the regulator for the jurisdiction is the authority.
- Separate state and territory electrical safety and environment protection legislation imposing their own incident notification duties with their own triggers, referenced in §03. An incident can be notifiable under more than one regime simultaneously, and notification under one does not satisfy another.
- Structured incident investigation methodologies used across Australian construction and resources, which analyse an event through absent or failed defences, individual actions, task and environmental conditions and organisational factors — the shape described in §06. These are industry methodologies rather than statutory requirements; the recommendation to reach organisational factors is the guide’s own.
- Legal professional privilege as it applies to investigations conducted for the dominant purpose of obtaining legal advice, referenced in §08. Whether privilege attaches is fact-specific and a matter for legal advice; nothing in this guide should be relied on as establishing it.
- Related TenderBuilt guides carrying the primary-source detail referenced above: WHS management plans and SWMS, workers compensation and injury management, making an insurance claim on a civil job, insurance requirements, temporary works and excavation support, working near overhead powerlines, utility and telecommunications civil works, environmental approvals and permits and civil contractor prequalification.