Development Intent
AtlasWestminsterOfficersTristan Goldsmid
Case officer · Westminster Planning

Tristan Goldsmid.

Active — last recorded decision May 2026

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

Planning officer320 decisions85% 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 →
320
Applications
2022–26
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%83%202283%202386%202493%202580%2026
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate85% · 55th 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 reports278 officer reports parsed
14%
Approves despite concerns
of approvals record a documented reservation
9%
Negotiated approvals
approvals mentioning revisions/amendments
9%
"On balance" reports
reports using explicit balancing language
83%
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.

Privacy & overlooking
1.76× borough avg
Energy & sustainability
1.59× borough avg
Outlook & amenity
1.48× borough avg
Transport & parking
1.31× borough avg
Bulk & massing
1.26× borough avg

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

How they reason — coded from their reports

Goldsmid's caseload (2022-era, under the newer numbered City Plan) spans Mayfair office-rooftop terraces and residential unit amalgamation/loss cases. On rooftop terrace extensions he treats already-lawful larger terraces at other levels of the same building as setting the reasonable envelope for hours and scale of a new terrace, rather than assessing each addition against a blank amenity standard. On residential unit loss (amalgamating two flats into one) he applies the City Plan's family-housing exception test precisely — checking whether the RESULTING unit is family-sized and whether either INPUT unit already was, rather than treating any net unit-count reduction as automatically unacceptable. He is willing to refuse on fire safety and amenity where an unauthorised, retrospective use has an established history of enforcement action for the same or related breaches.

Observable habits

· treats an already-lawful, larger terrace/use elsewhere in the same building as setting the reasonable envelope (hours, scale) for assessing a new addition, rather than a blank-standard test

· on residential unit amalgamation, applies the City Plan's family-housing exception precisely: checks whether the resulting unit is family-sized AND whether either input unit already was, rather than treating any net loss as automatically unacceptable

· credits design changes made following the Design Officer's specific comments (dormer changed to mansard) and notes when supporting technical assessments (daylight/sunlight) have or haven't been updated to match the revised scheme

· on retrospective/unauthorised uses, checks the property's specific enforcement history for related prior breaches before assessing the current application on its own terms

What their reports consistently look for

· what this officer's reports consistently look for: what terraces/uses are ALREADY lawful elsewhere in the same building, to set the reasonable envelope for a new addition

· what this officer's reports consistently look for: whether the resulting unit from an amalgamation is family-sized and whether either input unit already was, under the specific policy exception test

· what this officer's reports consistently look for: a property's specific enforcement history for related prior breaches before assessing a retrospective application

Assigned Tristan Goldsmid 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

Neither of the previous applications for terraces (16/10066/FULL and 18/02732/FULL) restricted the hours of use of these terraces and, considering these pre-existing lawful terraces, it is not considered reasonable to restrict the hours of the terraces in this case.

22/01069/FULL

Neither of the units being reconfigured are family sized units so the proposals would be considered acceptable in principle under Policy 8 part C2.

22/01198/FULL

Under the enforcement case 20/73762/U, an Enforcement Notice was served requiring the cease of use of part of the car park as a delivery hub for the storage, collection and return of mopeds for hot food delivery

22/01715/FULL

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

T5
8 times cited
D6
3 times cited
MD2
2 times cited
MD4
2 times cited
MD1
2 times cited
S33
2 times cited
D12
1 times cited
D11
1 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

Where this officer's caseload concentrates, 2022–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
25/09350/FULL
Full Planning Permission Application
Approved
2026-06-04
26/00173/FULL
Full Planning Permission Application
Approved
2026-05-28
25/09350/FULL
Full Planning Permission Application
Approved
2026-06-04
26/00173/FULL
Full Planning Permission Application
Approved
2026-05-28
Full application history locked
Subscribe to see all 320 decisions →
Consultants approved most— subscriber data
1. Gerald Eve
2. Rolfe Judd Planning
3. Howard De Walden Estate
4. Studio80six Ltd
At a glance
OfficerTristan Goldsmid
RolePlanning officer
Experience
Applications320 (2022–26)
Approval rate85%
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, 2022–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 278 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.