Alice Murphy.
Active — last recorded decision May 2026
A case officer at Richmond Upon Thames with an approval rate of 79% across 803 decided planning applications, spanning 30 wards.[1] Decision speed and appeal performance publish when decision notices are ingested.
Topic mentions per 1,000 words of their own report text (boilerplate stripped), indexed against all parsed Richmond Upon Thames reports. Attention, not stance.
Mark = borough average (1×). Bar capped at 2×.
Murphy's reports are dominated by dense, numeric physical descriptions of the proposed works (exact depths, eaves heights, ridge heights, widths in metres) for garden extensions, dormers, garages and outbuildings, most under the [Professional comments] heading, with the conclusion on design compliance with LP1 and the House Extensions and External Alterations SPD following directly from those measurements. Neighbour amenity, where addressed, is folded into the same paragraph rather than given its own heading in most reports.
· opens with a bare list of the proposal's physical dimensions (depth, width, eaves height, maximum height) before making any design judgement
· checks a new extension's dimensions and roof form against a specific SPD clause (e.g. depth-related privacy/overlooking thresholds, or Permitted Development Class A/C limits) and states compliance line by line
· cites specific comparator permissions/appeals at neighbouring addresses (e.g. an adjoining semi-detached pair's approved extension) to justify consistency of scale
· what this officer's reports consistently look for: precise dimensions of the proposed extension or structure (depth, width, eaves height, maximum height) stated before any design conclusion
· what this officer's reports consistently look for: whether proposed materials (brickwork, render, tiles/slate) match or harmonise with the existing dwelling
· what this officer's reports consistently look for: a specific SPD threshold (e.g. 2m/3.5m extension depth, dormer set-in from eaves/ridge) that the scheme is measured against
“The applicant proposes a single storey side infill extension which would project 2m from the existing side of the outrigger to the northern property boundary. The eaves height will be 2.82m at the boundary for a depth of 5.6m and the maximum height is 3.8m where the roof of the extension meets the outrigger.”
19/3721/HOT
“The 2.25m boundary treatment for a depth of 3.5m is proposed to mitigate potential overlooking between properties as the proposed raised platform is on the boundary between no.436 and the subject site. This will ensure the privacy of adjoining occupants is safeguarded.”
19/3773/HOT
“The dormer extension will be set in 750mm from the eaves, 450mm from the ridge. Therefore, the dormer is not considered to dominate the existing roof.”
20/0049/FUL
Measured from 741 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.
The policies this officer cites most in their own reports — times cited across 741 parsed reports. Whether refusals citing each survive appeal isn't traced per policy yet.
Show all 30 rows
Where this officer's caseload concentrates, 2020–26.[1] Click the map above to focus this page on a ward, or a row to open the ward.
- [1]Applications decided, approval rate, per-year trend and ward breakdown — London Borough of Richmond Upon Thames planning register and published decision notices, 2020–26. · methodology
- [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]Condition load — Richmond Upon Thames's decision-notice parsing is limited coverage, so no borough or officer figure is shown.
- [4]"How this officer decides", the policy playbook and all quotes — parsed from 741 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.