What is a designated pedestrian route on a construction site?

A designated pedestrian route is the strip of your site where people can walk without a banksman watching their back, a demarcated path kept apart from plant movement, deliveries and reversing vehicles by a physical barrier rather than a painted line on compacted hardcore. On a live site, "designated" has to mean enforced: hard barriers, pedestrian gates, crossing points with their own controls. Not a route that exists on the site logistics plan but gets blocked the first week groundworks start.

The CDM 2015 duty sits with the principal contractor to keep vehicles and pedestrians apart wherever reasonably practicable. In practice that falls to the traffic management plan, and to whoever is walking the site checking it's still being followed once the plan meets actual trades, actual deliveries and actual mud.

What counts as segregation, and what doesn't

A yellow line is not segregation. A line of cones knocked flat by a telehandler by Tuesday lunchtime is not segregation either. Proper pedestrian segregation on a construction site means a physical barrier that a vehicle can't drive through by accident and a pedestrian can't casually step round: Heras fencing, pedestrian guard rail, kerb and footway, a hoarded walkway.

The vehicle-pedestrian interface is every point where that barrier has a gap. A site gate. A loading bay. A crossing point near the welfare cabins. The spot where the route narrows next to a laydown area that's crept two metres over its marked boundary. These interfaces are where most near misses happen, and they're also the points most likely to drift out of spec without anyone updating the drawing to match.

Why the route on paper stops matching the route on the ground

A site logistics plan gets drawn once, maybe revised at a few key gateways. The site underneath it changes daily. A delivery gets dropped where it's convenient rather than where it's marked. A subcontractor's plant parks across the walkway for an hour. A stack of formwork grows until it's narrowed the route to single file next to moving traffic. None of that shows up on the drawing unless someone's physically walking the route, and on a site of any size, walking the whole logistics plan every week to check laydown areas, access routes and edge protection against what's marked is a half-day job nobody has spare time for.

That gap between what the plan says and what's actually on the ground this week is where site access route compliance fails. Usually because nobody's walked that stretch of route since the barrier got bridged by a dropped delivery, not because anyone decided to ignore the plan in the first place. It's also the gap Site Logistics Audit is built to close: a weekly overhead read of the site that flags laydown-area encroachment, blocked access routes and missing edge protection as a straight list, so the walk you'd otherwise do on foot gets done from above instead.

Checking a route is still compliant

A few things worth confirming on every walk, or every audit, rather than assuming from the induction pack:

• Is the physical barrier still continuous, or has it been bridged by stored material, a parked plant item or a dropped delivery?
• Are crossing points still marked and controlled, or has a shortcut worn in next to one?
• Has a laydown area spread past its marked boundary and into the route or the vehicle swept path?
• Is edge protection still in place anywhere the pedestrian route runs near an excavation, a slab edge or a level change?

None of these take long to check individually. Confirming all of them across a full site, every week, is the part that gets skipped when the programme gets busy, which is exactly when it matters most.

If your logistics plan looks better on paper than it does on the ground this week, that weekly audit list is worth a look.