Digital stormwater inspections
Digital Stormwater Inspections for MS4 Teams.
Replace the inspection PDF, the photo folder, and the follow-up spreadsheet with one workspace. Structured forms per inspection kind, photos and GPS on the record, tasks for follow-up, field markups, draft notices, enforcement tracking, and exportable records.
01 · Who this is for
Coordinators and inspectors moving from the PDF and folder stack to a structured workspace.
For Phase II MS4 programs running construction, source control, IDDE, and O&M inspections. A digital inspection workflow is more than a fillable form: it is a record that knows what kind of inspection it is, what site it belongs to, what the last finding was, and what task it should open if something is wrong.
Most teams start with the 60-day Guided Pilot at $999 to test the workflow on a focused slice of the program, then move to Inspection Starter or Inspection Team annual tiers when scope is clear.
02 · Inspection workflows supported
All four kinds an MS4 program runs.
Each kind has its own structured form. The full inspection workflow is detailed on the inspections page, and the broader landing-page overview is on the stormwater inspection software page.
Workflows
- IDDE complaint intake, dry-weather screening, and source-tracing
- Source Control inspections at industrial and commercial sites
- Construction Stormwater inspections during active build-out
- O&M / Good Housekeeping inspections for municipal facilities
03 · What inspectors do
The work the inspector actually does in the field.
The inspector opens the site on a map, sees the last inspection history, fills out the structured form, attaches photos and files, marks the missing catch basin or pipe as a field markup on a separate layer, and starts a draft notice if the finding warrants one.
In the inspector's day
- Sites and contacts on a live map
- Site history and last finding visible on every record
- Structured forms per inspection kind
- Photos and files attached to the inspection
- Tasks for deficiencies, return visits, and cleanup checks
- Field markups as a separate exportable layer
- Draft notice templates from inspection records
- CSV and GeoJSON exports of records, markups, and evidence
04 · What supervisors see
The state of the program, not just one inspection.
My Work surfaces personal load. Overdue tasks bubble up across the program. Enforcement records link back to the inspection that triggered them, so the chronology is preserved through the next audit.
What supervisors see
- My Work view that surfaces what each user owns
- Overdue and due-soon tasks across the program
- Enforcement tracking linked to the inspection that triggered it
- Exportable records for internal review and recordkeeping
Scope: NPDESTracker does not submit reports to any state agency and does not certify compliance. Smart Draft is assistive — staff review every save. See Terms and Smart Draft disclosure for the full posture.
06 · FAQ
Frequently asked questions.
Honest answers to the questions that come up most often.
What makes a digital stormwater inspection different from a PDF form?
A digital inspection is a record that knows what kind of inspection it is, what site it belongs to, and what the last finding was. A PDF is a snapshot. The digital record carries photos, GPS, follow-up tasks, and the next visit's findings, so the chronology survives staff turnover and audit requests.
Do digital inspections work in the field without strong cell signal?
Mobile web works today on phones and tablets through any modern browser. A native iOS field app is planned for offline inspection workflows, not launched. Inspectors typically draft the inspection during the visit and finalize when the device reconnects.
Can the inspection record start a follow-up task automatically?
A deficient finding opens a follow-up task attached to the original inspection. The task carries a due date, an assignee, and the closure evidence when the next visit confirms the issue is fixed. Overdue tasks bubble up on the program dashboards.
Where do photos and files live?
On the inspection record, with GPS pinned at the moment of capture. Files attach to the same record. Nothing lives in a shared folder that depends on someone remembering where they put it.
Does the system update our existing GIS?
No. Field markups for missing catch basins, pipes, or field observations land on a separate exportable layer rather than the authoritative GIS. The city's source of truth stays under GIS staff control. The markup layer exports as GeoJSON for the GIS team.
Is there a pilot we can run before the annual tier?
Yes. The 60-day Guided Pilot at $999 is the most common starting point for a small team to test digital inspections on a focused slice of the program. A clean export is available if the city does not continue.
Related inspection software pages
The rest of the inspection cluster.
Each page covers a focused slice of the inspection workflow. Pricing is the same across the cluster: the 60-day Guided Pilot at $999, then Inspection Starter or Inspection Team for the annual tier.
stormwater inspection software
The overview landing page for MS4 inspection teams.
OpenMS4 inspection software
Permit-aligned inspection workflow across MCM 3 through MCM 6.
OpenIDDE inspection software
Complaint to closure on one thread per incident.
Opensource control inspection software
Industrial and commercial site inspections with re-inspection cadence.
Openconstruction stormwater inspection software
Active build-out, rainfall-triggered, and BMP findings on one record per visit.
Openfield inspection software for MS4 teams
Mobile web in the field today, native iOS planned.
OpenSee the digital inspection workflow on sample data.
Open the sample workspace to walk through the inspection workflow end-to-end, or view pricing for tier details.