Responding to a highway authority objection

A highway authority objection is not a refusal, and it is answered more often than it is fought. National policy sets a high bar: development should only be prevented or refused on highways grounds where there would be an unacceptable impact on highway safety, or where the residual cumulative impacts on the road network would be severe. Most objections, read carefully, do not assert either of those things.

So the first job is to work out what the objection actually says, and the second is to test whether what it says meets the policy test at all. Check the current wording and policy reference in the published Framework before you quote it in a submission, because the numbering has changed more than once.

Reading the objection for what it actually says

Consultee responses fall into recognisable types. A holding objection says the authority cannot advise because information is missing. A conditional objection says the scheme is acceptable subject to works or contributions not yet secured. A safety objection says a specific manoeuvre or geometry creates risk. A capacity objection says a junction will operate beyond capacity with the development in place.

Only the last two go to the policy test, and they go to different limbs of it. Treat them separately in your response, because a reply that blends them lets the officer conclude that both remain unanswered.

Read for what is asserted and what is merely implied. An objection that says a junction "will experience increased delay" has not said the residual cumulative impact is severe, and pointing that out politely, with the policy wording quoted, is often the whole of the answer.

The policy test the objection has to meet

Increased delay is not severe impact. Traffic growth is not an unacceptable safety impact. The test is deliberately demanding, and the case officer has to apply it rather than simply adopting the consultee's conclusion.

Two supporting points strengthen that argument. The residual impact is what remains after mitigation, so an objection that ignores your offered mitigation is testing the wrong thing. And cumulative means the effect with committed development included, which cuts both ways: it can be used against you, and it also means the authority has to show the increment your scheme adds rather than the total position it inherits.

Where the objection relates to the strategic road network rather than local roads, a different consultee and a different national policy position applies, and the threshold for intervention there is set out in the relevant government circular.

Evidence that answers a capacity objection

Capacity objections are answered with modelling and assumptions, not with assertion. Ask for the authority's own basis: which junction, which peak hour, which growth factor, which committed development list, and whether they have run their own model or relied on yours with different inputs.

Then respond in this order:

1. Confirm or correct the trip generation, with the survey basis stated
2. Confirm or correct the distribution and assignment, and offer a sensitivity test at the assumptions the authority prefers
3. Show the junction results under both sets of assumptions, so the officer can see whether the conclusion changes
4. Quantify the residual impact in queue length and delay terms, then set that against the policy word severe
5. Offer mitigation only where it is proportionate and deliverable

The strongest responses concede something. Agreeing that the authority's growth factor is the right one, and showing the scheme still works with it, is far more persuasive than defending every input. The underlying Transport Assessment usually contains everything needed, and the response is a matter of presentation rather than new work.

Answering a safety objection with collision data

Safety objections need personal injury collision records for the study area, normally for the most recent five-year period available, analysed for pattern rather than counted. The question is whether there is a collision type that the proposal would make more frequent or more severe.

Three findings commonly defeat a safety objection. That the recorded collisions have no causation link to the manoeuvre being objected to. That the site access has operated at a similar intensity historically without incident. That the geometry meets the visibility standard for the observed speeds, evidenced by a speed survey rather than by the posted limit.

Observed speeds are the one worth spending money on. Visibility splays are set from actual vehicle speeds, and a speed survey frequently shows lower 85th percentile speeds than the limit implies, which reduces the required splay. Our note on using personal injury collision data properly sets out the analysis traps.

Be careful with the absence of collisions. It is evidence, but an officer can fairly say that an absence of recorded injury collisions does not prove a junction is safe. Pair it with a geometric analysis rather than relying on it alone.

Mitigation offers and how to frame them

Frame mitigation as proportionate to the impact, tied to the specific problem, and deliverable within your control. A junction improvement that requires third-party land you do not own is not mitigation, it is a hope.

Common proportionate offers include a visibility improvement within the site frontage, a contribution to an existing programmed scheme, a Travel Plan with monitoring and a review mechanism, footway widening along the frontage, and a construction traffic routeing agreement.

Say what secures each one. Section 278 for works in the highway, section 106 for contributions and travel plans, conditions for anything within the site. An offer without a securing mechanism reads as a negotiating position rather than a commitment.

Escalating within the authority

If the objection is not moving, escalate in writing and politely. Ask the case officer to arrange a meeting with the highways officer. Ask for the objection's evidential basis in writing where it has not been given. Where the authority holds a model, ask for the run outputs.

Two things help at this stage. A short technical note, three or four pages, that sets out the objection, the policy test, the evidence and the offered mitigation in that order. And a recognition that the highways officer is a consultee, not the decision maker: the recommendation is the planning officer's, and the planning balance includes benefits the highways officer is not asked to weigh.

Do not let an extension of time drift. Agree one with a date, and use it.

When to accept refusal and appeal instead

Sometimes the authority will not move and the evidence is on your side. An appeal on a highways refusal is decided by an inspector applying the same policy test, and inspectors are generally willing to find that an impact falls short of severe where the evidence is clear.

Two practical points. A costs application can follow where a refusal on highways grounds is unsupported by evidence, and the guidance on unreasonable behaviour in appeals sets out what that means. And the appeal is decided on the evidence before the inspector, so the technical note you prepared for the case officer becomes the backbone of the statement of case.

Choose the procedure to fit. Written representations suit a self-contained technical disagreement. A hearing is better where the highway authority's reasoning needs testing in discussion.

Structuring the response document is the part PlanScope can help with, drafting the policy framing around your transport evidence. Browse all 66 report types to check the rest of the pack is complete.

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.