Construction stormwater inspections are the part of an MS4 program with the most volume during build-out season. A small Phase II city with active development is doing weekly inspections at half a dozen sites, plus rainfall-triggered inspections whenever a storm event meets the program threshold.
This post is for the construction inspector, the supervisor managing the program through build-out season, and the program manager who has to assemble the MCM 4 numbers at year end.
Routine cadence inspections
The baseline cadence at an active construction site is weekly (or biweekly for some programs) while the site is open. The inspector walks the site, checks the BMPs, photographs the conditions, and writes up what they saw.
A useful construction inspection workspace shows the inspector the prior week’s finding before they start the new inspection. If the silt fence was sagging last week, that is the first thing to check this week. The form is shaped by what is already on the record.
Rainfall-triggered inspections
A rainfall event over the program threshold (commonly 0.5 inch in 24 hours, but programs vary) triggers an additional inspection. The rainfall inspection is a distinct kind of record from the routine weekly walkthrough.
The inspection record should capture the rainfall trigger, the rainfall amount, the date and time, and the BMPs inspected. A program that flattens rainfall inspections into the same form as routine inspections loses the ability to filter rainfall events out at year end.
SWPPP, contractor, and permit attached to the site
The site record should carry the SWPPP, the contractor of record, the permit identifier, and the inspection history. When the inspector arrives, they see what the SWPPP requires. When the auditor reads the record later, they see which contractor was responsible for the BMPs at the time of the inspection.
The contractor information matters for enforcement. If a finding escalates to a correction request, the request is addressed to the contractor on the record at the time of the finding.
BMP findings on one record per visit
Each inspection covers a list of BMPs: silt fence, concrete washout, inlet protection, stockpile cover, stabilized construction entrance, slope stabilization, perimeter controls. The form should let the inspector mark each BMP as compliant, deficient, or not applicable, with photos and notes per BMP.
A finding marked deficient opens a corrective action task tied to the inspection. The task carries a due date and an assignee. The next inspection should confirm closure or escalate.
Corrective actions and re-inspections
A deficient BMP usually means a corrective action and a re-inspection sooner than the routine cadence. The re-inspection date should be set automatically by the program’s rule (often 48 to 72 hours for active deficiencies on construction sites).
If the corrective action does not close on the next visit, it stays open. Overdue corrective actions bubble up on the supervisor’s program view.
Enforcement tied back to the construction inspection
Repeat findings, ignored corrections, or serious BMP failures escalate. The enforcement record links back to the construction inspection that triggered it. The chronology stays intact through the annual report and any state-agency review.
Notice drafts always support copyable or printable delivery. Direct email delivery, reply capture, and retained correspondence history are deployment-dependent and confirmed during setup; do not assume those capabilities are included unless they are named in the order.
Photos with GPS, on the record
A photo of a failed silt fence is what the record needs. Photos belong on the inspection record at the moment of capture, with GPS pinned. A photo in a separate folder on a shared drive is a photo that will not be there in 18 months when someone needs it.
Annual report tie-in
Construction stormwater inspections can support MCM 4 reporting when the applicable annual-report template and purchased scope have been independently verified. Supported export formats depend on the modules included in the order and are confirmed during setup.
How NPDESTracker handles construction stormwater
The construction stormwater inspection software landing page covers the workflow in more detail, including the rainfall-triggered inspection pattern, the SWPPP and contractor attachment, and the corrective-action chain. The broader cluster covers MS4 inspection software and stormwater inspection software.
The public demo unlocks Dashboard, My Work, Coordinator, Inspections, Tasks, and Map on a fictional tenant; it is read-only except for Map, and dedicated creation and notice workflows are locked. Explore demo for that tour, or start with the 60-day Guided Evaluation at $999 to test the construction inspection workflow on your own sites.