Source control is the part of a municipal stormwater program that small staffs tend to under-resource. Construction sites have a clear permit cycle. IDDE has a complaint phone. Source control has a list of industrial and commercial sites that need recurring inspections, mostly without a forcing function.
This post walks through what source control inspection software should actually carry, in the working order an inspector encounters.
A site inventory you can keep current
The list of industrial and commercial sites in a small program tends to live in one of three places: a spreadsheet, a list of business licenses, or in the coordinator’s head. None of those scale across staff turnover.
A working source control workspace holds the site inventory with classification (auto shop, restaurant with grease handling, materials yard, fueling, vehicle wash), inspection cadence, contact, and inspection history. New sites flow in from business licenses or annexations. Closed sites get marked inactive without losing the inspection history.
Inspection forms shaped to the site
Source control inspections are not all the same. An inspection at an auto repair shop cares about used fluid storage, parts cleaning, and outdoor materials. An inspection at a restaurant cares about grease handling, dumpster lids, and outdoor cleaning practices. An inspection at a fueling station cares about spill response, secondary containment, and stormwater drains.
The structured form should match the site classification. A generic source control form forces the inspector to describe everything in a free-text note, which makes future reading hard.
Findings that turn into corrective actions
Most source control inspections find something. Not always serious, but something. A loose dumpster lid. An open container in a vehicle wash bay. A spill that was cleaned but not reported.
The finding should turn into a task with a due date and an assignee. The next inspector who walks the site sees the open finding. If the finding does not close in time, it bubbles up on overdue lists. Closure evidence attaches to the same record.
Re-inspection cadence after a deficient finding
A deficient finding usually means a re-inspection sooner than the routine cadence. Source control software should set the re-inspection date automatically based on the program’s rule (30 days, 60 days, whatever the policy says). The supervisor reviews the open re-inspections rather than rebuilding the list from email.
Enforcement actions tracked back to the inspection
Repeat findings, ignored corrections, and serious issues escalate. A warning, a correction request, a notice of violation, sometimes a stop work or fine. The enforcement record links back to the source control inspection that triggered it. The chronology stays intact for the annual report and any state-agency request.
The software does not send the notice or letter. Notice templates draft from the inspection record and copy or download as email-ready text. The send happens through your existing email or letter channel.
Field markups for missing assets at the business
Source control inspectors notice site features the city’s GIS does not know yet: a roof drain that was not in the inventory, a private storm drain inlet at the back of the lot, a grease interceptor location.
The right pattern is a separate exportable layer the inspector draws on, distinct from the authoritative GIS. The markup exports as GeoJSON for the GIS team to review and merge on their own schedule. The city’s source of truth stays under GIS staff control.
Annual report tie-in
Source control inspections feed MCM 6 of a Phase II MS4 annual report. Inspection counts roll up automatically from the records on the Full MS4 Platform tier. On the Inspection Starter or Inspection Team tier, inspection records export as CSV / GeoJSON for whatever annual reporting process the city uses.
How NPDESTracker handles source control
The source control inspection software landing page covers the workflow in more detail, including the form per classification, the re-inspection cadence, and the corrective-action chain. The broader cluster covers MS4 inspection software and stormwater inspection software.
Try the demo to walk a sample source control inspection on a fictional industrial site. The 60-day Guided Pilot at $999 is the most common starting point for a small program that wants to test the workflow on its own site list.