Developer · London
B.T. PLC..
A developer bringing schemes forward across London. Has 9 applications in 9 boroughs, at a 100% approval rate, 1996–03.[1] Where they build, and how, is below.
Developer9 boroughs100% 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 →9
Applications
London 1996–03
—
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.
Approval rate over time — improving or slippingtheir London-wide rate by year
What they build — by scheme type
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
Where this developer builds, 1996–03.[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
Redbridge
Full Planning Permission
Approved
2003-10-16
Hammersmith And Fulham
Full Planning Application
Approved
2001-08-31
Hammersmith And Fulham
Full Planning Application
—
2001-07-03
Hammersmith And Fulham
Full Planning Application
Approved
2000-06-23
Harrow
Prior Telecommunications Notice
Refused
1999-07-20
Merton
Full Planning Permission
Approved
1997-11-06
Harrow
Prior Telecommunications Notice
Not required
1997-09-04
Harrow
Prior Telecommunications Notice
Not required
1996-03-19
Tower Hamlets
Cert. of Law. Proposed Dev. (TCPA S192)
Approved
1996-03-18
Redbridge
Full Planning Permission
Approved
2003-10-16
Hammersmith And Fulham
Full Planning Application
Approved
2001-08-31
Hammersmith And Fulham
Full Planning Application
—
2001-07-03
Show all 59 rows
Hammersmith And Fulham
Full Planning Application
Approved
2000-06-23
Harrow
Prior Telecommunications Notice
Refused
1999-07-20
Merton
Full Planning Permission
Approved
1997-11-06
Harrow
Prior Telecommunications Notice
Not required
1997-09-04
Harrow
Prior Telecommunications Notice
Not required
1996-03-19
Tower Hamlets
Cert. of Law. Proposed Dev. (TCPA S192)
Approved
1996-03-18
Consultants they instruct— subscriber data
At a glance
DeveloperB.T. PLC.
Coverage9 London boroughs
Applications9 (1996–03)
Units sought—
Approval rate100%
London rank#6191 of 16,342
Who decides here
Related investigations
Sources & method
- [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]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.