Transport Statement or Transport Assessment: the section test

The difference between a Transport Statement and a Transport Assessment is scope, not quality. A Transport Statement describes the site, the access and the likely trips. A Transport Assessment models them. If you are asking transport statement vs transport assessment because a validation officer has queried your submission, the answer is almost always decided before you write a word, by the number of homes or the floorspace you are proposing.

Get it wrong in the light direction and the application sits invalid. Get it wrong in the heavy direction and you have paid a transport planner for junction modelling nobody asked for.

The threshold that usually decides it

There is no national statutory threshold. National guidance leaves the trigger to local judgement, and each local planning authority publishes its own in a validation checklist or local plan policy. What exists in practice is a widely used pair of numbers that most authorities land near.

Those are the thresholds PlanScope uses to flag reports when it looks at a site, and they sit close to what most English councils apply. Your council's own validation list and the highway authority's requirements take precedence over both. Sensitive locations move the line: a site inside an Air Quality Management Area, on a trunk road, or served by a single-track lane may attract a full assessment at a fraction of those figures.

What a Transport Statement contains

A Transport Statement is a description with numbers attached. Expect six to fifteen pages covering the site and its existing use, the proposed access geometry, walking and cycling routes with distances to shops, schools and a bus stop, public transport services, an estimate of vehicle trips in the morning and evening peaks, parking provision against the adopted standard, and servicing and refuse collection.

What it stops short of is modelling. No junction capacity runs, no assignment of trips onto a network, no accident cluster analysis beyond a short check. It asserts that the traffic effect is not material and shows enough working for a highways officer to agree.

That assertion is the whole document. If a reader can dispute the trip estimate and the statement offers nothing to fall back on, the officer will ask for an assessment. Sourcing the trip rates properly, usually from the TRICS database with the site selection criteria stated, is what keeps a statement standing up. Our note on evidencing mode share targets in a Travel Plan covers the same discipline applied to the follow-on document.

The sections a Transport Assessment adds

A Transport Assessment keeps everything above and adds the analytical layers:

1. A baseline built from surveyed traffic counts in a neutral month, not from assumption.
2. Personal injury collision data, normally over five years, checked against the proposed access.
3. Trip generation with a stated TRICS site selection, plus distribution and assignment across the network.
4. Junction capacity modelling for the affected junctions, in the peak hours, for a future assessment year.
5. Committed development added to the future baseline, taken from the council's own list.
6. Parking accumulation and, where relevant, a survey of on-street stress.
7. Mitigation, including any highway works to be secured under section 278 of the Highways Act 1980.
8. Residual effects, tested against the national policy test of a severe residual cumulative impact on the road network.

That last line is where the argument is actually won. National policy sets a high bar for refusal on highway grounds, and an assessment that reaches the severe test squarely, with the modelling behind it, is doing something a statement structurally cannot.

Councils expect a suitably qualified author for a Transport Assessment, and professional review is strongly advised before submission.

Scoping the scope with the highway authority

Ask the local highway authority to agree the scope in writing before any survey work. The four things worth pinning down are the assessment years, the junctions to be modelled, the survey dates and the trip rate approach.

Junction selection is where budgets are lost. An officer who wants five junctions modelled when the scheme adds forty trips in the peak is asking for money that adds nothing, and the time to say so is at scoping rather than after the model is built. Equally, an authority that agrees two junctions in writing is unlikely to ask for a third at week ten.

Survey timing matters as much. Traffic counts taken in August or the fortnight before Christmas will be challenged, and school holidays distort peak flows on any road with a school on it. Neutral months, broadly March to June and September to November outside half terms, are the convention.

Where a statement gets upgraded mid-application

It happens, and it is usually one of four causes. The description of development changes and the unit count crosses the threshold. A highways officer disputes the trip rates and asks for surveyed evidence. A neighbouring application is consulted on and the cumulative effect becomes an issue. Or the access geometry turns out to fail visibility requirements, which pulls collision data and speed surveys into the frame.

The programme cost of an upgrade is worse than the fee. Surveys need a neutral month, modelling needs the survey data, and an eight-week determination period does not pause while you wait for September. If there is any prospect of the threshold being crossed, commission the surveys early and hold the modelling.

An illustrative comparison for a nine-dwelling scheme

Take a scheme of nine houses on a former paddock served off an unclassified village road, roughly 1.2 km from a primary school and 400 m from an hourly bus service. This example is illustrative.

A Transport Statement here would set out the access design with visibility splays measured on site, walking routes and distances, the bus timetable, a TRICS-derived estimate of around five to six two-way vehicle trips in each peak hour, parking at the adopted standard with dimensions, and refuse vehicle tracking to show a bin lorry can turn.

A Transport Assessment on the same site would add nothing a decision maker needs. Nine houses do not move a junction's capacity, and modelling one would produce a page confirming it. The exception is the access itself. If visibility falls short of the geometry set out in Manual for Streets for the measured speed of traffic, the highway authority will want speed surveys and collision data whatever the scheme size, and that work sits inside a statement perfectly well.

What to submit when you fall between the two

Write the Transport Statement and add the one analytical section the site actually needs. A statement with a properly evidenced access and visibility chapter is a stronger document than a thin assessment, and highways officers read the section that answers their question rather than counting the pages.

Say what you have done and why. A short scoping note at the front, recording the threshold applied, the authority's confirmation and the reason a fuller assessment is not proportionate, gives the validation officer a reason to accept the submission rather than a gap to query. Where a Travel Plan is also being conditioned, cross-reference it rather than repeating it, and check the full list of planning report types so the transport documents match the rest of the pack.

Enter your postcode on PlanScope to see which transport documents your site is likely to need, then have the draft reviewed by a transport planner before submission.

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.