Development Intent
AtlasEnfieldOfficersJeremiah Ayerh
Case officer · Enfield Planning

Jeremiah Ayerh.

Active — last recorded decision May 2026

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

Planning officer606 decisions74% approvalSave
Enfield · 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 →
606
Applications
2021–26
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%72%202373%202474%202579%2026
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate74% · 29th of 63
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 reports163 officer reports parsed
16%
Approves despite concerns
of approvals record a documented reservation
3%
Negotiated approvals
approvals mentioning revisions/amendments
2%
"On balance" reports
reports using explicit balancing language
74%
Bespoke reasoning
of report text written for the case, not recited
What they write about — vs Enfield's average officer

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

Flooding & drainage
1.92× borough avg
Bulk & massing
1.64× borough avg
Precedent & consistency
1.46× borough avg
Daylight & sunlight
1.33× borough avg
Character & heritage
1.16× borough avg

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

How they reason — coded from their reports

Ayerh writes checklist-narrative reports and is a consistent precedent-comparator: for schemes that exceed DMD11's 3m depth guideline he does not simply cite it as a bright-line failure but names two or three specific comparator addresses on the same street with similarly larger extensions, using 'when viewed within the wider context' as his recurring framing before concluding no harm.

Observable habits

· names two or three specific comparator addresses with similarly non-compliant extension depths as evidence the wider street context makes a scheme acceptable, using the phrase 'when viewed within the wider context'

· checks BOTH the ground-floor 45-degree line and separate depth criteria for each affected neighbour individually within the same report

· for crossover/hardstanding applications, runs an explicit Google Maps Street search as evidence of existing parking demand before concluding on highway-safety objections

What their reports consistently look for

· what this officer's reports consistently look for: two or three specific comparator addresses on the same street with similarly larger extensions, used to justify a DMD11 depth exceedance 'within the wider context'

· what this officer's reports consistently look for: the 45-degree line and the depth criterion checked separately for EACH affected neighbour, not a single blended conclusion

· what this officer's reports consistently look for: an explicit Google Maps Street search of existing parking demand before drawing a highway-safety conclusion on a crossover application

Assigned Jeremiah Ayerh 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

The proposed rear extension would exceed the depth requirement listed within Policy DMD 11 where it states that rear extensions should not exceed 3m in depth beyond the original rear wall in the case of terraced and semidetached properties. However, when viewed within the wider context there are similar larger rear extensions seen at Nos. 54, 103 Kingsfield Drive given the existing examples seen in existence within the vicinity of the area, the proposed single storey wrap around extension would not result in harm caused to the character of the area

23/03522/HOU

Upon further assessment, from carrying out a Google Maps Street search, there currently appears of be a high demand for off street parking with many vehicles utilizing the off-street parking-controlled parking zones, seen along Vicars Moor Lane

23/03787/FUL

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

DMD 6
47 times cited
DMD 37
44 times cited
DMD 59
11 times cited
DMD 61
10 times cited
DMD 45
4 times cited
DMD 13
4 times cited
DMD 14
3 times cited
DMD 8
2 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

Where this officer's caseload concentrates, 2021–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/01234/HOU
Householder
Approved
2026-06-09
26/01168/FUL
Full
Refused
2026-06-09
26/01234/HOU
Householder
Approved
2026-06-09
26/01168/FUL
Full
Refused
2026-06-09
Full application history locked
Subscribe to see all 606 decisions →
Consultants approved most— subscriber data
1. ERK STRUCTURAL & DESIGN CONSULTANCY
2. Town & Country Planning Limited
3. ELA Design
4. John Perrin & Sons Ltd
At a glance
OfficerJeremiah Ayerh
BoroughEnfield
RolePlanning officer
Experience
Applications606 (2021–26)
Approval rate74%
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 Enfield planning register and published decision notices, 2021–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 Enfield 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 163 published Enfield 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.