Estate road drainage and the section 38 adoption process

Estate road drainage is adopted by the highway authority under a section 38 agreement, not by the water company, and the split between the two regimes decides who maintains every gully, carrier drain and outfall on a new development for the next century. Section 38 of the Highways Act 1980 lets a highway authority agree to adopt a street, and the drainage that serves that street comes with it. Anything the authority will not take, someone else has to.

What the highway authority adopts and what it refuses

The adoptable package is narrower than most layouts assume. A highway authority will normally take the carriageway, footways, verges, the gullies and their connections, the carrier drain within the highway, and the outfall arrangement up to the point of discharge. Street lighting is sometimes adopted and sometimes left with a management company, depending on the authority.

Refusals cluster around anything needing specialist or frequent maintenance. Open sustainable drainage features such as swales and basins are usually refused by highway authorities, because their staff and budgets are set up for pipes and gullies rather than for vegetation. Permeable surfacing on an adoptable carriageway is refused by many authorities outright and accepted by some on parking bays only, on the basis that the maintenance regime for restoring permeability is not one they operate. Proprietary treatment devices, tree pits with structural soil, and anything with a manufacturer's service contract usually fall outside as well.

Establish the adoption boundary before the layout is fixed, not after. The related question of who holds the rest of the system is set out in our note on SuDS adoption and maintenance.

Gullies, carrier drains and outfall arrangements

Highway drainage design is governed by the authority's own design guide, drawing on Manual for Streets for residential streets and the Design Manual for Roads and Bridges for anything of higher order. The principles are consistent even where the detail varies.

Gully spacing is set by the area of carriageway each gully has to drain, and a common working figure is one gully for around 200 m² of drained surface, closer at low points, at the tangent points of bends and upstream of every crossing point. Longitudinal falls have to keep flow moving without producing excessive velocities, and crossfalls need to shed water to the channel rather than pond against the kerb line.

The carrier drain takes the collected flow to the outfall, and that is where the adoption boundary usually sits. Where the outfall is a public sewer, the connection needs the sewerage undertaker's agreement. Where it is a watercourse, land drainage consent from the lead local flood authority is needed for the structure, and the discharge rate has to match what was agreed at the planning stage in the Drainage Strategy.

Permeable surfacing and where SuDS cross the boundary

The awkward cases are the ones where a sustainable drainage train starts in the adoptable highway and finishes somewhere else. Road water running into a roadside swale, then to a basin in public open space, then to a watercourse, crosses at least two ownerships and possibly three.

Deal with it by agreeing three things in writing before technical approval. First, the physical interface: a defined structure, usually a headwall, manhole or flow control, that marks where one party's responsibility ends. Second, the rights: an easement or deed of grant allowing the highway authority's water to discharge into land it does not own, and allowing the maintaining party access. Third, the failure case: what happens if the downstream party stops maintaining, and whether the highway authority has a step-in right.

Without those, you get a system that works perfectly and an adoption that stalls for a year while solicitors invent the answer. The position on the statutory approving body for sustainable drainage in England remains unresolved, as our piece on Schedule 3 SuDS approval explains, which is why these arrangements are still being negotiated site by site.

Bonds, commuted sums and technical approval

Three financial mechanisms run alongside the agreement.

1. The bond, set as a proportion of the estimated cost of the highway works, held so the authority can complete the street if the developer fails. It is released after adoption, sometimes in stages.
2. Commuted sums, paid for items the authority will adopt but which cost more to maintain than its standard details. Block paving, non-standard lighting columns, street trees and any retained sustainable drainage feature commonly attract one.
3. Inspection and technical approval fees, charged as a percentage of works cost or on a published scale, covering the authority's checking and site supervision.

Take the current figures from the authority's published developer information. They are revised, they differ substantially between authorities, and a figure carried over from a scheme in the next county is a good way to lose money on a land bid.

Technical approval itself is a document exercise: drawings, calculations, materials, a construction specification and a safety audit. Expect comments, expect to resubmit, and allow for the authority's own timescales rather than yours.

Sequencing section 38 with the planning conditions

The planning permission usually carries a condition requiring the estate road and drainage details to be approved before work starts, and a further condition tying occupation to completion of the access. Those conditions and the section 38 process test the same drawings, but they are separate decisions made by different teams, sometimes in different organisations.

Run them together. Submit the same drawings to both, tell each that the other is looking at it, and resolve any difference in comments before building anything. Where the district is the planning authority and the county is the highway authority, the highway officer's consultation response on the application is the first sign of what technical approval will say.

Sign the agreement before the road is built. A street constructed ahead of the agreement can be refused, and the authority is entitled to require it be opened up for inspection.

Management company arrangements for the remainder

Whatever is left over goes to a management company: the open space, the attenuation basin, the private drives, the unadopted parking courts, and often the sustainable drainage features. Residents pay for it through an estate charge.

Two things make that arrangement work better. A schedule, drawn up at the design stage, listing every asset with its owner, its maintenance operation and its frequency, so nothing sits in the gap between the highway authority, the sewerage undertaker and the management company. And funding from the outset, meaning the developer pays the management company's costs until enough plots are sold, so the first residents are not funding a basin for four hundred homes on their own.

A schedule of that kind also answers the question a buyer's solicitor asks about estate charges, which is worth having ready before the first plot is marketed.

Councils are increasingly interested in this, both because the lead local flood authority wants to know the drainage will be maintained, as covered in our note on what the lead local flood authority checks, and because unadopted estates generate complaints for years.

This is general guidance, not legal advice; check the position with your highway authority, your lead local flood authority and your local planning authority before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.