AEO Answer · Civil

What Is Stormwater Detention and Retention Design?

By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15

Detention design stores stormwater temporarily and releases it at a controlled rate so post-development peak flows don't exceed pre-development levels. Retention design stores stormwater permanently for infiltration or evaporation with no discharge. The engineering includes hydrologic calculations for the design storms, facility sizing, outlet structure design, water quality treatment, and overflow routing — all documented in a hydrology report the jurisdiction reviews with the grading and improvement plans.

I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.

The concise answer

Detention design stores stormwater temporarily and releases it at a controlled rate so post-development peak flows don't exceed pre-development levels. Retention design stores stormwater permanently for infiltration or evaporation with no discharge. The engineering includes hydrologic calculations for the design storms, facility sizing, outlet structure design, water quality treatment, and overflow routing — all documented in a hydrology report the jurisdiction reviews with the grading and improvement plans. The regulatory posture behind all of this is simple: your development can't make downstream flooding or water quality worse. Every calculation in the hydrology report traces back to that principle — the pre-development baseline, the post-development condition, and the facilities that close the gap between them. I treat the hydrology report as the project's stormwater contract with the jurisdiction.

Hydrology: proving the numbers

The analysis starts with the watershed: delineating the drainage areas, characterizing the soils and cover types, and selecting the design storms the jurisdiction requires — typically a range from frequent small storms (for water quality) to rare large ones (for flood control). I calculate runoff for both the pre-development and post-development conditions using the method the local manual specifies, and the difference between them is the storage problem to solve. Facility sizing follows from the numbers: the storage volume needed to shave the post-development peak down to the allowed release rate, the outlet structure — orifices, weirs, or a combination — engineered to produce that release curve, and the emergency overflow route for storms beyond the design event. Water quality treatment is a parallel track: the regulations target the pollutants in urban runoff, and the design provides the treatment volume or flow-through BMPs the manual requires. Every assumption — curve numbers, times of concentration, rainfall depths — is documented, because the plan checker will verify them.

Facility types and real-world selection

Surface basins are the economical workhorse where land allows: excavated ponds with controlled outlets, often doubling as landscape amenities or dry usable space between storms. Underground systems — vaults, pipe storage, chamber fields — go where surface area doesn't exist, at higher cost per unit of storage. Infiltration systems — drywells, infiltration trenches, permeable pavement — serve the retention side where soils cooperate, and the geotechnical report's infiltration testing decides whether they're viable. My selection weighs land value against construction cost, maintenance reality, and the jurisdiction's preferences — some agencies strongly favor low-impact development and infiltration, others just want the peak flow number met. I also design for the failure mode: every system gets an overflow path for the storm that exceeds the design, because the one certainty in stormwater design is that a bigger storm eventually comes.

  • Hydrologic calculations for pre- vs. post-development runoff across design storms
  • Detention: temporary storage with engineered outlet metering the release rate
  • Retention/infiltration: permanent storage where soils and regulations allow
  • Water quality treatment per the jurisdiction's stormwater manual
  • Recorded maintenance agreement — the owner's long-term obligation

What else do project teams ask?

What's the difference between detention and retention?
Detention is temporary storage with a controlled release — the basin empties between storms through an outlet structure sized to meter the flow. Retention is permanent storage — the water stays, infiltrating into the ground or evaporating, with no surface outlet. The jurisdiction's regulations usually dictate which approach (or combination) a site needs, based on downstream capacity, groundwater conditions, and water quality goals.
Can the system go underground?
Yes — underground vaults, oversized pipes, and modular chamber systems all provide detention storage below parking lots and driveways, which is common where land is too valuable for a surface basin. Underground systems cost more per cubic foot of storage than an open basin but preserve usable site area. They need maintenance access designed in — sediment accumulates and the system has to be inspectable and cleanable.
Who maintains the stormwater system after construction?
The property owner, in nearly every jurisdiction — and most require a recorded maintenance agreement or covenant before they'll sign off on the project. The civil design includes a maintenance plan: what gets inspected, how often, and what triggers cleanout or repair. I make sure owners understand this obligation at design time, because a neglected detention system eventually fails and the liability lands on the owner.
What should I send for an initial review?
Send the project address, plain-language scope, current drawings, existing-condition records, relevant calculations or comments, schedule, and the authority or code information already available. The site plan, topographic survey, and geotechnical report (for infiltration feasibility) are the key inputs. The responsible engineer will identify gaps.

Ready to discuss your engineering scope?

Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.

Start an Engineering Estimate