If you are evaluating MS4 inspection software for a small or mid-sized Phase II program, the marketing materials are not going to help you much. Every vendor claims permit alignment. Most do not actually implement it. This post is a practical checklist for the questions to ask before signing anything.
The framing assumes a small city, county, or special district running Phase II under a state-issued general permit. The checklist works the same for adjacent state programs.
Does the form know what kind of inspection it is
A construction site inspection, a source control inspection, a vault inspection, an IDDE field visit, and a post-construction BMP inspection are not the same form. They share some fields and differ on most. Software that flattens all of these into one generic form is software that did not read the permit.
What to test: ask the vendor to walk you through three different inspection forms on sample data. If they are recognizably different forms, that is a good sign. If they are the same form with a “type” dropdown, that is not.
Does a deficient finding open a follow-up task automatically
The hardest record to defend at an audit is the finding that nobody followed up on. The inspection found the problem. Then what.
What to test: ask the vendor to show you what happens when an inspection finding is marked deficient. A follow-up task should open against the inspection, with a due date, an assignee, and a place for closure evidence. If the vendor has to “configure” this for you, the workflow is not native.
Do photos and GPS land on the record
Photos in a separate folder go missing. Photos on the record do not. The location pinned on the inspection should be the location where the photo was taken, not the location where someone uploaded the photo later.
What to test: walk through a sample inspection on a phone, take a photo, save the record, and reopen it. The photo should be there with a timestamp and coordinates.
Can the inspector capture in the field on a phone
A truck-friendly digital inspection workflow means a phone or tablet browser, not a desktop app installed on the inspector’s laptop. The form should work without juggling a separate app, and the connection back to the office side should be the same record.
What to test: open the inspection workflow on a mid-range phone over LTE. If the form takes more than a few seconds to load, the inspector is going back to paper.
Honest note: mobile web is the field workflow today on the products that handle this well. Some vendors claim native iOS or Android apps that are not actually shipped. Ask whether the iOS app is in the App Store and downloadable today, or planned.
Does the inspection record support field markups
Inspectors notice things the authoritative GIS does not know yet: a catch basin in the wrong place, a pipe alignment that drifted, a pond that was added. The right pattern is a separate exportable layer the inspector can draw on, distinct from the authoritative GIS that GIS staff maintain.
What to test: ask the vendor what happens when an inspector sees a missing catch basin in the field. If the answer is “they update the GIS layer,” walk away. The city’s source of truth should not be edited in the field. If the answer is “they draw it on a separate markup layer that exports to GIS,” that is the right pattern.
Does the software claim to send notices and letters automatically
Some vendors claim “automatic enforcement letters” or “real email sending from the platform.” Both of those are usually overstated. What the product actually does is draft from the inspection record. The send happens through the agency’s existing email or letter channel.
What to test: ask whether the product sends real email to a real recipient. If yes, ask how the address is verified and how the sent record is logged. If no, the product is drafting, not sending. That is the more common honest answer.
Do records export cleanly to CSV and GeoJSON
A state-agency reviewer asking for “every construction inspection on Site 04 between June and February” should get a clean CSV in two clicks. Same for spatial records: GeoJSON exports cover the inspection’s coordinates and the field markup layer.
What to test: export a small subset and open it in Excel and in QGIS (or ArcGIS Pro). The structured fields should map cleanly.
Does the annual report assemble from the records
For programs running the annual report in the same workspace, inspection counts should roll up automatically. MCM 4 construction inspections, MCM 5 post-construction BMPs, MCM 6 facility inspections. The reviewer should be able to click a count and see the source records.
What to test: ask the vendor to walk through the annual report assembly on sample data, in real time. If the workflow does not make sense in five minutes, it is not the workflow.
A pilot before the annual tier
A 60-day pilot on a focused slice of the program is the right way to evaluate. Configure the workspace to one permit framework, import a starter site list, run real inspections, and decide at day 60. The pilot should include a clean export if the city does not continue.
How NPDESTracker handles the checklist
The MS4 inspection software landing page lines up to this checklist. The broader cluster covers digital stormwater inspections, IDDE inspection software, source control inspection software, construction stormwater inspection software, and field inspection software for MS4 teams.
Try the demo to walk a sample inspection through the workflow, or start with the 60-day Guided Pilot at $999 on a slice of your own program.