Shared surface streets: what highway officers want to see

A shared surface only works where the traffic is light enough that drivers accept they are guests. Manual for Streets, published by the Department for Transport in 2007 and extended by Manual for Streets 2 in 2010, treats the shared surface as a place-led layout for low flow residential streets, and it indicates that such streets suit vehicle flows in the order of 100 vehicles per hour or fewer. Above that, the pedestrian priority the design depends on stops being credible.

Architects put shared surfaces on layouts because they look better than a standard estate road with footways both sides. Highway authorities resist them for reasons that have little to do with appearance. Understanding those reasons is how you get the layout through.

What the design is trying to achieve

The intent is a street where vehicle speeds fall to walking pace through the geometry itself: narrow effective widths, frequent changes in alignment, parking and planting that interrupt long sight lines, and surface materials that read as a courtyard rather than a carriageway.

Manual for Streets sets a design speed of 20mph or less for these streets and accepts shorter forward visibility than older highway standards allowed. That is the point of the document. It replaced the assumption that generous geometry is always safer with evidence that generous geometry invites speed.

So the test an officer applies is not whether your street is pretty. It is whether a driver entering it at 20mph would naturally slow without a sign telling them to.

Speed control through geometry

Things that work, in roughly descending order of effect:

• Keeping any straight run short, typically under about 60 metres, with a deflection at the end that is real rather than a gentle curve.
• Placing on-street parking bays alternately on each side so the through route weaves.
• Bringing building frontages close to the street edge so enclosure is felt.
• Using a change of surface material and colour at the entry threshold, with a raised table so vehicles physically cross into a different environment.
• Planting trees in the carriageway envelope rather than only behind the building line.

Things that do not work: 20mph signs on a straight 90 metre run, a single speed table halfway along, and painted markings on block paving that disappear within two winters.

Accessibility is the objection you have to answer

This is the ground on which shared surface proposals fail. Blind and partially sighted people use a kerb as a detectable edge, and a fully level surface removes it. The Department for Transport's Inclusive Transport Strategy in 2018 asked authorities to pause new shared space schemes with level surfaces in busy commercial settings pending further work, and that caution now colours how highway officers read residential layouts too.

The answer is a delineated safe route rather than an undifferentiated sheet of paving. Provide a continuous strip along at least one side, set out with a material change that is detectable underfoot and by long cane, a corduroy or blister surface at crossing points, and enough tonal contrast to be visible to someone with low vision. Inclusive Mobility treats an upstand of around 60mm as reliably detectable, so a flush junction across the whole width will be questioned.

Write this into the Design and Access Statement explicitly, with a plan showing the safe route. If the access section says nothing about how a cane user finds the edge, an objection from an access group is likely and the highway authority will have nothing to lean on when it defends the layout.

Adoption, and what happens if the authority says no

Most highway authorities have a design guide that either prohibits shared surfaces or permits them only on short cul-de-sacs serving a limited number of dwellings. Some will adopt them with a commuted sum for the higher maintenance cost of block paving. Others will not adopt them at all.

An unadopted shared surface has consequences the design team should price in early:

1. A management company and a service charge running for the life of the development, disclosed to purchasers.
2. No traffic regulation order, so parking obstruction cannot be enforced by the council and must be handled through the estate management deed.
3. Maintenance liability for the surface, the drainage and any street lighting sitting with the residents.
4. Adoption of drainage by the sewerage undertaker becoming harder where the road itself stays private.

Where adoption is the plan, the mechanics and the bond are set out in the note on section 38 agreements and the road adoption bond. Settle the adoption question before the layout is fixed, because retrofitting footways into a shared surface destroys the design.

Parking, refuse and emergency access

Shared surfaces fail in occupation when parking spills onto them. Allocate more parking than the minimum you think you can argue for, keep bays within the visual envelope of the street, and use bollards, trees or level changes at the points where drivers will otherwise mount the paving.

The fire appliance requirement does not relax because the street is shared. Approved Document B expects a route capable of taking a pump appliance with a minimum width of 3.7m and a maximum of 45m from the appliance to the dwelling entrance, and that route has to be kept clear in practice. Emergency access on small estate roads is covered in more detail in emergency vehicle access to a new dwelling or estate road.

Refuse vehicles are the other constraint, and the collection authority will apply its own carry distance and reversing rules, discussed in bin storage and carry distances. A shared surface that cannot be serviced without a reversing manoeuvre past a blind corner will be refused on highway safety grounds whatever its merits as a place.

An illustrative example

Illustrative only: a scheme of 14 houses off an existing estate road, arranged around a 55 metre shared surface with a 180 degree turning head. Entry is over a raised table with a material change. Parking sits in alternating bays with trees between them, and a 1.8 metre delineated strip with contrasting paving runs along the northern side to the turning head, where a blister surface marks the crossing to the footway on the existing road. Refuse is collected from a bin presentation point at the entry, keeping the collection vehicle on the adopted road.

That layout gets a conversation rather than a refusal, because every standard objection has a drawn answer.

Drainage and level detailing

Without kerbs you have no obvious channel, so the falls have to be designed rather than assumed. Options are a central channel with crossfalls from both sides, an offset channel on one side, or linear drainage across the width at intervals. Whichever you pick, keep a minimum crossfall that actually moves water on block paving, detail thresholds so surface water cannot enter dwellings, and show the exceedance route for rainfall that exceeds the design event.

Level thresholds under Part M and flood resilience pull in opposite directions here. Resolve it on a section drawing, not in the covering letter.

Set the shared surface out at 1:200 with parking, trees, delineation, refuse and fire access on the same sheet, and submit it with a Transport Statement that explains the design speed logic. To see which supporting documents a residential layout of your size usually needs, enter the postcode on PlanScope.

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.