MS4 Metrics
A read-only snapshot of program health.
MS4 Metrics is the supervisor view inside the broader NPDESTracker platform. It summarizes inspections, IDDE, outfalls, reporting, and enforcement records that live in their own modules. Program health, overdue work, reporting readiness, and permit-related workload across modules, filtered to a reporting year. It summarizes records the other modules already hold. No data entry happens here. The public demo is limited to Dashboard, My Work, Coordinator, Inspections, Tasks, and Map; the full supervisor view across a live program is walked through on request.
01 · The supervisor view
Where does the program stand right now.
A stormwater supervisor preparing a council briefing, a public works status update, or a budget request needs the same information every time: how much work is on track, how much is overdue, how the annual report is shaping up, and where enforcement stands. MS4 Metrics is that view. The numbers come from inspection, IDDE, outfall, reporting, and enforcement records the program already keeps.
- Inspection coverage and overdue inspections by program
- IDDE incident activity for the reporting year
- Outfalls flagged by latest screening result
- Annual report readiness across all six MCMs
- Enforcement actions opened, closed, and outstanding
- Cadence drift across construction, post-construction, and good-housekeeping work
02 · Source modules
Records live in their own modules.
Every metric on this dashboard summarizes records that live somewhere else. A coordinator who clicks into a number lands on the underlying records inside the relevant module. The dashboard is a view, not a separate database.
- Inspections (construction, post-construction BMPs, source control, O&M, outfall screening)
- IDDE (complaints, incidents, source-tracing chronologies)
- Outfalls (inventory plus latest screening result)
- Annual Reporting (year state, answers logged, readiness rollup)
- Enforcement (notices of violation and resolution status)
Data entry stays in inspections, IDDE, outfalls, annual reporting, and enforcement. The metrics page renders what is already there.
03 · Honest about scope
What MS4 Metrics is and is not.
We would rather render the records honestly than invent a number that looks impressive in a screenshot.
What MS4 Metrics is
- A read-only supervisor snapshot built from records other modules already hold
- A supervisor-facing read of the program's own records: cadence, IDDE response, evidence-link readiness, and enforcement activity inside the tenant
- Filtered to a selected reporting year and the prior year for comparison
- Permit-aligned: every metric ties back to a specific MCM and the records behind it
- Useful for a stormwater coordinator preparing a status update for council, public works, or finance, and for an auditor or state-agency reviewer wanting source records behind each number
What MS4 Metrics is not
- Not a data-entry surface: records are created and edited inside their own modules
- Not an invented compliance score from fields no one filled in
- Not the annual report itself (the report lives in the reporting module)
- Not a replacement for the underlying program records it summarizes
- Not a cross-tenant benchmark: MS4 Metrics does not compare your program against other cities, and it does not score or rank inspectors
See it on sample data.
Open the demo to tour Dashboard, My Work, Coordinator, Inspections, Tasks, and Map, or request a guided walkthrough of this module.