What small MS4 programs need from compliance software

If you work at a small municipal stormwater program, you probably wear about four hats. Some weeks five. The compliance work is real, the staffing is small, and the tools were never designed for the job.

This post is about what small and mid-sized Phase II MS4 programs actually need from compliance software. Not the polished sales answer. The version a working coordinator would describe at the end of a long day.

Small MS4 teams are stretched thin

A lot of small Phase II programs are running on one or two people doing nearly everything. The same person who shows up at a public works open house at 6 PM is the same person who walks the bioswales the next morning and writes the annual report in March.

That is not a complaint. That is the reality, and it shapes what kind of software actually helps. Anything that takes more than a few minutes to learn loses. Anything that adds a separate place to log into loses. Anything that needs another full-time admin to maintain, loses harder.

The right software for a small MS4 program respects how thin the team is. The records should be quick to enter. The map should be quick to open. The audit trail should be there without anyone configuring it.

Spreadsheets work, until the program grows

Most small programs start on spreadsheets. Spreadsheets are honestly great. They are also the reason annual reporting feels like an archeology project every spring.

A typical stack at a small Phase II city looks like this:

A spreadsheet for inspection counts
A folder of inspection PDFs on a shared drive
An inbox of IDDE complaints
A binder of enforcement letters
A separate spreadsheet for the post-construction BMP inventory

That stack works. Until the program grows. New permit cycle. New inspector. A reviewer asks how a finding from last November got resolved. Suddenly the spreadsheet is the only person who knows, and that person is busy.

The first thing that breaks is the link between an inspection and what came after it. The inspection PDF lives in one folder. The deficient finding lands in a follow-up spreadsheet. The closure email is in someone’s inbox. Six months later the chain has to be reconstructed from memory.

The second thing that breaks is the cadence. A spreadsheet does not warn you that catch basin 04CB17 is twenty days overdue. The program drifts past due dates in the quiet way.

The third thing that breaks is staff turnover. The mental model of where everything lives walks out the door with the person who built it. Software that requires that mental model to be in someone’s head is not really software. It is a person.

Why records need to connect

The clearest way to think about MS4 compliance software is as a graph. Records connect. The shape of those connections is most of the value.

A small program is generating these records every year:

Construction site inspections during active build-out
Source control inspections at industrial and commercial sites
IDDE complaints, screening visits, source-tracing, and closure
Outfall inspections paired with dry-weather screening
Drainage structure inspections (catch basins, manholes, vaults)
Post-construction BMP inspections on accepted assets
Operations and maintenance inspections at municipal facilities
Public Education and Outreach (MCM 1) activities
Public Participation (MCM 2) meetings and events
Tasks and corrective actions on deficient findings
Enforcement actions and notices of violation
Training records

Software earns its keep by holding all of this in one place and connecting it. Not as one giant table. As typed records that know how they relate to each other.

A construction site has a project, a SWPPP, a contractor, a series of inspections, and a closure date. That is one record with relationships, not a row in a spreadsheet.

An IDDE complaint opens a thread. Screening visits, source tracing, samples, and enforcement actions all hang off the original complaint. The chronology is obvious from the record itself.

A post-construction BMP carries an as-built reference, a responsible party, and an inspection history forever. It is a long-term obligation, not a checkbox.

The annual report is what happens when those records connect properly. Counts come from the actual records. Each question on the report can link to the inspections, BMP records, IDDE incidents, and enforcement actions that support it. The longer take is on the annual reporting page, and the program-level overview is on the MS4 compliance software page.

GIS context, without trying to be a GIS platform

Stormwater is spatial. The program is anchored to specific physical things in specific places. So the map matters.

A coordinator should be able to open a map, click an outfall pin, and see the screening history. Click a BMP, see its inspection history. Click a construction site, see the active cadence.

That is GIS-aware compliance software. It is not a GIS platform. The city’s authoritative spatial data should stay in ArcGIS Online, ArcGIS Enterprise, or QGIS. The compliance software should sit beside that, read and write standard formats, and not try to be the source of truth for the storm drain network. The longer take is in MS4 software vs ArcGIS. The product page is on the GIS workspace page.

Evidence matters more than fancy dashboards

A lot of compliance software shows you a “92% compliant” gauge calculated from fields no one filled in. That number is fiction. It looks good in a council briefing and falls apart in an audit.

What an MS4 program actually needs is the evidence underneath. Photos and GPS pinned to inspections. Tasks that close with the proof of how they closed. Audit trails on key compliance records and reporting actions. The “what changed and who changed it” answer on screen, not in someone’s head.

When a state-agency reviewer asks about any number in the annual report, the underlying records should be one click away. That is what evidence-backed records mean. It is the unglamorous version of compliance, and it is the version that holds up.

What to ask before buying software

If your team is evaluating MS4 compliance software, here are the questions I would actually ask. Forget the marketing checklist.

Does the software know the permit? Does it ship with the right MCM structure, the right question prompts, and an annual report template that matches your state’s actual permit? Or does someone have to assemble that from scratch?

Does the field workflow survive a real day in the field? Mobile-friendly forms, photo and GPS evidence, structured fields. The inspector in the truck should not need a separate app to install.

Do deficient findings actually go somewhere? A finding that opens a follow-up task with a due date and an owner is doing the job. A finding that lands in a free-text note is not.

Are records typed, with audit trails? Create, edit, and override events should be timestamped and attributed. The audit story should be on screen.

Does the report assemble from records? Or does someone retype counts every March from five different places?

Are exports honest? CSV exports for supported operational records is a real promise. “Export anything in any format” is usually not. Ask for specifics.

Does the security page tell the truth? A page that says what controls are held and which are not held is much safer than a page full of vague assertions.

Is AI scoped honestly? AI-assisted drafting on long-form questions can save real time. The vendor should be able to explain when it calls an external AI provider, what data is sent, how to disable it, and what the human still has to review. AI features that submit, certify, or replace staff review on the annual report should be a hard no.

Is the team accountable? A small product where the buyer can email the founder is usually a better fit for a small program than an enterprise sales process.

The shortcut version of all of this: ask the vendor to walk through the annual report assembling on sample data, in real time. If the workflow does not make sense in five minutes, it is not the workflow.

How NPDESTracker fits

For a small Phase II MS4 program looking at this stuff, NPDESTracker is built first for you. Two paths run from here.

Annual Platform is the main product, built around the full MS4 program. Inspections, IDDE, outfalls, BMPs, tasks, Public Education (MCM 1), Public Participation (MCM 2), MS4 Metrics, GIS, and the annual reporting workspace, all in one place. The annual report assembles from the records logged through the year. Counts come from the records. Each question can link to its supporting evidence. There is also Smart Draft, an assistive drafting feature that turns linked evidence into a starting-point draft for a coordinator to edit and save. Smart Draft does not submit, certify, lock, or replace staff review. The full posture is on the Smart Draft page and the Smart Draft and AI disclosure. Annual Platform starts at $13,000 a year.

Inspection + GIS Starter is for teams that already handle annual reporting somewhere else and just need a workspace for inspections, GIS, assets, corrective actions, attachments, and exports. It is a different workspace with a different scope, not a smaller version of the Annual Platform. From $7,500 a year. The full description is on the Inspection + GIS Starter page, and the search-intent overview is on the stormwater inspection software page.

NPDESTracker does not submit annual reports to Ecology, EPA, or any state agency on a customer’s behalf. The submission step stays with the human at the agency, on the agency’s submission channel.

Where to look next

If a sales-page version of this is more useful than a blog post, the MS4 compliance software overview covers it.

If you want to see the workspace itself, the interactive demo is browse-only, sample data, no signup. Open the inspection workflow and the GIS view side by side and see whether the shape matches how your program runs.

Pricing covers the Founder Pilot at $2,500 and Standard Pilot at $4,900 for 90-day evaluations, the Inspection + GIS Starter at $7,500 a year for inspection-only teams, and the Annual Platform from $13,000 a year for the full annual reporting cycle.

The work small MS4 programs do is real. The audits are real. The deadlines are real. I hope the workflow gets a little easier this year than last.