Water and external systems · Drainage & Rainwater
Below-Ground Drainage Network System
A reference on why the faults in a buried drainage network gather at its chambers, its junctions, its connection point and the places where fall was lost, and on how bedding, access and stream separation govern it.
Educational reference entry. How this system behaves depends on climate, jurisdiction, loading, substrate, the adjacent systems it meets, how the building is used, the manufacturer's instructions and qualified professional design.
Overview
What buried drainage network is
A below-ground drainage network is everything between the point where water or waste enters a buried pipe and the point where it becomes another party's responsibility. That takes in the runs themselves, the material they are laid on and surrounded by, the junctions and bends, the chambers making the system reachable, and the arrangement at the boundary where it connects to a sewer, a treatment arrangement or a disposal point.
The pipe is the least eventful part of it. Blockages, collapses and misconnections cluster at chambers, junctions, connections and the places where the fall was lost, not in the middle of a straight run, and almost all of those follow from how the pipe was supported and arranged rather than from the pipe itself. A network is more usefully understood as a set of joints held at a constant slope by the ground around them.
Foul and surface water are kept apart wherever the receiving arrangement expects them to be, and that separation is a property of the whole network rather than of any pipe. A misconnection is invisible from the surface: nothing leaks, nothing smells, and the fault is found only by tracing. It is among the few construction defects that can persist unnoticed for the life of a building while continuously affecting something outside it.
Its nearest sibling is the site surface water collection system, and the boundary between them is the inlet. Collection is about shaped surfaces, kerbs, gratings and where water is caught; this system begins the moment water is inside a pipe. Soil, waste and vent pipework above ground within a building belongs to building services and is not covered here.
Terminology
Common names and aliases
These names describe the same assembly. The encyclopedia keeps one entry per system so that a trade term or a regional name never becomes a second, thinner page.
- underground drainage
- buried drain runs
- private drainage network
- external gravity drainage
- drain runs and inspection chambers
Purpose
What this system is intended to do
The job the assembly exists to perform, conceptually. An intention is not a guarantee that any particular build achieves it.
- Carry foul and surface water away from a building and its site under gravity, to where it becomes another party's responsibility.
- Hold a continuous fall, so that liquids and the solids they carry travel together rather than separating along the way.
- Stay reachable, so that clearing a blockage is a visit rather than an excavation through a finished surface.
- Keep foul and surface water in the streams the receiving arrangement expects to find them in.
- Survive the loads and the ground movement imposed by whatever is built or driven over it.
Composition
The roles this system is made of
What each part does in the assembly and what it depends on — never a product, a thickness, a fixing or a determination that anything is adequate for the role.
Order is not meaningful in this system. It is distributed rather than stacked: what matters is that the path connecting these roles stays continuous and unobstructed, not the order they are listed in.
- Service zoneGravity drain runs
The pipe runs carrying flow between inlets, chambers and the connection point. Their line and level do the work, and their material behaviour matters mainly through how it interacts with the support around them.
- SubstrateBedding, surround and backfill
The material the run is laid on, packed around and covered with. It holds the pipe at the level it was set to and spreads what is above it, and it is the component that decides whether the fall survives the backfilling operation.
- Jointing and sealingJoints, junctions and changes of direction
Every connection between lengths, every branch and every bend. These are where flow patterns are disturbed, where deposits begin, and where root ingress and infiltration find their way into an otherwise sound run.
- Cavity or voidInspection chambers and rodding access
The openings that make a buried network reachable, conventionally placed where the geometry is awkward. Their benching shapes the flow through them, and their spacing determines whether a rod reaches a blockage from either side.
- Control layerSeparation of foul and surface water
The arrangement keeping the streams the receiving system expects apart, from the first inlet to the boundary. It is not a physical layer but a discipline held across the whole network, and it fails silently at a single wrong connection.
- Edge and terminationConnection to the receiving system
The point where the private network meets a public sewer, a treatment arrangement or a disposal point. Ownership, permission and the level available all change here, and what is possible on a site is often decided at this junction alone.
- Service zoneVentilation of the network
The path allowing air to move through the system so that pressures caused by flow do not draw traps or force air the wrong way. It sits mostly above ground but exists because of what happens below it.
- ProtectionProtection beneath trafficked and built-over areas
Surrounds, slabs and lintels arranged where a run passes under a drive, close to a foundation or beneath a structure. Their job is to keep loads and settlement away from a pipe that has no way to accommodate either.
- Edge and terminationTransition at the building face
The opening through the wall or foundation where the network leaves the building, together with the first length beyond it. It exists so the structure and the ground can move independently, and it is arranged around that difference rather than around flow.
Interaction
How the parts work together
The reason this is a system rather than a list of parts: what depends on what, and what stops working when one part is changed.
The pipe and its surround are a single structural item. A rigid pipe carries load through its own wall and needs bedding supporting it evenly rather than at hard points; a flexible pipe borrows its shape from the material packed around it and deforms where that material is loose or uneven. In both cases the visible consequence is the same and it is not a crack, it is a dip in the fall, and a dip holds a little water and a little solid material after every use.
The fall is what makes a network self-cleaning, and it is a relationship between slope, flow and the solids being carried rather than a property of the pipe. A run laid flatter than intended, or one that has lost its fall locally, is where deposits begin, because the water there is too slow to move what it has been given. The deposit narrows the run, which changes the flow again, which deposits more, so one construction defect starts a process that accelerates on its own. What fall a particular run and duty calls for is settled by the drainage designer against the guidance that applies.
Junction geometry decides where that process begins. A branch swept in the direction of flow merges with the main run; a branch entering against it creates a standing disturbance in which paper, grease and grit collect every time either run is used. Abrupt changes of direction behave the same way, which is why chambers are conventionally placed at junctions and bends: where the awkward geometry is and where access is provided turn out to be the same decision.
Access provision converts an unreachable buried asset into a maintainable one, and its arrangement decides whether rodding reaches a blockage at all. A network in which every length can be rodded from either end and one in which most lengths cannot look identical from the surface and are ignored at the same cost; they differ entirely on the day something blocks, when one is a lifted cover and the other is a search followed by excavation through a finished garden or drive.
Where the network leaves the building it crosses a boundary between things that settle differently. The structure moves on its foundations and the ground outside moves on its own, so the opening through the wall and the first length beyond it are arranged to tolerate that difference rather than resist it. A rigid connection at that point feeds building movement into a pipe with no capacity to accommodate it.
Materials
Material families commonly met in each role
Commonly encountered, not recommended. Whether a material suits a given project depends on the whole assembly, the exposure, the manufacturer's documentation and qualified professional review.
Substrate
Concrete surrounds and haunching are commonly encountered where a run is shallow, sits beneath a trafficked surface or passes close to a structure. Whether a surround is called for, and what form it takes, is set by the drainage design rather than decided on site.
Primary support
Inspection chambers and manholes are commonly encountered constructed from these families, in built and precast forms. Which is used follows the depth, the ground conditions and what passes over the cover, all settled in the project documentation.
Edge and termination
Covers, frames and gratings at chambers and access points are commonly encountered in these families. What sits above them, whether a lawn, a path or a drive, governs the loading and sealing arrangement, and that is a matter for the designer.
Jointing and sealing
Chamber benching, cover bedding and connections into existing structures are commonly encountered detailed with these families. Pipe joints themselves belong to the pipe and are governed by the manufacturer's documentation rather than by a general choice.
Protection
Protective slabs and lintels bridging over a run near a foundation or beneath a hard surface are commonly encountered in these families. Their use follows from the relationship between the run, the loads above and the structure beside it.
Junctions
Where this system meets others
Interfaces are where most assemblies actually fail, so they are set out explicitly rather than left inside the prose. What resolves a junction is a detail designed for the specific building — not a rule of thumb.
The inlet as the boundary between collection and conveyance
Gullies, channels and yard inlets hand water over at exactly the point this system begins. What they trap, and whether their traps are maintained, determines what the buried runs are asked to carry and where the first deposits form.
Read about Surface Water Collection →Downpipe connections into the network
A downpipe entering a buried run brings leaf litter and grit straight into a pipe that has no interception of its own. Whether it discharges into a trapped gully or directly into the drain changes what can be cleared and from where.
Read about Roof Rainwater Drainage →Runs close to and beneath foundations
A drain trench beside a foundation removes support the foundation was relying on, and a foundation bearing over a drain imposes load the drain cannot take. That relationship is a structural decision rather than a drainage layout preference.
Read about Strip Foundation →Runs passing beneath a slab
A pipe under a floor slab is the least reachable part of any network and the one where a repair is most disruptive. Where a run passes through or under the slab, the opening also has to deal with differential movement between them.
Read about Ground-Bearing Slab →Penetrations through below-ground water-resisting construction
A drain crossing a basement wall or slab makes an opening in a continuous barrier, and the detail that closes it belongs to the barrier rather than to the drainage. Sealed pipe entries of this kind are among the most common leakage points in a basement.
Read about Barrier Waterproofing →Handover to a controlled discharge
Where surface water passes into storage before leaving the site, the network both feeds the store and receives what the flow control lets out. Its levels and surcharge behaviour set what the control can actually do.
Read about Attenuation Storage →
Considerations
Topics worth discussing
Which topics genuinely apply to this system and what to raise about them. Measured values, classes and ratings come from a qualified professional's design for the specific building, not from a reference page.
- Durability
- Failure is progressive rather than sudden: a slight loss of fall, a rough joint or a root at a junction each start a deposit that narrows the run and hastens the next. What looks like a blockage is usually the last stage of something years old.
- Movement
- Ground and structure settle at different rates, and the network crosses between them at every building face. Trees add another pattern of movement and of root growth, and both act on joints rather than on the middle of a run.
- Buildability
- Runs are set before most of the site exists and are then buried, driven over and built around by later trades. The fall achieved at laying is not necessarily the fall present at handover, which is why the network is conventionally checked after backfilling.
- Maintenance and access
- The one property an owner will care about is whether a blockage can be reached. Chambers built over by a later extension, buried under a raised patio or paved across are common, and each converts a routine visit into excavation.
- Interfaces
- What the network can do is decided at its connection point. The level, capacity and ownership of the receiving system govern what falls are available across the whole site, sometimes ruling out layouts that are otherwise sensible.
- Documentation
- A network is invisible and a record of it is the only practical way to know what connects where. Without one, tracing is required before any extension, and the misconnection risk rises with every alteration made in ignorance.
Design
Questions the design has to answer
The decisions this assembly turns on. They are questions rather than answers, because the answer depends on the building.
- Where does this network connect, who owns the receiving system, and what level is available there?
- Are foul and surface water kept separate, and does the receiving arrangement expect them to be?
- Where are the chambers, and can each length between them be rodded from either end?
- Does any run pass beneath the building, a drive or a future extension, and what protects it there?
- How close do runs come to foundations, and who has checked that relationship?
- Are there trees near the route, now or planned, and what has been assumed about their roots?
- What record of the finished network will be handed over, and in what form?
Boundaries
Commonly misunderstood points
Distinctions that are easy to blur, and the places where a familiar term means something narrower than it sounds.
- Adding fall reads as a free improvement, when a steeper run buys depth, and depth is paid for in excavation, in backdrops at chambers and in the level left at the connection.
- A blockage is rarely a pipe defect; it usually marks a junction, a bend or a place where the fall was lost during construction.
- Connecting a surface water run into a foul drain is not a harmless simplification, because it sends every storm through an arrangement not intended to receive it.
- Access chambers are not optional detail; without them a buried network can only be investigated by digging it up.
Conversations
Questions for qualified professionals
Bring these to the relevant qualified professional, manufacturer or authority. Requirements vary by project and location.
- Where does this drainage connect, and what permission or agreement covers that connection?
- Which runs are foul, which are surface water, and how has that been confirmed rather than assumed?
- What testing was carried out after backfilling, and what did it show?
- Where does the network pass beneath a structure or a trafficked area, and what protects it there?
- Has anything been built over an existing chamber or run, and what was agreed about that?
- What survey information exists for the network already on the site?
- How should the finished network be recorded so a future owner can work from it?
What this page does not do
- Falls, pipe sizes, chamber spacing and testing requirements are set by the drainage design and the relevant authority, and none are stated here.
- Connections to a public sewer, and building over or near an existing drain, are subject to permissions determined by the authority responsible for it.
- An existing network's route and condition are established by survey; assumptions drawn from where covers happen to be visible are frequently wrong.
- Foul drainage arrangements affect public health and are designed and altered by qualified professionals rather than adapted informally.
Related systems
How this system relates to others
Every link states what the relationship actually is, rather than leaving a bare list of related pages to be read as a suggestion.
Meets these systems
Systems this one physically meets. The junction is usually where the design problem lives, so these are worth reading together.
Commonly built alongside
Systems routinely present in the same building without necessarily touching this one.
Go deeper
Related Build Design Hub guides
Planning guidance behind the decisions this assembly involves.
Preparation
Related planning checklists
Owner-side preparation before the conversation where this system comes up.
Site Drainage and Rainwater Management Systems
Stages in the single route water takes from the surface it lands on to the point it leaves the site, each one defined by where it hands the water on.
Browse all drainage & rainwater entries →