Appeal 3315650
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
6 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
a first floor extension.
Section 02
Decision
The appeal is allowed and planning permission is granted for a first floor extension at [site address] in accordance with the terms of the application Ref 22/3058/HOT, dated 9 October 2022, subject to the conditions set out in the attached Schedule.
Section 03
[name]
The main issue is the effect of the proposal on the character and appearance of the host property and its surroundings.
Section 04
Reasons
The appeal property is a semi-detached dwelling set in a street showing typical suburban characteristics. It has been extended before with a side/rear, mainly flat roofed two storey extension, and another full width ground floor extension at the rear. The appellant wishes to extend the bathroom on the first floor at the rear.
The proposed development is described as ‘very small’ in the grounds of appeal. The Council agrees that, in itself, the proposal could possibly be described in these terms, but considers it should be assessed in the context of the extensions already carried out to the house and to those already approved or consented1.
On this basis, the Council considers that the cumulative effect of this and the other extensions would materially affect the character and appearance of the dwelling at the rear to its detriment, it would represent overdevelopment and the proposal would breach the guidance contained in its SPD2 that ‘two storey 1 The appellant points out that these are already built. 2 Supplementary Planning Document – [name] and [name] side and rear extensions should not be greater than half the width of the original building, to ensure the extension does not over-dominate the building’s original scale and character’.
I understand the Council’s points, but do not share its view. To my mind, the extension sought can properly be described as small and would fit in neatly within the gap between the existing flat roof first floor extension and the wide bedroom bay window which occupies the original wall of the dwelling at the rear. Little remains of the original character of the dwelling at the rear because of the alterations and additions already carried out. Having regard to its design, this small addition, in my view, would be unobtrusive, and would be successfully subsumed within the whole without causing visual harm or giving rise to an overdeveloped appearance.
Moreover, the rear of the dwelling is visually sheltered. A railway in cutting lies to the north with trees, a high fence and outbuilding providing screening from this direction. The existing first floor extension would largely mask views of the proposed extension from a significant proportion of the domestic gardens to the west; the extension could be seen from a limited number of private gardens to the east, but it would be set against the backcloth and profile of the existing first floor extension. The proposed extension would therefore be barely noticeable if built.
I conclude that having regard to the particular circumstances of the case the SPD’s guidance on the width of extensions need not be slavishly adhered to. This small extension would sit harmoniously in its much-changed visual context without harming the character and appearance of the host property or its surroundings. Accordingly, the proposals accord with those provisions of LP3 policy LP1 requiring the design to demonstrate a thorough understanding of the site and relates well to its existing context.
Section 05
Conditions
In the interests of visual amenity, I shall impose a condition in respect of external materials, although it will vary from that suggested by the Council.
It is necessary, in the interests of certainty that the development shall be carried out in accordance with the approved plans.
To ensure compliance with policy D12 of the London Plan I shall impose the Council’s suggested condition relating to [name].
I consider a further condition restricting building times is necessary so as to protect neighbouring amenity.
Section 06
Other matters
I have taken account of all other matters raised in the representations including the representations made by a local resident which relates principally to the nuisance claimed to have been caused to residents arising from building works recently carried out in this part of the street. A condition regarding hours of building is imposed so that people may enjoy their gardens at reasonable times. 3 Richmond Local Plan 2018 2
Comments are also made by the resident in respect of the alleged overdevelopment, which I have already dealt with, and impact on neighbours by reason of the extension’s effect on sunlight and daylight. The officer report assesses possible impacts on neighbouring amenity and I share the conclusion reached that the extension, if built, would not give rise to any harmful consequences on neighbouring residents.
All other matters raised have been considered but none outweighs the considerations which led to my conclusions.
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 2949No official casework-database value to compare
- Extracted decision date · page 1
- 30 June 2023Matches the official casework database
- Extracted site visit dates
- 6 June 2023 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3315650
- Application reference
- 22/3058/HOT
- Lead case reference
- Not recorded
- Planning authority
- Richmond Upon Thames London Borough Council
- Planning authority code
- E09000027
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
- Unknown
- 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
- 4 m²
- 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
- Allowed
- Decision category
- Allowed
- Received date
- 29 January 2023
- Valid date
- 8 February 2023
- Start date
- 28 March 2023
- Planning authority decision date
- 19 January 2023
- Appeal decision date
- 30 June 2023
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
- 34884
- First seen
- 20 August 2026 at 14:24
- Last seen
- 20 August 2026 at 16:27
- Removed from release
- Not recorded
- Record created
- 20 August 2026 at 14:24
- Record updated
- 24 August 2026 at 16:21