If a new development road is meant to end up in public hands, section 38 highways adoption is usually the mechanism that gets it there. In theory, that sounds straightforward: the developer builds the road, the highway authority checks it, and once everything meets the required standard, the road becomes highway maintainable at public expense. In practice, though, Section 38 can become one of the slowest-moving parts of a scheme if it isn’t handled early and properly.
We see that tension all the time across planning and transport work. A planning permission may be in place, the layout may look settled, and yet the adoption route is still fuzzy, or worse, key technical issues such as drainage, geometry, visibility, levels, or bond arrangements are left to be sorted later. That “later” can be expensive.
For architects, planners, lawyers, surveyors, developers, builders, and local councils, the value of getting this right is obvious. Adoptable roads affect deliverability, sales, risk, estate management, future maintenance, and resident expectations. They also sit right at the intersection of planning, highways, engineering, and legal process.
In this guide, we set out what Section 38 really means in practice, when it is needed, what can be adopted, how it differs from Section 278, and where schemes commonly stall. We also look at the technical approval, inspection, bond, and maintenance stages that determine whether a road actually reaches final adoption, not just in principle, but on the ground.
What Section 38 Highways Adoption Means In Practice

Section 38 of the Highways Act 1980 allows a local highway authority to enter into an agreement with a developer for the making up of new roads so they can become part of the public highway network. That’s the legal framework. But in day-to-day project terms, it is best understood as a structured bargain.
The developer agrees to design and build a new estate road and associated infrastructure to the authority’s adoptable standard. In return, once the works are completed, inspected, certified, and any maintenance obligations have been satisfied, the authority adopts them as highway maintainable at public expense.
That matters because adoption changes who carries the burden. Before adoption, the developer usually remains responsible for defects, upkeep, and compliance. After adoption, the highway authority takes on future maintenance and most public highway liabilities, funded in the normal way through public resources rather than a private estate arrangement.
In practice, Section 38 is not just about carriageway surfacing. It can cover footways, kerbs, verges, drainage, lighting, signs, road markings, and in some cases structures or other supporting highway assets. It is a legal, technical, and financial package all at once.
And that’s why it tends to involve more than a simple engineering sign-off. If the design team treats adoption as an afterthought, problems often surface late, usually when they are hardest to fix.
When A Section 38 Agreement Is Needed

A Section 38 agreement is typically needed where a developer is creating a new road that is intended to serve the public and become adopted highway once complete. The classic example is a residential estate road, but the same principle can apply to mixed-use, employment, logistics, or commercial development where new internal roads are intended to connect into the wider public network.
The key point is that Section 38 is about new highway infrastructure that does not yet exist as public highway. If the intention is for that road to remain private and be managed by a management company or landowner, Section 38 may not be necessary. But if purchasers, occupiers, funders, or the local planning authority expect eventual public adoption, the agreement usually needs to be put in place.
Timing is important. In most cases, the process starts after planning permission has been granted, but before construction begins. Waiting until works are well underway is risky. Highway authorities generally want to review and approve detailed technical drawings, drainage proposals, levels, construction details, and specification information before the roads are built.
We’d also add a practical note: even where planning drawings show an access and internal layout, that does not mean the roads are automatically acceptable for adoption. Planning consent and adoptable highway approval are related, but they are not the same thing.
Which Roads And Features Can Be Offered For Adoption

The adoptable package under a Section 38 agreement usually includes more than many non-specialists expect. Yes, the carriageway is central. But highway authorities often assess the whole functional corridor and the assets needed to make it operate safely and maintainably over time.
Typical items that can be offered for adoption include:
- estate roads and shared surface streets
- footways and footpaths
- verges and visibility splays where relevant
- kerbs, edging, signs, and road markings
- street lighting infrastructure
- highway drainage systems serving the adopted road
- traffic calming features
- retaining structures or other supporting highway structures, where accepted by the authority
Whether a feature is accepted depends on two things: public function and compliance with standards. A road or asset may be physically present within the development, but if it mainly serves a private parking court, private drive, or gated area, the authority may refuse adoption. Likewise, a feature that is novel, difficult to maintain, or below standard can trigger a request for redesign or a commuted sum.
Drainage is a common boundary issue. Some authorities will adopt highway drainage linked directly to the road: others will require parts of the wider drainage network to remain under separate management arrangements. So the answer is rarely “everything within the red line”. It depends on purpose, ownership, specification, and local policy.
How Section 38 Differs From Section 278 And Private Street Arrangements
This is where confusion creeps in, especially on schemes with multiple access works.
Section 38 deals with the creation and adoption of new roads. The developer builds them, the authority checks them, and if the process is completed successfully, those roads become public highway maintainable at public expense.
Section 278, by contrast, is used where a developer needs to carry out works to the existing public highway. Think junction alterations, new signal equipment, crossing points, right-turn lanes, bus stops, or changes to kerbing and lining on roads that are already adopted. Section 278 does not, by itself, adopt new estate roads. It is about altering the public network that already exists.
Some schemes need both. For example, a housing site may require a new estate road within the site under Section 38, plus off-site junction improvements on the adjoining adopted road under Section 278.
Private street arrangements sit elsewhere again. These are roads that remain privately maintained, whether by residents, a management company, a landowner, or another private body. They may still need planning approval, drainage agreements, or licences for works affecting the public highway, but they do not pass into public maintenance through Section 38.
That distinction matters commercially. Private roads may give developers more design flexibility, but they also create long-term management and resident communication issues. Adopted roads reduce that uncertainty, provided the route to adoption is realistic from the outset.
The Main Parties In A Section 38 Agreement
At the centre of every Section 38 agreement is the relationship between the developer and the local highway authority. But in practice, several other parties usually shape the outcome.
The developer is the party promoting the scheme and taking responsibility for delivering the road works. If the site is being funded, sold in phases, or delivered through a housebuilder following a land promotion process, the exact identity of the contracting party matters. Authorities will want clarity over who is legally bound to complete the works.
The local highway authority, often the county council, unitary authority, or metropolitan borough, is the body deciding whether the road is acceptable for adoption. It reviews technical submissions, sets standards, inspects construction, manages certification, and eventually determines whether final adoption can occur.
Then there are the technical advisers. These often include the developer’s transport consultant, highways engineer, drainage engineer, street lighting designer, and legal team. The authority may also involve its own engineers, inspectors, legal officers, and, where relevant, structures or drainage specialists.
A bond provider or surety is another critical party. The authority usually wants a financial guarantee so that if the developer fails to complete the road to standard, funds are available to step in.
In our experience, schemes move fastest when these parties are aligned early. Where legal, technical, and commercial workstreams drift apart, Section 38 becomes a snagging list with no owner.
The Typical Section 38 Process From Planning To Final Adoption
The broad process is fairly consistent across England and Wales, even though local forms, standards, and terminology vary.
A development first secures planning permission with an indicative or approved road layout. That establishes the principle of access and internal movement, but not full adoptable detail. The developer then submits detailed engineering information to the highway authority for technical approval. Once the design is accepted, the authority’s legal agreement is prepared, fees are paid, and the bond level is set.
Construction can then proceed, subject to any pre-start requirements. During the works, the authority inspects key stages and may require material test data, drainage records, as-built information, and certification. If the road is substantially complete and fit to open, the authority may issue a provisional certificate or equivalent approval. A maintenance period follows, often around 12 months, during which defects must be rectified.
After that, a final inspection is carried out. If outstanding items, commuted sums, legal points, and certificates are all resolved, the authority can issue final adoption.
Smooth on paper. Less smooth when design details were weak at the start.
Planning Stage Considerations And Technical Approval Requirements
The planning stage is where many later adoption problems are either prevented or quietly planted.
At planning application stage, the emphasis is often on access strategy, swept paths, visibility, sustainable transport, and whether the overall layout is acceptable in principle. But for roads intended for adoption, we need to look beyond the red-line concept plan. Geometry, gradients, forward visibility, junction radii, parking relationships, refuse tracking, drainage falls, and service coordination all affect whether a layout is genuinely adoptable.
Once planning permission is granted, the technical approval stage becomes more detailed and less forgiving. Authorities usually require full engineering drawings, longitudinal sections, cross-sections, construction details, drainage calculations, lighting proposals, signing and lining layouts, and sometimes road safety or non-motorised user considerations depending on the scheme.
Local standards matter. One authority may accept a shared surface arrangement or a particular drainage detail: another may push back hard. That’s one reason we favour local-authority-led transport and highway input as early as possible, especially where planning thresholds, design guides, and adoption expectations differ across council areas.
The simplest way to avoid delay is to design for adoption from the beginning, not retrofit adoptable detail onto a planning layout that was never quite workable.
Construction, Inspection, And Certification Stages
Once the agreement is in place and pre-commencement requirements are satisfied, the focus shifts from drawings to delivery. This stage sounds straightforward, build what was approved, but site realities have a habit of intervening.
Levels may shift. Utility conflicts appear. Drainage runs may need adjustment. Kerb lines that looked clean on CAD can become awkward when tied into existing ground. The danger is that “small” site-led changes are made without authority approval, then discovered later during inspection.
Most highway authorities inspect works at defined stages, such as formation, drainage installation, kerbing, base course, binder course, and final surfacing. They may also witness testing or require formal submission of material test certificates, compaction records, CCTV drainage surveys, lighting certificates, and as-built drawings.
Certification is not just bureaucracy. It is the evidence trail showing that the road was built to the agreed standard. Missing records can hold up provisional certification just as much as defective construction.
By the time the road is nearing completion, a practical question tends to dominate: is it safe and complete enough to open to traffic? That answer can affect occupations, sales, and programme. Which is why inspection planning, not just construction planning, deserves proper management throughout.
Bonds, Fees, Commuted Sums, And Maintenance Periods
Financial obligations sit at the heart of Section 38, and they are often underestimated at appraisal stage.
The bond or performance guarantee protects the highway authority if the developer fails to complete the works or walks away. The amount is usually linked to the estimated cost of delivering the road and associated infrastructure, sometimes with allowances or percentages applied under local procedures. If the developer defaults, the authority can call on the bond and complete the works itself.
Then there are fees. Authorities typically charge for technical checking, legal drafting, inspections, and administration. These are not incidental. On larger or more complex schemes, they can become a meaningful line in the budget.
Commuted sums may also be required, particularly where the authority is being asked to adopt features that create above-normal future maintenance burdens. That might include non-standard paving, specialist lighting, structures, pumped drainage, landscaped elements within highway land, or bespoke materials. Some authorities are strict: others are more flexible, but none like inheriting expensive assets without funding.
The maintenance period usually starts after provisional completion. A 12-month period is common, though not universal. During that time, the developer remains responsible for defects, settlement, drainage issues, and any failures that emerge before final adoption.
This is where commercial teams sometimes get caught out. Final adoption is not triggered by surface appearance alone. It depends on defects being resolved, fees settled, certificates provided, and any commuted sums paid in full.
Common Reasons For Delay And How To Reduce Risk
Most Section 38 delays are not caused by one dramatic failure. They tend to arise from a stack of small unresolved issues that become critical together.
The most common causes include:
- incomplete or inconsistent engineering submissions
- layouts that secured planning permission but do not meet adoptable standards
- unresolved drainage strategy or ownership boundaries
- delays in securing the bond or signing the legal agreement
- unapproved changes during construction
- missing test certificates, as-built drawings, or inspection records
- outstanding defects at the end of the maintenance period
- unpaid fees or commuted sums
Some of these are technical. Some are administrative. A few are just project management problems wearing a highways hat.
Risk reduction starts early. We recommend engaging with the highway authority before technical positions harden, especially on geometry, drainage, lighting, and any non-standard materials. It also helps to define clearly which roads are intended for adoption and which are to remain private: blurred boundaries cause endless downstream confusion.
Programme realism matters too. If sales, occupations, or funding assumptions depend on rapid adoption, the project team needs to understand that final adoption often occurs well after first occupation. Provisional completion is not the same as final sign-off.
And one more thing: appoint the right technical team early. A concise, authority-aware transport and highway package can save months. That’s exactly why specialist support, such as the locally informed reporting and engineering input we provide at ML Traffic, often pays for itself long before the agreement reaches legal stage.
Design Standards, Drainage, And Road Safety Issues To Resolve Early
If we had to pick one theme that separates smooth adoptions from painful ones, it would be this: unresolved technical detail.
Highway authorities assess adoptable roads against a mix of local standards and national guidance. The exact suite varies, but the recurring issues are familiar, carriageway width, junction geometry, tracking, gradients, visibility splays, forward visibility, footway continuity, turning provision, and the relationship between parking and highway function.
Drainage is often the biggest pressure point. Authorities want confidence that highway water will be collected and disposed of properly, without future flooding, unclear maintenance responsibility, or over-reliance on systems they are unwilling to adopt. Interface points between highway drainage, private drainage, and wider SuDS features need to be mapped carefully. If they aren’t, adoption can stall even where the road construction itself is fine.
Road safety issues also need attention from the start, not after objections arise. That includes pedestrian crossing points, tactile paving, vehicle speeds, refuse and emergency access, street lighting coverage, visibility around bends and junctions, and how vulnerable users move through the site.
The awkward truth is that some planning layouts look attractive on paper but fight basic highway logic. Narrowed corners, parking overrun, weak visibility, and leftover drainage space can all undermine adoption. Early technical testing is the cure. Redesigning before consent is inconvenient. Rebuilding after construction is much worse.
What Adoption Means For Future Maintenance, Liability, And Residents
Once final adoption takes place, the road becomes part of the public highway network and is generally maintainable at public expense. That shift is the whole point of the process.
For the highway authority, it means taking on future maintenance responsibility for the adopted assets, subject to the scope of what was actually adopted. For the developer, it means the formal end of responsibility for those works, assuming defects have been resolved and the agreement fully discharged. For residents and occupiers, it usually means they are no longer dependent on a private estate arrangement to fund upkeep of the adopted road through direct service charges.
That said, adoption does not magically sweep away every future responsibility on a development. Private drives, shared courtyards, landscaping, parking courts, unadopted drainage assets, and management-company land may still sit outside the adopted highway. Residents often assume “the council owns it all” once they move in: that is frequently wrong.
Liability also becomes clearer after adoption. Highway maintenance obligations transfer to the authority for the adopted parts, rather than lingering in a grey area between developer, landowner, and residents.
From a placemaking and sales perspective, this clarity matters more than people sometimes admit. Mortgage lenders, purchasers, and solicitors tend to prefer certainty. An adopted estate road is not always essential, but where it is promised, everyone benefits from making sure the promise is actually deliverable.
Conclusion
Section 38 isn’t just a legal formality tagged onto the end of a planning permission. It is the route by which new roads move from development infrastructure into the public realm, with all the design, financial, inspection, and liability consequences that go with that change.
For developers, planners, architects, lawyers, and councils, the practical lesson is simple: treat adoption strategy early, not late. The schemes that progress best are usually the ones where adoptable intent is clear, technical standards are understood upfront, drainage and safety issues are resolved early, and the legal and bond requirements are not left to chase the programme.
In other words, successful section 38 highways adoption starts long before the final surfacing goes down.
If a project needs transport assessment, highway input, or authority-aware support to de-risk the planning and adoption path, getting experienced advice in at the right moment can make the difference between a clean handover and a long trail of post-completion problems.
Section 38 Highways Adoption – Frequently Asked Questions
What is Section 38 highways adoption and why is it important?
Section 38 highways adoption is a legal agreement under the Highways Act 1980 where a developer builds new roads to an adoptable standard, and the local highway authority adopts them as public highway maintainable at public expense. It shifts maintenance and liability from the developer to the authority.
When should a Section 38 agreement be established during development?
A Section 38 agreement is typically needed after planning permission is granted but before construction starts. Early engagement with the highway authority is crucial to ensure technical approval and avoid costly delays during road construction and adoption.
Which roads and features can be included for adoption under a Section 38 agreement?
Adoptable features commonly include estate roads, footways, verges, kerbs, street lighting, highway drainage systems, traffic calming measures, and supporting structures, provided they serve the public and meet authority standards.
How does Section 38 differ from Section 278 agreements and private street arrangements?
Section 38 governs adoption of new roads built by developers. Section 278 covers changes to existing public highways, such as junction improvements. Private streets remain privately maintained and do not pass into public maintenance through Section 38 adoption.
What are common causes of delays in the Section 38 adoption process?
Delays often result from incomplete or inconsistent engineering submissions, failure to meet adoptable standards, unresolved drainage issues, late bond or fee payments, unapproved construction changes, missing certificates, outstanding defects, and unpaid commuted sums.
What happens after final adoption of roads under Section 38?
Once roads are finally adopted, the local highway authority assumes future maintenance and liability as part of the public highway network, and residents typically no longer pay private service charges for upkeep, improving clarity on responsibility and funding.




































