Development Intent
AtlasMertonOfficersSarah Muckian
Case officer · Merton Planning

Sarah Muckian.

Active — last recorded decision May 2026

A case officer at Merton with an approval rate of 80% across 545 decided planning applications, spanning 34 wards.[1] Decision speed and appeal performance publish when decision notices are ingested.

Planning officer545 decisions80% approvalSave
Merton · 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 →
545
Applications
2021–26
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%89%202183%202277%202375%202480%202591%2026
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate80% · 12th of 17
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 reports387 officer reports parsed
13%
Approves despite concerns
of approvals record a documented reservation
14%
Negotiated approvals
approvals mentioning revisions/amendments
2%
"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 Merton's average officer

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

Flooding & drainage
1.43× borough avg
Energy & sustainability
1.35× borough avg
Precedent & consistency
1.23× borough avg
Transport & parking
0.98× borough avg
Bulk & massing
0.95× borough avg

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

How they reason — coded from their reports

Muckian's caseload is dominated by rear/side extensions, dormers and prior-approval applications, and she is unusually explicit about naming EACH affected neighbouring property by house number and address in its own dedicated sub-paragraph before reaching a verdict on that specific relationship, rather than a single combined amenity paragraph. Her refusals — a comparatively high share of this volume group — concentrate on cases where an extension would be 'entirely visible' from a neighbour with no existing comparable structure and would exceed half the depth of that neighbour's own garden, a specific proportionality test she applies repeatedly across GPDO prior-approval refusals.

Observable habits

· addresses each affected neighbouring property in its OWN named sub-paragraph (by street address, not just house number), reaching a separate mini-verdict for each before an overall conclusion

· on refusals, applies a specific proportionality test — whether the extension would exceed roughly half the depth of the affected neighbour's own garden — as the recurring metric for 'considerable loss of sunlight, overshadowing and increased sense of enclosure'

· distinguishes cases where a neighbour already has an EXISTING comparable extension (impact judged as incremental) from cases where the extension would be 'entirety... visible' with no existing mitigating structure

What their reports consistently look for

· whether each specific named neighbour already has an existing extension of comparable depth, or would see the whole of the new extension for the first time

· the proportion of the affected neighbour's own garden depth that the extension would occupy

· whether setback/side-access provisions available at the specific site reduce an otherwise-harmful impact

Assigned Sarah Muckian 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 northern-facing and relatively short gardens of these terrace dwellings, it is considered that the extension would result in a considerable loss of sunlight, overshadowing and increased sense of enclosure toward the rear of the neighbouring properties

21/P3999

It would be particularly overbearing to the northern neighbour at no.22 whose garden tapers inwards and is significantly smaller than the adjacent application sites'. It is considered that no.22 would experience negative harm given the extension would exceed half the length of their rear garden

21/P4371

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

D3List of Buildings of Special Architectural or Historic Interest
202 times cited
D4
199 times cited
DM D2
198 times cited
CS14Design. Strategic
195 times cited
DM D3
167 times cited
D1Conservation Areas Designation
59 times cited
DM T3
59 times cited
CS20Parking, Servicing and Delivery. Strategic
58 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward
Ward
Decisions
Approval rate

Where this officer's caseload concentrates, 2021–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
26/P0131
Householder
Approved
2026-06-04
26/HOUSE/0417
Householder
Approved
2026-06-04
26/P0131
Householder
Approved
2026-06-04
26/HOUSE/0417
Householder
Approved
2026-06-04
Full application history locked
Subscribe to see all 545 decisions →
Consultants approved most— subscriber data
1. Planning Additions
2. Revive Renovations Ltd
3. Resi Design Ltd
4. GBS Architectural Ltd
At a glance
OfficerSarah Muckian
BoroughMerton
RolePlanning officer
Experience
Applications545 (2021–26)
Approval rate80%
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 Merton planning register and published decision notices, 2021–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 — Merton'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 387 published Merton 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.