MS4 inspection software: what a small program actually needs from it

If you work in a small or mid-sized stormwater program, you already know that inspections are the part of the job that touches almost everything else. Construction sites, outfalls, BMPs, source control, IDDE follow-ups. They all start with someone in a truck looking at something, taking a few photos, and writing it down somewhere.

This post is for the people who do that. Coordinators at Phase II MS4 cities. Inspectors who carry a clipboard and a phone. Public works directors trying to get their program on a system that does not fall apart when one person leaves.

I want to walk through what good MS4 inspection software should actually help with. Not the marketing version. The version a working coordinator would describe over coffee.

What MS4 inspections usually involve

A small Phase II program is doing more inspections than people outside the program think. A typical year touches:

Construction site inspections during active build-out, often weekly or biweekly while a site is open
Source control inspections at industrial and commercial sites that handle materials of concern
Operations and maintenance inspections at municipal facilities (yards, fueling stations, fleet wash bays)
Catch basin, manhole, and vault inspections on a structure cadence
Outfall inspections, often paired with dry-weather screening
Post-construction BMP inspections on bioswales, vaults, ponds, infiltration trenches
Follow-up visits when the first inspection turned up a deficient finding

Each one looks a little different. A construction site inspection cares about silt fence, concrete washout, and stockpile cover. A vault inspection cares about whether the sump is half full of grit. A bioswale inspection cares about ponding depth, clogging, and vegetation health. Generic inspection apps tend to flatten all of this into “did you find a problem? yes or no.” That is not how the work goes.

Why spreadsheets and shared folders get hard to manage

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

A typical small-program stack looks something like:

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 BMP inventory

That stack works. Until it does not.

The first thing that breaks is the link between an inspection and what came after it. The inspection PDF is in one place. The deficient finding is in a follow-up spreadsheet. The closure letter is in someone’s email. Six months later, when the state-agency reviewer asks how that finding got resolved, the answer is held in someone’s head.

The second thing that breaks is the cadence. A spreadsheet does not warn you that catch basin 04CB17 is twenty days overdue for its annual inspection. By the time anyone notices, the year already shifted.

The third thing that breaks is staff turnover. The mental model of where everything lives goes out the door with the person who built it. That part is rough.

None of this is the program’s fault. It is what happens when general-purpose tools are asked to do permit-aligned work.

How sites, outfalls, structures, inspections, photos, and tasks connect

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

A useful workspace holds:

Sites. Each construction project, source control facility, or municipal yard is a site. The site has an address, a parcel, a classification, an ownership record, and a history of inspections logged against it. Open the site, see every inspection on a clean timeline.

Outfalls. A live inventory with location, receiving water, and a screening history. When an IDDE complaint traces back to an outfall, the outfall record is where the chronology lives.

Drainage structures. Catch basins, manholes, vaults. Each carries a maintenance and inspection cadence. The system knows which ones are due, which are overdue, and which were just walked.

BMPs. Every post-construction BMP the city has accepted is a long-term obligation. Each one needs an as-built reference, a responsible party, and an inspection history.

Inspections. A typed record per kind, with the right structured fields. Photo and GPS evidence pinned to the record. A clear distinction between site-level work (the project) and structure-level work (the catch basin or BMP).

Tasks and corrective actions. When an inspection turns up something deficient, a follow-up task opens against the record. Due date, assignee, closure evidence. The work the deficient finding caused is visible and trackable, not lost in someone’s email.

Follow-up records. Re-inspections, notices of violation, compliance schedules, and closure documentation, all linked to the original finding.

The point of all of this is that you can answer two questions on the spot. What was found? What happened next? If your software cannot answer both questions in two clicks, the spreadsheet is winning.

Why GIS context matters

Stormwater is spatial. The program’s job 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 when it was last inspected and whether the last finding was closed. Click a construction site, see the active inspection cadence.

That is not a GIS platform. That is GIS-aware compliance software. A real GIS platform like ArcGIS Online or QGIS is great for what it is great at: maintaining the city’s authoritative spatial data, hydraulic modeling, public-facing maps. The compliance software should sit beside that, not try to replace it. The longer take on this is in the MS4 software vs ArcGIS post.

What I want from the GIS view is not analytics. I want to find the record fast and trust the location it was logged against.

How inspection records support annual reporting

This is where MS4 inspection software earns its keep at the program level.

A Phase II annual report asks for counts. Construction inspections in the reporting year. Post-construction BMPs inspected. IDDE incidents resolved. Facility inspections completed. Training events delivered.

If the inspection records already carry the right shape (date, kind, site, finding, closure), the counts come from the records themselves. No retyping. No “let me dig through the folder.”

When a customer is on the Annual Platform, inspection records also feed into an evidence workspace where each annual report question links directly to the inspections, BMP records, IDDE incidents, and enforcement actions that support it. There is also an assistive drafting feature called Smart Draft that turns linked evidence into a starting-point draft of an answer. A coordinator reads the draft, edits it, and saves the answer. Smart Draft does not submit, certify, lock, or replace staff review. The full description is on the Smart Draft page and the Smart Draft and AI disclosure.

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. That posture matters for procurement, and I think it is the right one.

Inspection + GIS Starter vs Full MS4 Platform

Two distinct offers. They are different workspaces with different scopes, not a smaller-bigger pair.

Inspection + GIS Starter is for teams that handle annual reporting somewhere else and just need a workspace for field inspections, GIS, assets, corrective actions, attachments, and exports. From $7,500 a year. The Starter includes the inspection workflow, the GIS map, sites, outfalls, structures, BMP inventory, tasks, photo and GPS evidence, audit trails on key records, and CSV exports for supported operational records.

Annual Platform is the full MS4 program workspace. It is the main product, built around the full annual reporting cycle for small and mid-sized Phase II MS4 permittees. From $13,000 a year. It adds the annual report evidence workspace, Smart Draft, Public Education and Public Participation modules (MCM 1 and MCM 2), MS4 Metrics, certification capture, the print-friendly annual report preview, and permit-specific report templates. Plus everything in Inspection + GIS Starter for the inspections side of the program.

The honest version: if the agency wants annual reporting in NPDESTracker, the Annual Platform is the right tier. If the agency just wants a clean, audit-ready inspection workspace and handles the annual report another way, the Starter is built for that. Either way the platform is the same underneath. Same tenant isolation, same role-based access, same audit trails on key records.

A short buyer checklist for MS4 inspection software

If your team is evaluating, here are the questions I would actually ask. Not the marketing checklist.

Does it know the difference between an inspection kind? Construction, source control, structure, outfall, BMP, facility. Each one needs its own form, not a single generic template.

Can field staff capture photos and GPS without juggling a separate app? Browser-based with mobile-friendly forms is fine. Inspectors will not install one more thing.

Does a deficient finding actually go somewhere? A finding that creates 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 “who changed this and why” answer should be on screen.

Does the map help find a record? Or is the GIS view a sales screenshot that nobody actually uses day to day?

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 vendor say what they do not do? A page that names what is held and what is not held tells you more than a page that promises everything.

Does the inspection workflow connect to annual reporting? If the agency wants both in one place, ask whether inspection records actually feed the annual report or whether they live in a separate system. Does the report assemble from records, or does someone retype counts?

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.

Where to look next

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

If you want to see the inspection workflow itself, the inspections page and the GIS workspace page walk through what is in the product.

If you want to evaluate the fit on your own, 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 small and mid-sized Phase II MS4 permittees doing the full annual reporting cycle.

If you have questions about whether a small program is even at the point where it needs software, that question gets a real answer in when does a small MS4 program actually need software.

Whatever path you take, I hope the workflow gets a little easier this year than last. The work is real and the people doing it deserve tools that respect that.