Inspections
Built for the inspector in the field.
Inspections happen where the work happens — at the site, on a phone, with photo and GPS attached. NPDESTracker captures the inspection cleanly and routes everything that follows it: site history, follow-up tasks, escalation, and the report at year-end.
01 · Mobile-first in practice
Made for the truck, not the desk.
Inspectors aren't at a workstation. They're at a construction site, behind an industrial facility, walking a creek. The UI is built around that reality — mobile-density, sticky action cells, tap targets sized for thumbs, no horizontal scrolling, no menu archaeology to find the next inspection.
- Browser-based — runs on any phone, tablet, or ruggedized field device
- Mobile-density UI — sticky action cells, tap targets sized for thumb use
- Photo capture and GPS attached directly to the record being filled out
- Offline-friendly — log inspections without connectivity; sync when back in range
- One tap to start the right inspection at the right site, with the type prefilled
02 · Site context
Every inspection is tied to a site.
An inspection doesn't live on its own — it's anchored to a site record that knows its address, classification, parcel info, and history. Open a site and you see every inspection, incident, and follow-up that's ever touched it. Open the GIS workspace and the same sites are pinned on the map, color-coded by status.
- Site records carry address, classification, parcel, and ownership
- Inspection history per site, on a clean status timeline
- Linked incidents — IDDE complaints, screening results, source tracing
- Same sites pinned on the GIS map, color-coded by status
- "Open site" from anywhere — list, map, inspection, follow-up — to see the full record
03 · Cadence
The cadence is in the system, not in your head.
Different programs run on different cadences. Construction sites need inspection during active disturbance. Post-construction BMPs are typically annual. Outfall screening follows quarterly dry-weather cycles. Municipal facilities are annual. NPDESTracker tracks the cadence per site and per program, and surfaces what's overdue and due-soon — before it becomes an audit finding.
04 · Follow-up & escalation
Findings don't fall through cracks. There's no crack.
A deficient finding spawns a follow-up automatically — re-inspection date, assigned owner, photo evidence preserved on the original record. If the finding escalates to a notice of violation or a compliance order, that record links back to the inspection that triggered it and stays linked through closure.
- Deficient findings auto-create follow-up tasks tied to the site
- Re-inspection scheduled with a target date and assigned owner
- Photo and GPS evidence preserved on the original record
- Escalation to a notice of violation or compliance order links back to the source inspection
- Closure status visible from both the site record and the program dashboard
05 · How it feeds reporting
Every inspection becomes part of the report — or it doesn't.
When you log an inspection, it counts in the underlying records — and rolls into the matching MCM section of the annual MS4 report automatically. No re-keying. No copying numbers between systems. No inflated stats.
If you didn't run the inspection, the report doesn't pretend you did. The full reporting story — counts derived from records, the audit log, and the readiness rollup — lives on the reporting page.
Walk the daily flow.
Open the demo and click through a sample inspection on the daily workspace. Browse-only, sample data, no signup.