Erosion and sediment control audit app
Construction sites operate under an erosion and sediment control plan, and certifiers or environmental officers audit the controls — sediment fences, basins, check dams, stabilised entries — especially before and after rain. A useful audit says which control failed, where, and what has to be fixed by when, with a photo. The follow-up audit then needs to show whether it was.
Built for certifiers running teams of roughly 3–50 inspectors.
Sample ESC compliance report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
ESC compliance report
ESC audit — Post-rainfall
- Site
- Hillcrest Estate Stage 2 (fictional)
- Audit date
- 23 February 2026
- Rainfall since last audit
- 48 mm
| Control | Finding | Status |
|---|---|---|
| SF-04 Sediment fence, lot 22 | Undermined over 6 m; sediment on footpath | Status: Fix in 24 h |
| SB-01 Sediment basin | Water level at spillway; not dosed | Status: Treat |
| SE-01 Stabilised entry | Rock clogged, tracking onto road | Status: Renew |
| CD-02 Check dams, swale | Functioning, minor scour | Status: OK |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the ESC compliance report where your template puts it.
Per control
- Control ID and type (from the ESC plan)
- Condition
- Sediment leaving site
- Required action and due date
- Photo
Audit
- Rainfall since last audit
- Stage of works
- Basin water quality before discharge
- Previous actions closed
Standards the report works to
- IECA (2008)Best Practice Erosion and Sediment Control
- Control types, design and maintenance expectations audits are measured against.
- Landcom (2004)Managing Urban Stormwater: Soils and Construction, Volume 1 (the “Blue Book”)
- The standard reference for ESC practice in New South Wales.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the ESC compliance report gets built
Capture it once, offline
Your firm builds the erosion and sediment audit form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your sample locations
Enter sample locations once, as a register. Every one of your samples, bores and monitoring rounds then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The ESC compliance report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a ESC compliance report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The report says every bore was sampled to three metres; the form has BH07 refused at 1.2 m.
Checks a environmental framework usually carries
- Every exceedance in the results tables is discussed in the assessment text
- The guideline values cited match the land use actually being assessed
- No sample or bore ID appears in the prose that is absent from the data
- Data gaps, refusals and deviations from the sampling plan are stated as limitations
Questions
- Can actions from the last audit be checked off on the next one?
- Controls are a register, so each audit points at the same control and can record whether the previous action was closed.
- Can photos be annotated with comments?
- The photo-with-comment field keeps a note attached to each image, and the note follows the photo into the report.
- Can the builder receive a short action list?
- A second template can render only the open actions from the same audit, as a separate document.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other environmental work we cover
- Odour surveysOdour assessment report
- Pest animal control programsControl program report
- Phase 1 site assessmentsESA report
- Phase 2 contamination samplingSampling analysis report
- Rehabilitation monitoringRehab progress report
- Riparian zone assessmentsRiverbank condition report
- Sediment samplingSediment quality report
- Soil sampling programsSoil test report
Other disciplines
Rebuild your ESC compliance report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.