Spill response and incident report app
When fuel, oil or chemicals escape on a site, the environmental officer has two jobs at once: contain the spill and record what happened while it is fresh — the product, estimated volume, where it went, what was done, and who was notified. Weeks later the incident report goes to management, the client or a regulator, and it is only as credible as the notes and timestamped photos taken during the response.
Built for environmental officers running teams of roughly 3–50 inspectors.
Sample Incident spill report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Incident spill report
Incident report — Hydraulic oil release
- Site
- Northern Road upgrade, compound 2 (fictional)
- Date and time
- 12 May 2026, 07:15
- Product
- Hydraulic oil from excavator hose failure
| Step | Detail | Status |
|---|---|---|
| Source stopped | Machine shut down, hose clamped 07:18 | Status: Done |
| Containment | Absorbent booms around spill; drain covered | Status: Done |
| Extent | Approx. 40 L on gravel hardstand, none to drain | Status: Recorded |
| Contaminated material | Gravel excavated to 100 mm, in lined skip | Status: Dispose |
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 incident spill report where your template puts it.
Incident
- Date, time and location
- Product and estimated volume
- Source and cause
- Receiving environment (soil, drain, waterway)
Response (repeat, timestamped)
- Action taken
- Time
- Person
- Photo
Follow-up
- Notifications made
- Waste disposal
- Corrective actions
Standards the report works to
- AS 1940:2017The storage and handling of flammable and combustible liquids
- The bunding and spill containment requirements a corrective action may refer to.
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 incident spill report gets built
Capture it once, offline
Your firm builds the spill response documentation 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 incident spill 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 incident spill 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 response steps be timestamped as they happen?
- Response actions are a repeatable group with time fields, filled in as the response unfolds, offline if needed.
- Can a voice note be used during the clean-up?
- Yes. Audio can be recorded on the device during the response and transcribed afterwards.
- Can incidents across projects be compared?
- Each incident is structured data, so product, volume and cause can be filtered across every report in the submissions grid.
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
- 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
- Surface water samplingWater quality report
Other disciplines
Rebuild your incident spill 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.