What is a Drain Run

A drain run is a defined length of drainage or sewer pipe extending between two identifiable points in a network. The endpoints may be manholes, inspection chambers, junctions, rodding points, changes in pipe configuration or other locations that allow the section to be distinguished from the adjoining drainage system.

The term is practical rather than a description of a particular pipe product. A drain run can be short or long, carry foul water or surface water, and form part of a domestic drain, private drainage system or larger sewer network. What makes it a run is that the section can be treated as one identifiable length for purposes such as mapping, CCTV inspection, cleaning, condition assessment or repair planning.

Defining drainage as individual runs is particularly useful because underground networks are continuous systems. A defect described only as being “in the drain” provides little useful location information. Recording it within a specific run, together with a measured distance from a known access point, creates a much more precise reference.

The Endpoints Define What Belongs to a Drain Run

A drain run is normally identified by its start and end points. These references turn an otherwise continuous underground pipe into a manageable section that can be described, inspected and recorded.

Manholes and inspection chambers are convenient boundaries because they provide visible, identifiable nodes in the network. A run might therefore be recorded as extending from chamber MH01 to chamber MH02. The next section from MH02 to MH03 becomes a separate run even if the pipe material and diameter remain unchanged.

Not every network provides such regular access. Smaller drainage systems can contain buried junctions, limited access or long lengths between chambers. In these cases, the way runs are defined depends on the network layout and the purpose of the survey or maintenance record.

A run boundary may be useful where there is a significant change in:

• pipe diameter;
• pipe material;
• direction or alignment;
• gradient;
• drainage function;
• connection arrangement;
• access conditions.

A change does not automatically create a new drain run in every recording system. The important point is that the convention used for defining runs should remain consistent enough for another person to identify the same section later.

Direction also needs to be recorded clearly. A run described as MH01 to MH02 is not necessarily interchangeable with MH02 to MH01 when survey observations are being located by distance.

If a CCTV survey starts at MH01 and records a defect at 12.4 m, that measurement refers to distance travelled from MH01. If the same pipe is surveyed in the opposite direction, the recorded distance to the same defect will be different.

For a run of length L, a simple conversion can be made where both measurements follow the same pipe centreline:

distance from opposite end = L – distance from original end

For example, on a 30 m run, a defect 8 m from one end would theoretically be approximately 22 m from the other. In practice, survey distance measurements can contain some error due to wheel slip, debris, cable behaviour and equipment calibration, so calculated positions should not be treated as survey-grade coordinates without appropriate verification.

A clear run reference should therefore contain more than a length. At minimum, the two endpoints and direction need to be identifiable where observations are being located within the pipe.

A Run Provides the Reference Framework for CCTV Inspection

CCTV drainage surveys are commonly organised around individual pipe sections because the camera has to enter at an access point and travel towards another known part of the system. Treating each section as a drain run provides a logical structure for the survey record.

A typical run record can combine physical pipe information with observations made during the inspection.

This framework is particularly useful when a pipe contains several different observations. Instead of creating an isolated record for each crack, root intrusion, displaced joint or deposit, the observations can be associated with one defined section.

A survey might establish, for example, that one run contains a lateral connection at 4.8 m, root ingress at 11.2 m and a displaced joint at 17.5 m. Those observations have greater practical value when they are tied to a known run and survey direction.

The run length also provides context for the distribution of defects. Three defects concentrated within one metre can indicate a different local condition from three similar defects distributed over a 60 m section.

CCTV equipment does not always reach the intended endpoint. Heavy deposits, a severe deformation, a collapse or another obstruction may stop the camera partway through the run. The inspected length and the defined run length should then remain distinguishable.

If a 40 m run is defined between two chambers but the camera reaches only 24 m, the remaining 16 m has not automatically been shown to be defect-free. It is simply uninspected from that direction unless another access route provides coverage.

This distinction becomes important when inspection records are later used to plan rehabilitation. The unit being managed may still be the full drain run even though condition information is incomplete.

Hydraulic Conditions Can Change Within a Single Run

Defining a drain run as one record does not mean conditions are uniform throughout its entire length. Pipe gradient, invert level, deposits, connections and local deformation can all affect how flow behaves within the section.

For a gravity drain, the difference in invert elevation between the two endpoints is closely related to the overall gradient. A simplified average gradient can be expressed as:

S = Δh / L

where S is gradient, Δh is the difference in invert level and L is horizontal length.

If the invert falls by 0.30 m over a 30 m horizontal run, the average gradient is:

S = 0.30 / 30 = 0.01

This corresponds to a fall of 1 in 100.

An average gradient does not prove that every part of the run has the same fall. Local settlement can create a depression even when the two endpoint levels indicate an acceptable overall fall.

That distinction is important in drainage diagnostics. Water can remain standing in a local low point, sediment can accumulate there and the CCTV camera may show a section of pipe partially submerged even though the run has an overall downstream fall.

Other features that can make conditions vary along a run include:

1. local pipe deformation;
2. displaced or poorly aligned joints;
3. changes in bedding or ground support;
4. intruding connections;
5. sediment or scale reducing the effective bore;
6. root growth at individual joints;
7. changes in flow caused by lateral connections.

A drain run is therefore a convenient management unit rather than proof of uniform hydraulic or structural behaviour.

The same distinction applies to pipe capacity. If one part of a run has a significantly reduced bore, that local restriction can influence the hydraulic performance of the entire section. Describing the run only by its nominal diameter would not capture that condition.

Connections also matter. A run may receive progressively more flow as lateral drains enter along its length. The discharge near the downstream endpoint can consequently be greater than near the upstream endpoint even though both locations belong to the same defined run.

Working by Drain Run Makes Network Records More Precise

Dividing a network into runs provides a practical basis for comparing information collected at different times. A particular section can be inspected, cleaned, repaired and later reinspected while retaining the same endpoint references.

This is useful when deterioration is being monitored. If an earlier survey recorded a defect at a known position within run MH04 to MH05, a later inspection can return to the same section and compare its condition.

Run-based records can also help separate local problems from network-wide ones. If repeated blockages occur within the same section while adjoining runs remain clear, investigation can concentrate on the characteristics of that run rather than treating the entire drainage network as one undifferentiated system.

For maintenance planning, individual runs can be associated with:

• previous blockage locations;
• recurring root ingress;
• sediment accumulation;
• known structural defects;
• access limitations;
• previous cleaning or rehabilitation work;
• sections requiring repeat inspection.

The usefulness of these records depends on stable identification. If chamber references change between surveys or the start and end points are recorded inconsistently, historical comparisons become much harder.

Length measurements also need context. A CCTV counter measures camera travel rather than independently establishing the geographical position of the pipe. Differences can arise between measured survey length, mapped length and distances derived from surface coordinates.

For complex networks, run references can be linked to asset maps or digital drainage records. Each run then represents an edge connecting network nodes such as chambers or junctions. Diameter, material, invert levels, condition observations and other attributes can be attached to that edge.

This node-and-run representation reflects the physical organisation of many drainage systems. Chambers and junctions identify points where the network can change or branch, while runs describe the pipes connecting those points. It allows a blockage, defect or maintenance activity to be associated with a defined section instead of an approximate area of an underground network.