Chapter 11 storm drainage design, roof drain sizing, combined sewers, secondary drainage.
2
hours
0.2
CEUs
Codes and Standards
1.7.3
This course covers material relevant to the following ICC certification exams:
Chapter 11 storm drainage design, roof drain sizing, combined sewers, secondary drainage.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamStorm drainage is one of the more consequential systems a plumbing reviewer signs off on, because its failure mode is structural rather than merely a nuisance. Rainwater is not sewage, and the code treats it as its own distinct system — separate in purpose, sizing logic, and disposal path — from the sanitary drainage system that carries wastewater out of the building. This course explains why that separation matters, how the primary-plus-secondary drainage concept functions as a built-in safety redundancy, and where storm water is and is not permitted to go once it leaves the roof or paved surface. Reviewers who internalize this logic catch the failure patterns that recur most often on real projects, well before they become an emergency call during a storm.
Size roof drains and storm drainage piping for rainfall intensity
Storm drainage governs one job: getting rainwater off roofs and paved areas and safely away from the building before it can accumulate. It is easy to blur storm drainage together with sanitary drainage — both involve pipes and drains, and both leave the building — but they are not the same system. Storm water carries none of the health hazard that drives sanitary drainage requirements, but it carries a hazard sanitary drainage does not: volume. A rain event can deliver an enormous quantity of water onto a roof in a short window, and if that water has nowhere to go, it accumulates exactly where it landed.
That accumulation is why storm drainage is a life-safety and property-protection concern, not a convenience feature. A roof that cannot drain ponds water, and ponded water is heavy. A roof assembly never designed to carry standing water as a sustained load can deflect under that weight, and a deflected low spot tends to pond more water, adding more weight and deflecting the structure further still — a genuine structural overload and collapse hazard. That is why storm drainage sizing and redundancy receive the scrutiny they do in plan review; a system that merely handles most rain events most of the time is not adequate.
The roof-drainage system, conceptually, has two halves working together. The primary system — roof drains, scuppers, or gutters, depending on configuration — is sized and positioned to carry away the design rain event under normal, unobstructed conditions. On its own, that primary system is never treated as sufficient. Debris blocks drains, ice dams a gutter, and any of those conditions can defeat the primary path exactly when a storm is delivering the most water. Because the primary system can and does fail in the field, the code requires a second, independent overflow path — the secondary drainage system — engineered to activate only when the primary system cannot keep up. This primary-plus-secondary structure is the single most important concept in this course.
Sizing the primary system is not a rule of thumb applied uniformly everywhere. The system is sized to a design storm — the rainfall intensity expected for that specific location, drawn from local rainfall data rather than a generic assumption. A reviewer's job is not to independently derive that figure, but to verify the design actually used the correct local basis rather than one borrowed from an unrelated project or climate.
Consider a plan review for a new commercial building with a large, low-slope roof. The documents show roof drains at reasonable intervals and piping that routes water down through the building and out to the site. Before accepting that layout, the reviewer's first move is to confirm what design storm the engineer actually used — is it tied to the rainfall data appropriate for this jurisdiction, or does it look like a template pulled from an unrelated project? The reviewer also checks that the roof drainage design was coordinated with structural plan review, since the roof framing must account for ponded water as a real load case if drainage is ever impaired. During the rough-in inspection that follows, the inspector confirms that what was installed matches what was approved — drains at the intended low points, piping routed as shown, and no field substitutions that quietly reduce capacity without a corresponding recalculation.
The most common error is treating storm drainage sizing as a rough approximation rather than a calculation tied to a verifiable design basis — a design that "looks about right" is not the same as one actually sized against correct local rainfall data. A related error is evaluating the roof drainage layout in isolation from structural plan review, since drainage performance and structural performance are two views of the same problem. A third is accepting a design showing only a primary path, with no independent secondary or overflow provision — because primary systems clog, freeze, or otherwise fail in foreseeable ways, that omission removes the exact safeguard the code relies on. The correction: confirm the design-storm basis, verify structural coordination, and confirm both a primary and an independent secondary path are shown before moving on.
Code Reference: IPC Chapter 11 - The code establishes minimum requirements for size roof drains to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Understand secondary drainage requirements and overflow provisions
Secondary drainage — sometimes called overflow or emergency drainage — is where the storm drainage system's real safety logic lives, and it deserves to be understood as more than a redundant pipe added out of caution. The premise is straightforward and unforgiving: primary drains clog. Leaves, roofing debris, ice, sediment, and ordinary wear all reduce a primary drain's capacity over time, and a system that performs perfectly on the day of inspection is not guaranteed to perform perfectly during the storm that matters most. Because that failure mode is foreseeable rather than exotic, the code treats secondary drainage as a required, independent system capable of carrying water away even when the primary system cannot.
The word independent is doing real work in that description. A secondary or overflow path that shares piping, a leader, or a discharge point with the primary system is not actually a backup at all — whatever blocked the primary path is equally capable of blocking the shared portion of the "secondary" path, defeating the entire purpose of a second system. The secondary system has to function entirely on its own for it to be a genuine safeguard rather than a paper requirement.
That independence traces directly back to the ponding-and-structural-load concept from Module 1. Secondary or overflow drainage exists specifically to interrupt a dangerous feedback loop: standing water is heavy, added weight can deflect a roof structure, and a deflected surface tends to pond even more water, compounding the load further. An independent overflow path breaks that cycle by giving water somewhere to go the moment the primary path is overwhelmed. Overflow provisions are also deliberately visible in many configurations — a scupper discharging water where it can be seen from the ground functions as a built-in warning that the primary system has failed, turning a silent, worsening hazard into an observable one.
Picture a flat commercial roof where the construction documents show primary roof drains at appropriate intervals, but nothing else — no scuppers, no overflow drains, no secondary path of any kind. On paper, the primary system might appear adequately sized for the design storm, tempting a reviewer moving quickly to sign off on that basis alone. But sizing the primary system correctly answers only part of the question; it says nothing about what happens the day that system is partially blocked by debris, an ordinary, expected occurrence over the life of a roof.
The reviewer's responsibility is to recognize that a primary-only design leaves the building with no safeguard against exactly the failure mode secondary drainage exists to address. The correction is not a minor comment — it is a requirement that the design add an independent overflow provision, discharged independently of the primary system rather than tied back into it. If the project proceeds without that correction and a storm later clogs the primary drains, the roof has no fallback: water ponds, the structure deflects, and the ponding deepens in a self-reinforcing cycle. Catching the missing secondary system at plan review, rather than after a roof is already ponding, is precisely the value this course reinforces.
The most consequential mistake is a design that provides no secondary or overflow drainage at all, treating the primary system as though it were failure-proof. A closely related but more subtle error is providing something labeled secondary drainage that is not actually independent — an "overflow" drain tied into the same leader as the primary system offers no real protection once that shared component is blocked. The correction: confirm a secondary or overflow provision exists, and trace it to its discharge point to confirm it never merges with the primary system.
Code Reference: IPC Chapter 11 - The code establishes minimum requirements for secondary drainage requirements to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Apply combined sewer and stormwater management requirements
Once water leaves the roof through the primary and secondary systems, it has to travel somewhere, and the conveyance path follows a consistent conceptual sequence: roof drains collect the water, leaders (sometimes called conductors) carry it down through or along the building, and that water joins the building storm drain, which delivers it to an approved point of disposal. What counts as an approved point of disposal depends on the site and jurisdiction — a storm sewer serving the area, or, where allowed, an approved alternative such as controlled surface discharge or an on-site detention or retention feature. The consistent thread is that the disposal point has to be approved; storm water does not simply go wherever gravity and convenience suggest.
The single most important boundary in this conveyance chain separates storm drainage from the sanitary system. Storm water and sanitary wastewater are different in kind, and the code maintains that distinction all the way to disposal — storm drainage is not permitted to discharge into the sanitary sewer. This no-cross-connection principle exists because a sanitary system that also has to absorb storm flows during a rain event can be overwhelmed by volume it was never sized to carry, which can back sewage up into the building or overload downstream infrastructure. Some older municipal systems do intentionally carry both flows together as a deliberate public-utility decision, but that is not license for a building's own plumbing design to casually route storm water into a sanitary connection; the building-level requirement runs the other direction — keep the two systems separate unless the local authority has specifically established and approved a combined arrangement.
Storm drainage is not limited to what falls on the roof. Site and subsurface drainage extends the same concept to the ground itself. Area drains collect surface water at grade — low points in paving, courtyards, or site depressions — and route it into the storm system rather than letting it pond or find its own path toward the building. Foundation and subsoil drains address a related concern: managing groundwater and subsurface moisture at and below the foundation, which connects directly to the below-grade waterproofing principle covered elsewhere in this program — a foundation drain and the waterproofing or dampproofing protecting the foundation wall work as complementary lines of defense against the same underlying water-management problem. Both ultimately discharge to the same kind of approved location required for roof drainage, never released wherever is most convenient, and never routed into the sanitary system.
Consider a site plan review for a commercial project with substantial paved parking and a below-grade mechanical room. The civil drawings show area drains collecting runoff from low points in the parking area, and the foundation plan shows a subsoil drain around the perimeter of the below-grade space. The reviewer's task is to trace where each system actually discharges. If both route to the building storm drain and ultimately to an approved storm sewer or another approved disposal method, the design follows the correct conceptual path. If instead one of those drains is shown tying into the sanitary lateral — sometimes done informally because a sanitary cleanout happens to be nearby — that connection is a cross-connection the reviewer needs to catch before it is buried and inaccessible. The same tracing exercise applies to field inspection: an inspector should follow each drain's piping to its termination and confirm it lands where the approved plans show, rather than assuming visible drains at grade are automatically routed correctly underground.
The recurring failure pattern is a storm drain — an area drain, a foundation drain, or a roof leader — cross-connected into the sanitary system, usually not from intent to violate the code but because a sanitary line was the nearest and easiest connection point in the field. Because that connection is often made underground, it has to be caught during plan review and rough-in inspection, rather than discovered later when a sanitary system starts backing up during storms for no apparent reason. A second common failure is directing storm discharge to a location that was never actually approved. A third is treating site and subsurface drainage as separate from the roof drainage system, when in practice all of it has to be coordinated as one storm drainage strategy sharing the same disposal-point requirements and prohibition against merging with the sanitary system. The correction: trace every storm drainage component from its source to its actual point of discharge, confirm that point is approved, and confirm at every junction it never merges with the sanitary system.
Code Reference: IPC Chapter 11 - The code establishes minimum requirements for combined sewer to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
This course provides comprehensive professional development in IPC storm drainage systems, built around a single unifying idea: storm water is not sewage, and every requirement in this chapter flows from managing it as its own dedicated system, sized to the right design basis, backed by genuine redundancy, and delivered only to an approved point of disposal. Roof drainage functions as a paired primary-and-secondary system because the primary path can and does fail, and that redundancy exists to prevent the well-understood hazard of progressive ponding and structural overload. That same discipline extends outward from the roof to the site — area drains, foundation drains, and the building storm drain all answer to the same logic, and all of it stays separated from the sanitary system. Participants develop the plan-review and field-inspection habits needed to verify the design-storm basis, confirm genuine independence between primary and secondary drainage, and trace every discharge point back to an approved location.