Development Intent
AtlasRichmond Upon ThamesOfficersIzabela Moorhouse
Case officer · Richmond Upon Thames Planning

Izabela Moorhouse.

Recently active — last recorded decision Feb 2025

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

Planning officer423 decisions78% 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 →
423
Applications
2022–25
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%77%202277%202377%202479%2025
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate78% · 45th 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 reports419 officer reports parsed
12%
Approves despite concerns
of approvals record a documented reservation
8%
Negotiated approvals
approvals mentioning revisions/amendments
3%
"On balance" reports
reports using explicit balancing language
58%
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.

Precedent & consistency
1.53× borough avg
Character & heritage
1.12× borough avg
Noise & disturbance
1.12× borough avg
Materials & detailing
1.09× borough avg
Trees & landscape
1× borough avg

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

How they reason — coded from their reports

Moorhouse's reports move quickly through window-hierarchy and materials-matching detail for heritage/BTM and conservation-area properties, repeatedly checking whether replacement fenestration or extensions 'retain an acceptable window hierarchy' and match host-dwelling materials, and she names the specific comparator property on the same row (e.g. 'no. 74', 'no. 9') used to justify eaves height or depth.

Observable habits

· checks new or replacement windows/doors against the concept of an 'acceptable window hierarchy' relative to the rest of the host dwelling

· names a specific numbered neighbouring property on the same row that already has a matching extension/depth as the basis for finding no additional harm

· notes when submitted drawings fail to illustrate neighbouring context and flags missing information (e.g. bin capacity, glazing bar details) as points requiring further detail or conditions

What their reports consistently look for

· what this officer's reports consistently look for: whether new/replacement fenestration retains an acceptable window hierarchy matching the host dwelling

· what this officer's reports consistently look for: a specific numbered neighbouring property with an equivalent existing extension used as the precedent for 'no additional harm'

· what this officer's reports consistently look for: missing technical detail (glazing bar sections, bin/cycle capacity) that would need to be secured by condition

Assigned Izabela Moorhouse 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

Officers consider the reinstatement of the bay window to enhance the character of the property, with it noted that this would involve the reinstatement of an original feature.

22/0307/FUL

It is noted that No.10 benefits from a rear extension of the same depth as the proposed, which abuts the boundary. As such, no additional harm would arise.

22/0544/HOT 8 Rectory Road, Barnes, SW13 0DT Alterations to rear

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

D12Teddington School
79 times cited
D4Teddington Station
76 times cited
HC1
27 times cited
D3Teddington Library
8 times cited
D1Normansfield
7 times cited
T6.1
6 times cited
H2Sunnyside Reservoir, Lower Sunbury Road
5 times cited
D5Queens Road Clinic
5 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

Where this officer's caseload concentrates, 2022–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/3079/FUL
Full Application
Approved
2025-10-06
24/0793/FUL
Full Application
Approved
2025-08-18
24/3079/FUL
Full Application
Approved
2025-10-06
24/0793/FUL
Full Application
Approved
2025-08-18
Full application history locked
Subscribe to see all 423 decisions →
Consultants approved most— subscriber data
1. RLX HOMES
2. b3 cc limited
3. Chestnut Planning
4. Mrs Alex Leahy, Design Service
At a glance
OfficerIzabela Moorhouse
RolePlanning officer
Experience
Applications423 (2022–25)
Approval rate78%
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, 2022–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 419 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.