Construction stormwater inspection software for MS4 programs.

Active site inspections, rainfall inspections, BMP observations, and corrective actions captured on one record per visit. SWPPP, contractor, and permit number stay on the site, so the next inspection picks up where the last one left off.

Try the demo See pricing

01 · What the work looks like

Construction inspections are a small program's biggest record stream.

A construction site under a Phase II MS4 program generates more inspection records than almost anything else the program runs. The cadence inspection schedule alone produces several visits per site, then a storm event triggers another round, then a deficient finding triggers a follow-up. Each visit produces photos, observations, BMP notes, and sometimes a corrective action that has to verify before the site moves on.

The hard part is keeping the chain together. The inspection from May 4th has to talk to the corrective action from May 11th, which has to talk to the verification on May 18th, on the same site, with the same SWPPP, under the same permit. NPDESTracker holds those records on one site, with the history visible at a glance.

Routine cadence inspections on active construction sites
Rainfall inspections triggered by storm events that meet the program threshold
Pre-construction inspections at site start, with the SWPPP and site map attached
Follow-up inspections on previously deficient BMPs or open corrective actions
Final inspections at site stabilization and project closeout

02 · The inspection record

Structured fields shaped around how the form is actually filled out.

A construction inspection on paper has a predictable shape: site, weather, BMPs observed, findings, corrective actions, photos, sign-off. NPDESTracker captures that as structured fields on a single record, with the photos and GPS attached to the BMP or location they belong to, not to a folder somewhere.

On every construction inspection

Site name, address, permit number, contractor of record, and SWPPP reference
Inspection type and trigger (cadence, rainfall, complaint, follow-up, closeout)
Weather and rainfall notes, with the date of the storm event when relevant
Erosion and sediment control observations: silt fence, inlet protection, stabilization, perimeter controls
Photos pinned to specific BMPs or site locations, with GPS captured at the inspection
Findings list separated into deficient findings and informational notes
Corrective actions with target dates, responsible party, and verification status
Re-inspection scheduling created automatically from open deficient findings
Inspector sign-off and timestamp on the completed inspection record

03 · Rainfall inspections

The visits that prove the program responded to storm events.

Rainfall inspections are some of the most important records a Phase II MS4 program keeps, and they are often the ones a state agency reviewer asks about first. NPDESTracker captures the storm event date, the inspection date, the weather notes, and the BMP observations on the same record. The connection between the rain and the inspection is on screen, not buried in a notebook.

When the annual report opens, rainfall inspection counts roll up from the records the team already kept. Linked evidence stays attached so a reviewer can verify the response time and the conditions observed.

04 · Corrective actions and follow-up

Deficient findings drive the next visit.

When a deficient finding gets logged on a construction inspection, NPDESTracker creates a follow-up task automatically, with a target date, an assignee, and a link back to the inspection that generated it. The contractor contact, the SWPPP, and the photo of the issue stay attached, so the verification visit walks in already knowing what to look for.

Verification gets recorded against the original finding, with a closure note, a timestamp, and inspector attribution. The chain from finding to verification holds, instead of breaking across a paper folder and an email thread.

05 · Feeds MCM 4 annual reporting

Construction records become the annual report.

Counts of construction inspections completed in the reporting year, deficient findings, corrective actions verified, and rainfall inspections come from the records, not from a number a coordinator types in. The full annual reporting story is on the reporting page, and the evidence side is on the evidence tracking page.

Inside the annual report workspace, Smart Draft is an assistive drafting feature that pulls from the linked construction records to help start a narrative answer. A coordinator reads the draft, confirms the totals, edits anything that needs judgment, and saves the final language. Smart Draft does not submit, certify, lock, or replace staff review.

NPDESTracker does not submit annual reports to any state or federal agency. The submission step stays with the human at the agency, on the agency's submission channel.

06 · Honest scope

What this does, and what it does not do.

NPDESTracker is a record-keeping workspace for construction stormwater inspections. It is not an emergency response platform, a 24/7 dispatch tool, or a public-safety system. It does not page on-call staff and it does not carry legal enforcement authority on its own. Stop-work orders, notices of violation, and other enforcement decisions stay with the program and its legal counsel; NPDESTracker holds the records of those decisions.

NPDESTracker does not promise compliance. Compliance is what the program does. The software is here so the inspection records hold up across staff turnover and audit cycles.

See the construction workspace on sample data.

The demo is browse-only with sample records. The Founder Pilot runs it on your own program for 90 days.

Try the demo Or read about the Founder Pilot