Greenwich Planning Application Refusals: What the Data Shows

We analysed publicly available planning decision documents for the London Borough of Greenwich and extracted the canonical refusal reasons cited by case officers. Below we share what turns up most often and the practical patterns behind those refusals, so you can design and submit with fewer surprises.

Key Takeaways

• Context-led design and massing is decisive

• Permitted development compliance is a frequent stumbling block

• Liveability tests matter more than unit counts

• Missing or inconsistent information sinks otherwise workable schemes

• Neighbour amenity impacts are closely scrutinised

Top 20 Refusal Reasons: Technical Notes & Examples

1. design, including its siting, scale, bulk, form, quality, and materials, does not respect or enhance the character and appearance of the site and its surroundings, including heritage assets and conservation areas

Case officers point to an unsympathetic architectural response to the established grain and heritage context. The usual concerns are weak proportioning, poor relationship to building lines and rooflines, and materials or detailing that read as generic rather than locally grounded. In conservation settings the decisive test is whether proposals preserve or enhance significance, so unresolved junctions, loss of historic fabric, or visually intrusive elements in public views often lead to harm findings.

How to avoid:

• Prepare a character appraisal and set a clear design rationale

• Test massing with street elevations and verified views in sensitive areas

• Specify durable materials with manufacturer data and samples

• Include a proportion and alignment study for bays, parapets and rooflines

---

2. design's excessive scale, depth, and bulk results in a dominant and bulky addition that harms the character and appearance of the property and surrounding area

Over-deep or bulky additions overwhelm the host building or terrace rhythm and unbalance the plot. Officers look for evidence that rear and side projections remain visibly subordinate, that eaves and ridge lines are respected, and that additions do not read as a second principal volume. Where bulk drives overshadowing or an overbearing presence, design quality alone will not offset the fundamental scale conflict.

How to avoid:

• Compare depth and height against local extension guidance

• Use set-backs and step-downs to subordinate additions

• Provide streetscene elevations to test proportionality

• Evidence cumulative impact where prior extensions exist

---

3. design's excessive depth, bulk, scale, and form, including their cumulative impact, results in a dominant and unsympathetic development that harms the character and appearance of the property and surrounding area

The combined envelope, taken as a whole, tips into overdevelopment. Multiple additions that may be tolerable in isolation can collectively distort the original building’s composition, close off gaps between buildings, and erode the rhythm of the street. Case officers weigh the cumulative townscape effect and whether the scheme still reads as a coherent, subservient extension to the host.

How to avoid:

• Present options testing smaller envelopes and show why the preferred option fits best

• Use sections to demonstrate subordination to the host building

• Reference local design guides and similar consents on the street

• Commit to high quality detailing that refines bulk

---

4. proposed development fails to comply with dimensional and siting limitations of permitted development rights

Schemes relying on the GPDO fall down on height, projection, eaves and ridge, or building line limits. Officers check measurements precisely, including cumulative additions, curtilage coverage and relationships to principal elevations and boundaries. A single failed criterion removes the PD fallback and the proposal is judged as requiring full planning permission or prior approval.

How to avoid:

• Cross-check every dimension against the correct GPDO Class with annotated drawings

• Include cumulative calculations where previous additions exist

• Flag any prior approval triggers and supply required statements

• Use a certificate of lawfulness route if seeking PD confirmation

---

5. development, by virtue of its siting, scale, form, bulk, design, or materials, is incongruous, dominant, or unsympathetic, disrupting the established development pattern and harming the character and appearance of the property and surrounding area

Refusals cite a poor townscape fit that jars with plot structure, rooflines, rhythm and materials. Typical red flags are additions that step forward of building lines, remove the grain of gaps, or introduce façade orders and finishes that do not sit comfortably with neighbours. The test is whether the proposal contributes positively to the streetscene rather than simply avoiding the worst harm.

How to avoid:

• Provide a streetscape study of rooflines, plot widths and façade rhythms

• Justify materials with samples and product cut-sheets

• Use subservient massing moves such as set-backs and recesses

• Align openings and proportions with local typologies

---

6. poor quality of accommodation due to inadequate space, insufficient facilities, outlook, privacy, daylight/sunlight, or other deficiencies impacting living conditions

Homes are judged on liveability, not only numbers. Shortfalls in NDSS, daylight and sunlight, outlook, ventilation, private amenity space and basic functionality undermine internal quality and can indicate overdevelopment. Case officers expect evidence that rooms are usable, naturally lit and ventilated, with noise, overheating and storage needs addressed.

How to avoid:

• Evidence NDSS compliance for GIA, bedrooms and storage

• Provide daylight and sunlight analysis for habitable rooms

• Demonstrate natural ventilation and mitigate overheating risk

• Deliver usable private and communal amenity space

---

7. proposed development exceeds the scope of permitted development rights

Elements fall outside the cited GPDO Class or combine in ways the Class does not allow. Frequent pitfalls include mixing roof forms, extending on elevations that are excluded, exceeding curtilage or volume allowances, or relying on PD where Article 4 directions or previous restrictions apply. Any misclassification or aggregation that breaches scope removes PD protection.

How to avoid:

• Identify the exact GPDO Class and itemise each criterion with evidence

• Separate non-PD elements into a planning application

• Show curtilage coverage and roof form diagrams against the Class rules

• Avoid aggregating past works that tip the scheme beyond the Class scope

---

8. conflict with permitted development use or rights

The PD route is misapplied or relied on without clear proof, so officers cannot accept it as a fallback. Missing plans, ambiguous descriptions, or reliance on assumptions about similar appearance and prior works leave insufficient certainty that the proposal meets all PD criteria and conditions. Where doubt remains, refusal follows and a full application is required.

How to avoid:

• Provide scaled, dimensioned drawings aligned to GPDO text

• Add a compliance schedule that cross-references each criterion

• Address boundary and building line relationships with sections

• Use an LDC where appropriate to lock down the PD position

---

9. conditions cannot be discharged due to inadequate submitted information and non-compliance with planning policies

Post-permission submissions fail where reports, drawings or certification do not match the wording of conditions or the approved plan list. Generic brochures, missing method statements, or uncoordinated updates that shift from what was approved will not pass. Authorities need specific, testable details that can be enforced on site.

How to avoid:

• Reproduce each condition and respond point by point

• Attach required certification or test evidence, not generic brochures

• Cross-reference drawing numbers back to the approved plan list

• Coordinate consultant inputs so they align with the approved layout

---

10. conflict with permitted development use or rights, including due to inaccurate, inconsistent, or insufficient information

Missing or contradictory PD evidence prevents officers concluding that the works are lawful. Common problems include unmeasurable drawings, discrepancies between plans and descriptions, or incomplete history on prior additions that affect PD limits. Without a complete and consistent PD case, the fallback fails.

How to avoid:

• Provide measured surveys and consistent existing and proposed drawings

• Include photographs and site notes for key relationships

• Supply a PD compliance matrix with page references to drawings

• Resolve discrepancies across plans, elevations and sections

---

11. conflict with permitted development use or rights, including due to inaccurate or insufficient information

A shorter variant of 10 with the same evidential gap. If the submission does not clearly prove each PD criterion and condition, officers cannot reasonably rely on the PD position and will refuse or seek a full application instead.

How to avoid:

• Audit all drawings for internal consistency and scale bars

• Add dimensioned details for eaves, parapets and projections

• Include certificates for any PD conditions that trigger materials or privacy controls

• Provide a covering note tying evidence to each PD criterion

---

12. design's scale, height, bulk, massing, or discordant quality is inappropriate for the context, harming the character and appearance of the surroundings, including heritage assets and conservation areas

In sensitive areas the threshold for harm is lower. Overscaled or discordant forms can erode group value, interrupt key views or diminish the legibility of historic fabric even if materials are well specified. Case officers look for clear justification that the proposal preserves or enhances significance and that visibility and prominence have been tested rigorously.

How to avoid:

• Provide a heritage impact assessment with clear significance mapping

• Use verified views where visibility is contested

• Demonstrate subordination through set-backs and ridge alignment

• Agree materials and details upfront with a robust palette board

---

13. design's depth, scale, height, siting, bulk, massing, or discordant quality is inappropriate for the context and harms the character, appearance, or visual amenity of the surroundings, including protected or open land

Encroachment into protected or open land or visually sensitive settings draws objections on visual amenity and openness. Large footprints, tall or reflective structures, and urbanising boundary treatments are typical sources of harm. Proposals must show that openness, landscape character and long views are preserved.

How to avoid:

• Map policy designations and explain how openness and visual amenity are preserved

• Minimise built form and visual clutter with subservient structures

• Use landscape-led mitigation and management plans

• Provide representative viewpoints if the site is exposed

---

14. siting, scale, depth, massing, or design leads to unacceptable impacts on neighbouring amenity, including sense of enclosure, poor outlook, loss of daylight/sunlight, or inadequate ventilation

Neighbour effects are assessed using BRE metrics, sections and relationship studies. Deep projections and high flank walls near windows can create enclosure and overbearing impacts even where daylight is technically compliant. Poor orientation and single-aspect rooms can also compromise ventilation and outlook.

How to avoid:

• Submit BRE daylight and sunlight analysis with sections through key windows

• Provide overshadowing studies for gardens

• Use set-backs, lower eaves and screening for terraces and balconies

• Demonstrate compliance with local residential extensions guidance

---

15. development, by virtue of its excessive scale, form, bulk, or design, is incongruous, dominant, or unsympathetic, harming the character and appearance of the property and surrounding area

A repeat theme where the envelope reads as too assertive for its context. Officers consider whether the proposal erodes subservience, upsets roof and façade hierarchies, or introduces forms that are atypical of the street. If the result competes with rather than complements the host, refusal is likely.

How to avoid:

• Show comparative studies of massing options and choose the least harmful that delivers objectives

• Calibrate proportions, window hierarchy and solid-void balance to neighbours

• Commit to high quality detailing and robust materials

• Use contextual elevations to evidence fit

---

16. insufficient information to demonstrate compliance with permitted development conditions

PD conditions still bite. Without explicit evidence on similar appearance, roof pitch, obscure glazing, balcony restrictions or privacy safeguards, PD cannot be relied upon. Officers expect the drawings and notes to address each condition clearly and in a way that can be enforced.

How to avoid:

• List each PD condition and show compliance on drawings

• Specify materials and roof details explicitly

• Include privacy measures and terrace screens where relevant

• Tie notes to drawing references so they are enforceable

---

17. insufficient or inaccurate details provided to assess the proposal

Authorities cannot reach a positive conclusion without a reliable technical baseline. Common problems include unscaled or inconsistent drawings, missing elevations or sections, and absent reports where triggers exist for transport, flood, ecology or heritage. If the submission cannot be measured and tested, the safest outcome for officers is refusal.

How to avoid:

• Submit scaled, consistent plans, elevations and sections with dimensions and scale bars

• Align the description of development with the drawings and statements

• Provide triggered assessments such as heritage, transport, flood risk or ecology

• Include a clear drawing register and version control

---

18. proposed amendment is not non-material due to significant impacts requiring full planning assessment

If an amendment materially alters scale, appearance or amenity effects, it cannot be handled as an NMA. Changes that reposition openings, increase bulk, switch materials or introduce new impacts will require either a Section 73 variation or a fresh application. The threshold turns on external effects and the decision-maker’s ability to re-run the planning balance.

How to avoid:

• Reserve the NMA route for truly minor drafting corrections or like-for-like tweaks

• Use Section 73 or a fresh application where impacts change

• Provide mark-up drawings isolating the amendment

• Explain clearly why any change has no additional external impact

---

19. proposal exceeds cubic volume permitted under development rights

Roof enlargements that exceed the relevant Class B volume allowance, or that combine with earlier additions to push the total over the limit, are not PD. Errors often arise from measuring to the wrong baseline or overlooking previous roof changes. Where the intended scale cannot meet the allowance, a full application is needed.

How to avoid:

• Provide a cubic volume calculation with diagrams of measurement extents

• Confirm the correct baseline roof form for the Class

• Avoid combining roof additions that cumulatively exceed limits

• Use a full planning application where PD cannot accommodate the quantum

---

20. proposed design elements are not similar in appearance to the existing dwellinghouse, failing to meet permitted development conditions

PD often requires additions to be similar in appearance to the existing dwellinghouse. Discordant materials, profiles, roof pitches and window proportions fail this condition even if dimensions are compliant. Officers look for a coherent match in finish, colour and detailing that reads as part of the same building.

How to avoid:

• Match principal materials, colours and finishes with product cut sheets

• Replicate profiles such as brick courses, eaves and reveals where appropriate

• Evidence visual similarity from the public realm with photos

• If contrast is intended, use a full planning route with a design-led justification

How we approached the analysis

We reviewed publicly available planning decision notices for refused applications in the London Borough of Greenwich. From each decision we captured the stated refusal reasons and key context (e.g., brief proposal description and any cited policies). We then created a simple taxonomy that groups similar wordings into canonical refusal reasons. Finally, we counted how often each canonical reason appeared across our dataset to understand relative frequency. Where a decision listed multiple reasons, each reason was counted in its relevant category.

Conclusion

A clear pattern emerges in Greenwich: refusal risks concentrate in a handful of themes: permitted development compliance, design and townscape plus heritage fit, quality of accommodation, neighbour amenity, information sufficiency and condition discharge. In Greenwich, heritage sensitivity around historic centres and the riverside means early engagement with context, massing and materials pays off. Treat these as pre-submission gates: dimension everything against the right tests, show how the scheme fits its street and policy context, evidence liveability and amenity, and tie off legal and management requirements. This is exactly the kind of pre-flight AICHITECT can assist with, surfacing policy checks, flagging PD, NDSS and amenity risks, and highlighting missing information before you submit.

Appendix: Top Canonical Refusal Reasons (by percentage share)