Appeal 3307060
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
9 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
new front porch and new parking space in the front garden with dropped kerb.
Section 02
Decision
The appeal is dismissed insofar as it relates to a new parking space in the front garden with dropped kerb. The appeal is allowed insofar as it relates to a new front porch and planning permission is granted for new front porch at [site address] in accordance with the terms of the application, Ref 22/1035/HOT, dated 29 March 2022, and the plans submitted with it, insofar as relevant to that part of the development hereby permitted.
Section 03
[name]
The description of development on the planning application form includes words that are not acts of development and therefore I have excluded them in my banner heading above. The planning application form states that the proposed development is completed.
Section 04
[name]
The main issues are the effect of the proposal upon the character and appearance of the area; and highway safety.
Section 05
Character and appearance
The appeal site is a mid-terraced two storey property, with a modest front garden. In the wider area, frontage boundary treatments generally comprise low walls/fences and gates. Front gardens vary in the scale and level of planting, but the prevailing character includes modest lawns, shrubs, plants and hedging. The pavement includes street trees. The street rhythm is generally consistent and harmonious, and the character and appearance of the streetscene is pleasant.
According to the London Borough of Richmond Upon Thames Twickenham Village Planning Guidance Supplementary Planning Document, 2018 (TVPG), the appeal site is located within the [address] character area, which identifies a threat from the removal of front garden walls for off road parking. The London Borough of [name] Planning Document, 2020 (SPD) details guidance and standards for parking in front gardens to ensure that proposals respect the streetscene.
The plans submitted detail a frontage boundary treatment comprising three pillars positioned to form an open ungated frontage to allow vehicle access and a pedestrian access with gate; a very narrow border along the side boundary from the edge of the front porch; and a small border adjacent to the bay window. This does not comply with the SPD which requires openings to be kept to a minimum with two thirds of the boundary retained (para 4.8) and sufficient room for generous planting (para 4.1) to minimise adverse harm upon the streetscene and to effectively mitigate the impact of any hard surfacing.
At the time of my visit, the hard surfaced area comprised uneven block paving with a concrete strip at the opening. Due to their height, width and depth, the brick pillars dominate the frontage. Planting is barely noticeable. The overall appearance is harsh and undermines the rhythm and harmony of the streetscene and the prevailing character of the area.
The front porch has been constructed in accordance with the submitted plans and is considered acceptable by the Council. I find no reason to disagree. It is clearly severable from the remainder of the proposed development, as it is physically and functionally independent.
Consequently, I conclude that the proposed development, insofar as it excludes the front porch, undermines the character and appearance of the streetscene and the wider area. It conflicts with Policies LP1 and LP45 of the London Borough of Richmond Upon Thames Local Plan, 2018. These policies seek to ensure that development is of a high quality design that respects existing street and development patterns; and, to resist the provision of front garden parking spaces where they harm the local character including the streetscene. It would also conflict with the TVDG and the SPD which seek to ensure that development does not unduly harm the streetscene.
Section 06
Highway safety
The appeal site is located within a controlled parking zone, whereby parking bays are provided parallel to the kerb, and there is an extensive bay occupying the immediate kerbside to the appeal site. Although not referred to in the Council’s Planning Report, Meadway links to the A316 ([address]) to the north, and the A305 ([address]) to the south. Signage depicts that Meadway forms part of [name].32. There is a [address]. The road has a range of traffic calming measures, and it is not on a bus route. There is a school safety zone and a public park, both located further south of the appeal site. The time of my extensive visit was off-peak, and Meadway was well trafficked with vehicles and pedestrians.
The Council’s position is that the provision of front garden parking spaces results in a reduction of communal street parking, which then perpetuates a proliferation of front garden parking as street parking becomes more difficult. The reduction of communal parking therefore leads to impedance of free traffic flow as a matter of principle. The proposed development would result in exceedance of the SPD requirement for single crossovers to be 2.4m wide (para 5.11) to retain as much kerbside space for communal parking as possible. The appellant has provided no justifiable reason to overcome the Council’s position.
The proposal would result in a vehicle being required to undertake a reversing manoeuvre across the pavement when entering or leaving the car parking space, impeding the free flow of traffic. Given my observations that the appeal site is located on a road serving two class ‘A’ roads, well trafficked, on a London cycle route and that Meadway has a public park and a school safety zone, I also consider that the proposed development would increase the risk of accidents and create a further hazard to pedestrians and other road users.
The Council’s Planning Report referred to Meadway being a ‘C Class classified road’, and that the proposed crossover will only be approved if it can be demonstrated that a vehicle can enter and leave the site in forward gear (SPD para 5.5). The appellant argues that Meadway is a non-classified road, and the officer’s report is in error, but provides no evidence to support the assertion. In any event, the approval of a crossover is a matter for the highway authority. Even if Meadway is a non-classified road, the harm I have identified would still arise due to the need to employ a reversing manoeuvre.
The Council’s Planning Report noted a lack of information to a sufficient level of detail to demonstrate the permeability and gradient of the hard surface of the proposed car parking space area. However, it also acknowledged that this matter could be overcome by a minor amendment to the application. In any event, the appellant contends that sufficient information has been provided. I disagree. The drawings do not demonstrate a gradient, nor do they provide assurance of permeability through materials. As such, the proposal fails to demonstrate that surface water would be sustainably drained. Without such assurance, the proposal could result in surface water flooding the footway and/or the road, which poses further risk to highway safety.
Consequently, I conclude that the proposed development, insofar as it relates to new car parking space and dropped kerb would unacceptably impact upon highway safety. It would conflict with Policy LP44 and LP21 of the London Borough of Richmond Upon Thames Local Plan, 2018. These policies seek to ensure that development does not severely impact the operation and safety of the highway network; and, to minimise flood risk and deliver sustainable drainage. The proposal fails to comply with the requirements and guidance of the SPD, which seeks to ensure highway safety.
Section 07
Other Matters
The appellant refers me to five examples in support of his appeal. I do not have full details of how those sites came to be built. The main parties agree that three of those examples have planning permission. However, these permissions pre-date the SPD and TVDG, and no evidence has been submitted as to whether they were built when the controlled parking zone was in force. Accordingly, I find no direct comparison between these examples and the proposal before me that weighs in favour of the appeal.
The presence of front garden parking spaces and dropped kerbs elsewhere does not justify further proposals that undermine the character and appearance of the area or result in an unacceptable impact upon highway safety. The further erosion of the character and appearance of the area as a result of the proposal could result in proposals from neighbouring occupiers in the immediate area seeking to do the same, which could further compound the harm that I have identified.
The benefit of the proposal in providing an electrical charging point for a vehicle does not outweigh the harm to the character and appearance of the area or the impact on highway safety that I have identified.
Section 08
Conditions
The Council suggested conditions in the event that the appeal was successful. A standard commencement condition is not necessary as the proposed new front porch is completed. A standard plans condition is not necessary as I have referenced the plans insofar as they relate to the proposed new front porch in my formal decision above.
A condition requiring the development to be carried out in accordance with the provisions of a [name] (FSS) was suggested. However, the Council’s Planning Report acknowledges the acceptance of a [name], and that a FSS is not required for the scheme. As such, this condition is not necessary, nor is it reasonable.
[name] am dismissing the appeal insofar as it relates to a new parking space in the front garden with dropped kerb, I do not need to consider conditions that refer to the proposed new parking space or landscaping treatment.
Section 09
Conclusion
For the reasons given above I conclude that the appeal should be allowed in part and dismissed in part. No material considerations have been shown to carry sufficient weight to warrant a decision otherwise.
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 5599No official casework-database value to compare
- Extracted decision date · page 1
- 16 January 2023Matches the official casework database
- Extracted site visit dates
- 19 December 2022 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3307060
- Application reference
- 22/1035/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
- 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
- 24 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
- Split Decision
- Decision category
- Split decision
- Received date
- 15 September 2022
- Valid date
- 15 September 2022
- Start date
- 21 October 2022
- Planning authority decision date
- 28 June 2022
- Appeal decision date
- 16 January 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
- 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
- Horizon
- Dataset status
- Current release
- Catalogue record ID
- 26546
- 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