Every year, your post-construction project list gets a little longer. Another subdivision approved. Another commercial development that broke ground, installed its wet pond, and handed the keys to a private landowner who may or may not know they’re responsible for maintaining a stormwater control measure.
Post-construction compliance is permanent work. Projects don’t age out, maintenance requirements don’t lapse, and the list compounds every year.
Most programs manage this the way they manage everything else: a color-coded spreadsheet of projects, a folder of letters, a field crew making judgment calls, and one staff member holding the institutional knowledge. That works until someone leaves, a regulator asks for your documented process, and “we’ve been doing it this way for years” no longer holds up.
Scaling a post-construction program means building for three things at once: flexibility to match your permit requirements and local conditions, efficiency so administrative work doesn’t compound with the project list, and defensibility so you can document every decision when a regulator asks. We walked through all five strategies in a recent webinar. The full recording is available if you’d rather watch than read.
Strategy 1: Build a Digital Inventory
Every year, most programs face the same question: are we doing maintenance letters this year, field inspections, or some mix of both, and what about the new projects that just came out of construction? When those decisions live in a spreadsheet or in someone’s head, they don’t survive the next staff transition. Your team relitigates the same choices every January.
Store those decisions in a digital inventory, and they carry forward. Every project is accounted for, every new completion is captured, and the logic behind your compliance approach is documented and repeatable, no longer dependent on any one person’s memory. Build it from whatever records you already have and connect it to your construction program so that new projects roll in as they finish. On a map, you can see the full scope: where all your projects are, their condition, and what compliance work is current and what still needs to be done.
Strategy 2: Automate Your Maintenance Notices
Every year, you draft letters to every private landowner responsible for maintaining their post-construction BMPs, collect their evidence, review what came back, and build a compliance record. Most programs call this letter season. It takes weeks.
The letterhead, the boilerplate describing post-construction requirements, the response deadline: identical for every letter. The property name, the contact, the list of assets: different for every site. Generating those letters by hand, tracking responses via email, and figuring out whether what came back is even usable is what makes it take weeks.
With the right system, you can define the template once and pull site-specific data. Each letter includes a URL that takes the landowner to a portal where they respond asset-by-asset, submitting notes, photos, and inspection forms for each BMP. Responses land in the project record. Your to-do list updates as they come in. Letter season finishes in days.
Strategy 3: Target Your Field Inspections
Maintenance notices are self-reported. At some point, you need your own eyes on the ground.
Some sites go on your inspection list because of their water quality significance or permit requirements. Others earn a spot because the maintenance response raised questions. A landowner sends a blurry photo of something that might be a pond or a parking lot, and your crew needs to go see it. Sites with a history of problems appear on your reinspection list.
Field inspection planning can be easy with the right system. Plan work by geography: filter your asset list to a watershed or neighborhood, build this week’s route, and assign specific assets to specific staff. Before your crew leaves the office, they have the inspection history and current condition for every BMP they’re evaluating. At a site with five BMPs, your team has the map and details to find and inspect every asset based on its type to ensure any issues are captured. After inspections close, automatically generate a letter to the O&M contact with a detailed summary of the assets with findings. Skip the ones that passed.
Strategy 4: Track Your Program Metrics
Your director wants a summary. Your regulator wants site-level detail. You need to know whether your program is keeping pace with a growing project list.
Most teams pull this together just before the annual report is due, reconciling numbers across spreadsheets and hoping the math holds. Track it as work gets done instead: project and asset count year over year, summarize notices generated and responses received, unresponsive contacts, monthly workload trends, structural BMP inspection progress, summary of asset condition findings, etc. Your annual report is already assembled without the stress and headaches. Your director asks for a mid-year update, and you have it on the ready.
Strategy 5: Stay Audit-Ready
When a regulator asks to see your program, they don’t want a summary. They want to see specific sites, specific compliance actions, and how your process works.
If your program lives in spreadsheets and filing cabinets, that request triggers a scramble, pulling records from multiple places, numbers that need reconciling, gaps you hope don’t show. Build the record as you go. Every notice sent, every response received, every inspection completed, every follow-up documented, all time-stamped in a single system. A regulator calls and you pull up the fact sheet for any site. The notices, the responses, the inspection history: all building up as you worked through the year.
Regulators understand that landowners don’t always comply on the first try. A consistent, documented process holds up regardless.
Putting It Together
Build an inventory. Automate the repetitive work. Deploy your field team to the right sites at the right time. Track metrics as you go. Document everything.
Most programs run these tasks across disconnected systems: GIS layer here, elaborate spreadsheet there, email threads everywhere. A new hire spends months reconstructing program history. Annual reporting requires weeks of pulling numbers from separate systems. A regulatory request sends you scrambling.
Bring these strategies together in a single system, and your program works the way it’s supposed to. New staff open the platform and find the full history. Your data stays up to date as work gets done. A regulator calls, and you’re ready.
Maggie Matthias is Chief Product Officer and Catherine Riihimaki is Research Director at 2NDNATURE, makers of 2NFORM, the GIS-native stormwater management platform built for MS4 NPDES compliance. If you’ve spent weeks on your post-construction maintenance letter campaign, rebuilt institutional knowledge after a staff transition, or braced for a surprise regulatory visit, we’d like to show you what your program could look like. Request a demo or reach out at info@2ndnaturewater.com.
