Stormwater detention and retention pond field guide for site crews

What a detention pond is, and why it protects everything downstream

A detention pond is a basin that catches the runoff coming off a developed site during a storm, holds it for a few hours, and lets it back out slowly through an outlet structure. The whole point is to slow the water down. The outlet is sized so the rate leaving the basin during a design storm is no higher than the rate that left the same ground before anyone paved it. The water still leaves. It just leaves at a pace the channel and the storm system downstream can take.

Picture the ground before development. Rain hits grass and woods, soaks in, and trickles off slow. Now pave it. The same rain hits roofs and asphalt, soaks in nowhere, and arrives at the property line in a fraction of the time, in a much bigger surge. That surge is what floods the creek below you, scours the channel banks, and backs water up onto the neighbor. The basin sits between the pavement and the property line and chews the top off that surge.

Three things make a basin actually do that job: the storage volume built to the engineered grades, the outlet built to the design release rate, and the embankment that holds it all in. Get those right and keep sediment and trash out of the outlet, and the pond protects what is downstream for the life of the site. Let any of the three go and the basin either floods the site it sits on or sends the surge downstream it was built to stop. The infiltration-based green-infrastructure side of stormwater, the rain gardens and bioretention cells, is its own subject. So is the surface grading that feeds the basin. This guide is the detention basin itself, the structure that controls the peak.

Why development needs detention in the first place

Development changes water in two ways at once, and both make the problem the basin solves. It adds impervious area, so more of every rain runs off instead of soaking in, which means more total volume. And it speeds the runoff up, because smooth pavement and pipe move water far faster than soil and grass, which means the same volume arrives sooner and stacks into a higher peak. More water, arriving faster, concentrated into a sharper spike. That spike is the thing.

The basin attenuates the peak. It does not make the water disappear, and a dry detention basin barely cleans it. What it does is take that sharp post-development spike and stretch it back out over time, so the highest rate leaving the site drops back down toward what the undeveloped ground produced. Downstream of you, a channel sized by decades of natural flows sees roughly the flow it always saw, instead of the flood the new pavement would have sent it.

This is why the work is regulated rather than optional. Most jurisdictions limit how much a site can change the rate and volume of water leaving it, and that mandate usually flows down through the local stormwater code and the site's stormwater permit. The required release rate, the design storms it has to meet, and the volume the basin has to hold all come off that code and the civil engineer's calculation, not a rule of thumb. Build the basin smaller than the design, or with an outlet that lets out faster than the limit, and the site is out of compliance whether or not anything has flooded yet.

What is the difference between detention and retention?

Detention holds the storm and then empties. Retention holds a permanent pool of water and never fully empties. That single difference, dry between storms versus wet all the time, drives everything else about how the two are built, what they do, and how they are maintained.

A detention basin, the dry kind, sits empty most of the time. A storm fills it, the outlet meters the water back out, and within a day or so it draws down to the bottom and waits for the next storm. Its job is peak control, plain and simple. It is the cheaper, simpler structure, and on a lot of sites it is all the code requires.

A retention basin, the wet kind, holds a permanent pool at a set elevation. A storm raises the pool, the outlet lets the rise back down to the permanent level, and the pool stays. That standing water is doing a second job the dry basin cannot: water quality. Sediment settles out in the pool, and biological processes work on the pollutants over the days the water sits, so the wet pond removes far more of the nutrients, metals, and suspended solids than dry detention does. Which one a site gets depends on what the permit demands, peak control alone or peak control plus water quality, and on whether the site can sustain a permanent pool. The civil and geotech engineers and the local stormwater manual make that call, not the field.

Dry, wet, and extended detention

Three pond types cover most of what gets built, and they line up along how long the water stays. The dry detention basin empties between storms and controls the peak. The wet retention pond keeps a permanent pool and adds water quality. Extended detention sits in between.

Extended detention is a dry basin tuned to drain slowly on purpose. Instead of metering the water out as fast as the peak limit allows, the outlet holds the smaller, frequent storms back longer, often a target drain time in the range of 24 to 48 hours for the water-quality portion, so sediment has time to settle before the basin empties. It buys some of the water-quality benefit of a wet pond without the permanent pool. The trade is a low outlet that wants to clog, because it is metering small flows through a small opening.

Wet extended detention combines both: a permanent pool for treatment, plus storage above it that fills and drains slowly during storms for peak control and extra quality. The names matter once a permit and a design are involved, because each type carries a different sizing method, a different outlet, and a different maintenance burden. Build a dry basin where the plan called for a wet one and the water quality the permit credited never happens. The approved design says which type the site has, and that is the one you build.

Peak attenuation: the one thing the basin has to get right

Peak attenuation is the core function, and it comes down to one rule: the rate of water leaving the basin during a design storm has to be at or below the rate that left the site before it was developed. The basin does this by storing water faster than it lets it out. Inflow pours in at the developed peak, the outlet only passes a metered trickle, the difference piles up as depth in the basin, and what leaves is a lower, longer flow instead of a sharp spike.

The engineer proves this with three linked relationships, and they are worth understanding even if you never run the math. The stage-storage curve says how much water the basin holds at each depth, which is set by the grades you build. The stage-discharge curve says how much the outlet passes at each depth, which is set by the outlet you build. Routing combines them with the inflow to show the actual peak that leaves. Build the grades wrong and the storage is wrong. Build the outlet wrong and the discharge is wrong. Either error throws off the result the whole design depends on.

The release limits, the design storms, and the routing all come from the local stormwater code and the engineer's stamped calculation, and they vary a lot between jurisdictions. Some hold the post-development peak to the pre-development peak for a set of storms. Some go further and limit volume or require a release below the predeveloped rate. This is not a place to carry a number in your head. Build the volume to the stage-storage the plan shows and the outlet to the dimensions the plan calls out, and confirm anything that does not match before you finish, because the basin only attenuates the peak if it was built to the curves the engineer routed.

What is an outlet control structure?

The outlet control structure is the part of the basin that sets the release rate, and it is the heart of the whole design. Everything else stores water. The outlet decides how fast it leaves. Get the outlet wrong and the most carefully graded basin in the county still fails its release limit. It is usually a vertical riser, a standpipe or a concrete box, standing in the basin with the outlet pipe running out through the embankment to the downstream system. Water enters the riser through openings set at different heights and drains out the pipe at a controlled rate.

The reason it has openings at different heights is that one basin has to handle storms of wildly different sizes, and a single fixed opening cannot meter all of them to their separate limits. So the structure is built in stages. A low opening near the bottom handles the small, frequent storms. A larger opening or a weir higher up handles the bigger storms. The top of the riser itself, or a separate spillway, handles the extreme event. Each stage is sized so the basin holds the storm assigned to it and releases at or below that storm's limit.

The exact configuration, the size and elevation of every opening, the riser dimensions, the outlet pipe, comes off the engineer's stage-discharge design and is shown on the plan to the inch. Those dimensions are not suggestions and they are not the place for field judgment. A low orifice drilled an inch bigger than the plan changes the release rate for every small storm. Build the structure to the elevations and the openings on the approved detail, and if a dimension cannot be built as drawn, that is a call to the engineer before concrete, not after.

Orifices, weirs, and the low-flow opening

The openings in the outlet structure come in two basic shapes, and they meter water differently. An orifice is a hole, a round or square opening the water is pushed through under the depth of water above it. A weir is an edge the water flows over, like the lip of the riser or a notch cut in it. Orifices control well at depth and are how the low, frequent flows usually get metered. Weirs pass a lot of water for a given rise and are how the bigger storms usually get handled.

The low-flow orifice is the small opening down low that controls the frequent, small storms, and it is the one that causes the most trouble in the field. It has to be small to meter a small flow to a low release rate, and a small hole is exactly what leaves and trash and sediment plug. A clogged low-flow orifice turns a detention basin into an accidental retention pond, holding water it was supposed to release, which then either floods the basin or breeds mosquitoes or both. The low orifice is the reason the structure gets a trash rack and the reason somebody has to inspect it.

Sizing the orifices and weirs is the engineer's job, driven by the release rate each storm has to meet, the maximum ponding depth, and the drain-down time. The dimensions and elevations are on the plan. Build them as drawn, and do not enlarge an orifice in the field to make a basin drain faster, because draining faster than the design is the same compliance failure as a basin that will not drain at all. If the basin is not draining, the answer is almost always a clogged opening to clear, not a bigger one to cut.

The emergency spillway and what happens in the storm bigger than the design

Every basin needs a path for the water to leave safely when a storm exceeds what the outlet structure can pass, and that path is the emergency spillway. The outlet handles the design storms. The spillway handles the one bigger than that. Without it, when the basin fills past the top of the riser faster than the riser can drain, the water rises until it pours over the lowest point of the embankment, and water pouring over an earth embankment cuts it apart. A breached embankment dumps the whole basin at once on whatever is downstream, which is the failure the entire structure exists to prevent.

The spillway is built to take that overflow somewhere it will not do damage. It is commonly a broad, armored channel or a weir set above the design high-water level and below the top of the embankment, sized to pass an extreme event, often referenced to a 100-year storm or a larger check flood depending on the size of the basin and what sits downstream. Good practice puts the spillway over undisturbed ground at the end of the embankment, not over the fill, because the fill is the part that erodes.

Here is the blunt part. Do not block the emergency spillway, ever. It gets graded flat for a wider lawn, filled to square off a parking area, planted with a screen of shrubs, or fenced across, and every one of those turns the safety valve off. The spillway looks like useless dead ground for years, right up until the storm that needs it arrives, and then it is the only thing standing between a high pond and a washed-out embankment. Keep it clear, keep it armored, and keep the elevation it was built at. The exact storm it has to pass comes from the engineer and the local code, so hedge the number to them, but the rule does not bend: the spillway stays open.

The embankment that holds the water in

The embankment is the earth dam that impounds the basin, and on a pond of any size it is a structure that fails hard when it is built or kept up wrong. It holds water, and water finds every weakness in earthwork. The two ways it fails are overtopping, which the spillway prevents, and seepage that turns into piping, which compaction and the right soil prevent. Piping is water working a path through the fill until it carries soil with it, opens a channel, and collapses the embankment from the inside.

Building it to hold means compacting the fill in lifts to the density and moisture the geotech specifies, not dumping and tracking it. It means a low-permeability core or the right clay content so water cannot move through the fill freely. It means an anti-seep collar or an approved equivalent on the outlet pipe where it passes through the embankment, because the contact between pipe and soil is a classic seepage path, and a leaking pipe joint or a missing collar is a documented cause of piping failure. None of these are field calls. They are the geotechnical design, and the fill placement usually gets tested as it goes in.

Keep trees and deep-rooted shrubs off the embankment. Roots open channels for seepage, and a tree that blows over tears a root ball and a void out of the dam face. On embankments large enough to be regulated as dams, no woody growth is allowed at all, and that rule is enforced. A basin above a certain height or storage volume is a regulated dam under the state's dam-safety program, with its own design, inspection, and maintenance requirements that go well beyond an ordinary pond. Where that line sits varies by state, so the engineer and the dam-safety authority govern whether a given embankment is a regulated structure.

The sediment forebay that protects the main basin

A sediment forebay is a small settling pool at the point where runoff enters the basin, built to catch the coarse sediment before it spreads across the whole pond. The water comes in concentrated, hits the forebay, slows down, and drops its heavy load right there in one defined spot. It is the same idea as the pretreatment on a bioretention cell, sized for the bigger flows a detention basin sees.

The reason it earns its place is maintenance, not treatment. Sediment is going to arrive at the basin no matter what, and it has to be removed before it fills the storage the basin needs for peak control. Without a forebay, that sediment settles in a thin layer across the entire basin floor, which is slow and expensive to clean and means working the whole basin. With a forebay, most of the load drops in one small, accessible pool you can dig out with a single machine in a fraction of the time. Clean the forebay and you protect the storage volume and keep the load off the outlet.

The forebay gets cleaned out on a schedule tied to how full it is, commonly when it has lost about half its volume, and that cleanout is a maintenance line item somebody has to own and budget. It needs real access for a machine, a stable bottom to dig to without tearing up a liner, and a marker for the cleanout elevation so a crew knows when half is gone. A forebay nobody can reach with equipment is a forebay that never gets cleaned, which defeats the reason it was built.

Underground detention where there is no room for a pond

Where land is too tight or too expensive to give up a surface basin, the detention goes underground. The function is identical, storing the storm and metering it out slow, but the storage sits in buried chambers, large-diameter pipe, or a concrete vault under a parking lot, a drive aisle, or a building pad instead of an open pond. On a dense urban infill site or a data center maxing out its footprint, underground detention is often the only way the numbers work.

The systems are usually plastic arch chambers or crates, runs of large HDPE or corrugated metal pipe laid in parallel and surrounded by stone, or a cast or precast concrete vault. Open-bottom chamber systems also let some water infiltrate where the soils allow it. Whatever the form, the storage volume and the outlet control still come off the same stage-storage and stage-discharge design as a surface basin, and an outlet structure still meters the release to the permit limit.

The catch with underground systems is that they are out of sight, which makes maintenance easy to ignore until it is a failure. Sediment still accumulates inside the chambers and the pipe, and an underground system that silts up loses storage just like a pond does, except you cannot see it happening and you cannot dig it out with a machine from above. These systems need isolator rows or sediment sumps, real access points, and a jet-vac maintenance plan built in from the start. The structural design, the loading for the traffic above it, and the sizing are the engineer's, and an underground system with no access for cleaning is a deferred failure with a date on it.

Water quality and the permanent pool

Peak control and water quality are two different jobs, and a plain dry detention basin only does the first. It slows the water down, but the water that leaves is about as dirty as the water that came in, because it does not sit long enough for much to settle. Where the permit requires treatment, the design adds a quality function on top of the peak control, and that usually means time and a pool.

The wet pond does it with its permanent pool. Runoff enters, mixes into the standing water, and the next storm pushes the older, settled water out while the new sediment drops to the bottom. The days the water spends in the pool let sediment settle and biological processes work on nutrients and pollutants. Extended detention does a lighter version with time alone, holding the small storms long enough to settle some of the load before the basin empties. The volume set aside for this, often called the water-quality volume or WQv, is a runoff depth off the drainage area the basin has to capture and treat, and it is sized separately from the peak-control storage.

The infiltration-and-filtration approach to water quality, the bioretention cells and rain gardens that filter runoff through engineered soil, is covered in its own guide and is often used alongside a basin rather than instead of it. The split is worth keeping straight: a pond settles and detains, a bioretention cell filters and infiltrates, and a site may need both to meet its permit. The water-quality volume, the treatment method, and how the credit is calculated come from the local stormwater manual and the engineer, so hedge those numbers to the design.

The design storms the basin has to handle

A basin is not designed for one storm. It is designed for a set of them, each with its own job and often its own release limit. The common set is the 2-, 10-, 25-, and 100-year events, and the engineer routes each one through the basin to confirm the outlet and the volume handle it. The smaller, frequent storms test the low-flow control and often the water-quality drawdown. The larger storms test the upper outlet stages and the storage. The extreme storm tests the spillway and the freeboard.

A storm's return period is a probability, not a calendar. A 100-year storm is the storm with a 1 percent chance of being equaled or exceeded in any given year, which means a site can see two of them a decade apart and the name still holds. The basin has to pass the rare one safely even though it may never arrive while anyone who built it is still around, which is exactly why the spillway and the freeboard get built and then ignored until they matter.

Which storms apply, what release each one is held to, and the rainfall depths that define them are entirely a function of the local stormwater code and the regional rainfall data the engineer uses, and they vary widely from one jurisdiction to the next. This is the part to hedge hardest. Do not assume the storm set or the release limits from one project carry to the next, and do not size or check anything off a remembered number. The design storms, the routing, and the limits come off the stamped plan and the adopted code, full stop.

Building the basin to the grades and proving it with the as-built

The storage volume lives in the grades, so building the basin is building to the stage-storage the engineer designed. The bottom elevation, the side slopes, the high-water level, and the contours at each depth are on the grading plan, and the volume the basin holds at every stage depends on hitting them. Cut the basin shallow, leave the side slopes too steep, or set the bottom high, and the basin holds less than the design at the depths that matter, which means it cannot store the storm it was sized for. The surface grading that feeds runoff to the basin, the swales and the positive drainage that get the water there, is its own subject covered in the drainage and grading guide.

Side slopes get built stable and, where the basin is mowed or accessed, mowable, commonly flatter than a 3:1 grade on the parts crews walk and mow, with the actual slopes set by the plan and the geotech. A dry basin usually wants a low-flow channel or a slight grade across its bottom so it actually drains to the outlet instead of leaving a wet, mucky low spot that never dries and cannot be mowed. A basin floor graded dead flat ponds in puddles the design never intended.

Shoot an as-built survey when the basin is done and compare it to the design. The as-built is what proves the basin holds the volume it was permitted for and what the reviewer checks against the plan. The two elevations worth getting exactly right are the outlet structure openings, which set the release, and the basin bottom and high-water contours, which set the storage. A basin that was never surveyed as-built is a basin nobody can prove was built to hold what the permit credited, and that gap becomes the owner's problem at the first inspection.

Liners, clay, and what the subgrade soil decides

The soil under the basin decides whether it can hold water or whether it leaks, and that is a different question for a dry basin than for a wet one. A dry detention basin is supposed to empty, so a bottom that lets some water soak away is no problem and can even help. A wet retention pond has to hold a permanent pool, so a bottom that leaks is a pond that drains down between storms and loses the standing water its water quality depends on.

On a wet pond over sandy, permeable soils or fractured rock, the pool will not stay without a liner. A liner is commonly a layer of compacted clay, often called out around a foot thick with cover soil over it, or a synthetic geomembrane, or a bentonite treatment, picked to match the site and sealed at the seams and penetrations. The geotech investigation is what tells the engineer whether the native soil holds water on its own or needs a liner, and that report drives the call.

The same investigation governs the embankment soils, the seasonal high water table, and whether the subgrade can carry the structure. A high water table changes how a dry basin drains and whether a wet pool even needs a liner, because groundwater can hold the pool up by itself. None of this is a field judgment. Test the soils, build to what the geotech and the engineer specify for the liner and the subgrade, and raise it before you build if what you dig into does not match what the report assumed.

The inlet and protecting against scour

Where runoff enters the basin it comes in fast and concentrated, usually out of a pipe or a channel, and fast water hitting bare earth digs. An unprotected inlet scours a hole, undercuts the pipe, and washes the eroded soil straight into the basin as sediment the maintenance crew then has to remove. The inlet is one of the points on the whole site where flow is most concentrated, so it is one of the points that has to be armored.

Energy dissipation at the inlet breaks up that concentrated flow before it touches soil. The common forms are a riprap apron, a bed of graded stone the water spreads and slows across, or a plunge pool, or a baffle below the inflow that knocks the energy out, which doubles as a spot for the heaviest sediment to drop. The inlet apron and the sediment forebay often work together, the apron killing the velocity and the forebay catching the load.

Size and detail the dissipation to the flow it will see, which the engineer sets. Undersized riprap washes downstream in the first big storm and leaves the soil bare again, so the stone gradation and the apron length are part of the design, not a field guess. The same principle holds at the outlet end where the pipe discharges downstream: that point gets an apron too, because a controlled release dumped onto bare soil cuts a crater just as readily as an unprotected inlet does.

The basin during construction: sediment trap first, detention basin second

While the site is under construction it is bare dirt, and bare dirt sheds mud. So the detention basin footprint very often does double duty during the build, serving as a temporary sediment trap or sediment basin that catches the muddy runoff off the disturbed site before it leaves the property. This is part of the construction stormwater program and the site's SWPPP, the plan that keeps sediment on the job and out of the storm system and the receiving water. The full set of construction erosion controls, the silt fence, the inlet protection, the stabilized entrances, lives in the erosion-control side of the work.

Running the basin as a sediment trap during construction protects the downstream water, but it also fills the basin footprint with the sediment it traps. That is the part crews miss. The basin cannot do its permanent detention job full of construction sediment, so before it is brought online as the permanent BMP, the trapped sediment gets cleaned out and the basin is graded and finished to its design elevations. A temporary sediment basin is commonly converted to the permanent basin once the drainage area is stabilized and the disturbed acreage draining to it drops below the threshold the permit sets.

The handoff from temporary control to permanent BMP is a real step with real consequences, and it has to follow the SWPPP and the permit. Convert too early, while the site is still shedding mud, and the new permanent outlet structure clogs with construction sediment. Skip the cleanout and the basin starts its permanent life already short on storage. The sequence, the stabilization criteria, and the conversion requirements come from the construction stormwater permit and the engineer, so confirm them rather than assuming.

Why do detention ponds need maintenance?

The number one reason detention ponds fail is that nobody maintains them. Not bad design, not bad construction. Maintenance nobody did. A basin is a structure that fills with sediment, grows woody plants in the wrong places, and clogs at the outlet, and every one of those gets worse on its own until the basin no longer does its job. The work is not complicated. It just has to actually happen, year after year, for the life of the site.

The recurring tasks are short and they all protect a specific function. Remove sediment from the forebay and the basin before it eats the storage the peak control depends on, commonly on a cleanout schedule tied to a percent of capacity lost. Mow the basin and the embankment so woody plants never get established on the dam. Keep the outlet, the trash rack, and the low-flow orifice clear so the basin drains at its design rate. Inspect the embankment for seepage, settling, animal burrows, and erosion. Keep the emergency spillway open and armored.

The operation and maintenance plan is usually required by the permit, and it spells out who does what and how often. That obligation runs with the property for the life of the site, which means the owner inherits it and it survives the property changing hands. Most failures in the field are not engineering problems sitting on a clogged, silted-in, tree-covered basin. They are years of skipped maintenance that an inspection finally caught. Build the basin right and it still fails if it is abandoned. Maintain it or it fails. That is the blunt truth of these structures.

The outlet clogs, and that is why ponds flood

If a detention basin floods the site it sits on, the first thing to check is the outlet, because a clogged outlet is the most common reason a basin overflows when it should be draining. The outlet meters the water out. Plug it and the water has nowhere to go but up, and up means over the design high-water level, into the freeboard, toward the spillway, and onto whatever the basin was supposed to protect. The basin is full of water it cannot release, which is the exact opposite of its job.

The low-flow orifice and the trash rack are the usual culprits. The orifice is small by design, so leaves, sticks, trash, grass clippings, and a slug of sediment will block it, and once it blocks the basin holds water it was supposed to let out within hours. The trash rack over the riser is there to keep the big debris off the openings, and it clogs too, matting over with leaves and floatables until the rack itself becomes the blockage and water cannot even reach the structure. A clogged rack and a clogged orifice produce the same result: a basin that will not drain.

So you clear it, and you inspect it after storms, because right after a storm is when the debris has just arrived and when a blockage will flood the basin if it is not pulled. Walk the outlet, rake the trash rack clean, clear the orifice, and confirm the basin is drawing down on schedule. This is the single highest-payback maintenance task on the whole structure and the one most likely to be skipped between site visits. A basin floods on the day the outlet is blocked, not the day it was built.

Standing water, mosquitoes, and nuisance

A dry detention basin that holds water it should have released is a mosquito problem. Mosquitoes need standing water for several days to complete their cycle, so a basin that draws down on schedule never gives them the window. A basin that ponds for days because the outlet clogged or the bottom was graded flat hands them exactly the habitat they need. The fix for mosquitoes in a dry basin is almost never spraying. It is getting the basin to drain.

This is one reason the drawdown time is part of the design and why guidance often caps it, with a maximum drain time in the range of about 48 to 72 hours commonly used to limit mosquito breeding and keep the vegetation alive. A low-flow channel across the basin bottom that drains to the outlet keeps the floor from holding puddles between storms. A wet retention pond manages the same risk differently, with a permanent pool deep enough and circulated enough to support the fish and predators that keep larvae down, rather than the shallow, stagnant water that breeds them. Either way, the nuisance is a symptom. A basin that drains and a pool that stays healthy do not breed mosquitoes, and the design that delivers that comes from the engineer.

Inspecting the embankment, the outlet, and the basin

Inspection is what catches a problem while it is still cheap to fix, and on a basin it focuses on the parts that fail. Walk the embankment for seepage, soft or wet spots on the downstream face, settling or slumping, animal burrows, and any woody growth getting started. Check the outlet structure and the trash rack for debris and the orifice for blockage. Check the forebay for how full it is. Check the emergency spillway is clear and undamaged. Check the inlet and outlet aprons for scour. Confirm the basin draws down in the design window after a storm.

The timing that matters most is right after a real storm, because that is when seepage shows on the embankment, when the outlet has just taken its debris load, and when you can actually watch whether the basin draws down on schedule. A dry-weather walk catches the slow problems. A post-storm walk catches the ones that flood the site. Both belong in the routine, and the post-storm check is the one that earns its keep.

Basins large enough to be regulated as dams carry a separate, formal inspection requirement under the state dam-safety program, often on a set schedule by a qualified inspector, with the findings reported to the regulator. That is a different and stricter obligation than an ordinary pond inspection, and where it applies it is not optional. Whether a given embankment crosses that line, and what the inspection regime is, comes from the dam-safety authority and the engineer, so confirm the basin's regulatory status rather than assuming it is just a pond.

Records, the O&M plan, and proving the work happened

The operation and maintenance plan is the document that says what the basin needs, how often, and who is responsible, and it is usually a condition of the permit rather than a nicety. It runs with the property, so the current owner owns the obligation no matter who built the basin or who owned it before. An inspector asking whether the basin is being maintained is really asking to see the records, because a basin that drains today proves nothing about whether it was cleaned last year or will be cleaned next.

So the value is in documenting the work as it happens: every inspection, every sediment cleanout with how much was removed, every time the outlet was cleared, every embankment issue found and fixed, with dates and photos. That record is what shows the basin is doing the job the permit credited it for, and it is what protects the owner when a downstream complaint or a routine audit puts the basin under review. A clogged, silted basin nobody logged is a violation waiting for an inspector to find it. A maintained basin with a clean record is a closed question.

This is the kind of recurring, scheduled, photo-backed field record that a tool like FieldOS is built to hold. Log each inspection and cleanout against the specific basin, attach the photos of the outlet and the embankment, and keep the running history in one place the owner and the inspector can both pull up. Carry that documentation per the engineer's O&M plan and the permit conditions, because the plan defines exactly what has to be recorded and how often, and it is the plan, not this guide, that the inspector checks against.

What to document

The record on a basin is what proves it was built to the design and kept up to the permit, and it has to survive the basin outliving the people who built it and the property changing hands. Capture the as-built and the recurring maintenance both, because the first proves it was built right and the second proves it still works.

Hedge the cleanout triggers, the inspection intervals, and the release rates to the engineer's O&M plan and the permit, because those are what set the actual thresholds. The table below is the working set of what a crew records on the structure and on each visit.

Common mistakes

• Skipping maintenance until sediment fills the storage the basin needs for peak control.
• Letting the outlet, trash rack, or low-flow orifice clog, so the basin floods instead of draining.
• Blocking, filling, or planting over the emergency spillway, turning off the safety valve.
• Allowing seepage, animal burrows, or trees and brush on the embankment that holds the water in.
• Building the basin off-grade, so the stage-storage volume is wrong and it cannot hold the design storm.
• Enlarging an orifice in the field to drain faster, which fails the release limit the same as a clogged one.
• Running no O&M plan and keeping no inspection records, so there is no proof the basin works.
• Bringing the basin online still full of construction sediment from its time as a sediment trap.
• Building a dry basin where the plan called for a wet pond, losing the water quality the permit credited.

Field checklist

Standards and references

The documents that govern a detention basin are local, and that structure is the actual shape of stormwater regulation, not a way to dodge specifics. The local or state stormwater code and BMP or design manual set the release limits, the design storms, the sizing methods, and the construction details, and they vary widely between jurisdictions. Build to the manual the reviewer is using and the limits in the site's stormwater permit, which is usually issued under the NPDES program and, for many sites, tied to the municipality's MS4 permit. The water-quality volume, the peak-control limits, and the storm set all come off that code, not a remembered number.

The engineered design itself, the stage-storage and stage-discharge curves, the routing, the outlet sizing, the embankment, the liner, is the civil and geotechnical engineer's, and it is stamped. The geotech report governs the soils, the compaction, the liner decision, and the subgrade. During construction, the work falls under the construction stormwater permit and the SWPPP, again under the NPDES program, with the erosion and sediment controls that are required and inspected. Embankments large enough to be regulated as dams fall under the state's dam-safety program, which adds its own design, inspection, and maintenance requirements above an ordinary pond, and the threshold that triggers it is set by the state.

All of the storm sets, volumes, release rates, and structure sizes in this guide are described to show how the pieces fit, not as values to build from. Every one of them is set by the stamped design, the adopted local code, and the AHJ for the specific site. The field job is to build the outlet and the volume to that design, keep the outlet and the spillway clear, and maintain the basin per the O&M plan, because a basin only works if it is built to the curves the engineer routed and kept up for the life of the site. Cross-check the bioretention guide for the infiltration and water-quality BMPs that often run alongside a basin, and the drainage and grading guide for the surface grading and outlets that feed it.

Units, terms, and conversions

Detention work picks up terms from hydrology, civil design, and dam safety, and the same basin reads differently across a permit, a grading plan, and an outlet detail.

Flow rates are in cubic feet per second, cfs, in most US work, with the release limit set as a peak cfs the outlet may not exceed. Storage volumes are in cubic feet or acre-feet, or expressed as a runoff depth in inches over the drainage area for the water-quality volume. Storm size is named by return period, the 2-, 10-, 25-, and 100-year events, which are annual probabilities, not calendar guarantees. Drawdown and drain-down times are in hours.

Detention

Holding stormwater temporarily and releasing it slowly so the peak rate out is no higher than pre-development; the basin empties between storms

Retention

Holding a permanent pool that never fully empties, which adds water-quality treatment on top of peak control

Peak attenuation

Cutting the highest flow rate leaving the site by storing water faster than the outlet releases it, the core job of a basin

Outlet control structure

The riser, orifice, and weir assembly that sets the release rate, often multi-stage for different design storms

Stage-storage

The relationship between water depth in the basin and the volume it holds at that depth, set by the grades you build

Forebay

A small settling pool at the inlet that catches coarse sediment before it spreads across the basin, making cleanout easier

Emergency spillway

The armored overflow path that safely passes the storm bigger than the outlet can handle, protecting the embankment from overtopping

Freeboard

The vertical distance between the design high-water level and the top of the embankment, a safety margin against overtopping

WQv

Water quality volume, the runoff the basin is sized to capture and treat, set by the local manual and permit

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is bioretention, and is it the same as a rain garden?
• How much should the ground slope away from a house?
• When do you need a SWPPP?
• What is a French drain?
• What is pervious concrete?