Highway trees, sightlines and street lighting conflicts

A highway tree sightline conflict is usually discovered after the landscape drawing has been approved, when the highway authority reviews the section 38 submission and asks for three trees to be deleted. By then the planting scheme has been conditioned, the biodiversity figures assume the canopy, and the developer is choosing between a section 96A amendment and an argument.

The order of precedence is worth stating plainly. Highway safety requirements come first, adoption standards come second, and the landscape intention has to work within both. That is not a reason to design a bare street. It is a reason to involve the highway engineer while the layout is still a sketch.

Why highway requirements take priority

The highway authority is not approving a planting scheme, it is deciding whether it will take responsibility for a street in perpetuity. Its tests are about visibility, maintenance, liability and whether its own apparatus can be reached. A tree that obstructs a visibility splay, shades a lighting column or sits over a water main fails on grounds the authority cannot waive.

Where the street is to be adopted under a section 38 agreement, or altered under a section 278 agreement, the authority's standards apply as a condition of the agreement rather than as planning policy. A planning permission does not override that. So a landscape strategy which places street trees without checking the local adoption standard is proposing something the authority may simply decline to adopt, leaving the developer with a private street and a management company.

There is a route that avoids the whole argument, and it is underused: keep the trees out of the highway and put them in adjoining land within the development, with the planting secured by planning condition instead.

Visibility splays and what must stay clear

Manual for Streets sets the approach for residential streets, with stopping sight distance derived from design speed and visibility splays measured from a setback at the junction. At low design speeds the distances are short, which is why a 20mph street has far more planting freedom than a 30mph one.

Within the splay, the envelope that has to stay clear runs between driver eye height and object height, so low planting and high canopies are both acceptable and the middle band is not. That gives two workable approaches: keep planting below about 600mm, or use standard trees with the crown lifted clear and maintained clear.

Manual for Streets also accepts that some obstruction within a splay can be tolerated where it is narrow and the risk is low, which is the basis on which a single slender stem in a verge is sometimes agreed. Do not rely on it without asking, and do not rely on it for a species that will reach 600mm stem diameter.

1. Establish the design speed before fixing the geometry, because everything follows from it.
2. Draw the splays on the landscape plan as well as the highway drawing.
3. Fix the clear envelope heights with the authority and annotate them.
4. Choose species whose mature stem diameter still works within the splay.
5. Record who maintains crown lift and at what frequency.

Lighting columns and canopy clearance

Street lighting is designed to a uniformity as well as an average illuminance, following BS 5489-1, and a canopy over a column destroys uniformity locally. The dark patch beneath a mature canopy is a genuine safety and perception issue on a footway.

The conflict is geometric and predictable. Columns on a residential street sit at regular spacing, and a street tree planted at similar spacing will eventually intersect. Three resolutions exist. Two of them work.

Offset the trees from the columns so that canopies fall between them, which requires the lighting layout before the planting layout. Reduce column spacing and lower the mounting height so the light sits under the canopy, which costs more columns. Or plant species with a high, narrow crown and accept a permanent crown-lift obligation, which depends on someone doing the work in twenty years.

The third is the one most often chosen and least often honoured. If it is the answer, put the obligation somewhere it will be found: the management company's schedule, not a paragraph in an arboricultural report.

A Lighting Assessment is the place to show the interaction where a scheme is large enough to need one, and councils expect a suitably qualified author for that report type with professional review advised.

Services beneath the verge

Statutory undertakers have rights to place and maintain apparatus in the highway under the New Roads and Street Works Act 1991, and those rights do not bend for a tree. Water, gas, electricity and telecoms all tend to run in the verge, which is also the only place a street tree can go.

Industry guidance on utility apparatus near trees sets minimum separations and restricts excavation close to stems. In practice the authority will want either a clear separation between the tree pit and the apparatus, or a root barrier and a tree pit designed so that future excavation does not sever roots or destabilise the tree.

Two consequences follow. Tree pits become engineered elements with a cost, using structural soil or a cellular system rather than a hole in the verge. And the planting positions have to be coordinated with the service drawing, which means the utilities layout has to exist before the landscape drawing is finalised. On most schemes it does not, which is why this conflict recurs.

Adoption standards and species restrictions

Highway authorities publish their own design guides, and many restrict species, stock size, pit construction and the extent of verge planting. Some decline verge trees altogether and require a commuted sum for maintenance where they accept them.

Because those requirements are local, the only reliable step is to obtain the authority's current guide and read it before the layout is fixed. Do not infer what an authority will accept from what happened on another scheme in another district.

Where planting in the highway is the right answer and the authority is open to it, section 142 of the Highways Act 1980 provides a licence mechanism for an adjoining owner to plant in the highway, with the licence carrying maintenance obligations. Section 96 gives the authority its own planting powers. Both are worth knowing about because they change who holds the long-term duty.

Negotiating a scheme the authority will adopt

The negotiation goes better when the landscape case is quantified rather than asserted. Canopy cover targets, shading of the carriageway, surface water interception and air quality benefit can all be described in terms the highway engineer recognises as costs avoided elsewhere.

Illustrative example: a 96 dwelling scheme where the highway authority initially refused all verge planting. The revised layout moved 14 trees into private front garden areas and shared amenity space, kept 9 in the verge at positions offset from lighting columns with cellular tree pits and root barriers, and offered a commuted sum for the adopted trees. Canopy cover across the site was maintained. Figures here are illustrative.

Bring the arboriculturist to the highway meeting. A tree survey and the retention constraints it records carry more weight with an engineer when explained by the person who wrote them, and the same is true of the planting proposals in a Landscape Strategy.

Alternatives outside the highway boundary

The most reliable way to get trees onto a street is to plant them beside it rather than in it. Front garden trees, trees in landscape strips behind the back of footway, trees in parking courts and trees in shared amenity areas all read as street trees from the carriageway and none of them is the highway authority's problem.

That approach needs the layout to reserve the space, which means a decision at concept stage about plot depth and frontage treatment. Retrofitting it later costs a plot. Establishment and aftercare obligations still need pinning down properly, and our note on tree planting conditions sets out what the wording should cover.

Enter your postcode on PlanScope to see which reports a residential development at your site is likely to need. 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.