Reporting
Every number in your annual report links back to a record.
Counts come from the inspections, tasks, and enforcement records you already keep — not from a "compliance score" we invented. Override any value with a one-line audit-log entry.
01 · How rollups work
We count what you record.
Most MS4 software wants you to type your counts straight into the annual report — or generates a compliance score from fields it half-populated. NPDESTracker takes the opposite approach: every count in the report is computed from the underlying records logged through the year. If you ran 14 construction inspections last quarter, the report sees 14, traceable to those 14 records. The full inspection workflow is detailed on the inspections page.
Counts roll up from
- Construction site inspections
- Post-construction BMP inspections
- IDDE complaints, screenings, and source-tracing records
- Public education events and outreach activities
- Public involvement records and meeting minutes
- Municipal facility inspections and good-housekeeping logs
- Enforcement actions and notices of violation
- Staff training records
02 · Annual report
The annual report is a view of your year, not a separate document.
Each MCM section in the annual report rolls up automatically from the workflow that feeds it — IDDE incidents into MCM 3, construction inspections into MCM 4, post-construction BMPs into MCM 5, public outreach events into MCM 1.
State-agency line items map to the actual records, not to free-text fields you fill in twice. When August comes, the report is already assembled. You're reviewing it, not building it.
03 · Override + audit log
You can override any number — and the override leaves a trail.
Sometimes a count needs a manual adjustment — a record was logged in the wrong year, an inspection happened but never got entered, a duplicate slipped through. Every override creates a one-line audit-log entry with the user, timestamp, original value, new value, and the reason. State-agency reviewers see exactly what was changed and why.
04 · Honest scope
No invented compliance scores.
A lot of MS4 software displays "92% compliant" calculated from fields no one filled in. That's a false signal — it hurts your program in an audit and misleads council. NPDESTracker shows the records you have, the records you don't, and what's outstanding. Nothing more.
What you'll see
- Records you actually logged
- Counts derived from those records
- Overdue and due-soon items, by program
- What's complete, what's outstanding, what's flagged for review
What you won't see
- An invented "compliance score" calculated from fields you didn't fill in
- Zeros pretending to be data for programs you haven't configured
- Traffic-light theatre that hides where the program actually stands
- Year-over-year deltas computed from records that don't exist yet
05 · Readiness rollup
See where you stand for the year.
A program-level readiness view shows what's complete, what's overdue, what's flagged for review, and what's not yet started — across all six MCMs. Cadence-aware, so quarterly and annual obligations are surfaced before the deadline rather than after.
No traffic-light theatre. No manufactured percentages. Just what's in the records, on a timeline you can act on.
See it run.
Open the demo and try the daily workspace with sample data. Browse-only, no signup, no call.