Development Intent
Case officer · Richmond Upon Thames Planning

Phil Shipton.

Active — last recorded decision May 2026

A case officer at Richmond Upon Thames with an approval rate of 83% across 233 decided planning applications, spanning 17 wards.[1] Decision speed and appeal performance publish when decision notices are ingested.

Planning officer233 decisions83% approvalSave
Richmond Upon Thames · ward map
Approval rate — by ward
Lower ~68%
Higher ~90%
ShowingAll years · subscriber →across all years on record — a period re-scopes the headline figures and the trend
At a glanceEach metric links to the investigation behind it
All investigations →
233
Applications
2024–26
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%80%202483%202585%2026
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate83% · 27th of 67
higher is betterdashed = London avg
Decision time · publishes with decision notices
in development
Appeal overturn · publishes with decision notices
in development
How this officer decides — from their own reports245 officer reports parsed
0%
Approves despite concerns
of approvals record a documented reservation
10%
Negotiated approvals
approvals mentioning revisions/amendments
5%
"On balance" reports
reports using explicit balancing language
64%
Bespoke reasoning
of report text written for the case, not recited
What they write about — vs Richmond Upon Thames's average officer

Topic mentions per 1,000 words of their own report text (boilerplate stripped), indexed against all parsed Richmond Upon Thames reports. Attention, not stance.

Daylight & sunlight
2.7× borough avg
Flooding & drainage
1.53× borough avg
Energy & sustainability
1.41× borough avg
Noise & disturbance
1.2× borough avg
Bulk & massing
1.15× borough avg

Mark = borough average (1×). Bar capped at 2×.

How they reason — coded from their reports

Shipton's reports lean heavily on named consultee input, in particular quoting the Council's Urban Design Officer's own words directly rather than summarising them, and on measured sight-line/separation-distance evidence for neighbour amenity conclusions (e.g. exact metre distances to specific neighbouring windows). He frequently tests garage/outbuilding dimensions against the Transport SPD's specific 3.0 x 6.0m internal garage standard to determine whether a structure genuinely functions as vehicle parking or should be treated as storage.

Observable habits

· quotes the Council's Urban Design Officer's assessment directly in quotation marks rather than paraphrasing it

· tests a garage or side extension's internal width/door width against the Transport SPD's specific 3.0 x 6.0m garage dimension standard to decide whether it can genuinely house a vehicle

· states an exact measured separation distance (e.g. '20.0m separation distance') between a new habitable window and named neighbouring properties to justify a no-overlooking conclusion

· notes where a design feature (e.g. rooflights lacking a parapet screen) is 'a relatively minor point' that does not change the overall conclusion, rather than omitting it

What their reports consistently look for

· what this officer's reports consistently look for: whether a garage's actual internal dimensions meet the Transport SPD's 3.0 x 6.0m standard before it is credited as genuine vehicle parking

· what this officer's reports consistently look for: the Urban Design Officer's or Conservation Officer's own wording on a scheme's heritage impact, quoted rather than paraphrased

· what this officer's reports consistently look for: a specific measured separation distance to the nearest affected neighbouring window before concluding overlooking is or is not significant

Assigned Phil Shipton on a live case?What they pay attention to, how they reason, and what their reports consistently look for — so you can address it before they raise it.Subscribe to unlock →
In their own words

The proposed garage has an internal width of approximately 2.25m and a door width of approximately 1.6m. Such a width is considered highly unlikely to accommodate any modern 4-wheel vehicle.

24/0908/HOT

the approximate 20.0m separation distance between the east facing windows of the proposed first floor bedroom and the rear of the dwellinghouses at No.64 and No.62 Myrtle Road, is sufficient to ensure unreasonable overlooking not occur

24/1199/FUL

Measured from 245 published Richmond Upon Thames officer reports written by this officer, with recited policy boilerplate stripped before any counting. These describe how this officer works and writes — they are not outcome predictions. Every quote is from a named public report.

Policy playbook — what this officer cites[3]

The policies this officer cites most in their own reports — times cited across 245 parsed reports. Whether refusals citing each survive appeal isn't traced per policy yet.

D12Teddington School
145 times cited
D4Teddington Station
127 times cited
D11
107 times cited
HC1
80 times cited
D6The Causeway, Teddington
26 times cited
D14
14 times cited
D10
10 times cited
H1Mortlake Riverside strategy: conserve and enhance heritage
6 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

Where this officer's caseload concentrates, 2024–26.[1] Click the map above to focus this page on a ward, or a row to open the ward.

Recent applications
Address
Reference
Type
Outcome
Date
PA26/0759
Householder Application
Approved
2026-06-02
PA26/0759
Householder Application
Approved
2026-06-02
Full application history locked
Subscribe to see all 233 decisions →
Consultants approved most— subscriber data
1. Green Cu3ed Architectural Solutions Ltd
2. ajt design services ltd
3. GBS Architectural Ltd
4. Fisch Planning
At a glance
OfficerPhil Shipton
RolePlanning officer
Experience
Applications233 (2024–26)
Approval rate83%
London approval avg81%
Who decides here
GovernmentMayor of LondonCouncilCommitteeOfficersDecisionsApplicantsInspectorate
Related investigations
When committees overrule officers like this one →
How often members depart from officer recommendations, and how those overrides fare at appeal.
How much gets decided without a committee →
The delegated share by borough and officer — where the real power over decisions sits.
Sources & method
  1. [1]Applications decided, approval rate, per-year trend and ward breakdown — London Borough of Richmond Upon Thames planning register and published decision notices, 2024–26. · methodology
  2. [2]Appeal overturn and decision-time benchmarks — Planning Inspectorate (PINS) appeal decisions and application date pairs; not yet computed per officer, shown as a dash until they are. · PINS appeals casework
  3. [3]Condition load — Richmond Upon Thames's decision-notice parsing is limited coverage, so no borough or officer figure is shown.
  4. [4]"How this officer decides", the policy playbook and all quotes — parsed from 245 published Richmond Upon Thames officer reports written by this officer, recited policy boilerplate stripped before counting; disposition text coded from their own reasoning with every quote machine-verified verbatim. Descriptive of how they work — not outcome predictions.
Methodology is published in full so every number is traceable to its primary source.