The post-construction BMP is the asset most municipal stormwater programs are most likely to lose. Not “lose” in the sense that it gets stolen. Lose in the sense that the program forgets it exists. The BMP is still there, on a parcel somewhere, doing its job until it does not. It just stops appearing on the inspection list, drops out of the annual report, and shows up again only when something fails or an auditor asks.
This is the most common pattern in MCM 5 audit findings. Not bad inspections. Missing inspections, on assets the program no longer knows it owns.
This post is about how that happens, what a defensible BMP record looks like, and how to keep the inventory current across the staff transitions that almost always cause the loss.
How BMPs go missing
Post-construction BMPs enter a municipal inventory through development. A new subdivision installs a bioretention cell. A redevelopment retrofit adds a permeable pavement section. A commercial site builds a detention pond. The BMP is part of the development approval, gets installed during construction, gets accepted at closeout, and is supposed to land in the city’s stormwater asset inventory.
The handoff is where most BMPs die.
Common loss patterns:
The handoff never happens. Construction closes out, the engineer signs off, the as-built drawings get filed, and nobody updates the BMP inventory because no one person owns that step. The BMP exists physically and legally, but operationally it does not.
The handoff happens to a spreadsheet only one person knows. The coordinator who maintained the BMP spreadsheet for eight years retires. The spreadsheet is somewhere on a shared drive. New coordinator finds it eventually. Two reporting cycles have passed.
The BMP is private but the city is responsible for inspecting it. Many post-construction BMPs sit on private parcels under a maintenance agreement. The agreement is filed in the planning department. The inspection responsibility is in public works. Neither department updates the other when ownership changes hands.
The BMP type is unfamiliar. A small program that has been doing detention ponds and biofiltration swales for years gets handed a permeable interlocking concrete pavement section. The inspection cadence and procedures are different. The BMP gets entered in the inventory but with the wrong type, and the next inspector cannot find it under any of their usual filters.
The MS4 boundary expanded. Annexations bring in new neighborhoods with their own BMPs. The annexed assets do not transfer cleanly to the new authority’s inventory. The BMPs are physically part of the city now, but the records are still in the county’s filing system.
What a defensible BMP record looks like
A BMP record that survives a staff transition and an audit needs more than a name and an address. The minimum useful record:
Identity:
- Unique identifier (asset ID, not “Detention Pond at 3rd and Main”)
- BMP type and subtype (bioretention cell, dry detention basin, permeable pavement, infiltration trench, oil-water separator, etc.)
- Installation year
- Approval reference (development permit number, site plan reference)
Location:
- Coordinates in a standard projection
- Parcel reference
- Street address or nearest cross-streets
- Spatial reference on the city’s GIS layer
Ownership and responsibility:
- Owner of record (private property owner, HOA, city, state)
- Maintenance party (who actually does the maintenance, which is sometimes different from the owner)
- Inspection authority (who is responsible for inspecting it)
- Maintenance agreement reference if applicable
Design and capacity:
- Designed treatment volume or flow
- Drainage area served
- Receiving water or downstream system
- Design references (engineer of record, design year, applicable manual)
Operational history:
- Inspection log with dates, inspector, findings, and follow-up
- Maintenance log with dates, type of work, and contractor
- Any deficiency findings and resolutions
- Any modifications since installation
The first time most programs see this list, the reaction is “we do not have all of that for our existing inventory.” That is normal. The point is not to recreate the records retroactively. The point is to capture this much when a new BMP enters the inventory and to backfill what is reasonable for existing assets over time.
Inspection cadence
Cadence varies by permit and by BMP type. Typical patterns for Western Washington Phase II programs:
- Annual inspection for most structural BMPs
- Additional inspection after major storm events for some types
- More frequent inspection during the first year after installation, then transitioning to standard cadence
- Specific inspection triggers for BMPs in or near sensitive receiving waters
The cadence belongs in the system, not in someone’s head. A small program with sixty BMPs cannot rely on a coordinator remembering which ones are due. The inventory either flags overdue inspections automatically or it does not. If it does not, inspections drift, and drift becomes a finding.
Cadence handling is one of the places software earns its keep, regardless of which tool. A spreadsheet can hold the data. It cannot tell you on a Tuesday morning that three BMPs are now overdue and one is approaching. For more on cadence-tracking generally, see Stormwater inspection cadence: monthly, quarterly, annual, and why it matters for your audit.
What a clean inspection looks like
A defensible BMP inspection record:
- Date and inspector
- Inspection type (annual, post-storm, complaint-driven, follow-up)
- Photos of key features (inlets, outlets, treatment surface, vegetation if applicable)
- GPS confirmation that the inspector was actually at the BMP
- Structured findings against a checklist appropriate for that BMP type
- Any deficiencies identified with severity and recommended response
- Maintenance recommendations if applicable
- Sign-off
For BMPs with maintenance triggers (sediment accumulation, vegetation health, structural integrity), the inspection should record measurements, not just narrative. “Sediment depth approximately one-third of design capacity” is more useful than “sediment present.”
The inventory as a map
Post-construction BMPs are spatial. They sit on parcels, drain to outfalls, and are part of larger drainage networks. A flat list inventory misses most of what makes the inventory useful. The BMP belongs on a map, color-coded by status, with the underlying record one click away.
When the BMP inventory lives on a map, several common audit problems get easier:
- Discovering a BMP that should be in the inventory but is not, because the field staff can see a gap on the map
- Confirming that a complaint at an address links to the BMP that drains that area
- Spotting clusters of BMPs at a single development that may share inspection findings
- Producing a “show me the BMPs in this watershed” view for council briefings or grant applications
Map-aware BMP tracking is part of why stormwater software with real GIS coexistence matters. The product story for that is on the GIS workspace page.
How software fits
Software does not stop a BMP from disappearing from the inventory. The handoff still has to happen. What software can do is make the handoff easier and the inventory durable across staff transitions.
NPDESTracker keeps the BMP inventory on a live municipal map alongside outfalls, sites, and incidents. Each BMP carries a structured record (type, ownership, location, inspection history, maintenance log) that any authorized user can find without knowing where the previous coordinator filed it. Annual inspections feed the MCM 5 section of the report automatically, so the report counts what is actually inspected rather than a number a coordinator types in.
The full reporting story is on the reporting page, and the inspection workflow that feeds the BMP records is on the inspections page.
What still belongs to the program
A few things software cannot help with. The handoff between development approval and stormwater asset inventory is a process question that lives across departments. The maintenance agreement language for private BMPs is a planning and legal question. The decision about what cadence is right for a particular BMP type is engineering judgment.
Software can hold the result of those decisions. It cannot make them. Programs that do MCM 5 well have a clear handoff process, clear inspection cadence policies, and a clear path for adding annexed or transferred BMPs to the inventory. The software is what keeps those decisions findable five years later.
Further reading
- Stormwater inspection cadence: monthly, quarterly, annual, and why it matters for your audit
- How to make an MS4 program audit-ready (without rewriting your spreadsheets)
- MS4 annual report checklist for Western Washington Phase II permittees
- Handling illicit discharges from complaint to closure: a working playbook for MS4 coordinators