In reality, most planning permission refusals or delays don’t come from the architectural idea or design itself. They come from how clearly the proposal responds to planning policy, how well supported it is, and how effectively it’s presented to decision-makers.

And that’s where outcomes are often won or lost.

Why do planning applications get refused (or delayed)?

Most planning permission refusals typically fall into a few common categories:

1. Policy conflict

‍‍The proposal doesn’t fully align with local or national planning policy. For example:
‍

• A new-build dwelling in open countryside where local policy restricts development outside settlement boundaries, unless it meets very specific exceptions (e.g. agricultural need or rural exception housing).
  ‍
• A contemporary extension that significantly increases massing in a conservation area, where local policy requires development to preserve or enhance the character of the area.
  ‍
• A replacement dwelling that is materially larger than the original footprint in an area where policy limits “overdevelopment” or sets strict parameters for scale increases.
  ‍
• A design that doesn’t meet national policy expectations under the National Planning Policy Framework (National Planning Policy Framework), particularly around design quality or sustainability expectations.

In all of these cases, the issue usually isn’t the idea itself, it’s that the proposal needs to be better aligned or more clearly justified against the relevant policy wording.

2. Design and character concerns

The scale, materials, or form are not responding well to context

3. Insufficient information. ‍

Missing reports, unclear drawings, or weak justification
‍

4. Technical constraints

‍Drainage, highways, ecology, heritage, or viability issues
‍

5. Poor coordination

Conflicting advice between consultants or inconsistent submissions

6. Officer interpretation‍

Different readings of policy or site context
‍

In many cases, it’s not a “no” to the idea but a “not yet” to how it’s been presented.

What your architect should be doing when issues arise

When a planning issue comes back, a good architect shouldn’t just amend and resubmit. They should:

• Break down the refusal reason properly (what is policy-based vs subjective)
• Reassess the strategy, not just the drawings
• Coordinate consultants so everything is aligned
• Identify whether refinement or repositioning is needed
• Advise when a Planning Consultant or additional reports are required
• Keep the design intent intact while improving the planning argument

How many resubmissions is normal?

There isn’t a fixed number.

Some projects are approved first time.  Whereas many can go through one or two rounds of revision, and more complex or sensitive sites can take multiple submissions or appeals

What matters more than the number is whether each stage is making meaningful progress, or just repeating the same submission with minor changes.

When do you need to make bigger changes?

Not every refusal means starting again, but there are clear signals that you may need a more fundamental rethink:

• The same core issue appears in multiple refusal reasons
• The proposal is consistently at odds with local character or policy direction
• Technical constraints are driving the design in the wrong direction
• Planning officers are supportive in principle but not in form
• Minor amendments aren’t shifting the outcome

At that point, the strategy most likely needs to change.

What experienced architects will often suggest

Depending on the situation, a strong architectural and planning-led team might recommend:

• Reframing the design approach to better align with policy intent
• Reducing or adjusting scale/massing to respond to context
• Strengthening the planning statement or design justification
• Bringing in specialist consultants earlier (ecology, drainage, highways, heritage)
• Phased or alternative submission strategies
• In some cases, withdrawing and resubmitting rather than pushing a weak position

Why local context matters more than people expect

A proposal can fail or stall for very site-specific reasons, such as:

• Conservation area sensitivities or listed building proximity
• Local character expectations (materials, rooflines, density)
• Flood zones or drainage infrastructure limits
• Highway access visibility and safety concerns
• Ecology or tree protection constraints
• Local planning precedent (what has or hasn’t been approved nearby)

Understanding these early can often change the outcome entirely.

A recent example

A good example is our Pippins project, a new-build eco-home in Colchester, we’ve been designing from the outset.

It’s a full prefabricated, low-impact scheme, developed with both design intent and planning strategy embedded from day one. The focus has been on ensuring the proposal is carefully aligned with planning expectations while maintaining the original vision.

Like many projects, it has required refinement through the process – not because the design is weak, but because planning is iterative, and responses evolve as feedback is received.

Experienced input matters

Even well-designed schemes can take time to progress through planning.

The difference is often how they are guided through that process — whether there is clarity in strategy, coordination across consultants, and a clear understanding of how decisions are actually made.

That’s where experienced input matters.

Not to guarantee approval, but to improve the quality of the submission, reduce avoidable setbacks, and give the project the strongest possible chance of success.

‍