Two identical schemes, a mile apart, can face completely different parking requirements, density expectations and levels of scrutiny.

The reason is usually accessibility scoring. How well connected a site is to public transport gets expressed as a number, and that number drives a series of policy consequences that have nothing to do with the design of the scheme itself.

What PTAL actually measures

Public Transport Accessibility Level is the London measure, and it is the best known.

It works by measuring walking time from the site to nearby public transport access points, then combining that with the frequency of services at each one. The output is a PTAL score, banded from 0 for the least accessible to 6b for the most.

The important thing to grasp is what it does not measure. It takes no account of where the services actually go or whether they are useful for the trips people from that site would make. A site with frequent buses running in one direction can score well and still be poorly connected to anywhere its residents need to reach.

It also takes no account of crowding, cost, or how pleasant the walk to the stop is.

Outside London

Authorities elsewhere use their own approaches, and no single method applies everywhere.

Some apply distance thresholds to bus stops, rail stations and services. Some use accessibility zones defined in the local plan. Some assess it qualitatively, describing connections rather than scoring them. Several have adapted the PTAL method locally.

The consequence is that the same site would be described differently depending on which authority it sat in, so the first job on any scheme is establishing which method applies.

What the score is used for

This is where it stops being an academic exercise.

Parking standards frequently key off accessibility. A well connected site may face a low maximum, and a poorly connected site may face a minimum. The difference between bands can change the number of spaces by a substantial margin.

Density expectations tend to follow the same logic, with policy favouring higher density where accessibility is good.

The level of transport evidence expected with an application can vary too, and so can the weight given to sustainable transport arguments. A scheme in a low accessibility location arguing that residents will use public transport has a harder case to make.

Car-free and car-capped development is usually only acceptable where accessibility supports it.

Where the score is wrong

Scores are calculated mechanically, and mechanical calculations miss things.

A site may sit just outside a walking threshold to a station, scoring poorly, when the actual walk is straightforward and people plainly make it.

A new bus service, a changed frequency or a new station may not be reflected in a published score that was calculated some time ago.

A physical barrier, such as a railway line, a river or a dual carriageway, may mean the walking route is far longer than a simple distance suggests.

And the reverse happens. A site may score well on frequency when the services go nowhere useful.

Where the score does not reflect reality, the answer is evidence rather than argument. That means walking route analysis showing actual distances and times, service data showing where routes go and how often, and where necessary a site-specific accessibility assessment.

Improving the position

Some accessibility constraints can be addressed rather than accepted.

A new pedestrian link, a crossing, an improved footway or a route through a site can shorten walking distances to a stop. Those interventions are often modest in cost relative to what they unlock.

Contributions towards service improvements are another route, though these sit within Section 106 and have to meet the tests that apply to planning obligations.

Cycle provision changes the picture too, since accessibility by bike extends the catchment beyond walking distance. That makes cycle parking part of the accessibility argument rather than a separate requirement.

Presenting it properly

The common mistake is to state a score and move on.

A stronger approach sets out the score, then describes what the site is actually connected to: which services, running where, at what frequency, and how long the walk genuinely takes. Where the score understates the position, that description does the work the number cannot.

Where the score is accurate and low, acknowledging it and building the case around what the scheme provides is better than arguing with the calculation. Officers know the method and won’t be persuaded it produced the wrong answer without evidence.

If the point ends up being tested at appeal, that evidence is what carries it.

Getting it settled early

Accessibility drives parking, density and the shape of the transport case, so it belongs at the start rather than being described once the scheme is designed.

On a site where the position is marginal, establishing it before design starts can change what is worth pursuing. That is part of what pre-application work and early engagement are for.

If you have a site where accessibility is likely to be contested, you can reach the team through the London office, the Bristol office, the Cambridge office, the Norwich office or the Welwyn Garden City office.