By Jamie Otto, Product Manager, Stormwater — SwiftComply
I live in the Pacific Northwest, where water is part of daily life. I paddleboard in it, I watch it run off the hills, I see where it goes when the rain comes. That connection is part of what drew me to stormwater work, and it’s also what makes me acutely aware of how much goes into keeping that water clean before it reaches the places we love.
Most people don’t think about what happens to rainwater after it hits the ground. But for stormwater managers at cities and municipalities across the country, it’s the center of their professional world — and the compliance obligations that come with it are substantial, complex, and often managed with far fewer resources than the job demands.
Key Takeaways
- The compliance challenge: Municipalities face heavy Clean Water Act burdens with limited administrative resources.
- The paper trap: Reliance on physical forms creates data silos, lost inspection records, and audit risks.
- The solution: Modern stormwater programs require mobile-first, configurable data tools to unify field-to-office reporting.
A Mandate That Touches Every City
Stormwater regulation in the United States traces back to the Clean Water Act and has evolved significantly over the decades. Today, municipalities operate under permit requirements that place the burden of protecting stormwater squarely on cities — requiring them to monitor, inspect, document, and report on a wide range of activities happening within their boundaries.
Those requirements span six core program areas, and they don’t operate in isolation. A city has to manage active construction sites, inspect its own infrastructure, monitor private businesses for potential discharges, look for illicit connections and illegal dumping, and run public education programs — all while producing the documentation that proves the work is being done.
For a large city, that means multiple departments, dozens of staff, and a significant coordination challenge. For a smaller city, it might mean one person responsible for all of it.
Either way, the compliance burden is real, and it doesn’t scale itself to the size of your team.
The Paper Problem
Ask almost anyone working in stormwater compliance what their biggest frustration is, and the answer usually comes back to data — specifically, how it’s collected, where it ends up, and what it takes to make it useful.
The current reality for many programs is still largely paper-based. Inspectors head into the field with printed forms, document what they find at a construction site or catch basin, and bring those forms back to the office. From there, the data gets manually entered into a spreadsheet. Somewhere. Hopefully filed correctly. Hopefully not lost in transit.
We’ve heard directly from stormwater teams that paper inspection forms sometimes don’t make it back to the office at all. When your compliance record depends on that data, losing a form isn’t just inconvenient — it’s a gap in your audit trail.
And audits do happen. When a regulatory agency comes calling and asks a city to produce its inspection history for the past year, having to reconstruct that record from scattered spreadsheets and partial files is not where you want to be.
What Stormwater Programs Actually Need
The stormwater professionals I’ve worked with are not looking for complicated technology. They’re looking for something that works the way their job works — in the field, across multiple sites, with different team members, on different schedules — and pulls everything together without creating extra work.
That means a few specific things in practice.
- Mobile-first data collection. Inspectors need to capture information at the site, not reconstruct it later. A mobile app with offline capability means data gets entered once, in the field, and automatically syncs back to the system when connectivity is restored. No re-entry. No lost forms. No gaps.
- Configurable forms. No two cities run their stormwater program exactly the same way. The inspection forms, the workflows, the required fields — these need to match how a given program actually operates, not force the program to adapt to a rigid template. Configurability isn’t a nice-to-have; it’s the difference between a tool that gets used and one that gets abandoned.
- A single view of everything. Program managers need to be able to see what’s been done, what’s pending, and where issues are emerging — across all of their sites and all of their team members — without logging into three different systems or opening five different spreadsheets. When everything is in one place, pulling together an audit response or an annual report stops being a crisis and becomes a routine task.
- Data that can be shared. Stormwater compliance doesn’t happen in a vacuum. Program managers report to leadership. Cities report to the EPA. In some cases, the public has a legitimate interest in understanding the health of local waterways. Having data that can be exported, visualized, and shared — in the format each audience actually needs — is part of running a credible, transparent program.
The Bigger Picture
Stormwater is inherently local. How much it rains, what industries operate nearby, what’s upstream, how old the infrastructure is — all of it shapes what a given program faces. In Hawaii, stormwater runs directly into the ocean, making every discharge a matter of immediate environmental consequence. In Texas, where rain can be intense and development is constant, construction site runoff is a persistent challenge. In the Pacific Northwest, where I work, the volume and frequency of rainfall makes year-round monitoring a real operational demand.
What’s consistent across all of these contexts is that the people doing this work care about it. Stormwater professionals tend to be deeply connected to the water in their communities — not just as a regulatory responsibility, but as something genuinely worth protecting.
The tools they’re working with should match that commitment. Managing a complex, multi-faceted compliance program on paper forms and disconnected spreadsheets doesn’t serve the environment, and it doesn’t serve the people trying to protect it.
There’s a better way to do this work. And when the technology finally fits the job, the difference shows up not just in efficiency — but in the quality of the programs that protect the water we all depend on.
Jamie Otto is the Product Manager for Stormwater at SwiftComply, where she leads product development for municipal stormwater compliance programs.