Environment protection licence compliance round app
An environment protection licence sets conditions on a premises — bunding, discharge points, monitoring, housekeeping, records — and the licensee must report compliance each year. Many sites run a monthly internal round so the annual return is not a scramble. The round is a checklist built straight from the licence, and each non-compliance needs a photo, a cause and a corrective action so the annual return can be written honestly.
Built for EPA licensees running teams of roughly 3–50 inspectors.
Sample License condition checklist
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
License condition checklist
Monthly licence condition round — September
- Premises
- Fictional Metal Finishers, Unit 3
- Licence
- Environment protection licence (fictional number)
- Round date
- 30 September 2026
| Condition | Evidence | Status |
|---|---|---|
| Chemical storage within bunds | All IBCs bunded; bund clean and dry | Status: Complies |
| Stormwater pit isolation valve closed | Valve found open after washdown | Status: Non-compliance |
| Monthly discharge sample taken | Sample LDP1-09 collected | Status: Complies |
| Complaints register current | One odour complaint, not yet responded to | Status: Action |
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 license condition checklist where your template puts it.
Per licence condition
- Condition number and summary
- Complies / non-compliance / not applicable
- Evidence observed
- Photo
- Corrective action and owner
Round
- Monitoring samples taken
- Complaints received
- Incidents since last round
Standards the report works to
- Protection of the Environment Operations Act 1997 (NSW)Protection of the Environment Operations Act 1997
- The Act environment protection licences and annual returns are issued under 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 license condition checklist gets built
Capture it once, offline
Your firm builds the environmental license compliance round 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 license condition checklist 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 license condition checklist 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 the checklist be built from our licence conditions?
- Yes. Your firm authors the form, so each licence condition can be its own question, grouped as the licence groups them.
- Can twelve monthly rounds feed the annual return?
- Each round is stored as structured data, so non-compliances across the year can be filtered and tabulated for the annual summary.
- Can multiple premises use the same checklist?
- A reusable module can hold common conditions, with site-specific conditions added per premises form.
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
- Phase 2 contamination samplingSampling analysis report
- Rehabilitation monitoringRehab progress report
- Riparian zone assessmentsRiverbank condition report
- Sediment samplingSediment quality report
- Soil sampling programsSoil test report
- Spill response documentationIncident spill report
- Surface water samplingWater quality report
- Vibration monitoringVibration compliance report
Other disciplines
Rebuild your license condition checklist 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.