Appeal 6005040
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
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
erection of fence and gate (retrospective).
Section 02
Decision
The appeal is dismissed.
Section 03
Preliminary matter
The proposed sliding gate, green metal mesh fencing and other fence panels were in place at the time of my site visit, though it appeared that the mesh fencing may be slightly taller than proposed - up to about 2m height on the frontage. Where there is any discrepancy, this decision relates to the proposal as detailed on the submitted plans and application form rather than to the development as carried out.
Section 04
[name]
The main issues are the effects of the proposal on: i) The character and appearance of this part of [site address] ; and ii) The safety of public highway users.
Section 05
Character and appearance
The A428 [site address] is a primary route between Coventry and Rugby, lined here by rows of mainly detached houses. Some of the frontages are open, but most have a variety of front enclosures including walls, fences, railings, hedges and shrubs.
No [site address] is the first house on the north side of the street, on the approach from Coventry. It is a large detached house, set back from the street with a parking area and tall evergreen hedging to the front. The green mesh fencing has been added to the front of a low timber post and rail fence, on the street boundary. The tall sliding gate that closes off the double width access is set back from the fence line and faced with timber effect composite cladding. The side panels enclosing the gaps to the frontage fencing are clad in the same material.
Even within the context of the varied enclosures nearby, the composite cladding of the gate and side panels stands out as being incongruous and unsympathetic in appearance due to its relatively bright colour and artificial character. Its visual impact is exacerbated by its prominent position on the entrance to [site address] , by its substantial width and by its opaque character, blocking views through.
The green mesh fencing is/would be of substantial height. It is more industrial and less domestic in style than other nearby enclosures. The evergreen hedging helps it to blend in at present, but that cannot be relied on in the long term. The hedge plants are overgrown and now resemble truncated trees more than hedging. At some point in the future they will likely need to be removed. Without thick evergreen hedging the mesh fence would also stand out as being an unsympathetic and uncharacteristic feature in the street scene.
I conclude that the proposal unduly harms the character and appearance of this part of [site address] . It therefore conflicts with policy SDC1 of the Rugby Borough Council Local Plan 2011-2031 (LP), which aims to secure high quality design that responds to and improves local character.
Section 06
Highway safety
[site address] is a busy A road, with one lane of traffic in each direction, footways, and a 30mph speed limit as it passes through [site address] . The Council’s concern, based on advice from the County Highway Authority, is that the gate is not set far enough back from the public highway to allow vehicles to safely pull off the road before stopping to open the gate.
The 2 councils (the planning and highway authorities) seem a bit confused and inconsistent regarding the required set back for the gates. Three different measurements are referenced – from edge of carriageway, edge of footway and edge of public highway – and the required set back is alternatively quoted as being 5m and 5.5m. The highway authority‘s [name] (WDG) advises that gates should be set at least 5.5 metres back from the back of the public highway footway. The WDG was adopted following public consultations, but does not appear to have any formal status in the planning system. I therefore treat it as good advice rather than planning policy.
The gate at No [site address] is set back about 5.7m from the edge of carriageway and about 3.9m from the back of the footway. This means that almost all cars could easily pull off the carriageway, perpendicular to the street, even when the gate is shut. In doing so, they would partially block the footway, but should not have to block it completely. In most cases, therefore, pedestrians should not have to step into the street to pass a stopped vehicle.
There are a number of factors here which help to minimise danger to highway users. Firstly, the 30 mph speed limit means traffic speeds are relatively low and driver visibility is good along this straight section of road. Secondly, the footway on the opposite side of the road is likely to be more heavily used since it gives access towards the nearby commercial/shopping area of Coventry whereas the footway in front of No [site address] terminates not far to the west. Thirdly, there are no parking restrictions here so that visitors’ vehicles and delivery vans can park within the public highway. Finally, the gate is controlled electrically so that in many cases it could be opened without a car needing to wait in the drive for any significant length of time.
Taking all these factors into account, I conclude that the proposal should not prejudice the safety of public highway users. It accords in this respect with LP policy D1 and the National Planning Policy Framework, which aim to ensure safe access is provided to sites.
Section 07
Other matters
The appellant states that the fence and gate are needed for security reasons, in light of vehicle theft and an attempted break in. I recognise this to be a legitimate requirement here, but am not convinced that the current proposal is the only way to address this situation.
I have considered whether a condition could be used to satisfactorily remedy the harm to local character and appearance. The appellant states that she would be willing to compromise by removing the green mesh and reducing the height of the gate to 1m. I cannot, however, impose a condition that would so radically change the proposal.
The appellant’s appeal statement also refers to the possibility of the fence and gate being permitted development1 if the fence is no more than 1m high and the gate no more than 2m. The Council has no opportunity, however, to comment on this assertion within the procedure for this appeal. It is outside of the scope of this decision to assess what alternatives might or might not be permitted development.
Section 08
Conclusion
[name] find in favour of the appellant on the second main issue, my concerns about the first main issue are sufficiently compelling for me to find that the proposal conflicts with the development plan, taken as a whole. I see no overriding factors which would indicate a decision in conflict with adopted policy. For the reasons set out above, and having regard to all other matters raised, I conclude that the appeal should not succeed.
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 890No official casework-database value to compare
- Extracted decision date · page 1
- 7 April 2026Matches the official casework database
- Extracted site visit dates
- 24 March 2026 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 6005040
- Application reference
- R25/0885
- Lead case reference
- Not recorded
- Planning authority
- Rugby Borough Council
- Planning authority code
- E07000220
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
- Not recorded
- Appeal reason
- refused
- Type detail
- Householder
- Jurisdiction
- No Jurisdiction Associated
- Link status
- Not recorded
Site and development
Published appeal-site measurements and planning designations, without the withheld precise location fields.
- Site area
- 0 hectares
- Floor space
- 312 m²
- Number of residences
- Not recorded
- Site in Green Belt
- No
- Agricultural holding
- Not recorded
- Affects setting of a listed building
- Yes
- 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
- 12 February 2026
- Valid date
- 17 February 2026
- Start date
- 17 February 2026
- Planning authority decision date
- 28 January 2026
- Appeal decision date
- 7 April 2026
Case administration
Published recovery, call-in, costs and enforcement information for this case.
- Redetermined
- Not recorded
- Bespoke
- Not recorded
- Date recovered
- Not recorded
- Date not recovered or derecovered
- Not recorded
- Call-in date
- Not recorded
- Costs applied for
- No
- 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
- Back Office
- Dataset status
- Current release
- Catalogue record ID
- 87080
- First seen
- 20 August 2026 at 14:25
- Last seen
- 20 August 2026 at 16:29
- Removed from release
- Not recorded
- Record created
- 20 August 2026 at 14:25
- Record updated
- 24 August 2026 at 16:21