Development Intent
AtlasRedbridgeOfficersSubash Jain
Case officer · Redbridge Planning

Subash Jain.

Active — last recorded decision May 2026

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

Planning officer75 decisions89% approvalSave
Redbridge · 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 →
75
Applications
2020–26
Approval rate over time — tougher or softer 🔒Dashed line = London average
avg 81%100%2020100%202189%202271%202391%202496%2025
Approval-rate trend is subscriber dataSubscribe to see the trend →
What they decide — by application type
How they compareVersus peers
Approval rate89% · 3rd of 32
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 reports56 officer reports parsed
0%
Approves despite concerns
of approvals record a documented reservation
9%
Negotiated approvals
approvals mentioning revisions/amendments
5%
"On balance" reports
reports using explicit balancing language
89%
Bespoke reasoning
of report text written for the case, not recited
What they write about — vs Redbridge's average officer

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

Daylight & sunlight
2.41× borough avg
Bulk & massing
1.91× borough avg
Materials & detailing
1.54× borough avg
Outlook & amenity
1.32× borough avg
Trees & landscape
1.24× borough avg

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

How they reason — coded from their reports

Jain's reports consistently use a distinctive possessive phrasing referring to 'its' depth, 'its' boundary and 'its' neighbours when describing the application site itself, and he works through GPDO gap-and-continuity questions (whether adjoining extensions with small gaps should be treated as one continuous enlargement) citing a named appeal decision on the point.

Observable habits

· uses a distinctive possessive construction ('its depth', 'its neighbour', 'its boundary') to describe the application site's own dimensions throughout

· addresses whether small gaps between adjoining extensions should be treated as one continuous enlargement, citing a named appeal decision on the same point

· compares a proposed extension's depth directly against a specific prior approval already granted at a named neighbouring address

What their reports consistently look for

· what this officer's reports consistently look for: whether a gap between adjoining extension elements is material enough to avoid the whole being treated as one continuous enlargement, tested against appeal precedent

· what this officer's reports consistently look for: a specific named neighbouring prior approval cited as the depth comparator

· what this officer's reports consistently look for: worked measurements described using the site's own dimensions ('its depth', 'its width') rather than a generic description

Assigned Subash Jain 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

Officers do not consider this gap to be of a material size and the proposed extension would therefore still effectively join to and project past a side elevation of the original dwellinghouse and have a width greater than half the width of the original dwellinghouse. This view is shared by a comparatively recent appeal decision from 3rd January 2024 (APP/N0410/X/23/3317280)

0854/25

The proposed single storey outrigger extension would in line with the 6 meters deep extension approved under prior approval determination (2511/24 on 4th October 2024 at 102, Highwood Gardens

1340/25

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

D12
11 times cited
LP26and LP27). This will enable a large
11 times cited
LP30Household Extensions
9 times cited
D3
8 times cited
LP29Amenity and Internal Space Standards
4 times cited
LP38Protecting Trees and Enhancing the Landscape
3 times cited
G7
2 times cited
HC1
2 times cited
Which policies this officer leans on is subscriber intelligenceSubscribe to unlock →
Decisions by ward

Where this officer's caseload concentrates, 2020–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
Full application history locked
Subscribe to see all 75 decisions →
Consultants approved most— subscriber data
1. Consulting Ltd
2. Design Ghar Limited
3. Scientific Design and Construction
4. Merritt Design Partnership Ltd.
At a glance
OfficerSubash Jain
BoroughRedbridge
RolePlanning officer
Experience
Applications75 (2020–26)
Approval rate89%
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 Redbridge planning register and published decision notices, 2020–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 Redbridge 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 56 published Redbridge 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.