Skip to main content
Official casework recordDismissedCurrent release

Appeal 3340195

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

8 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

application for fence and gates to front facing highway 1.2m in height.

  1. Section 02

    Decision

    The appeal is dismissed.

  2. Section 03

    Procedural Matter

    A fence has already been erected around the property however the proposed development is for a fence and gates to the front facing highway which is a reduced height of 1.2m.

  3. Section 04

    [name]

    The main issues are: • The effect of the development on the character and appearance of the street scene and the wider area; and • Whether the proposal makes suitable provision for safe access and parking of vehicles.

  4. Section 05

    Character and Appearance

    The appeal site is located in a verdant residential area comprising two-storey, brick built, detached properties with small front parking and garden areas. Most front boundaries are enclosed by low level brick walls with some properties having no means of enclosure. Side boundaries are comprised of low-level fencing or hedging. These low-level boundary features are a key characteristic of the area and create a sense of openness to the street scene.

    The proposal is for the provision of 1.2m high fencing along the front boundary of the site, constructed of timber and composite posts with composite infill panels.

    The materials and height of the fencing would be a discordant feature in the streetscape which is not in keeping with the existing local character of low-level boundary treatments. The solidity of the proposed fencing would create an enclosed appearance around the property, interrupting the open aspect of the street scene and would harm the character and appearance of the local area.

    I therefore conclude that the proposal would have a significantly detrimental effect on the character and appearance of the street scene and the wider area. Hence it would be contrary to the design requirements of Policy P10 of the [name] (as amended by the [name] 2019) (CS), Policies GP5 and N25 of the Leeds Unitary Development Plan (Review 2006) (LUDP) and Policy HDG1 of the Householder Design Guide Supplementary Planning Document (2012). These policies require development to respect the character of the locality and for site boundaries to be designed using walls, hedges, or railings which are appropriate to the character of the area. The proposal would also conflict with the requirements for good design set out in the National Planning Policy Framework (the Framework).

  5. Section 06

    [name]

    The proposed fence and the panels are positioned up to the footway for [address]. Together with the width of the gates, their location, height and materials of construction, they would restrict the inter-visibility between the vehicles exiting the site and other road users and pedestrians, to the detriment of the safety of all concerned.

    The depth of the footway is also insufficient for vehicles to wait clear of the road and for pedestrians to pass. Therefore, whilst the gates are opened for vehicles to enter the site, vehicles may need to wait stationary on the footway, overhanging the carriageway. This would be an inconvenience and safety risk to users of the footway who would be likely to need to enter the road to navigate around vehicles parked on the footway.

    The width of the proposed vehicular access gates is not of an appropriate size and therefore is likely to lead to on street parking, which would obstruct the safe movement of traffic along this stretch of [address] and represent a danger to other road users and pedestrians.

    I have been provided with an illustrative example of how the top composite panel of the driveway gates and adjacent panels could be replaced by trellis panels. While this may allow for a greater extent of visibility, it would not be unrestricted due to the presence of posts and the trellis, so there would still be potential for accidents to occur.

    For the reasons outlined above, I conclude that the proposed development would not make suitable provision for safe access and parking of vehicles and therefore would have an unacceptable impact on highway safety. Hence it would conflict with the aims of Policy T2 of the CS and Policy GP5 of the LUDP, which seeks to ensure that development provides safe and secure access for pedestrians, cyclists and people with impaired mobility and requirements. The proposal would also be contrary to the aims of the Framework in relation to highways safety.

  6. Section 07

    Other Matters

    I note that the appellants reasons for the erection of the fencing are in relation to security but there is no substantive evidence before me to suggest that other security deterrents have been explored or would not be equally effective. Nonetheless, this does not outweigh the harm of the proposed development as outlined above.

  7. Section 08

    Conclusion

    The proposal conflicts with the development plan and the material considerations do not indicate that the appeal should be decided other than in accordance with it. For the reasons outlined, 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 5170No official casework-database value to compare
    Extracted decision date · page 1
    6 June 2024Matches the official casework database
    Extracted site visit dates
    14 May 2024 (page 1)

Reference and authority

Official identifiers and the planning authority recorded against this case.

Case reference
3340195
Application reference
23/05624/FU
Lead case reference
Not recorded
Planning authority
Leeds City Council
Planning authority code
E08000035

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
1 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
7 March 2024
Valid date
7 March 2024
Start date
15 March 2024
Planning authority decision date
21 December 2023
Appeal decision date
6 June 2024

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