Development Intent
AtlasRichmond Upon ThamesOfficersRamasankaran Rajendran
Case officer · Richmond Upon Thames Planning

Ramasankaran Rajendran.

Last recorded decision Feb 2024 — no decisions in this record since

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

Planning officer32 decisions76% 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 →
32
Applications
2023–24
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%90%202368%2024
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate76% · 53rd 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 reports50 officer reports parsed
28%
Approves despite concerns
of approvals record a documented reservation
6%
Negotiated approvals
approvals mentioning revisions/amendments
8%
"On balance" reports
reports using explicit balancing language
53%
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.67× borough avg
Bulk & massing
1.69× borough avg
Privacy & overlooking
1.58× borough avg
Materials & detailing
1.56× borough avg
Flooding & drainage
1.4× borough avg

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

How they reason — coded from their reports

Rajendran's reports give precise physical dimensions for extensions and outbuildings (depth, eaves height, maximum height, width) before assessing acceptability, and he repeatedly cross-references specific comparator addresses and application numbers on the same street to justify why a scheme is or is not out of character. He frequently separates a scheme into named sub-elements (e.g. 'Rear dormer' then 'Front porch') within a single report rather than treating the whole proposal as one design issue.

Observable habits

· states exact dimensions (depth, eaves height, maximum height, width) for the specific extension/outbuilding before reaching a design conclusion

· names specific comparator properties and their application references on the same street to support a 'not out of character' finding

· breaks a single application into separately-headed physical elements (e.g. rear dormer, then front porch) each assessed in turn

What their reports consistently look for

· what this officer's reports consistently look for: precise measurements of the proposed extension or structure (depth, eaves height, maximum height) checked against SPD depth/height limits

· what this officer's reports consistently look for: named comparator extensions/outbuildings at specific neighbouring addresses, with their application references, to establish local pattern

· what this officer's reports consistently look for: whether a proposed bin/bike or garden store is taller or larger than other approved examples in the borough, treated as a reason it becomes highly visible

Assigned Ramasankaran Rajendran 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

given the rear elevation of the dormer would be set in from the eaves by approx. 0.2m, this is considered adequate to restrict lines of sight into neighbouring gardens

23/0992/HOT

it would be similar to the scale of the existing extensions to other ground floor extensions visible in the surrounding area, such as the No. 19 (16/3328/HOT) 19 Devon Avenue, ensuring that the proposed development would not appear incongruous in the context of the terrace

23/2636/HOT 17 Devon Avenue Twickenham TW2 6PN Proposed single storey rear extension Ramasankaran Rajendran 22.11.2023

the bin/bike store is larger than the other approved bin/bike stores at the front garden in the borough. Consequently, it interrupts the openness of the front gardens

23/1831/HOT

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

D4Teddington Station
27 times cited
D12Teddington School
27 times cited
HC1
2 times cited
D6The Causeway, Teddington
1 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

Where this officer's caseload concentrates, 2023–24.[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
23/3340/HOT
Householder Application
Refused
2024-04-25
23/1284/HOT
Householder Application
Approved
2024-04-15
23/3340/HOT
Householder Application
Refused
2024-04-25
23/1284/HOT
Householder Application
Approved
2024-04-15
Full application history locked
Subscribe to see all 32 decisions →
Consultants approved most— subscriber data
1. JUTTLAND SURVEYORS LTD
At a glance
OfficerRamasankaran Rajendran
RolePlanning officer
Experience
Applications32 (2023–24)
Approval rate76%
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, 2023–24. · 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 50 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.