Stormwater Management and Inspection: The Complete Guide

Stormwater vs. Sanitary Systems

Stormwater and sanitary networks both live underground, yet they exist for different reasons and behave differently. Treating them as the same system leads to missed risks, compliance issues, and wasted budget. This chapter sets clear definitions so your program can focus inspections where they matter most.

Purpose and flow

Sanitary sewer systems carry wastewater from homes, businesses, and industry to a treatment plant. Flow is relatively consistent. Everything is designed for reliable conveyance under regulation and oversight.

Stormwater systems collect rain and surface runoff from roads, roofs, and land. Flow is highly variable. Much of this water does not receive treatment before reaching rivers, lakes, or retention basins. The system must tolerate sudden surges that follow weather events.

Network design and access

Sanitary networks are usually linear and predictable under streets and alleys with manhole access. Stormwater networks are irregular. They include closed pipes, culverts under roadways, catch basins, ditches, channels, detention ponds, and outfalls spread across a wide area. This makes stormwater assets harder to map and reach, which affects how you budget time, crews, and equipment.

Inspection goals and failure modes

• Sanitary focus: capacity, inflow and infiltration, blockages, grease, structural defects, and regulatory compliance.
• Stormwater focus: sediment and debris accumulation, collapsed or corroded culverts, undermined roadways, vegetation overgrowth, inlet and outfall erosion, and illicit discharges.

When stormwater assets fail, common results include sinkholes, roadway subsidence, and localized flooding. When sanitary assets fail, results include overflows and environmental violations. The risk profiles and inspection intervals should be different.

Confusion and how to prevent it

Disconnected teams lead to cross-system problems. Stormwater surges can flood sanitary lines, and overflows can spill into storm drains. Clear data, defined workflows, and GIS-linked inspections keep systems separated and protected.

The key to avoiding confusion between stormwater and sanitary systems is centralizing inspection data in one place. When observations, condition scores, and media are tied directly to GIS features, teams can enforce consistent data standards and keep workflows aligned. This reduces duplication, eliminates guesswork, and ensures both systems get the distinct attention they require.

For additional insights, see: Storm vs. Sanitary: Key Differences in Pipe Inspection

Quick comparison

GIS as the System of Record for Stormwater

A modern stormwater program uses GIS as the backbone for planning, scheduling, field capture, and reporting. Maps do more than visualize lines. GIS connects assets, inspections, risks, and work orders so that decisions are made with context rather than isolated records.

Why GIS changes outcomes

• Context for every asset. See a pipe not only as a length and diameter but as part of a basin with upstream and downstream impacts.

• Shared source of truth. Public Works, Engineering, and Planning see the same network, statuses, and priorities.

• Faster planning. Overlay flood-prone zones, road classifications, schools, hospitals, and sensitive waterways to set smarter inspection routes.

• Defensible budgets. Map-based condition scoring and risk heatmaps help justify funding and capital plans.

What to map for stormwater

• Asset geometry and attributes: pipe size and material, culvert type, installation year, condition score, last inspection date.

• Hydrology context: basins and sub-basins, floodplains, low-lying roads, detention facilities.

• Risk indicators: past failures, complaints, critical facilities, traffic volume, ground type.

• Inspection layers: recent observations, sediment levels, defects, photos, and videos tied to features.

A Day in the Life of a Connected Stormwater Program

1. Plan: Supervisors identify older culverts in high-traffic areas using GIS filters and condition scores.
2. Inspect: Field crews head out with mapped routes and collect photos, videos, and condition notes in the field.
3. Analyze: Engineers overlay inspection results with flood and watershed data to pinpoint vulnerable crossings.
4. Act: Urgent repairs move into work orders, while lower-priority fixes are planned for future maintenance cycles.
5. Report: Leadership uses dashboards to track inspection coverage, asset conditions, and upcoming priorities.

Modern pipe inspection software works hand in hand with Esri ArcGIS to keep stormwater programs running smoothly. Field data collected during inspections automatically links back to GIS features, creating a centralized source of truth. This eliminates duplicate entry, keeps data consistent across departments, and allows leaders to see condition scores and progress toward inspection goals in real time.

For additional insights, see: How GIS Is Transforming Stormwater Inspection and Planning

From Maps to Management – Real-World Examples

Loveland, CO
A city with aging storm infrastructure launched a multi-year inspection initiative. Early on, GIS data was incomplete and many buried assets were unmapped. After integrating inspection data with GIS, the city uncovered bottlenecks and missing assets, prioritized replacements, and dramatically increased the number of storm lines inspected and cleaned each year. Within just three years, the city inspected more mileage than in the previous two decades combined.

Building a Proactive Inspection and Maintenance Program

Reactive work is expensive. A proactive program reduces emergencies, extends asset life, and helps leadership see progress. This chapter provides a practical blueprint for inventory, risk, inspection, and action.

Step 1: Build or refine your inventory

• Consolidate all asset lists into GIS.
• Fill gaps with field verification and desktop review.
• Record core attributes: location, size, material, installation year, last inspection, condition score.

Step 2: Score risk and set priorities

Many agencies use a simple risk model that multiplies Likelihood of Failure by Consequence of Failure to prioritize inspections and repairs.

Likelihood factors often come from inspection data such as pipe age, material, observed defects, sediment levels, soil type, and hydraulic condition. NASSCO-certified condition scores are a common input for this step.

Consequence factors may include traffic load above the crossing, downstream receptors, detour feasibility, proximity to critical facilities, and estimated repair costs.

Start with the data you can measure consistently and refine your model as data quality and inspection coverage improve

Step 3: Choose inspection methods

• CCTV crawlers: inside closed pipes for detailed defects.
• Zoom cameras: fast screening in manholes or at inlets.
• Walk-through or float inspections: large culverts where safe.
• Drones and ROVs: long culverts, detention ponds, or hazardous areas.
• Sensors: water level, flow, and rainfall correlation at critical points.

AI-assisted detect coding can accelerate review, reduce backlog, and link results directly to GIS features for faster reporting. Results tie to GIS features so analysis and reporting are immediate.

Step 4: Standardize data capture and QA

• Use consistent codes for observations and conditions.
• Train crews on photo and video standards.
• Review a sample of each crew’s work for accuracy.
• Document repeatable rules for condition scoring and follow-up actions.

Step 5: Turn findings into maintenance

• Create work orders for urgent items.
• Bundle moderate repairs into projects by basin or neighborhood.
• Schedule routine cleaning for chronic sediment locations.
• Track completion dates and costs to refine ROI.

Step 6: Report results that leadership understands

• Summaries that show miles inspected, condition trends, and risk reduction.
• Before and after photos for key sites.
• A map that highlights what was inspected this quarter and what is planned next quarter.
• A short list of funding asks tied to risk reduction.

Annual plan template

• Objective: Inspect high-risk basin A and B, screen basin C.
• Scope: 45 miles CCTV, 25 miles zoom camera, 60 inlets cleaned.
• Deliverables: Condition scores, GIS feature updates, repair list with cost ranges.
• Timeline: March to September for field work, October for analysis, November budget requests.
• KPIs: 90 percent of high-risk crossings inspected, 20 percent reduction in emergency culvert failures year over year.

For additional insights, see: Why Stormwater Systems Deserve Proactive Inspection Programs

The Future of Stormwater Management

Stormwater work is becoming more data driven. Climate patterns are shifting. Expectations for transparency and speed are rising. Programs that adapt now will serve their communities better.

• Climate resilience. Short, intense rain events place new stresses on older systems. Programs should recheck design assumptions and update risk models.

• AI and predictive analytics. Teams move from simply describing defects to anticipating failures and scheduling work at the right time.

• Sensors and IoT. Water level and flow sensors at key crossings provide early warnings and improve post-storm assessments.

• Smart city dashboards. Stormwater data does not live alone. It feeds into executive dashboards that also track roads, signals, and utilities for a citywide view.

Public transparency. Many agencies now share maps, schedules, and progress updates. Clear communication builds trust and supports funding.