What is the Section 38 Application Process?

What a Section 38 agreement is

A Section 38 agreement is a contract between a developer and the local highway authority, made under Section 38 of the Highways Act 1980. It sets the standard the new estate roads must be built to, and it commits the authority to adopt them once they are built and to maintain them at public expense from that point on. Until adoption is certified, the roads remain private and the developer remains responsible for them.

That is the whole mechanism. Everything else, the technical approval, the bond, the inspections, the maintenance period, exists to give the authority confidence that it is taking on a road it will not have to rebuild.

Two things follow from that, and they explain most of the friction on these projects. The authority is not a consultee here, it is the future owner, so it reviews the design as something it will have to live with for decades. And the agreement is a legal document as well as a technical one, so solicitors on both sides are involved and that takes its own time.

When you need one, and when you don’t

You need a Section 38 where new roads are intended to become publicly maintained. On most housing estates of any size that is the expectation, and it is often secured by a planning condition or a Section 106 obligation.

You do not need one where:

  • the road is a private drive serving a small number of dwellings and will stay private
  • the development will be managed by a management company that takes on the roads, the lighting and the drainage
  • the work is an alteration to an existing public highway rather than a new road. That is Section 278, and the two are compared below
  • you only need a vehicle crossing over the footway. That is a Section 184 application, a much smaller piece of work

There is one point that catches developers out. Under the Advance Payments Code at Section 219 of the Highways Act 1980, where a building is erected fronting a private street, the authority can require money to be deposited with it before work starts, to cover the cost of making up that street in future. Entering into a Section 38 is one of the routes that exempts a scheme from that requirement. If you intend the roads to stay private, check the position early rather than discovering it at build stage.

Deciding this early matters more than it sounds. A road built to private standards cannot simply be offered for adoption later, because the construction, the drainage and the levels will not meet the authority’s specification, and nobody will have inspected it while it was being laid.

Section 38 and Section 278 compared

Both sit in the Highways Act 1980 and both involve the highway authority, which is why they get confused. They do different jobs.

Section 38Section 278
What it coversNew roads built by a developer that the authority will adoptWorks to the existing public highway, paid for by a developer
Typical exampleEstate roads on a new housing developmentA new junction, a widened carriageway, a right turn lane, a signalised access
Who builds itThe developer, to the authority’s specificationEither the developer under licence, or the authority at the developer’s cost
Who owns it at the endThe authority, once adoptedThe authority. It already did
Usual triggerPlanning condition or Section 106 obligation requiring adoptionPlanning condition requiring access works before occupation
SecurityBond or cash depositBond or cash deposit, and often payment in advance
Maintenance periodYes, commonly twelve months before adoptionYes, commonly twelve months before the works are taken over

Many schemes need both. A new estate with a new access onto a classified road needs a Section 278 for the junction and a Section 38 for the roads behind it, and the two have to be designed as one piece of highway even though they are two agreements on two timetables.

The process, step by step

The sequence below is the shape of it. Authorities vary in what they call each stage and in how much they run in parallel.

  1. Pre-application discussion. Establish which roads the authority will consider adopting, where the adoption boundary runs, which design standard applies, and what it wants to see. This is the cheapest hour on the whole project.
  2. Detailed design and technical approval. A full design package: horizontal and vertical alignment, construction build up, drainage, levels, street lighting, signs and markings, visibility splays, swept paths, and the adoption plan showing exactly what is offered. The authority checks it and comes back with comments. Expect more than one round.
  3. Road safety audit. Carried out at design stage and again before the road opens, by auditors independent of the designers. Items raised have to be answered, and where they are not designed out, the reasons have to be accepted.
  4. The agreement itself. Drafted by the authority’s legal team, with the developer’s solicitor on the other side. The technical approval usually has to be settled before the agreement can be completed, because the agreement refers to the approved drawings.
  5. The bond. The agreement does not complete until the security is in place.
  6. Construction, with inspection. The authority inspects as the work proceeds, which is the point of adoption: it sees the sub base and the drainage before they are covered up. Work built without inspection at the right stage may have to be opened up again.
  7. A first certificate. Issued when the roads are substantially complete and to standard, this starts the maintenance period. Names vary by authority.
  8. The maintenance period. Commonly twelve months, during which the developer remains responsible for defects.
  9. The final certificate, and adoption. Issued at the end of the maintenance period once outstanding defects are made good. The roads become publicly maintainable and the bond is released.

The bond

The bond is security. It exists so that if the developer stops work, becomes insolvent, or walks away from a half built estate, the authority has the money to finish the roads to a standard it can adopt, rather than a street of houses served by an unfinished road it did not agree to take on.

It is usually a surety bond from a bank or an approved insurer. A cash deposit is normally accepted as an alternative, and on small schemes it is sometimes simpler, though it ties up money for the whole construction and maintenance period.

The amount is usually based on the authority’s own assessment of the cost to complete the works, which is often higher than the developer’s build cost. That is not the authority being awkward: it would be procuring the work at short notice on a site somebody else has left.

Two points worth knowing. Many authorities will reduce the bond as work is certified complete, so it does not sit at its full value for the whole build, but this is not automatic and you should ask. And the bond is released on the final certificate, not on the first one, so it stays in place through the maintenance period.

The bond is not the same thing as a commuted sum. The bond is temporary security that comes back to you. A commuted sum is a payment you do not get back, contributing to the future maintenance of items the authority is taking on.

Fees

The authority charges for its own work, and these are separate from the bond. Expect:

  • A technical approval or checking fee, covering the review of the design. Usually calculated as a percentage of the estimated works cost.
  • An inspection or supervision fee, covering site inspection during construction. Also commonly a percentage.
  • Legal fees, the authority’s own costs in drafting and completing the agreement. The developer pays both sides.
  • Commuted sums, where the authority is adopting items with a maintenance liability it would not otherwise carry. Street lighting and drainage features are the usual ones.

Percentages and thresholds vary from authority to authority, and they are revised. Get the current figures from the authority you are dealing with rather than budgeting from what applied on your last scheme in a different county.

Timescales, and what actually causes the delay

As a guide, allow a minimum of three weeks for the first review of a submitted package, and at least two weeks for each subsequent revision. Review times differ from council to council. On real schemes the whole process from first submission to adoption commonly runs to many months, and more than a year is not unusual once the maintenance period is included.

The elapsed time on a Section 38 is rarely dominated by the authority’s review clock. It is dominated by:

  • Rounds of revision. Two rounds is normal. Five happens, and it is usually a sign the design did not start from the right standard.
  • The legal drafting, which often runs slower than the technical side and cannot finish until the technical side has.
  • Getting the bond in place, which involves a third party with its own process.
  • Unresolved adoption questions, particularly on drainage, where nobody has confirmed who is adopting what.
  • Land. Visibility splays or the adoption boundary crossing land the developer does not control, which is a legal problem, not a design one.

Drainage and adoption, which is where these schemes come unstuck

This is the part most likely to hold up a Section 38.

Highway drainage within the adopted boundary, the gullies and the carrier drains that take water off the carriageway, is normally adopted with the road under the Section 38. That is straightforward.

Foul and surface water sewers serving the development are a different route entirely. They are adopted by the water company under Section 104 of the Water Industry Act 1991, against the sewerage sector’s own design and construction guidance, on its own timetable. Two applications, two bodies, two sets of standards, and they have to agree with each other at the point where the highway drainage meets the sewer.

Then there are the SuDS features, and this is where it gets awkward. There is no SuDS Approving Body in England and no separate SuDS approval to apply for, because Schedule 3 of the Flood and Water Management Act 2010 remains uncommenced here. Surface water is dealt with through the planning system with the lead local flood authority consulted. We cover that in full on is there a SuDS Approval Body in England?

What that means for a Section 38 is that adoption of the SuDS elements is not resolved by a single approval. A swale or a filter drain within the highway boundary may be adopted by the highway authority, often with a commuted sum. An attenuation tank or a basin serving the development may be adopted by the water company under Section 104 if it meets the guidance. Anything that meets neither ends up with a management company, which has to be set up and funded, and which the planning authority will want to see evidence of.

The practical rule: decide the adopting body for every drainage element before the design is fixed, not after. The answer changes the design. A basin that a water company will adopt is not built the same way as one a management company will maintain, and moving between the two late means redrawing the scheme and going back round the approval loop.

Why Section 38 submissions stall

The recurring reasons are:

  • The adoption boundary was never agreed. The drawing shows a line, the authority expected a different one, and everything inside the discrepancy is disputed.
  • Levels and drainage were designed separately from the road. The falls do not work, the gully spacing does not suit the gradient, or the outfall is lower than the receiving system.
  • SuDS features with no adopting body. Covered above, and the single most common one.
  • Designed to the wrong standard. A scheme worked up to one manual when the local highway authority’s own design guide takes precedence.
  • Road safety audit items left unanswered, or answered by exception rather than designed out.
  • The Section 38 and the Section 104 submitted out of step, so each body is waiting on the other.
  • Visibility splays over third party land, discovered at technical approval.
  • Street lighting and structures treated as an afterthought, when both have their own approval route and their own commuted sum.

Most of these are decisions that were never made, rather than mistakes that were made. They are cheap to settle at the start and expensive to settle at revision three.

Frequently asked questions

What is a Section 38 agreement?

A contract between a developer and the local highway authority under the Highways Act 1980, under which the developer builds new roads to an agreed standard and the authority adopts them and maintains them at public expense once they are complete and certified.

What is the difference between a Section 38 and a Section 278?

A Section 38 covers new roads that the authority will adopt. A Section 278 covers works to an existing public highway, paid for by the developer. Many developments need both.

What is a Section 38 bond?

Security, usually a surety bond or a cash deposit, held so the authority can complete the roads to an adoptable standard if the developer does not. It is based on the authority’s estimate of the cost to complete, and it is released at the final certificate.

How long does a Section 38 take?

Longer than the review periods suggest. As a guide, allow a minimum of three weeks for the first review and at least two weeks for each revision, then add the legal drafting, the bond, and the twelve month maintenance period before adoption. On real schemes the whole process commonly runs to many months, and more than a year is not unusual.

Are Section 38 works inspected?

Yes. The authority inspects during construction, which is the point of the process. It needs to see the sub base and the drainage before they are covered.

Do I need a Section 38 if the roads will stay private?

No, but check the Advance Payments Code at Section 219 of the Highways Act 1980 before deciding, and make sure the management arrangements for the roads, the lighting and the drainage are set up, because the planning authority will ask.

How we help

We prepare Section 38 design packages and take them through technical approval. In practice that means producing the adoptable design, reconciling the highway levels with the drainage, agreeing the adoption boundary and the adopting bodies before the design is fixed, and answering the authority’s comments until the package is approved.

Drainage is our core discipline, and getting the Section 38, the Section 104 and the SuDS adoption route to agree with each other is the part that most often stalls a submission.

See highway design for the full scope, including Section 278, Section 184 drop kerb applications, junction design and swept path analysis, and our drainage design consultancy for the drainage strategy that sits behind it.

If you have a scheme with roads intended for adoption, or a submission that has come back with comments you would rather not work through yourself, get in touch.