Stormwater management is the engineering practice of controlling rainwater and snowmelt runoff on a developed site. It uses grading, drainage systems, detention or retention ponds, and best management practices (BMPs) to slow runoff, capture pollutants, prevent flooding, and meet federal, state, and local stormwater regulations.

For most land development projects, stormwater management is required by code, expensive to do badly, and relatively cheap to do well if it's planned early. This guide walks through what stormwater management actually is, why developers can't skip it, what's in a stormwater management plan, and the BMPs that make up the toolbox.

Why is stormwater management required?

Development changes how water moves on a site. A natural site with grass, trees, and undisturbed soils absorbs most of a rainfall event. The same site after development — rooftops, parking lots, driveways, and compacted lawn — sheds water rapidly. The runoff is faster, the volume is larger, and the water carries pollutants picked up from impervious surfaces.

Without stormwater management, that runoff causes downstream flooding, stream erosion, water-quality degradation, and overwhelmed municipal infrastructure. It's also why the Clean Water Act and EPA's National Pollutant Discharge Elimination System (NPDES) regulate construction stormwater nationally, and why states and local jurisdictions add their own rules on top.

The regulatory framework, briefly

Stormwater regulation is layered:

  • Federal: EPA's NPDES program covers construction sites disturbing one acre or more.
  • State: Each state has its own construction stormwater general permit. Minnesota's MPCA issues the Construction Stormwater General Permit (CSWGP). Colorado's CDPHE issues a similar construction stormwater permit.
  • Watershed/regional: In Minnesota especially, watershed districts often add their own water-quality treatment and rate-control requirements that can be stricter than state rules.
  • Local: Cities and counties layer additional requirements through engineering design standards, stormwater ordinances, and floodplain rules.

For a given site, the design has to satisfy whichever rules apply to the location. A licensed Civil Engineer familiar with the jurisdiction can navigate this stack.

What's in a stormwater management plan?

A stormwater management plan is the engineering document that describes how runoff will be controlled on the site. The contents typically include:

  • Hydrologic and hydraulic analysis — runoff volume calculations, peak flow analysis, and storm-event modeling using methods accepted by the local jurisdiction
  • Drainage system design — storm sewer alignments, inlet locations, swales, and outfalls
  • Detention or retention pond design — pond sizing, outlet structure design, and embankment grading
  • Best Management Practices (BMPs) — the specific structural and non-structural measures used to treat water quality and control runoff
  • Stormwater Pollution Prevention Plan (SWPPP) — for construction sites disturbing one acre or more
  • Erosion and sediment control plan — for the construction phase
  • Operations and maintenance plan — long-term obligations for keeping the system functioning after construction

For larger or more regulated projects, the stormwater management plan becomes its own bound document. For smaller projects, it might be integrated into the broader civil construction set.

Stormwater BMPs: the toolbox

BMPs (Best Management Practices) are the specific techniques used to control stormwater on a site. They're divided into structural BMPs (built features) and non-structural BMPs (operational practices).

Structural BMPs

  • Detention ponds — temporary storage that releases runoff slowly. Detention vs retention pond comparison →
  • Retention ponds (wet ponds) — permanent pool that provides water-quality treatment and rate control
  • Bioretention basins — engineered planted basins that infiltrate and treat runoff
  • Rain gardens — smaller bioretention features for residential or small commercial sites
  • Vegetated swales — grassed channels that convey and treat runoff
  • Sand filters — subsurface treatment for sites without enough land for ponds
  • Permeable pavement — pavements that allow infiltration through the surface
  • Underground detention — pipe or chamber storage below parking lots or other surfaces

Non-structural BMPs

  • Erosion control during construction — silt fence, sediment basins, inlet protection, stabilized construction entrances
  • Good housekeeping — practices that prevent pollution at the source (covered material storage, designated wash-out areas, spill prevention)
  • Sweeping and maintenance — regular cleaning of streets, parking lots, and structural BMPs
  • Public education — for some MS4 communities, education and outreach are part of the regulatory framework

The right combination is project-specific. A small commercial site might need a single bioretention basin and silt fence during construction. A 100-acre subdivision might need a regional detention pond, multiple bioretention practices, and a coordinated SWPPP.

What about water quality?

Water-quality treatment is the side of stormwater management focused on removing pollutants — sediment, nutrients (nitrogen and phosphorus), oils, metals — before runoff leaves the site. Most modern jurisdictions require water-quality treatment in addition to peak-flow control.

Common water-quality treatment approaches:

  • Settling — retention ponds and bioretention give sediment time to settle out
  • Filtration — sand filters, permeable pavement, and bioretention soils filter water through media
  • Biological uptake — vegetation in bioretention basins, rain gardens, and constructed wetlands removes nutrients
  • Source control — preventing pollutants from entering runoff in the first place

In practice, most projects use a "treatment train" of multiple BMPs in series. Pretreat with a forebay or sediment trap, then provide primary treatment in a bioretention basin or wet pond, then route runoff through final controls before discharge.

Cold-climate stormwater considerations

Stormwater design in Minnesota and northern Colorado has to handle conditions that warmer regions don't:

  • Snowmelt — significant runoff volumes outside of typical rainfall events, often concentrated in spring
  • Frozen ground — reduces infiltration capacity for weeks at a time
  • Frost heave — affects pond liners, outlet structures, and BMP soils
  • Salt loading — road salt enters stormwater systems and affects vegetation in bioretention BMPs
  • Ice cover on ponds — can affect outlet performance during winter and early spring storms

A stormwater design that works in Atlanta won't necessarily work in Minneapolis. This is one reason local engineering experience matters.

The cost of stormwater management

For a typical single-site commercial or residential project in MN or CO, stormwater management work might break down as:

  • Hydrologic and hydraulic analysis: a few thousand dollars
  • Stormwater management plan + drainage design: several thousand to tens of thousands depending on complexity
  • SWPPP: typically a few thousand for a focused permit-ready document
  • Construction-phase services: additional fee for SWPPP inspections, RFI response, and observation visits

Larger or more regulated projects (multi-phase subdivisions, mountain residential, sites in sensitive watersheds) cost more but the per-acre engineering cost typically goes down at scale. Land Pro Civil offers fixed-fee stormwater engagements with the number agreed in writing before work starts.

Common stormwater mistakes that cost developers

  1. Treating stormwater as a "fix it at the end" item. When stormwater is added after the site plan is locked, the pond ends up in the worst location, taking the most developable acreage. Plan stormwater early.
  2. Using boilerplate BMPs without site-specific analysis. A bioretention basin in clay soil with no underdrain doesn't work. A rain garden that sits below a winter snow pile fails.
  3. Underestimating maintenance. Stormwater facilities need ongoing maintenance. If the developer hands the project off without a clear maintenance agreement, the system degrades and the next inspection fails.
  4. Skipping coordination with the watershed district. In Minnesota, watershed districts can add requirements that double the size of a stormwater facility. Engaging them early prevents redesign.

Where to go from here

For developers planning a project in Minnesota or Colorado, the best move is to get a civil engineer involved before site plans are locked. Stormwater requirements shape site layout, parking ratios, building footprints, and developable acreage. Front-loading the analysis prevents expensive redesigns later.

For more on specific stormwater topics, see our detention vs retention pond comparison, our deep dive on what's actually in a SWPPP, or our stormwater management services page. For Minnesota-specific stormwater context (MPCA, watershed districts, SWPPPs), see our Minnesota service-area page.