Planning Atlas
AtlasDevelopersShell Pensions Trust Ltd
Planning AtlasDevelopersShell Pensions Trust Limited
Developer · London

Shell Pensions Trust Limited.

A developer bringing schemes forward across London. Has 7 applications in 4 boroughs, at a 86% approval rate, 2001–19.[1] Where they build, and how, is below.

Developer4 boroughs86% approval
Where they build — by borough · tap to focus
FewerMore applications
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 →
7
Applications
London 2001–19
Avg S106 / unit
awaits s106 ingestion
Why a developer? Listed as a developer because every application we hold for them names them as the applicant.Something not right? Claim · Correct · Merge
Is this your developer?This profile is built from public planning records. Claim it to add your intro, logo and project images.
Claim this profile →
Approval rate over time — improving or slippingtheir London-wide rate by year
60%80%100%’01’02’03’04’09’19
What they build — by scheme type
8decisions

Click a slice to reshade the London map by that type.

Their planning record — policies in play

The policies most in play across this developer's schemes — how often each appears, and how often a scheme citing it wins consent.

Policies are coded from each officer report and decision notice — this table publishes when decision-notice ingestion lands. No policy record is shown until it's real.
Case officers — win rate when this developer submits

How often each named case officer grants consent on this developer's schemes. Pairing patterns from the public register — not endorsements.

The officer↔developer pairing isn't joined in the data layer yet — this table publishes when it is. Each borough's officers are already ranked in Track Records.
Applications by borough
Borough
Applications
Approval rate
2
100%
Show all 4 rows
1
100%

Where this developer builds, 2001–19.[1] Click the map above to explore spatially, or a row to open the borough.

Outcomes secured — S106 by borough
S106 outcomes per unit aren't traced per developer yet — the borough-by-borough table publishes when the section 106 agreements and committee reports are ingested against this developer's consents.
Recent applications
Address
Borough
Type
Outcome
Date
Croydon
Discharge of Conditions
Approved
2019-06
Westminster
Full Planning Permission Application
Approved
2009-05-28
City Of London
Full Planning Permission
Approved
2004-10-14
Barnet
Full Application
Approved
2003-09-29
Westminster
Full Planning Permission Application
Approved
2002-12-12
Westminster
Full Planning Permission Application
Refused
2002-04-26
Westminster
Full Planning Permission Application
Approved
2001-01-03
Croydon
Discharge of Conditions
Approved
2019-06
Westminster
Full Planning Permission Application
Approved
2009-05-28
City Of London
Full Planning Permission
Approved
2004-10-14
Show all 8 rows
Barnet
Full Application
Approved
2003-09-29
Westminster
Full Planning Permission Application
Approved
2002-12-12
Westminster
Full Planning Permission Application
Refused
2002-04-26
Westminster
Full Planning Permission Application
Approved
2001-01-03
Consultants they instruct— subscriber data
At a glance
DeveloperShell Pensions Trust Limited
Coverage4 London boroughs
Applications7 (2001–19)
Units sought
Approval rate86%
London rank#6957 of 16,342
Related investigations
How every developer ranks →
Approval rate, units sought and borough coverage across London developers, consultants, officers and inspectors.
Refusal Hotspots — where it's hard →
The wards and boroughs where applications die — and the ones that wave almost everything through.
Sources & method
  1. [1]Applications, approval rate, borough breakdown and units — the planning applications across London on which this company is the named applicant, from borough planning registers. Individual householders are excluded. Units = residential units conservatively parsed from each proposal (sought, not delivered); not every scheme states a count. · methodology
  2. [2]Agents — the named planning agent on each of this developer’s applications, joined to the London consultant record. · methodology
Methodology is published in full so every number is traceable to its primary source.