Source control inspection software for MS4 programs.

One record per business inspection, with the findings, photos, BMP issues, and corrective actions linked together. Re-inspections schedule from deficient findings, so the inspector who shows up next month sees the history without digging through email.

Try the demo See pricing

01 · What source control covers

The business inspections that drive most stormwater findings.

Source control work is the day-to-day inspection program for businesses and commercial sites that touch stormwater. Restaurants with grease and dumpster issues. Auto shops with outdoor fluids and floor-drain concerns. Fleet yards with vehicle washing, fueling, and outdoor storage. Each one has its own inspection cadence, its own kind of findings, and its own pattern of follow-up.

The hard part is rarely the inspection itself. The hard part is keeping the photo, the finding, the corrective action, and the re-inspection on the same record over months. NPDESTracker holds the source control inspection as a typed record with structured fields, evidence attached, and an automatic re-inspection cycle when something needs to be checked again.

Restaurants and food trucks, where grease management and dumpster lid issues drive most findings
Auto repair and quick-lube shops, where outdoor fluids and floor-drain concerns come up
Dry cleaners and similar small industrial uses with chemical storage and disposal concerns
Fleet yards and equipment yards, where vehicle washing, fueling, and outdoor storage need attention
Property managers and HOA-owned facilities, where dumpster, landscape, and BMP maintenance show up
Commercial sites with outdoor material storage, painting, or pressure-washing activity

02 · The inspection record

The fields the work actually generates.

A good source control inspection produces a clear set of findings, a clear set of photos, and a clear set of corrective actions. NPDESTracker captures those as structured fields on a single inspection record, so the same record carries the history forward and the deficient findings drive the next re-inspection.

On every source control inspection

Business name, address, and site contact, with the inspection pinned on the map
Inspection type and inspection cadence (annual, semi-annual, complaint-driven, or follow-up)
Field observations on outdoor storage, dumpsters, drains, BMPs, and housekeeping
Photos of issues observed, attached directly to the inspection record
Findings list, separated into deficient findings and informational notes
Corrective actions with target dates, responsible party, and follow-up status
Re-inspection scheduling created automatically from open deficient findings
Closure note when corrective actions are verified, with timestamp and inspector attribution

03 · Corrective actions and re-inspections

The follow-up that usually slips through.

A finding without a follow-up is the most common breakdown in source control work. A restaurant gets a dumpster lid issue noted in May. The corrective action lives in an email. The re-inspection happens nine months later. By then, the original record is hard to find and the verification ends up paragraph-style and partly from memory.

NPDESTracker creates a follow-up task automatically when a deficient finding is recorded. The task has a target date, an assignee, and a link back to the inspection that generated it. The re-inspection happens against the original record, and the closure note ties the two together with a timestamp and inspector attribution.

04 · Map and site history

Every inspection lives on the site, not in a separate file.

Each business or commercial site has a record on the map with its address, contact, and inspection history attached. The next inspector who visits opens the site, reads the last two inspections, and walks in already knowing what was open. Repeat findings stay attached to the site, so a pattern at one property is obvious instead of buried in a folder.

The same spatial workspace holds outfalls, BMPs, and structures, so the source control inspection that turns up a discharge concern can link directly to the IDDE thread that follows. The full spatial story is on the GIS workspace page.

05 · Feeds MCM 6 annual reporting

Source control records become the annual report.

Counts of source control inspections completed, deficient findings, corrective actions verified, and re-inspections in the reporting year 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 source control 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 source control 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. The decision to escalate, the legal authority to enforce, and the agency response stay with the program and its legal counsel.

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

See the source control 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