ESC inspections after rainfall: the NSW 20mm trigger explained

Rain is when erosion and sediment controls earn their keep, and when they fail. A sediment fence that looked fine on Friday afternoon can be undermined, overtopped or flat on the ground by Monday morning. That is why NSW projects almost universally carry a condition, in the CEMP, the consent or the EPL, requiring an ESC inspection after significant rainfall. The most common trigger you will see is rainfall exceeding 20mm in a 24 hour period.

This article covers where that trigger comes from, what a competent post-rainfall inspection actually looks at, how to document what you find, and the failures that show up again and again on real sites.

Where the trigger comes from: the Blue Book

The reference document behind most ESC requirements in NSW is Managing Urban Stormwater: Soils and Construction, known across the industry as the Blue Book. It sets out the design standards for erosion and sediment controls on construction sites: how to size sediment basins, where to place fences, how to stabilise site access, and how to manage disturbed areas through the life of a project.

The Blue Book's core expectation is simple: controls must be maintained in effective working order for as long as the site is disturbed. Rainfall is the event most likely to degrade them, so inspecting after rain, and repairing promptly, is how you demonstrate that maintenance obligation is being met. Consent authorities and the EPA pick up that expectation and write it into approval documents as an inspection trigger, and the figure that has become the de facto standard on NSW projects is more than 20mm of rain in 24 hours.

Two things are worth being precise about. First, the trigger that binds you is the one written in your approval documents, not a number from an article or another project's CEMP. Read your conditions. Second, the rainfall trigger is usually in addition to a routine inspection cadence, commonly weekly, not a replacement for it. A dry fortnight does not mean no inspections.

Other states use different triggers

If you work across borders, do not assume the NSW figure travels with you. Victoria and Queensland commonly use lower or project-specific rainfall triggers, set in the CEMP or the relevant approval rather than in a single statewide reference document. Some projects also add a forecast-based trigger: inspect before predicted heavy rain, not just after it. The safe habit is the same everywhere: the trigger is whatever your approval says it is, and your inspection records need to show you honoured it. For a broader look at how obligations shift between jurisdictions, see our guide to environmental monitoring requirements by state.

Knowing when the trigger has fired

A surprising number of sites cannot actually answer the question "did we get 20mm yesterday?" with confidence. The options, roughly in order of defensibility:

• An on-site rain gauge, read and logged daily. The gold standard, because rainfall is hyper-local. A storm cell can dump 30mm on your site and 8mm on the nearest weather station.
• A nominated Bureau of Meteorology station, named in the CEMP as the reference gauge. Acceptable on many projects, but name it in advance. Choosing whichever gauge suits you after the event looks terrible in an audit.
• Nothing formal. This is where sites get caught. If you cannot show what fell, you cannot show whether an inspection was due, and an auditor will treat every wet day as a potentially missed trigger.

Whoever reads the gauge, the reading itself should be recorded. The rainfall log and the inspection log together are what prove the system worked.

What a post-rainfall ESC inspection covers

A trigger inspection is not a stroll around the site office. It is a systematic pass over every control and every point where water leaves the site. On most projects that means:

• Sediment fences. Look for undercutting, overtopping, collapsed sections, torn fabric, and sediment built up beyond roughly a third to half of fence height, the usual maintenance trigger for cleaning out. Check the returns at the ends: water outflanking a fence is as common as water breaching one.
• Sediment basins. Check available capacity, the condition of the inlet and the emergency spillway, and whether the basin discharged during the event. If it did, was the discharge treated and tested in line with your approval? Basin water quality before any dewatering is its own discipline, covered in our guide to dewatering discharge limits in practice.
• Stabilised site access. Rain turns a marginal rumble pad into a mud slick. Check whether the entry is still doing its job and whether sediment has tracked onto the public road. Mud on the road is the single most visible ESC failure a site can have, and the one most likely to generate a complaint.
• Discharge points and receiving waters. Walk every legal and accidental discharge point. Look for turbid plumes, scour, and sediment deposition beyond the site boundary. Evidence of polluted runoff leaving site is the finding that escalates fastest, because it can put you in breach of pollution offences under the POEO Act. Our explainer on POEO Act penalties covers why that matters.
• Stockpiles, batters and disturbed areas. Rilling and gullying on batters, scour around stockpile toes, failed temporary cover. These are early warnings of the next, bigger failure.
• Drainage controls. Diversion drains, check dams, catch drains and outlet protection. Confirm clean water is still being kept clean and dirty water is still being directed to treatment.

Documenting findings and corrective actions

The inspection only counts if it is recorded, and the record only protects you if it closes the loop. A defensible post-rainfall record shows:

• The trigger: the rainfall reading, the gauge it came from, and the date and time.
• The inspection: who did it, when, and what was checked, ideally against a consistent checklist so that nothing is silently skipped.
• Findings with photos. Time-stamped, located photos of each defect. "Fence damaged near ch 400" without a photo is a weak record; the same finding with an image and a pin is evidence.
• Corrective actions with owners and due dates. Each defect should become an action assigned to a person, with a timeframe that reflects the risk and any repair timeframe your approval specifies. Many approvals expect controls to be reinstated promptly, sometimes within a defined number of days, so check yours.
• Close-out evidence. A photo of the repaired control and a sign-off. An open action from March discovered in an October audit is a finding in itself.

If the same inspection also has to satisfy an EPL condition, make sure the record references the condition it discharges. Auditors work from the conditions list, not from your folder structure, and the mapping between what you did and what you were required to do is exactly what they test. Our piece on understanding EPA licence conditions goes deeper on that mapping.

Common failures, on the ground and on paper

• The Monday problem. Rain lands on Saturday, the inspection happens Monday, and the record is silent about the gap. If your trigger requires prompt inspection, weekend rain needs a weekend answer, a rostered person, an on-call arrangement, or an honest record of when the site was next accessible and why.
• Inspections that always pass. Twenty consecutive trigger inspections with zero findings is not a clean site, it is a red flag. Real rain finds real defects. Auditors know this.
• Findings without actions. The inspection notes "fence down at northern boundary" and the trail ends there. A documented defect with no documented fix is worse than useful, it proves you knew.
• No rainfall log. Without a record of what fell, you cannot demonstrate which days required inspections, so every gap becomes arguable.
• Controls never upgraded. If the same fence fails after every event, the corrective action is not another repair, it is a better control. Repeated identical failures show a system that records problems without learning from them.

Making the trigger automatic

Everything above is achievable on paper. The reason it decays is that paper systems depend on someone remembering, checking the gauge, remembering the trigger, chasing the fitter who fixed the fence for a photo. This is the workflow claused. was built around: rainfall-trigger inspections scheduled and assigned automatically, checklists completed in the field with photos attached from the field app, every finding converted to a tracked corrective action, and the whole record auto-tagged to the CEMP or EPL condition it discharges, ready to drop into an audit pack. You can see a worked example in the live demo workspace, or register for early access if you want to run it on your own site.

The short version

Know your trigger, and assume it is 20mm in 24 hours in NSW unless your documents say otherwise. Log rainfall so you can prove when the trigger fired. Inspect every control and every discharge point, not just the convenient ones. Photograph what you find, assign the fix, and close the loop with evidence. Rain will keep testing your controls; the inspection record is what shows you were paying attention when it did.