Development Intent
AtlasHarrowOfficersDeborah Ewenla
Case officer · Harrow Planning

Deborah Ewenla.

Last recorded decision Aug 2024 — no decisions in this record since

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

Planning officer28 decisions63% approvalSave
Harrow · 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 →
28
Applications
2023–24
Approval rate over time — tougher or softer 🔒Dashed line = London average

Not enough dated decisions for a trend yet.

What they decide — by application type
How they compareVersus peers
Approval rate63% · 55th of 72
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 reports164 officer reports parsed
0%
Approves despite concerns
of approvals record a documented reservation
0%
Negotiated approvals
approvals mentioning revisions/amendments
8%
"On balance" reports
reports using explicit balancing language
53%
Bespoke reasoning
of report text written for the case, not recited
What they write about — vs Harrow's average officer

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

Flooding & drainage
1.66× borough avg
Bulk & massing
1.29× borough avg
Privacy & overlooking
1.2× borough avg
Materials & detailing
1.1× borough avg
Trees & landscape
1.1× borough avg

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

How they reason — coded from their reports

Ewenla's corpus is dominated by prior-approval larger-home-extension applications and is notable for its consistent structure: 'Criterion D cites specific considerations of amenity' followed by an 'Impacts to Occupant/Neighbour amenities' section addressed strictly property-by-property with the exact rear-elevation projection distance for each named neighbour. She is one of the few officers to routinely flag when a submitted height has been measured from the wrong datum (patio level rather than natural ground level).

Observable habits

· addresses prior-approval amenity impacts strictly property-by-property under 'Impacts to Occupant/Neighbour amenities', citing the exact projection distance from each named neighbour's own rear elevation

· checks whether submitted height/eaves figures have been measured from the correct datum (natural ground level, not patio or raised deck level) and flags discrepancies explicitly

· for prior-approval schemes, states plainly whether the design 'meets the prior approval development requirements' as a discrete pass/fail sentence before any further discussion

What their reports consistently look for

· what this officer's reports consistently look for: whether submitted height/eaves measurements were taken from natural ground level rather than a raised patio or deck level

· what this officer's reports consistently look for: the exact rear-elevation projection distance from each named neighbouring property's own extension, not just the boundary distance

· what this officer's reports consistently look for: a discrete pass/fail statement on whether the prior-approval development requirements under the specific GPDO limitation are met before further discussion

Assigned Deborah Ewenla 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 fail to take into inconsideration the significant site level changes of the site, whereby the maximum height and eaves height have been taken from the patio level rather than the natural ground level

PL/1927/24

the 45 degree line would be breached, when taken from the window corner of this property

PL/1891/24

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

DM27Amenity Space
1 times cited
CS1
1 times cited
DM44Servicing
1 times cited
D3
1 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

Where this officer's caseload concentrates, 2023–24.[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
PL/1991/24
Householder
Approved
2024-09-12
PL/1937/24
Householder
Refused
2024-09-09
PL/1991/24
Householder
Approved
2024-09-12
PL/1937/24
Householder
Refused
2024-09-09
Full application history locked
Subscribe to see all 28 decisions →
Consultants approved most— subscriber data
1. Pawel Asif Development
2. Malathy Design
3. SSK Architects Ltd
4. Ideal Design Ltd
At a glance
OfficerDeborah Ewenla
BoroughHarrow
RolePlanning officer
Experience
Applications28 (2023–24)
Approval rate63%
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 Harrow planning register and published decision notices, 2023–24. · 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 Harrow 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 164 published Harrow 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.