In a small or mid-sized Phase II program, the MS4 coordinator is often the person who holds the whole thing together: the permit, the program document, the inspections other people perform, the outreach calendar and the annual report. Sometimes that is a full-time role. Often it is one of several hats the same person wears.
This post is about what that person actually needs. It starts from what the permit asks of the program and works toward the kind of help that is worth paying for. It is written for coordinators, and for the managers deciding how to support them.
What the permit asks of the program
The federal rule for small MS4 permits is a good map of the job, even though your state’s permit adds its own details. Under 40 CFR 122.34, a small MS4 permit must:
- be written in “clear, specific, and measurable” terms;
- require a written stormwater management program document that describes how the permittee will meet each minimum control measure;
- cover six minimum control measures: public education and outreach, public involvement and participation, illicit discharge detection and elimination, construction site runoff control, post-construction stormwater management, and pollution prevention and good housekeeping for municipal operations;
- require the permittee to evaluate its own compliance and the effectiveness of its program;
- require records to be kept for at least three years and made available to the public; and
- require reports that cover the status of compliance, the results of information collected, the activities planned for the next cycle, and any changes to the program.
Notice how much of that is about evidence. The coordinator’s job is not only to run the program. It is to be able to show, at any point in the year, what the program did and what it plans to do next.
A coordinator’s year
Every permit sets its own dates, so check yours, but most coordinators recognize a rhythm like this:
- All year: construction inspections while sites are active, complaint response, follow-up on findings, and questions from other departments.
- On a cycle: dry-weather outfall screening, post-construction BMP inspections, municipal facility inspections, and catch basin and structure maintenance.
- Seasonal: outreach campaigns, public meetings and comment periods, and staff training.
- Reporting season: pulling the year together, reviewing it with management, and submitting the report by the permit’s deadline.
- Every few years: a permit reissuance, with new requirements to read, map to the program and plan for.
The hard part is rarely any single task. It is that all of them run at once, and the evidence for each one tends to land in a different place.
What a coordinator needs
One place where each obligation lives, with its source. The program document says what you committed to; the permit says what you must do. When a requirement is in front of you, you should be able to see which page of the permit it came from, so you never have to wonder whether a task is required or just a habit.
Records that connect. An inspection, its finding, the follow-up task, the notice and the closure should be one chain, not five files. That is what makes the question “what happened next?” answerable in a minute. The full chain is walked through in from field observation to annual report.
A view of what is due. Overdue and due-soon items, by program and by person, before they turn into a finding. A spreadsheet will not warn you that a structure is twenty days late. A system can.
Delegation that stays visible. Inspectors, crews and other departments do much of the work. The coordinator needs to assign it, see it and follow up without chasing email threads.
Evidence ready at report time. Counts that come from the records themselves, evidence linked to each answer, and changes that leave a trail. The annual report should be a review of the year, not a rebuild of it.
Continuity. When a coordinator moves on, the program should not move with them. Records, history and the reasons behind decisions belong in the system, not in one person’s memory.
Honest tools. A “92% compliant” score calculated from empty fields is worse than no score at all. The coordinator needs tools that show what is missing as plainly as what is done.
What a coordinator does not need
- Another login that holds a separate copy of the same data.
- A dashboard nobody trusts, because nobody knows where its numbers come from.
- Software that claims to make the program compliant. No software does that. Compliance is what the program does; software helps it prove the work happened.
- A tool that needs a full-time administrator the program does not have.
Habits worth dropping
A few habits cost coordinators the most time, and most programs can drop them once the records are connected:
- Rebuilding the year from spreadsheets and inboxes in the weeks before the report is due.
- Keeping field photos on personal phones until someone remembers to upload them.
- Re-typing counts that already exist as records somewhere else.
- Tracking due dates in someone’s head, on a whiteboard, or in a personal calendar.
- Writing narrative answers from memory instead of from the records behind them.
Where software helps, and where it does not
Software is good at remembering, connecting and counting. It is good at telling you what is overdue and at keeping the evidence attached to the work. It is not good at judgment: deciding whether a finding is serious, whether a source is identified, or how to read an ambiguous permit condition. Those stay with the coordinator and the program’s leadership.
A useful test when you look at any tool: ask the vendor to follow one inspection from the field to the annual report, on sample data, in a few minutes. If the chain holds together, the tool will save you time. If it does not, it will add work.
How NPDESTracker fits
NPDESTracker is built for Phase II programs, with the coordinator’s job in mind. The Coordinator and My Work views show what is open and who owns it. Inspections, follow-up tasks and notices stay on one record. In the Full MS4 Platform, the annual report reads from those records, with evidence linked to each answer. We configure the workspace to your permit framework and walk your team through it; how it works describes onboarding.
The annual report template implemented in the product today is the Western Washington Phase II template. For other permits, the template is built and verified before Annual Reporting is switched on.
The public demo (opens in a new tab) includes the Coordinator, My Work, Inspections and Tasks views on fictional data. It is read-only on our side: an inspection you assign there is kept in your browser, and nothing you try there is saved on our servers or sent. To see the workflow on your own program, request a private demonstration. The MS4 compliance software page covers the product as a whole, and the MS4 overview is a plain-language primer for anyone new to the program.
Sources checked October 17, 2026.