Scoping a Transport Assessment with the highway authority

Transport assessment scoping is a written agreement with the highway authority about what your assessment will cover before you spend money modelling anything. Send a scoping note, get a response in writing, and the assessment that follows is far harder to reject. Skip it and you are guessing at the study area, the assessment year, the trip rate database filters and the junction list, then arguing about all four after submission.

National guidance expects the scale of a transport assessment to be proportionate and agreed with the authority. That single sentence is worth more to a consultant than any modelling manual, because it makes scoping the moment where the cost of the whole transport evidence base is set.

What a scoping request has to contain

A scoping note that gets a useful reply is usually four to eight pages plus drawings. It sets out the proposal in enough detail for the authority to judge the transport implications, and it proposes answers rather than asking open questions.

Include the site address and red line plan, the quantum of development by use class and unit or floor area, the access arrangement with a preliminary sketch, and the phasing if any. Then propose:

1. The study area and the specific junctions to be assessed.
2. The survey programme, including dates, and whether existing counts can be reused.
3. The trip generation method, with the database filters you intend to apply.
4. The distribution and assignment method.
5. The assessment years and the growth factors.
6. Committed developments to be included.
7. The modelling packages proposed for each junction.
8. Whether a travel plan and parking accessibility work are required.

Ask the authority to confirm or amend each numbered item. A note structured that way tends to come back annotated, which is exactly what you want on file. Whether the scheme needs a full assessment at all or only the lighter document is the first thing to settle, and the difference between a Transport Assessment and a Transport Statement is a threshold question that varies by authority.

Agreeing the study area, junctions and assessment years

Study areas are argued about because they drive cost. The defensible position is to include every junction where the development traffic exceeds a stated percentage of existing flows or of link capacity, and to say what that threshold is. Many authorities work to a percentage impact figure in their own published guidance. Where none is published, propose one and justify it.

Assessment years need three points fixed: the base year of the surveys, the opening year, and a future year normally taken as opening plus a design period. Growth between the base and future years is derived from national traffic forecasting factors, adjusted where a local model exists.

For junction modelling, the usual pairing is a deterministic package for priority and signalised junctions and a microsimulation model only where queues interact between junctions. Microsimulation is expensive and slow to calibrate. Propose it only where the network really requires it, and say why.

Do not let the survey programme drift into an unrepresentative period. Neutral months matter, school holidays distort peaks, and a count taken in the week before Christmas will be challenged. Where an accessibility or parking element is needed, the survey specification for a Parking Survey should be agreed at the same time so the fieldwork happens in one visit.

Building the committed development list

Committed development is the category where scoping most often unravels months later. The list should be drawn from the authority's own records: extant permissions not yet built out, allocations with resolution to grant, and any scheme with a signed section 106 that will generate traffic in the assessment years.

Ask the highway authority to supply or confirm the list rather than compiling it yourself from a search of the planning register. If the authority supplies it, a late addition becomes their problem to justify rather than a gap in your evidence.

Be explicit about how committed trips are treated. Double counting is common where a committed scheme's traffic is both in the growth factor and added separately. State the approach in the scoping note and repeat it in the assessment.

Choosing methods, and stating their limits

Trip rates from a national database are the standard starting point. What matters is the filter set: land use category, region, location type, survey date range, site size range and days of the week. Record every filter and the number of surveys the filtered set contains. Where the filtered sample is small, say so and consider a sensitivity test rather than presenting a single rate as certainty.

Mode share needs a source. Census travel-to-work data, the authority's own strategy or an accessibility assessment can each support it, and each needs naming in the text.

Where a scheme is likely to need a monitored travel plan, agree the target measures and the monitoring period during scoping. Retro-fitting targets after refusal is much harder, and a Travel Plan that arrives with agreed targets already reflected in the section 106 heads of terms rarely delays a committee report.

Every method carries limits. Say what they are in a short paragraph rather than burying them. An assessment that acknowledges a small trip rate sample and runs a sensitivity test reads as competent. One that hides the sample size reads as advocacy.

Recording the agreement so it binds later

Get the response in writing, from a named officer, with a date. An email confirming the numbered items of your scoping note is enough. Put it in an appendix to the transport assessment and reference it in the methodology chapter.

Where the authority agrees some items and reserves others, record the reservation rather than smoothing it over. A table in the assessment listing each scoped item, the agreed position and the date of agreement lets a case officer verify the scope in two minutes.

Officers change. A scoping agreement made with one engineer and inherited by another survives far better as a signed table than as a recollection of a phone call. And where the scheme changes materially after scoping, go back and re-scope the affected items rather than hoping the original letter still covers it.

When the authority will not engage

Some authorities charge for pre-application highways advice and some have no capacity to respond within any useful period. Neither removes the obligation to submit a proportionate assessment.

Where no response arrives, proceed on your stated assumptions and say so in the assessment. Set out the scoping note in an appendix, note the date it was sent, list the assumptions adopted in the absence of a reply, and be conservative with those assumptions. A slightly cautious study area costs less than a re-run.

Consider a planning performance agreement on larger schemes, which can buy named officer time and a written programme. On smaller schemes, a paid pre-application response that answers three specific questions is usually better value than a general meeting.

If the assessment is later challenged, the file that wins the argument contains the scoping note, the sent date, any reply, the survey certificates and the model audit trail. Start assembling it on day one.

To see which transport documents your scheme is likely to need, enter your postcode on PlanScope and answer the guided questions.

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.