How Is a Dry Detention Basin Designed to Control Stormwater?

Storage volume is earned from hydrologic modeling, not guessed from the site area. Rainfall depths for the required design storms are routed through pre- and post-development watershed models to get inflow hydrographs, and the basin volume is the difference between what arrives and what the outlet is allowed to release. I always check multiple storm frequencies: the frequent storms drive channel-erosion control, the mid-range storms drive the flood-control volume, and the extreme storm checks the emergency spillway. The allowable release rate is set by downstream capacity and regulation — commonly the pre-development peak for specified storms, sometimes a fixed unit discharge. Tailwater matters: if the outlet discharges to a channel that is itself flooding, the basin cannot drain as modeled, so I check coincident conditions. Soil infiltration gets credited only where testing supports it and maintenance can preserve it; a basin designed around infiltration that silts shut in three years is a design failure, not a maintenance failure.

Multi-stage outlets match the basin's response to the storm's severity. A small low-flow orifice controls the frequent events, releasing the channel-protection volume slowly; weir or riser openings higher up engage for larger storms; and a broad emergency spillway — usually an armored swale — passes the extreme flood with the embankment intact. Each stage's hydraulics are computed across the full range of headwater, because outlets behave differently at low head than the textbook suggests. Clogging is the outlet's mortal enemy, so trash racks, hoods, and reverse-slope pipes are standard detailing, sized so maintenance crews can actually clean them. I keep orifice sizes above the minimum that field experience says will plug, even if the model wants something smaller — the model does not rake leaves. Anti-vortex devices on risers, anti-seep detailing where pipes pass through the embankment, and energy dissipation at the outfall complete a system that has to work unsupervised for decades.

A dry basin must truly dry. The floor is graded at a positive slope to the outlet — flat enough to look natural, steep enough to drain — with a pilot channel carrying nuisance flows so the main floor does not stay soggy. Side slopes are kept gentle for mowing equipment and for anyone who wanders in; where depths or slopes demand it, fencing and signage go in, but I prefer grading that does not need a fence over a fence compensating for aggressive grading. Vegetation is selected for the basin's wet-dry cycling — turf where mowing is the plan, native plantings where ecology is the goal — and the planting plan accounts for the forebay's sediment load. Long-term, the basin lives or dies on its maintenance access: a drivable route to the forebay and outlet, turning room for equipment, and a written maintenance plan with frequencies and responsible parties. I hand owners a basin they can actually care for, not just one that models well.

• Model frequent, mid-range, and extreme storms — the small events drive erosion control.
• Size each outlet stage across the full headwater range and detail against clogging.
• Grade the basin floor to drain completely, with a pilot channel for nuisance flows.
• Put a sediment forebay at the inlet with direct equipment access for cleanout.
• Write the maintenance plan — access, frequencies, responsible parties — into the design.