Development Intent
Case officer · Richmond Upon Thames Planning

Tim Wilson.

Recently active — last recorded decision Sep 2025

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

Planning officer106 decisions86% 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 →
106
Applications
2024–25
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%90%202485%202550%2026
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate86% · 14th 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 reports120 officer reports parsed
25%
Approves despite concerns
of approvals record a documented reservation
7%
Negotiated approvals
approvals mentioning revisions/amendments
8%
"On balance" reports
reports using explicit balancing language
57%
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.

Privacy & overlooking
1.62× borough avg
Transport & parking
1.41× borough avg
Bulk & massing
1.39× borough avg
Flooding & drainage
1.38× borough avg
Energy & sustainability
1.3× borough avg

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

How they reason — coded from their reports

Wilson's reports frequently justify an extension's acceptability by naming a specific neighbouring property with a similarly-scaled existing extension ('a similar massing to the side extension at No. 11 Luther Road'), and where a scheme follows a previously refused application, he sets out precisely what was reduced or amended (setback distance, depth) to overcome the prior refusal reasons. He also separately assesses each of the two most-affected neighbouring properties by name in extension cases.

Observable habits

· names one specific comparator property with a similarly-scaled existing extension to justify a design conclusion (e.g. 'similar massing to the side extension at No. 11 Luther Road')

· when a resubmission follows a refusal, itemises the precise changes made (setback distance, depth reduction) that are said to overcome the previous reasons for refusal

· separately assesses each of the (usually two) most-affected neighbouring properties by address before reaching an overall amenity conclusion

· notes where an internal consultee (Transport, Trees) raised an objection and explains how that objection specifically bears on the recommendation

What their reports consistently look for

· what this officer's reports consistently look for: a named comparator property with an existing extension of similar scale/massing to justify why the proposal is acceptable

· what this officer's reports consistently look for: for resubmissions, a specific account of what was reduced or altered (setback, depth) since the previously refused scheme

· what this officer's reports consistently look for: a distinct, named assessment of each of the most-affected neighbouring properties rather than one general amenity conclusion

Assigned Tim Wilson 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 current proposal has maintained the separation between the rear ancillary building and rear extension, setback the extension by 1.2m from the western boundary and reduced the depth by 0.9m. Therefore, the proposal is considered to overcome the reasons for the initial refusal

24/2149/HOT 145 Powder Mill Lane, Twickenham, TW2 6EG Single storey side

The height is limited to single storey and would have a similar massing to the side extension at No. 11 Luther Road

24/1703/HOT

The existing garage is 3.5m wide by 6.3m deep which meets the standards for one parking space. The conversion of the garage would result in the loss of this space and would be counter to the condition of the original permission requiring its use as a garage.

24/2162/HOT

Measured from 120 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 120 parsed reports. Whether refusals citing each survive appeal isn't traced per policy yet.

D4Teddington Station
85 times cited
D12Teddington School
79 times cited
D11
58 times cited
D6The Causeway, Teddington
25 times cited
HC1
22 times cited
D14
9 times cited
D5Queens Road Clinic
8 times cited
D3Teddington Library
6 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

Where this officer's caseload concentrates, 2024–25.[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
24/3265/FUL
Full Application
Approved
2026-02-20
PA25/2761
Full Application
Refused
2026-01-13
24/3265/FUL
Full Application
Approved
2026-02-20
PA25/2761
Full Application
Refused
2026-01-13
Full application history locked
Subscribe to see all 106 decisions →
Consultants approved most— subscriber data
1. Generative Design Partnership Ltd
2. Grainne O'Keeffe Architects Ltd
3. Michael Hemmings Building Design
4. AECOM Planning
At a glance
OfficerTim Wilson
RolePlanning officer
Experience
Applications106 (2024–25)
Approval rate86%
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–25. · 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 120 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.