Traffic and Parking

Is traffic a material consideration?

Highway safety is - a specific, evidenced risk to road users (a new or altered access onto a busy road with poor visibility, a junction already prone to accidents, a development that would significantly increase traffic on a road unsuited to it). General increases in traffic volume or inconvenience are much harder to argue as a standalone reason for refusal; councils’ own highways teams are usually the ones who assess and comment on this. Councils will usually give significant weight to the advice of their highways authority, although well-evidenced resident concerns can still influence the assessment where they raise site-specific issues or information not otherwise considered.

Is a lack of parking a material consideration?

Often, yes, particularly where a development provides fewer parking spaces than your council’s adopted parking standards require for that type of property, or where on-street parking is already under pressure. It carries less weight in areas explicitly designed around limited car use (well-served by public transport, or subject to a car-free planning policy), where reduced parking provision may actually align with council policy rather than conflict with it.

What strengthens this objection

• Citing your council’s adopted parking standard for the relevant property type, if the application falls short of it
• Describing a specific visibility, access, or junction safety issue, ideally referencing an existing pattern of near-misses or accidents if you’re aware of any
• Explaining how existing on-street parking is already used (e.g. by residents without off-street parking, school pick-up, a nearby business) rather than asserting it’s “always full”

Where it tends to fail

“This will make parking worse” or “the road can’t take more traffic” without a specific safety issue or a comparison to an adopted standard reads as general inconvenience rather than a planning harm, and is usually given limited weight against an application that otherwise meets policy.

A worked example of a weak objection versus a strong one

Weak: “There’s already nowhere to park on this street and this will make it worse.” A real concern, but framed as inconvenience rather than a planning harm a case officer can weigh.

Strong: “The proposed conversion creates three additional one-bedroom flats but provides no off-street parking, against the council’s adopted standard of at least one space per unit for this area. [Street name] already operates at or near capacity for on-street parking during the evening, used mainly by existing residents without driveways - I’ve attached photos taken on three recent weekday evenings showing this. Without additional off-street provision, this application would add further pressure to a street that’s already at capacity, contrary to the adopted parking standard.” The second version cites the actual standard, describes current use with evidence, and connects the shortfall directly to the application rather than to parking pressure in general.

Common mistakes to avoid

• Objecting to increased traffic volume alone, without a specific safety issue - volume increases are usually assessed by the highways team against capacity thresholds, not treated as an automatic harm
• Asserting a junction or access is dangerous without any supporting detail - a description of sightlines, road width, or a known history of near-misses carries far more weight than the word “dangerous” on its own
• Overlooking your council’s adopted parking standards entirely - citing the actual number required versus proposed is one of the few genuinely quantifiable points available in a parking objection
• Objecting to construction traffic as if it were permanent - temporary construction-phase disruption is usually addressed through conditions (like a Construction Management Plan) rather than being a reason to refuse the application outright