What Is a Drainage Study?

When your jurisdiction will demand one

Commercial and multi-family projects almost always need a drainage study. Single-family projects on larger or sloped lots often need one as well. The usual trigger is impervious area. Once you pave or roof enough square footage, the city wants proof the water has somewhere to go. Requirements tighten in floodplains and in areas with known drainage problems, because a mistake there affects more than your own parcel. Do not wait for a correction letter to find out. Ask at the pre-application stage, check the submittal checklist, and scope the study with your site plan. Finding the requirement late is how a grading plan, a basin location, and a permit timeline all get reopened at once. Put the question on the record early, in writing, with the site address and the proposed impervious area attached. A clear early answer lets you budget the study, reserve space for mitigation, and set a submittal date the whole team can work toward instead of discovering a major civil scope after architectural design is already advanced.

What a passing study has to prove

A passing study proves one central point with numbers a reviewer can check: post-project runoff does not exceed what the site and the downstream system handled before development. The engineer models rainfall on the site before and after development, comparing how much runs off roofs and pavement against what soaked in before. Then the study sizes mitigation so the developed condition stays controlled. Every map, calculation, and basin size in the report exists to support that proof. A study that describes drainage in general terms without tying the numbers to your actual site, your actual impervious area, and your actual discharge point will not clear. Reviewers check this closely for a reason. Keep that proof visible in every drawing set you issue. When a client, lender, or partner asks how the site handles stormwater, you should be able to point to the same numbers the reviewer will check, stated the same way, rather than offering a verbal assurance that the final report may or may not support.

What goes into a complete submittal

You get a stamped report with calculations, drainage maps, and basin sizing that becomes part of the permit submittal. That package needs to read as one consistent story. The maps show where water collects and where it goes. The calculations show how much runoff the site produces before and after development. The sizing shows that the chosen mitigation holds and releases that water as intended. If the site plan changes after the study is done, the study has to change with it. Added pavement, a larger roof, a moved building footprint, or a relocated basin can all invalidate earlier numbers. Keep the civil plans and the study in lockstep through every revision, or expect review to catch the mismatch. Version control sounds dull until it saves a review cycle. Date every plan revision, note every footprint change in the transmittal, and confirm the study revision matches before anything goes to the city. Most mismatches are not engineering errors at all. They are filing errors, and they are the cheapest kind to prevent.

How runoff is modeled, in plain terms

Rain falls on every surface, and surfaces answer differently. Grass and open soil soak in a share of it. Roofs and pavement soak in almost none, so nearly all of that rain becomes runoff, and it arrives faster. Development usually replaces soak-in surfaces with shed-water surfaces, which is why a developed site can overwhelm a ditch, a storm drain, or a neighboring lot that handled the old site easily. The study models that before-and-after change for the storms the jurisdiction requires, then works out where the extra water will be held, slowed, or directed. You do not need to run the model yourself. You do need a site plan stable enough for the model to mean something. If any part of the site story is unclear, say so before the study is finalized. A discharge route that needs confirmation, an easement that needs checking, or a neighboring system whose condition is unknown should be flagged and resolved while the engineer can still design around the answer, not defended afterward.

Detention, retention, and other mitigation that actually gets approved

Mitigation is how the study closes the gap between the before condition and the after condition. The standard tools are detention or retention basins, underground chambers, and bioswales, sized so post-project runoff stays within the allowed limit. Which tool fits depends on your site. Basins need room and the right elevations. Underground chambers save surface area where land is tight or valuable. Bioswales handle water quality and flow in a shallower footprint. None of this is decorative landscaping added at the end. It is engineered infrastructure with a footprint, a depth, and maintenance access, and it competes for space with parking, landscaping, and utilities. Reserve the space early, before the site plan hardens around it. Location inside the site matters as much as total size. Place mitigation where water naturally collects and where maintenance crews can reach it after construction. A basin squeezed into leftover space at the wrong elevation may satisfy a drawing while failing in service, and relocating it later usually means regrading the whole site.

What drives cost and turnaround

Cost and speed follow scope, not just site size. A simple site with a clear discharge point, stable plans, and a standard mitigation layout moves fast. A sloped site, a floodplain, a known downstream problem, or a discharge point the jurisdiction disputes will take more modeling, more coordination, and more review cycles. Late site-plan changes are the biggest self-inflicted driver, because each one can force recalculation and resizing. Your fastest path is simple: commission the study early, freeze the impervious footprint before final calculations, and answer review comments with revised numbers rather than explanations alone. Torch scopes the study against your jurisdiction checklist up front, so the work starts aimed at the reviewer who has to accept it. Ask for a scope letter before work starts. It should name the jurisdiction checklist being designed to, the deliverables included, and the number of review-response rounds covered. That one page prevents the most common billing dispute on this kind of work: an owner who assumed review responses were included and an engineer who assumed they were not.

Review comments we see most, and how to avoid them

Reviewers return drainage studies for predictable reasons. The study and the site plan disagree on impervious area or basin location. The mitigation is described but not sized, or sized for a footprint that no longer matches the plans. The discharge point is asserted rather than shown. Downstream capacity is assumed instead of addressed. Requirements in floodplains or problem areas are treated as standard when the jurisdiction applies tighter ones. Each of these costs a full review cycle. Avoiding them is not cleverness. It is discipline: one current site plan, calculations that match it line for line, maps that show the full path of the water, and sizing a reviewer can reproduce from the numbers on the page. Keep a simple comment log from the first review letter. Each comment gets an owner, a response, and a plan or report page where the fix appears. Reviewers notice when a resubmittal answers their list completely and in order, and incomplete responses are a leading reason a second cycle turns into a third.

What Torch delivers

Torch delivers a stamped drainage study built as a permit document, not a memo: calculations, drainage maps, and basin sizing ready to join your submittal, with PE stamps backed by Apex Grid Engineering. We start from your jurisdiction requirement and your current site plan, model the before-and-after runoff, and size detention, retention, underground chambers, or bioswales to fit the ground you actually have. If review comes back with comments, we revise the engineering, not just the wording. The set is not finished when it is drawn, it is finished when it clears. Send us the site plan and the reviewer checklist, and we will tell you plainly whether a study is required, what it needs to contain, and what it will take to get it accepted. If you are buying the land, ask about drainage before you close, not after. A short feasibility conversation about triggers, mitigation space, and discharge can change what a parcel is worth to your project, and it costs a fraction of redesigning a site plan around a basin nobody left room for.

The bottom line

A drainage study is cheap insurance against the most expensive site problem there is: water in the wrong place. Expect it on nearly any project that adds pavement or roof.

More engineering answers · Get a quote