Skip to main content
Official casework recordDismissedCurrent release

Appeal 3287738

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

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

described as Composite eco fence erected at 1.9 metres high around the boundary of the property, adjacent to public footpath.

  1. Section 02

    Decision

    The appeal is dismissed.

  2. Section 03

    Preliminary Matters

    At the time of my site visit, I saw that the fence had been constructed. I have dealt with the appeal on this basis.

  3. Section 04

    Main Issue

    The main issue is the effect of the proposed development on the character and appearance of the surrounding area.

  4. Section 05

    Reasons

    The appeal site forms a corner plot at the junction between [address] and [address] and is situated diagonally opposite [site address] . It occupies a relatively prominent position in the public realm and is visible in both short and longer distance views. Boundary treatments fronting the highway in the surrounding area include generally low walls and timber fences – with hedges/vegetation visible behind – along [address] while higher timber fencing is present along the rear boundaries of the [address] properties which back on to [address]. The fence at No [address], which is situated on the other side of the junction from the site, also runs along much of that property’s [address] frontage. Although the locality therefore contains a mixture of boundary treatments facing the public realm, they generally have a modest presence due to either their low height or, in the case of the higher close boarded fencing described above, their set back from the footway and the inclusion of soft landscaping. The area in the vicinity of the site therefore has a relatively open character and verdant appearance, with boundary treatments neither dominating nor being particularly notable features in the streetscene.

    With its height and lack of set-back accentuating its prominence and limiting the opportunity for soft landscaping to soften its presence, the proposed fence – which faces both [address] and [address] – reads as a stark, obtrusive and harmful element in the streetscene. Its composite material and solid grey colour draw the eye – for some distance, including from across the Heath for example – to what is a conspicuous, unsympathetic and incongruous feature that does not reflect boundary treatment found in the surrounding area and erodes the open character of the locality.

    In coming to this view, I have taken into account that the proposed fence is similar in height to the close boarded fencing described above, the previous fence was longer than the proposed fence, the visual prominence of the property compared to the appeal proposal, and that buildings in the locality are not designated heritage assets or within a conservation area. Although the built environment in the surrounding area includes various grey elements, such as cladding, fenestration, driveways, walls, fences of various heights, grey painted buildings and the nearby pub’s conservatory, I observed on my site visit that such materials and features are not notable or defining characteristics of the area. Accordingly, the existence of such elements neither make the development acceptable nor lead me to a different conclusion.

    For the above reasons, I conclude that the proposed development would harm the character and appearance of the surrounding area. I therefore find that it does not accord with Policies DM1 and DM9 of the Maidstone Borough Local Plan (2017). Amongst other aspects, these seek development with good design and set out that proposals which respond positively to local character, retain traditional boundary treatment of the area and fit unobtrusively with the context will be permitted. The proposal would also be inconsistent with the guidance on boundaries in the Council’s Supplementary Planning Document, [name] (2009).

    I acknowledge that the appellant found the previous one metre high fence did not offer privacy to the property’s main garden and the family dog was able to jump over it, creating a dangerous situation for the dog and highway users. The proposed fence is said to have been complimented by various neighbours, keeps the dog(s) in and safe, and reduces the amount of rubbish being blown into the garden from the road. It has been put to me that the fence, providing privacy for the family and visitors, is also an environmentally friendly composite made from 95% recycled material and will not need annual maintenance with harmful chemicals. Be that as it may, the harm I have identified above, which could not be overcome by the imposition of planning conditions, and the conflict with the development plan are not outweighed by these considerations. Given the development’s harm on the character and appearance of the surrounding area, it does also not adequately address the social and environmental roles of sustainable development as set out in paragraph 8 of the National Planning Policy Framework.

  5. Section 06

    Conclusion

    For the above reasons, the appeal is 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 954No official casework-database value to compare
    Extracted decision date · page 1
    7 February 2022Matches the official casework database
    Extracted site visit dates
    26 January 2022 (page 1)

Reference and authority

Official identifiers and the planning authority recorded against this case.

Case reference
3287738
Application reference
21/502490/FUL
Lead case reference
Not recorded
Planning authority
Maidstone Borough Council
Planning authority code
E07000110

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
1
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
25 November 2021
Valid date
25 November 2021
Start date
15 December 2021
Planning authority decision date
21 October 2021
Appeal decision date
7 February 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
10130
First seen
20 August 2026 at 14:24
Last seen
20 August 2026 at 16:25
Removed from release
Not recorded
Record created
20 August 2026 at 14:24
Record updated
24 August 2026 at 16:21