Environmental incident notification duties on construction sites

A hydraulic hose bursts on an excavator working next to a creek. A sediment basin overtops into a stormwater drain during an unforecast downpour. A subcontractor punctures a fuel cell refuelling after hours. None of these are exotic events. On a busy construction site they are Tuesday. What separates a well-run project from one facing enforcement is not whether incidents happen, it is what the team does in the first hour afterwards.

Australian environmental law imposes a positive duty to notify the regulator when an incident causes or threatens serious environmental harm. In New South Wales, the Protection of the Environment Operations Act 1997 requires anyone carrying on an activity to notify a pollution incident that causes or threatens material harm to the environment, and to do so immediately after becoming aware of it. "Immediately" has been interpreted to mean promptly and without delay, not at the end of shift and not once the paperwork is tidy. Other states and territories have their own equivalents: duties to notify serious or material environmental harm under their environmental protection legislation, each with its own thresholds and timeframes, but all built on the same principle. If the environment is being harmed or is at real risk of harm, the regulator finds out from you, straight away, not from a neighbour's complaint three days later.

The stakes are real. Failing to notify is a separate offence from causing the pollution in the first place, and it is one regulators prosecute hard because it goes to the integrity of the whole system. Penalties for failing to notify are severe and can run into the millions for corporations, with individual liability for directors and managers in some circumstances. Courts consistently treat prompt, voluntary notification as a strong mitigating factor and silence as an aggravating one. For a breakdown of how the NSW penalty framework fits together, see our guide to POEO Act penalties for contractors.

What counts as a notifiable incident

The trigger in NSW is a pollution incident causing or threatening material harm to the environment. The threshold language differs between jurisdictions, but the practical questions a site team should ask are consistent:

• Has anything left the site or entered the environment? Sediment-laden water reaching a creek, fuel reaching soil or groundwater, dust or odour affecting neighbours, contaminated fill placed where it should not be.
• Is harm threatened even if it has not happened yet? The duty covers threatened harm. A ruptured tank held back by a failing bund is notifiable territory even before the first litre escapes containment.
• Is the harm more than trivial? The thresholds are generally framed around harm that is not trivial or that involves actual or potential loss, including clean-up costs above modest amounts. When the assessment is line-ball, the safe and expected course is to notify.

One trap worth naming: the duty falls on the person carrying on the activity, and on occupiers and employers in the chain. A head contractor cannot assume the subcontractor who caused the spill will notify, and a subcontractor cannot assume the head contractor has it covered. In practice, well-drafted incident procedures nominate exactly who makes the calls so nobody stands around assuming someone else did.

The sequence: make safe, capture, classify, notify

The first hour after an incident should run in a fixed order. Teams that improvise under pressure get the order wrong, usually by jumping straight to clean-up and losing the evidence, or by debating classification while the clock runs on the notification duty.

• Make safe first. People before environment, environment before paperwork. Isolate the source, stop the pump, close the valve, deploy spill kits and booms. Nothing in environmental law asks you to notify before you have controlled an active hazard.
• Capture the scene before it changes. Photos of the source, the pathway and the receptor. The state of controls at the time. Weather conditions. Approximate volumes and distances. Once the vac truck arrives and the absorbent pads go down, the evidence of what actually happened starts disappearing. Thirty seconds with a phone camera before clean-up begins is worth more than any statement written a week later.
• Classify against your triggers. Every project should hold a one-page decision aid: what counts as notifiable under the relevant Act, what the project approval or environment protection licence separately requires you to report, and who makes the call. Your licence conditions often carry their own incident reporting obligations on top of the statutory duty, sometimes with different thresholds and different recipients.
• Notify without delay. Once the incident meets the threshold, the calls happen now. In NSW the statutory duty is to notify immediately, and licence holders will typically have a pollution incident response management plan that sets out the full call sequence.

Who to call, and in what order

Notification is rarely one phone call. On a typical major project the sequence looks like this:

• Emergency services, if there is any immediate risk to people or property. That call always comes first.
• The environmental regulator. In NSW that means the EPA's environment line, and in some circumstances other relevant authorities such as the local council, the health authority or the safety regulator, depending on the nature of the incident. Other states have their own reporting lines and duty officers.
• The client or principal. Construction contracts on major projects almost always require prompt notification of environmental incidents to the principal, often within tight contractual timeframes that run in parallel with the statutory duty.
• Internal escalation. Project manager, environmental manager, and whoever holds the corporate reporting line. Senior management should never learn about a notifiable incident from the regulator.
• Follow-up in writing. Verbal notification usually needs to be followed by written details within a set period. Treat the written follow-up as part of the notification, not an optional extra.

Why per-call timestamps matter

When an incident later becomes a prosecution, an enforceable undertaking negotiation, or a contractual dispute, the questions get very specific. When did the operator first become aware? When was the environmental advisor told? When was the regulator called, who spoke to whom, and what reference number was issued? The gap between awareness and notification is often the single most examined fact in the whole matter.

A notification log that records each call as it happens, with a timestamp, the person calling, the person called and what was said, turns that examination into a non-event. A log reconstructed afterwards from memory does the opposite: every inconsistency between the log, the phone records and witness recollections becomes a credibility problem. The habit to build on site is simple. Every call in the sequence gets logged the moment it ends, from the field, not back at the site office at knock-off.

The records that defend you later

If the incident draws regulatory attention, and notifiable incidents usually do, you may face a site inspection, a statutory notice requiring information, or in the worst case a show cause notice. What stands between a closed file and an escalation is usually the quality of the contemporaneous record. The pack you want to be able to produce includes:

• The timeline, from first awareness through make-safe, notification calls and clean-up, with times and names.
• Photos and observations taken during the incident, not staged afterwards, ideally with time and location metadata intact.
• Evidence of the controls in place beforehand: the inspection records, maintenance logs and toolbox talks showing the incident happened despite a functioning system, not because there was no system.
• The corrective actions raised, assigned and closed out, with verification evidence. An incident with a documented, completed corrective action trail reads as a managed event. The same incident with loose ends reads as ongoing risk.
• Links back to your approval conditions. Regulators and independent auditors will ask which conditions the incident engaged and how you complied with each. Being able to answer condition by condition, rather than waving at a lever-arch folder, changes the tone of the entire interaction.

Build the muscle before you need it

None of this works if the first time your team runs the sequence is during a real incident. Drill it. Put the notification decision aid and call tree in the site induction. Make sure night shift and weekend crews know who holds the phone. And close the loop after every event, including near misses, because the near miss you capture and correct this month is the notifiable incident you avoid next month.

This is the part of the job claused. was built for. Field crews capture incidents, observations and photos on their phones through the field app, every entry is timestamped automatically and tagged to the approval conditions it engages, notification calls are logged as they happen, and corrective actions are tracked to verified closure. When the regulator or the client asks for the record, it is already assembled. You can explore the live demo or register for early access.

The duty to notify is one of the few obligations in environmental law where the clock is measured in minutes. Decide now who calls, who logs and who escalates, and the worst hour of your project becomes a well-documented one.