Section 38 agreements: adopting estate roads
A developer's guide to Section 38 agreements for new estate roads, from design approval and construction standards to inspection, bond and adoption.
At a glance
| Route | What it covers | Who agrees or signs | Security and maintenance |
|---|---|---|---|
| Section 38 | New highway built for possible adoption | Highway authority and developer; agreement terms apply | Security and maintenance terms are set by the agreement and authority |
| Section 278 | Works to an existing highway | Highway authority and developer | Security and defects terms depend on the agreement |
| Section 104 | Proposed sewer for adoption | Sewerage undertaker and developer | Security and maintenance terms depend on the undertaker and agreement |
A Section 38 agreement lets a highway authority adopt a new road after the agreed works and conditions are met. It applies to a new street intended for public maintenance, not changes to an existing highway. Those changes normally use a separate Section 278 agreement. A development may need both. Section 38 can cover its estate roads, while Section 278 covers an access or junction to the existing network.
So, the distinction matters from the first layout. An estate road designed only around construction access may not meet the authority’s eventual adoption requirements. Agree the intended highway status, design standard, drainage route and maintenance arrangements with the authority before the road design is fixed. The authority is not obliged to adopt a road merely because it has been built.
What the law provides
Section 38 of the Highways Act 1980 enables a highway authority to enter an agreement with a person proposing to construct a highway. The agreement can provide for the road to become a highway maintainable at the public expense from a date set in the agreement, once the specified works and conditions are met. The statutory provision is the starting point; the authority’s current design guidance, agreement form and technical requirements determine the project detail. Read Section 38 of the Highways Act 1980 alongside the relevant authority’s guidance.
Adoption is not the same as planning permission, building control approval or completion of the homes. These processes have different purposes and decision-makers. A planning condition may require an adoption agreement or an approved road design, but planning consent does not itself transfer the highway maintenance responsibility.
Establish the scope before the design is locked
First, identify the roads and associated assets proposed for adoption. The red-line or highway boundary, footways, verges, street lighting, signs, structures, drainage and service corridors can all affect what the authority is being asked to maintain. Do not assume every item within the street scene automatically forms part of the adopted highway.
Ask the authority which design standards and submission process apply. Requirements vary by authority and by road type. Typical design subjects include carriageway geometry, visibility, turning provision, pavement construction, gradients, footway widths, lighting, signing, utilities coordination and drainage. Confirm who reviews each element and what drawings, calculations, specifications and supporting information are required.
Drainage needs particular attention. Establish whether highway runoff connects to a public sewer, a watercourse, a highway drain or a sustainable drainage system, and identify the relevant owner and approvals. A SuDS feature can have a separate adoption or maintenance arrangement. Read Civcon’s guide to SuDS drainage adoption as a companion, not as a substitute for the Section 38 agreement.
What the agreement normally has to settle
In practice, the agreement records the parties’ obligations, the approved works, the applicable specification, inspection arrangements, security and the route to adoption. The exact provisions and terminology vary. Have the project team check the current authority form rather than relying on a template from another council or an earlier scheme.
Financial security is commonly required to protect the authority if the developer does not complete the agreed works. The form, amount, reduction mechanism and release conditions are authority-specific and should be confirmed from the agreement. Do not assume a bond percentage or release date from another project. The agreement may also address inspection charges, defects, maintenance, completion evidence and the process for the authority to take over the road.
Where works affect an existing highway, the related Section 278 agreement is a separate interface. The design, programme and boundaries need to align, but the two agreements have different statutory functions. Civcon’s Section 278 guide explains the existing-highway works route.
Construction and inspection
Once the technical design and agreement requirements are clear, turn them into an inspection-ready construction plan. Confirm the approved drawings on site, the hold points requiring inspection, the records to retain, and how proposed changes will be submitted for acceptance. Keep current drawings accessible to the site team and record departures before they become buried beneath later work.
The authority’s inspections do not transfer responsibility for the contractor’s quality control. The developer and its contractor remain responsible for delivering the works in accordance with the agreement and approved documents. Maintain records that can demonstrate what was installed: material information, test results, inspection records, drainage checks and as-built information where required by the authority.
Do not cover work that the authority needs to inspect before the relevant inspection or release is recorded. An inaccessible asset can create avoidable investigation and remedial work later. Agree notice arrangements with the inspecting team and allow for the authority’s process rather than treating an inspection request as an informal courtesy.
If a design change becomes necessary, assess whether it affects technical approval, planning conditions, utilities, drainage, the agreement or the adoption boundary. Obtain the right approval before implementing it. An informal site instruction is not a reliable substitute for the authority’s formal acceptance where the agreement requires one.
Completion is not automatically adoption
A road can be physically open while contractual and technical adoption steps remain outstanding. The agreement sets the evidence and conditions needed to reach the relevant completion stage and, ultimately, adoption. Confirm the sequence with the authority, including any inspections, outstanding defects, certificates, as-built documents and maintenance obligations.
Keep a close-out schedule from the start of construction. Assign an owner to each required item and keep evidence in a format the authority can review. Clarify when maintenance responsibility changes and what obligations continue during any maintenance period. Those details depend on the agreement and must not be inferred from the date the first resident moves in.
Common coordination failures
The first is designing before the authority’s adoption expectations are understood. That can leave the developer with a layout or detail that must be revised after planning or procurement has advanced.
The second is treating drainage as a late-stage detail. Outfall permission, sewer connections, easements and long-term maintenance responsibilities can involve parties beyond the highway authority. Map those interfaces early and make sure the adoption proposal is consistent with them.
The third is allowing construction changes to diverge from approved information. Maintain a controlled drawing set and route changes through the approval process before work proceeds.
The fourth is assuming the highway authority’s inspections are the contractor’s quality system. They are not. Plan independent checks and retain records that support the eventual handover.
Appointing a delivery contractor
For a Section 38 package, ask prospective contractors how they will manage approved drawings, inspection notices, drainage interfaces, quality records and close-out information. Establish the boundary between design responsibility, developer obligations and construction delivery. Confirm how the package interfaces with any Section 278 works at the site access.
Civcon delivers highways infrastructure works and drainage packages. For a scheme with an adoption requirement, share the authority’s current standards, design status, scope boundary and programme assumptions when requesting a discussion. That makes it possible to identify interfaces and information gaps without assuming that every authority follows the same process.
How we approach it
First, map the proposed adoption boundary and list every road asset. Next, speak with the highway authority about its current standards, submission route and agreement terms. Bring the latest layout, levels, drainage strategy, utility information and planning conditions. Then coordinate technical approval, security, inspection points and the construction sequence. Before work starts, check that the contractor holds the accepted drawings and knows how to request inspections. Finally, track tests, as-builts, defects and handover evidence against the agreement. This sequence exposes missing decisions before they become site changes.
This comparison is a starting point, not a substitute for the signed agreement. Each authority may set different project terms.
Sources and next step
Primary legislation: Highways Act 1980, Section 38. The agreement and the relevant highway authority’s current guidance should be checked for project-specific requirements.
Before freezing the estate road design, confirm the authority, adoption boundary, applicable standards, drainage ownership and the documents required for technical approval. Then align the agreement and construction inspection plan with those decisions.
Further primary reference: Highways Act 1980, Section 278, for the distinct route covering works to an existing highway.
