MCM 3 inspection workflow for Phase II MS4 programs

IDDE inspection software

IDDE Inspection Software for MS4 Programs.

Keep the complaint, the field check, the source-tracing visits, the sampling, the follow-up, and the closure on one thread per incident. Photos and files attach to every visit. Enforcement records link back to the case that triggered them.

Open the sample workspace View pricing

01 · Who this is for

IDDE coordinators and inspectors running MCM 3.

For the IDDE coordinator who answers the complaint phone, the inspector who drives out for the first field check, the supervisor who tracks open cases across the program, and the program manager who has to summarize MCM 3 at the end of the year. Background on the workflow itself is in the IDDE complaint-to-closure playbook.

The 60-day Guided Pilot at $999 is a focused way to test the IDDE workflow on a slice of your program. The annual inspection tiers carry IDDE alongside Source Control, Construction, and O&M.

A look at the workspace

See how a sample MS4 workspace connects sites, inspections, tasks, contacts, enforcement drafts, GIS context, and reporting evidence.

Open the sample workspace to walk it on fictional Phase II data.

02 · IDDE visits supported

Every visit kind, on the same case.

The chronology survives because each visit attaches to the original case. The broader IDDE workflow is detailed on the IDDE tracking software page, and the field-screening side is on the outfall inventory and dry-weather screening guide.

IDDE visit kinds

Complaint intake at the moment the report comes in
Dry-weather screening visits with the indicator panel
Source-tracing visits up the storm drain line
Sampling visits with sample results recorded on the case
Follow-up and re-screening visits after a flagged finding
Closure with verification on the same case record

03 · What inspectors do

One case, every visit attached.

The first field check, the source-tracing trips up the storm drain line, the sampling visit, the re-screening, the closure walk. Each one lands on the same case record with photos, GPS, and the inspector's notes. The next visit reads the prior visits as context.

Each IDDE visit carries

One case record per incident with the full chronology
Site, outfall, and structure context on the map
Photos and files attached to every visit
Tasks for follow-up visits and re-screening
Field markups for suspected source locations as an exportable layer
Draft notice templates for illicit discharge notices and correction requests
CSV and GeoJSON exports of cases, visits, and evidence

04 · What supervisors see

Open cases that should not drift.

Supervisors see what is open, what is overdue for follow-up, and which cases are waiting on closure verification. Enforcement actions link back to the case that triggered them so the chronology stays intact through the annual report and any state-agency request.

What supervisors see

My Work view that surfaces open cases each user owns
Overdue follow-ups and re-screenings across the program
Enforcement tracking linked to the case that triggered it
Closure verification on the original case before it leaves the open list
Exportable case histories for state-agency requests

Scope: NPDESTracker does not submit reports to any state agency and does not certify compliance. Smart Draft is assistive — staff review every save. See Terms and Smart Draft disclosure for the full posture.

06 · FAQ

Frequently asked questions.

Honest answers to the questions that come up most often.

What is IDDE inspection software?

Software that keeps the IDDE chronology on one record per incident. The complaint, the first field check, source-tracing visits, sampling, follow-up, and closure all attach to the same case, with photos and GPS on every visit. Designed for MCM 3 of a Phase II MS4 program.

How does the IDDE workflow stay on one thread per incident?

Each visit attaches to the original complaint record. The next inspector reads the prior visits before going out. The chronology survives staff turnover and audit requests because the case carries every screening result, photo, sample finding, and field note in order.

Can the software escalate an IDDE case to enforcement?

Enforcement records can be linked to the case that triggered them. The chronology is preserved so the original complaint, the screening visits, the source-tracing, and the enforcement action read as one continuous record. The product does not auto-send any notice or letter.

Does the demo show an IDDE case?

Yes. The public demo includes a sample IDDE incident on a fictional tenant, walking through complaint intake, field screening, source-tracing, and closure. Browse-only, no signup.

How do field markups work for suspected source locations?

Field markups land on a separate exportable layer rather than the authoritative GIS. An inspector can mark a suspected illicit connection or a pipe of interest during a source-tracing visit. The markup exports as GeoJSON for the GIS team to review.

How does this compare with general IDDE complaint tracking?

NPDESTracker is built around the IDDE case as the central record rather than the complaint ticket. The broader complaint-tracking framing is on the IDDE tracking software page; this page is focused on the inspection visits that document the case.

Related inspection software pages

The rest of the inspection cluster.

Each page covers a focused slice of the inspection workflow. Pricing is the same across the cluster: the 60-day Guided Pilot at $999, then Inspection Starter or Inspection Team for the annual tier.

Also see pricing and the demo.

Walk an IDDE case on sample data.

Open the sample workspace to walk the IDDE case thread on a fictional complaint, or view pricing for the Guided Pilot and annual tiers.