Common Reasons Planning Applications Get Refused

Common Reasons Planning Applications Get Refused

Planning refusals rarely happen because a homeowner asked for “too much”. They happen because the proposal does not prove, in planning terms, that it belongs on the site. In London, that proof sits in three places – policy, neighbours, and buildability. If you address all three early, you reduce redesign cycles and avoid the slow grind of resubmissions. That is why many clients start with Armstrong Simmonds Architects when the brief needs to be ambitious but approvable.

Policy and Context Misalignment

Policy comes first. A scheme can look refined and still fail if it conflicts with the local plan, character policies, conservation area guidance, or housing standards. Councils want consistency, not surprises, so your design narrative must align with the written policies and the street context. If the proposal leans on “precedent”, remember that older approvals may sit under different policies or different neighbour conditions and cannot be relied on without scrutiny.

Neighbour Amenity and Technical Evidence

Neighbour impact is the second pressure point. Most refusals rely on amenity grounds – daylight and sunlight loss, overshadowing, overbearing scale, overlooking, and noise. These impacts are measurable, which means they should be tested early through massing options, window positioning, and proper daylight analysis rather than assumed away. In tight terraces, small dimensional changes can materially affect the outcome.

Weak submissions and avoidable refusals

The third reason is largely avoidable – weak submissions. Some applications never receive a fair assessment because the information is incomplete, inconsistent, or poorly presented. Missing reports, unclear drawings, or a vague design justification leave officers little option but to refuse rather than negotiate. This is where Armstrong Simmonds Architects treats planning as part of design – aligning the architectural concept, technical evidence, and written case so the proposal can be assessed efficiently and on its merits.

Finally, do not ignore practical constraints that boroughs treat as non-negotiable: trees, access, parking stress, refuse and cycle storage, drainage, and construction logistics. A short pre-application discussion can surface red flags before they turn into sunk cost.

A few recurring triggers appear across London boroughs:

  • proposals that feel out of character in height, roof form, or materials
     
  • extensions that compromise neighbours’ light or privacy
     
  • schemes that ignore trees, ecology, parking, or access constraints
     
  • weak heritage logic for older or sensitive buildings
     
  • insufficient detail on servicing, drainage, or site set-up
     

The fix is not to design smaller. It is faster to adjust a sketch than to appeal a refusal. Design with constraints visible from day one, then submit a coherent story that reads the site, proves policy alignment, and protects neighbouring amenity.

Index