Planning Atlas
AtlasDevelopersFletcher S Earthmen Ltd
Planning AtlasDevelopersFletcher's Earthmen Ltd
Developer · London

Fletcher's Earthmen Ltd.

A developer bringing schemes forward across London. Has 3 applications in 5 boroughs, at a approval rate, 2000–01.[1] Where they build, and how, is below.

Developer5 boroughs 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 →
3
Applications
London 2000–01
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%’00’01
What they build — by scheme type
3decisions

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
20
69%
5
100%
2
Show all 5 rows

Where this developer builds, 2000–01.[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
Enfield
Works to a tree in a Conservation Area
2001-12-06
Enfield
Works to a tree in a Conservation Area
2001-11-06
Westminster
Applic. for works to trees in CA
No objection
2001-10-16
Enfield
Works to a tree in a Conservation Area
Approved
2001-07-17
Barnet
Trees: Works to TPO
Approved
2001-06-18
Barnet
Tree works
Approved
2001-06-18
Westminster
Applic. for wks to trees subject to TPO
No objection
2001-05-01
Barnet
Trees: Works to TPO
Approved
2001-03-01
Barnet
Tree works
Approved
2001-03-01
Barnet
Trees: Works to TPO
Approved
2001-02-22
Barnet
Tree works
Approved
2001-02-22
Barnet
Tree works
Refused
2001-01-23
Barnet
Trees: Works to TPO
Refused
2001-01-23
Barnet
Trees: Works to TPO
Withdrawn
2001-01-22
Enfield
Works to a tree in a Conservation Area
Approved
2001-01-18
Wandsworth
Works to a T.P.O. Tree
Approved
2000-12-20
Wandsworth
Work to trees in conservation area
Approved
2000-12-18
Barnet
Trees: Works to TPO
Refused
2000-12-08
Barnet
Tree works
Refused
2000-12-08
Barnet
Trees: Works to TPO
Approved
2000-07-19
Barnet
Tree works
Approved
2000-07-19
Barnet
Tree works
Not required
2000-04-26
Barnet
Notice of intent
Not required
2000-04-26
Barnet
Notice of intent
Other
2000-04-19
Barnet
Tree works
Other
2000-04-19
Enfield
Works to a tree in a Conservation Area
Approved
2000-04-05
Camden
Notification of Intended Works to Tree(s) in a Conservation Area
No objection
2000-02-25
Camden
Application for Works to Tree(s) covered by a TPO
Withdrawn
2000-02-25
Enfield
Works to a tree in a Conservation Area
2001-12-06
Enfield
Works to a tree in a Conservation Area
2001-11-06
Westminster
Applic. for works to trees in CA
No objection
2001-10-16
Show all 31 rows
Enfield
Works to a tree in a Conservation Area
Approved
2001-07-17
Barnet
Trees: Works to TPO
Approved
2001-06-18
Barnet
Tree works
Approved
2001-06-18
Westminster
Applic. for wks to trees subject to TPO
No objection
2001-05-01
Barnet
Trees: Works to TPO
Approved
2001-03-01
Barnet
Tree works
Approved
2001-03-01
Barnet
Trees: Works to TPO
Approved
2001-02-22
Barnet
Tree works
Approved
2001-02-22
Barnet
Tree works
Refused
2001-01-23
Barnet
Trees: Works to TPO
Refused
2001-01-23
Barnet
Trees: Works to TPO
Withdrawn
2001-01-22
Enfield
Works to a tree in a Conservation Area
Approved
2001-01-18
Wandsworth
Works to a T.P.O. Tree
Approved
2000-12-20
Wandsworth
Work to trees in conservation area
Approved
2000-12-18
Barnet
Trees: Works to TPO
Refused
2000-12-08
Barnet
Tree works
Refused
2000-12-08
Barnet
Trees: Works to TPO
Approved
2000-07-19
Barnet
Tree works
Approved
2000-07-19
Barnet
Tree works
Not required
2000-04-26
Barnet
Notice of intent
Not required
2000-04-26
Barnet
Notice of intent
Other
2000-04-19
Barnet
Tree works
Other
2000-04-19
Enfield
Works to a tree in a Conservation Area
Approved
2000-04-05
Camden
Notification of Intended Works to Tree(s) in a Conservation Area
No objection
2000-02-25
Camden
Application for Works to Tree(s) covered by a TPO
Withdrawn
2000-02-25
Consultants they instruct— subscriber data
At a glance
DeveloperFletcher's Earthmen Ltd
Coverage5 London boroughs
Applications3 (2000–01)
Units sought
Approval rate
London rank#12084 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.