Outfall inventory and dry-weather screening: a working MCM 3 guide for small MS4 programs

The outfall is the unit of work for most of MCM 3. Every illicit discharge investigation starts at one. Every dry-weather screening cycle visits some subset of them. Every annual report counts the number screened and the number flagged. When an outfall inventory drifts out of sync with the storm sewer system the agency actually operates, the program loses the foundation that everything else in MCM 3 sits on.

This post is for stormwater coordinators at small Phase II MS4 cities trying to keep the outfall side of MCM 3 audit-defensible. What an inventory should contain, how dry-weather screening actually runs, what to record at each screening, how to distinguish suspect flow from confirmed illicit flow, and how the screening trail feeds annual reporting and IDDE chronology.

What an outfall inventory should contain

The minimum useful record for each outfall on a municipal MS4 inventory:

Identifier. A unique asset ID, not “the outfall behind the boat yard.” The ID does not change when staff change.
Location. Coordinates in a standard projection, plus a descriptive address or cross-streets for field use.
Type and structure. Pipe diameter and material, headwall or no headwall, outlet style, any energy-dissipation features.
Receiving water. The waterbody the outfall discharges to, and the segment if the receiving water has segmentation in the state water-quality framework.
Drainage area. The contributing basin, ideally as a polygon on the GIS layer.
Land use in the contributing area. Residential, commercial, industrial, mixed. Outfalls draining industrial areas warrant tighter screening cadence in most permits.
Known contributors. Industrial connections, permitted dischargers, prior cross-connections that have been corrected.
Inspection and screening history. Every screening, with date, inspector, indicator results, and any follow-up action.
IDDE incident history. Every incident that has ever been associated with this outfall, on a single timeline.

Programs frequently have most of this in pieces but not in one place. The GIS team has the spatial data. The stormwater team has the screening log. The IDDE incidents are in a separate tracker. Pulling the threads together is what makes the inventory operationally useful rather than a static asset list.

A current inventory is also where new outfalls have to land when the field finds them. Outfalls discovered during inspections, reported by residents, or revealed during construction projects need to enter the inventory promptly. Otherwise they do not show up in the screening rotation, and the gap between the field reality and the documented inventory grows over time.

Dry-weather screening cadence

Screening cadence is set by the permit. Common patterns for Phase II programs:

Quarterly screening on a rotation, with the full network visited over a defined cycle (often five years for the entire inventory).
Tighter cadence for priority outfalls. Outfalls in industrial areas, outfalls with prior IDDE history, or outfalls discharging to sensitive receiving waters often run on a faster cycle.
Wet weather coordination. Some permits require some screening to occur during wet weather as well as dry, with different observation criteria.
Annual full-network reporting. Even when the cycle is multi-year, the annual report typically asks for a summary of screening activity for the reporting period.

A program that runs cadence cleanly has the schedule visible at the start of the year, has a clear assignment of which outfalls are due in which quarter, and surfaces overdue items before the cadence breaks. Cadence drift is one of the most common audit findings on MCM 3 work, and it tends not to be discovered until reviewers ask for the full screening log. The general framing is in the stormwater inspection cadence guide.

What to record at each screening

A defensible screening record holds:

Date, time, inspector, and GPS confirmation that the inspector was at the outfall.
Flow conditions. No flow, intermittent, or active flow. Flow rate estimates if measured.
Visual indicators. Color, sheen, foam, floatables, deposits. Each captured as a structured field, not as free text in a single notes box.
Odor. Sewage, petroleum, chlorine, none. Same structured-field treatment.
Field measurements. Where the program collects them, pH, temperature, conductivity, dissolved oxygen.
Indicator panel results. If the program runs sampling at screening, the indicator values and any thresholds crossed.
Photographs. The outfall, the discharge point, any visible indicator. GPS metadata should attach automatically. The full photo guide is in the photo and GPS evidence post.
Classification. No observed discharge, suspect flow, or illicit flow.
Follow-up action. Whether the screening triggered a re-screen, an incident, or no further action.

The classification field is where most programs lose audit defensibility. A screening logged as “no discharge” with a photograph showing flow does not match. A screening logged as “suspect” with no follow-up action eight months later reads as a missed investigation. The classification has to match the observations, and the follow-up has to match the classification.

Suspect flow vs illicit flow

The two terms are not interchangeable, and the distinction matters for both the screening record and the downstream classification of any incident that follows.

Suspect flow is observed flow during a dry weather period that is not yet confirmed as illicit. It might be groundwater infiltration, irrigation runoff, foundation drainage, or a permitted non-stormwater discharge. The screening record should classify it as suspect and trigger appropriate follow-up: re-screening at a different time, sampling, or upstream investigation.

Illicit flow is flow that has been confirmed as a non-stormwater, non-permitted discharge. The classification belongs on the screening record only when the evidence supports it. Until then, the right classification is suspect, and the investigation continues.

Some flow is allowable under the permit even though it is not stormwater. Foundation drainage, water line flushing, and certain landscape irrigation typically fall in this category, but the specifics are in your permit, not in any general guide. The screening record should reflect the actual permit framework your agency operates under.

The transition from a screening with suspect classification to a formal IDDE incident is one of the moments where multi-record continuity matters most. The screening triggered the suspicion. The investigation that follows belongs on its own incident record, but it should link back to the screening that started it. Without that link, an auditor cannot reconstruct why the investigation was opened.

Follow-up investigations

When a screening is classified as suspect or illicit, the investigation that follows is its own thread. The screening is the trigger record, and it should link forward to the incident.

Investigation steps were covered in detail in the complaint-to-closure playbook. The short version: every upstream step (manhole opened, contributor inspected, sample collected, communication with another agency) belongs on the incident record. The screening is the starting evidence. The incident is the chronology.

Closure of the incident does not erase the screening trail. The outfall record should still show the original screening that triggered the investigation, the incident that followed, and the resolution. That history is what makes the next screening at the same outfall faster: the inspector arriving for next year’s cycle can see at a glance whether this outfall has had recent activity.

The full IDDE software-evaluation lens is in the IDDE tracking software post.

How outfall data feeds annual reporting

The MCM 3 section of the annual MS4 report typically asks for:

Number of outfalls in the inventory at the start and end of the reporting year
Outfalls added during the year (new construction, annexation, discoveries)
Outfalls removed (decommissioned, found to be private, reassigned)
Number of dry-weather screenings conducted
Number of suspect or illicit flows detected
Number of investigations opened
Number of incidents closed
Outstanding investigations carried into the next year

If the outfall inventory and screening log live in the same system, those counts come directly from queries on the underlying records. If they live in separate spreadsheets, every count is a reconciliation project, and the spring scramble is most of what shows up in MCM 3 reporting work.

The full reporting architecture, including how counts get derived from records and how overrides are audited, is on the reporting page. For the broader software-evaluation lens, see the MS4 annual reporting software buyer’s guide.

Where software helps and where it does not

Software does not run the screening. The inspector and the field staff do. Software does not classify a discharge. The inspector does, and the classification has to match the observations. Software does not legally compel a property owner to correct an illicit connection.

What software does is:

Hold the outfall inventory on a live map alongside parcels, sites, and incidents
Surface what is overdue on screening cadence before the cadence breaks
Capture screening records with GPS, photos, and indicator data at the moment of inspection
Link suspect or illicit screenings forward to investigations on a per-outfall timeline
Roll up the year’s screening activity into the MCM 3 section of the annual report

NPDESTracker handles the outfall inventory and screening trail this way. The full GIS workspace where outfalls live alongside the rest of the program is on the GIS workspace page, and the inspection workflow that captures field screenings is on the inspections page. The product is built around the Western Washington Phase II permit and adjacent state programs.

The fastest way to see how outfall inventory, screening, and IDDE thread together on sample data is the interactive demo. Pricing starts with the free demo and a $4,900 90-day pilot, with Starter annual plans from $8,000 a year for small Phase II MS4 teams up to 5 users.