Development Intent
AtlasWestminsterOfficersMatthew Mason
Case officer · Westminster Planning

Matthew Mason.

Active — last recorded decision May 2026

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

Planning officer81 decisions99% approvalSave
Westminster · 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 →
81
Applications
2020–26
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%100%2020100%2021100%2022100%202393%2024100%2025100%2026
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate99% · 4th of 76
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 reports44 officer reports parsed
14%
Approves despite concerns
of approvals record a documented reservation
22%
Negotiated approvals
approvals mentioning revisions/amendments
2%
"On balance" reports
reports using explicit balancing language
94%
Bespoke reasoning
of report text written for the case, not recited
What they write about — vs Westminster's average officer

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

Energy & sustainability
3.8× borough avg
Transport & parking
2.5× borough avg
Daylight & sunlight
1.87× borough avg
Precedent & consistency
1.59× borough avg
Trees & landscape
1.27× borough avg

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

How they reason — coded from their reports

Mason's caseload includes numerous discrete infrastructure DCO-requirement discharge applications (Thames Tideway) where he cross-references a specific numbered Schedule requirement against a named consultee (HBMCE, Environment Agency, PLA) to confirm each discrete element (landscaping, drainage, river wall design) meets its own approval condition. He explains a design constraint (tree-planting spacing) by reference to an unrelated future operational need (crane access every 10 years for maintenance) rather than assuming an aesthetic-only reason.

Observable habits

· cross-references a specific numbered Schedule/DCO requirement against the relevant named consultee (HBMCE, Environment Agency, PLA, TfL) to confirm each discrete element independently meets its own condition

· explains an apparent design constraint (tree-planting spacing) by reference to an unrelated future operational necessity (recurring maintenance crane access) rather than an aesthetic-only reason

· notes where a stakeholder not formally a statutory consultee (the Port of London Authority) nonetheless requested specific additional detail (more ladders) that has since been incorporated by agreement

What their reports consistently look for

· what this officer's reports consistently look for: whether each discrete DCO Schedule requirement is independently confirmed acceptable by its own named relevant consultee

· what this officer's reports consistently look for: whether an apparent design constraint has an unrelated operational explanation (future maintenance access) rather than being purely aesthetic

· what this officer's reports consistently look for: whether a non-statutory stakeholder's specific request has been incorporated into the design by subsequent agreement

Assigned Matthew Mason 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

it is likely that spacing is dictated by the ten year maintenance plan of the dropshaft which will require full crane access every 10 years

20/00762/ADTTT

the PLA requested more ladders than shown in the approved application. The applicant advises that the ladder location and berth furniture such as the addition of a lifebuoy has now been agreed with the PLA

20/06611/ADTTT

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

PIM 2
1 times cited
PIM 3
1 times cited
PIM 4
1 times cited
PIM 10
1 times cited
T4
1 times cited
D12
1 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

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.

Recent applications
Address
Reference
Type
Outcome
Date
26/03208/FULL
Full Planning Permission Application
2026-05-14
26/02814/FULL
Full Planning Permission Application
2026-04-28
26/03208/FULL
Full Planning Permission Application
2026-05-14
26/02814/FULL
Full Planning Permission Application
2026-04-28
Full application history locked
Subscribe to see all 81 decisions →
Consultants approved most— subscriber data
1. Gerald Eve LLP
2. Ferrovial Agroman Laing O'Rourke Joint Venture (FLo)
3. DP9 Ltd
4. Turley
At a glance
OfficerMatthew Mason
RolePlanning officer
Experience
Applications81 (2020–26)
Approval rate99%
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 Westminster planning register and published decision notices, 2020–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 — mean effective conditions attached to Westminster decision notices (grant/split), parsed from the published notice text; a borough figure, not yet split per case officer.
  4. [4]"How this officer decides", the policy playbook and all quotes — parsed from 44 published Westminster 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.