Skip to main content
Official casework recordDismissedCurrent release

Appeal 3281829

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 works

One-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

Proposed single storey side/rear Conservatory.

  1. Section 02

    Decision

    The appeal is dismissed.

  2. Section 03

    Main Issue

    The main issue is the effect of the development on protected trees.

  3. Section 04

    Reasons

    The appeal site is occupied by a two storey, end of terrace dwelling of traditional appearance. Due to its corner location, the dwelling benefits from a generous garden located to both the rear and side of the property. The garden also contains two large, protected trees; a Beech and a Lime.

    Due to the topography of the site, the garden space slopes up from the dwelling. In addition, the space immediately outside the house provides a small patio area that is cut into the rising land. This provides a level space with retaining walls before the garden slopes up to the Lime Tree which is located to the rear of the property. The Beech Tree is located in the north-west corner of the site, more removed from the dwelling and the patio area.

    Due to the presence of the protected trees, the proposal has been supplemented by a substantial level of evidence regarding the arboricultural implications of the proposal. The evidence demonstrates that much of the existing dwelling and cut away patio area is located within the root protection area (RPA) of the Lime Tree. The Beech Tree is more removed from the dwelling, and in the current configuration, the evidence demonstrates that the RPA for this tree is currently unaffected by the existing property and patio area.

    The proposal would seek to introduce a conservatory to the side of the dwelling and to facilitate the addition, the existing cut away patio area would be enlarged. The effect of this would be to incur further into the RPA of the Lime Tree, and also partially into the Beech Tree.

    The evidence suggests that the proposal would eat into approximately 4% of the existing RPA of the Lime Tree, and some 1% of the Beech Tree. The footprint of the conservatory itself would be comparable with the existing cut away patio. Due to the presence of the existing hardstanding and the inevitable compacted ground below, I agree with the evidence that the root system of the Lime Tree is likely to have compensated for the presence of this structure.

    However, as identified above, the RPA of the Lime Tree would already appear to be compromised, and it is not clear in the evidence whether the RPA has been adjusted to compensate for the presence of the house and patio area. Accordingly, although I agree that a rooting system can compensate for a reduced RPA, the evidence is somewhat silent on the effect of the existing house on the tree. Consequently, I find that the evidence in relation to the RPA is not entirely compelling. Instead, the RPA appears to have been plotted in a manner that ignores established constraints.

    This may be a purposeful decision by the appellant, and may also accord with best practice. However, in a situation where the RPA is already compromised, in my judgement, to justify further encroachment requires clear and decisive evidence. I note the suggestion that the level of evidence is commensurate to the scale of the proposal. However, it is not simply the proposal that warrants the evidence, but the presence of large, imposing and protected trees in such close proximity to the location of the proposed works. The trees, particularly the Lime Tree, represent a fundamental constraint to further development and based on the evidence before me, I am not satisfied that the effect on the rooting system of this tree is fully understood.

    The evidence states that due to the depth and extent of the required excavation, this could be undertaken by hand. Such an approach would enable a degree of caution to protect the existing rooting systems, and this matter could be secured through the use of a planning condition. I also note that the evidence suggests that Lime is notably tolerant of root pruning and disturbance. However, without further evidence in relation to the rooting system of the tree, I find that the justification to incur further into the RPA does not exist.

    I also note the concerns from the Council regarding a future desire to reduce the canopy of the trees to reduce shade. However, due to the protected nature of the trees, the Council would retain control over such proposals. Nevertheless, for the reasons identified above, I do not find that the evidence before me provides a suitably compelling case regarding the protection of existing rooting systems. Consequently, I conclude that the proposal would have a harmful effect on the protected trees. It would therefore fail to comply with [name] DG1 and N6 of the Royal Borough of Windsor and Maidenhead Local Plan (2003) which taken together, require amongst other things, new development to protect and retain trees, and not cause harm to the character of the surrounding area.

  4. Section 05

    Conclusion

    For the reasons identified above, the appeal should be dismissed.

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 731No official casework-database value to compare
    Extracted decision date · page 1
    11 April 2022Matches the official casework database
    Extracted site visit dates
    29 March 2022 (page 1)

Reference and authority

Official identifiers and the planning authority recorded against this case.

Case reference
3281829
Application reference
21/01135
Lead case reference
Not recorded
Planning authority
Royal Borough of Windsor and Maidenhead
Planning authority code
E06000040

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
15 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
Dismissed
Decision category
Dismissed
Received date
27 August 2021
Valid date
27 August 2021
Start date
16 November 2021
Planning authority decision date
9 June 2021
Appeal decision date
11 April 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
13780
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