Appeal 3293139
Public case and site metadata stored from the official casework database, including fields that were empty in the source release.
A clearer next step
See how Inspectors approached issues like yours
Bring your planning decision into a private workspace. We separate the disputed points, then match them with source-located Inspector reasoning from similar appeals.
- See which issues the decision appears to turn on
- Compare the facts and open the full appeal records
One private comparison
How the refusal review worksOne-off service · No subscription
Similar appeals are evidence to inspect, not a prediction of your outcome.
Official decision document
The decision, section by section
5 sections
Read the development description and the Inspector’s text from the official decision PDF in source order. Source headings are retained where available. Personal and contact details are removed by an automated privacy filter; this is source material, not Rules for You analysis.
Section 01
Development description
No verified development description has been extracted from an official decision PDF yet.
Section 02
Decision
The appeal is dismissed.
Section 03
Main Issue
The Council had no objection in principle to the proposed single-storey side and rear extension or to the construction of a new wall on the property’s driveway. I have no reason to disagree. The main issue therefore is the effect of the proposed hip-to-gable change and rear dormer window on the character and appearance of [site address] and the wider area.
Section 04
Reasons
The appeal property is a two-storey, end-of-terrace dwelling located within a residential neighbourhood comprising properties of broadly similar age and style. The proposal comprises a number of elements including a hip to gable change to the dwelling’s existing roof profile and a dormer window to the rear elevation to facilitate a loft conversion.
Policy DMD 13 of the Council’s Development Management Document (DMD), adopted in 2014, deals with roof extensions. It states that roof extensions must be of an appropriate size and location within the roof plane and that roof dormers must be inset from the eaves, ridge, and edges of the roof, with insets normally between 500-750mm. They must also be in keeping with the character of the property and not dominant when viewed from the surroundings. The policy also requires that roof extensions to the side of a property must not disrupt the character or balance of the property or pair or group of properties of which the dwelling forms a part.
The short terrace of five dwellings, which the appeal property forms part (Nos 55-63 odd), is not symmetrical. The hipped roof form of No 63 is not reflected by No 55 at the opposite end which has a gabled flank wall. Furthermore, gabled roofs feature prominently within the street scene along [address] and the immediately surrounding area. No 63 currently has a hipped roof with a stepped ridge line due to a slightly subservient and narrow two-storey side extension that appears as a fully integrated part of the existing dwelling. The introduction of gabled ends to the side of the original building, and to the extension, would undeniably alter the existing roof profile but in my assessment this change would not unacceptably disrupt the character or balance of the property or terrace, given the context of its surroundings.
The proposed rear dormer would span virtually the full width of the original property and would be dependent upon the hip-to-gable change in order to accommodate its size. I therefore do not agree with the appellant’s view that it would be contained within the context of the roofscape associated with the original dwelling. Although it would appear to be reasonably set in from both sides of the extended roof, according to undisputed figures given by the Council it would be just 130mm above the eaves and just 50mm down from the ridge when taking account of the solar panels that are proposed to be installed on its flat roof. I do not share the appellant’s view that it would be subservient both physically and visually. On the contrary, it would be seen as a dominant addition that would significantly change the roof profile and character of the dwelling, and one which would be clearly viewed from the rear gardens and outlooks from surrounding properties. Its intrusive form would be exaggerated further through the proposed use at an elevated and prominent level of contrasting cedar cladding that would be set against the backdrop of traditional natural slate, and the almost floor to ceiling glazing which would show little correlation with the fenestration pattern below at first floor level. As such, I find that there would be clear conflict with Policy DMD 13.
I observed during my visit that Nos 59, 57 and [address] all have large, ‘box-like’ dormers to their rear roof slopes. These all give the impression of a second storey to these dwellings. I also accept that there are other examples nearby of large rear dormer extensions. Nevertheless, my overall impression was that such additions were by far the minority in the locality rather than the norm and that they were not so prolific to have changed the overriding cohesive architectural character of [address] and the immediate surroundings. Furthermore, I have no specific details of the planning history to any other properties in terms of either relevant policies that may have been in place at the time of granting planning permission, or even if planning permission would have been required. Regardless, the examples I saw on the other properties within the terrace served to demonstrate to me the harm that can be caused by insensitive extensions.
The development at [address], which has been drawn to my attention, is a stand-alone redevelopment that has nothing in common with the appeal proposal which is for extensions to an existing dwelling. 2
Overall, for the reasons given, I find that due to the size and appearance of the rear dormer, the proposal would be harmful to the character and appearance of [site address] and the wider area. I have identified clear conflict with Policy DMD 13 of the current DMD. By failing to achieve a high-quality design and appropriate regard to its surroundings, the proposed dormer would also conflict with [name] 6, DMD 8 and DMD 37, Core Policy 30 of the Council’s Core Strategy 2010, and Policy D4 of The London Plan 2021. For the same reasons there would be conflict with the National Planning Policy Framework’s (the Framework) objectives for achieving well-designed places.
Paragraph 2 of the Framework states that planning law requires applications for planning permission to be determined in accordance with the development plan unless material considerations indicate otherwise. The developments nearby and within the wider area that have been put to me do not lend sufficient weight in favour of the proposal to outweigh the harms that I have identified and the conflicts with local and national policy.
Section 05
Conclusion
For the reasons given, I find that the proposal would be harmful to the character and appearance of [site address] and the wider area. I have noted the appellant’s desire to expand their living space to accommodate their family’s requirements, including the need to work from home, but neither this, nor any other matters raised, alters my conclusion that the appeal should fail.
Planning inspector and document dates
The official casework attribution is grouped under a one-way keyed hash and shown only by its local identifier. Decision-letter dates and page references are extracted by fixed first-page rules and checked against that authoritative record.
Appeal Decision
- Extracted inspector · page 1
- Inspector attribution ID 286No official casework-database value to compare
- Extracted decision date · page 1
- 10 August 2022Matches the official casework database
- Extracted site visit dates
- 27 July 2022 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3293139
- Application reference
- 21/04203/HOU
- Lead case reference
- Not recorded
- Planning authority
- London Borough of Enfield
- Planning authority code
- E09000010
Casework details
The casework, procedure, development and linking details supplied by the official record.
- Casework type
- Householder (HAS)
- Procedure
- Written Representations
- Development type
- Householder developments
- Appeal type reason
- 1. Refused planning permission
- Appeal reason
- Refusal
- Type detail
- Planning Appeals - Full
- Jurisdiction
- Transferred
- Link status
- Not Linked
Site and development
Published appeal-site measurements and planning designations, without the withheld precise location fields.
- Site area
- Not recorded
- Floor space
- Not recorded
- Number of residences
- 0
- Site in Green Belt
- No
- Agricultural holding
- No
- Affects setting of a listed building
- Not recorded
- Historic building grant made
- Not recorded
- Relates to a conservation area
- Not recorded
- Flooding is an issue
- Not recorded
- Site within an AONB
- Not recorded
- Site within an SSSI
- Not recorded
Decision and dates
The published outcome and every imported case date.
- Official decision
- Dismissed
- Decision category
- Dismissed
- Received date
- 18 February 2022
- Valid date
- 18 February 2022
- Start date
- 3 March 2022
- Planning authority decision date
- 22 December 2021
- Appeal decision date
- 10 August 2022
Case administration
Published recovery, call-in, costs and enforcement information for this case.
- Redetermined
- No
- Bespoke
- No
- Date recovered
- Not recorded
- Date not recovered or derecovered
- Not recorded
- Call-in date
- Not recorded
- Costs applied for
- Not recorded
- Enforcement grounds count
- Not recorded
- Enforcement grounds
- Not recorded
Source and catalogue history
When this record appeared in the rolling official release and when the catalogue stored it.
- Source
- Planning Inspectorate casework database
- Source data system
- Horizon
- Dataset status
- Current release
- Catalogue record ID
- 19031
- First seen
- 20 August 2026 at 14:24
- Last seen
- 20 August 2026 at 16:26
- Removed from release
- Not recorded
- Record created
- 20 August 2026 at 14:24
- Record updated
- 24 August 2026 at 16:21