Betterment in highway terms: what a section 278 delivers

A section 278 agreement is the legal instrument under which a developer pays a highway authority to carry out works to the existing public highway, and under which the authority satisfies itself that those works benefit the public rather than only the applicant. The power sits in section 278 of the Highways Act 1980. The statutory test is short: the authority may enter the agreement if it is satisfied the works will be of benefit to the public, on terms that the other party pays the whole or part of the cost.

That public benefit test is what practitioners mean by betterment in highway terms. It is also the reason a section 278 cannot be treated as a simple purchase order for a new access.

What the section actually permits

The works have to be ones the authority is itself authorised to execute. A new bellmouth, a signalised junction, a pedestrian refuge, a bus stop relocation, a widened footway, a new crossing, traffic calming on an adjoining street: all of these sit comfortably inside the power because they are works to highway the authority already maintains.

The agreement typically covers more than construction. A standard set of terms will deal with design submission and technical approval, a design check and supervision fee calculated on the works value, a bond or other surety, insurance, a programme, a defects period after completion, and the point at which the works become highway maintainable at public expense.

Who physically builds the works varies. Some authorities insist on using their own term contractor. Most will allow the developer's contractor to build under supervision, which is usually faster and lower in cost, and which shifts the construction risk onto the developer where it belongs.

Where it differs from a section 38 agreement

The two are routinely confused, and the consequences of confusing them show up late, when a management company inherits a road nobody agreed to adopt.

A scheme of any size usually needs both. The estate road goes through section 38, the junction where it meets the public road goes through section 278, and the two have to be programmed so the junction is complete before occupation. On the strategic road network the counterparty is National Highways rather than the local highway authority, and the technical approval regime is heavier.

A dropped kerb for a single house is a different animal again. That is a vehicle crossing under section 184 of the same Act, handled as an application to the highway authority rather than as a negotiated agreement.

How it reaches a planning decision

Section 278 works are secured through the planning permission, not by the permission. A planning authority cannot grant a permission that itself authorises works in the highway, so it uses conditions and obligations to make the development dependent on the agreement being completed.

The usual mechanism is a Grampian condition: no occupation, or no start on site, until the highway works shown on an approved drawing have been constructed, or until an agreement under section 278 has been entered into. The Planning Practice Guidance on conditions is firm that a condition requiring the applicant to enter an agreement with a third party is not enforceable in itself, so the better drafting ties occupation to the physical completion of the works.

Commuted sums appear where the works leave the authority with a maintenance burden it would not otherwise carry. A new structure, a non standard surfacing material, an extra set of signals or new street lighting columns all generate future cost. Authorities calculate these from their own published maintenance rates, and the figure should be interrogated rather than accepted, because the calculation period and the discount basis vary widely between authorities.

The other cost that surprises people is the bond. A surety sized to the full works value sits on the balance sheet until the defects period ends, and for a small developer that can be the difference between one site and two. Some authorities accept a parent company guarantee or a cash deposit instead. Ask which forms of surety are acceptable before the agreement is drafted.

An illustrative example

This example is illustrative. A developer promotes 40 homes on the edge of a village. The access needs a priority junction with visibility splays onto a 40mph road, a 40 metre length of new footway to reach the nearest bus stop, and a pedestrian refuge island.

The junction and footway are classic betterment: they serve the development, and they also improve pedestrian connectivity for existing residents, so the authority is satisfied the public benefit test is met. The refuge island is more marginal. The authority wants it, the Transport Statement supports it on road safety grounds, and it is included.

The lighting columns on the new footway attract a commuted sum because the authority will energise and maintain them for decades. The developer's engineer asks for the calculation and finds it assumes a 60 year column life against the authority's own replacement programme. That conversation is worth having before the agreement is signed, not after.

Programming it properly

The agreement runs on its own clock, and it is almost always the item that delays a start on site.

1. Agree the layout in principle with the highway authority during pre-application, before the planning drawings are fixed.
2. Submit detailed design for technical approval once permission is granted, allowing for at least one round of comments.
3. Obtain any traffic regulation order needed for parking restrictions, waiting restrictions or a speed limit change, which carries its own statutory consultation.
4. Complete the legal agreement, lodge the bond and pay the fees.
5. Build the works, then survive the defects period before the maintenance liability transfers.

Traffic regulation orders are the step most often missed. If the junction needs double yellow lines to keep the visibility splay clear, that order is a separate statutory process with its own objection period, and it cannot be compressed to suit a build programme. Objections go to the traffic authority, which may hold them over to a committee cycle.

And the technical approval stage rewards early engagement. Submitting a design that already matches the authority's standard details, drainage requirements and construction specification removes most of the comments that would otherwise come back.

What to put in the application

An authority assessing highway works wants the design intent, the land interests and the deliverability in one place. The Transport Assessment or statement should cross refer to a general arrangement drawing showing the works within the adopted highway boundary, the visibility splays with the standard they are drawn to, swept path analysis where servicing is tight, and confirmation of who owns any verge or footway being altered.

Where third party land is needed to deliver a splay, say so plainly and explain the route to securing it. An application that shows a splay across land the applicant does not control, without explanation, invites a refusal on access grounds that is hard to recover at appeal.

Construction phase effects belong in a separate document. A Construction Traffic Management Plan dealing with wheel washing, routeing and the temporary closure of the footway will often be conditioned, and drafting it early avoids a condition that has to be discharged before works start sitting unresolved while the contractor waits.

Enter your postcode on PlanScope to see which transport and highway documents your site is likely to need, and which of the 66 report types the constraints on it trigger.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional 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.