Planning Atlas
Planning AtlasWaltham ForestForest ward261139
Planning application · Waltham Forest

261139.

ARCH 171A Midland Road, Leyton, London, E10 9JT

Full / Other Planning at ARCH 171A Midland Road, Leyton, London, E10 9JT, received 11 May 2026 — consultation/publicity.

Waltham ForestForestE10 9JT261139
ApprovedRefusedOther
At a glance · this applicationWaltham Forest profile →
Consultation/Publicity
Outcome
no decision date
Decision time
submission → decision
Conditions
not captured
11
Documents
11 linked
Objections
not captured
No
Appeal
none recorded
Record from the Waltham Forest planning register as captured; documents link to the council's own files. Nearby applications are context, not part of this application.
Application

What is it?

Internal works including the removal of a partition to facilitate the amalgamation of Arches 171a and 171b into a single commercial unit (Use Class B8). Works include removal of the existing blockwork with timber infills and installation of replacement brick infill incorporating curved fixed glazing

Reference
261139
Type
Full Planning
Applicant
Agent / consultant
Postcode
E10 9JT
Ward
Received
11 May 2026
Validated
2 Jun 2026
Target date
28 Jul 2026
Decision date
Decision route
Delegated (officer)
Status
Consultation/Publicity
Reference
261139
Type
Full Planning
Show all 16 rows
Applicant
Agent / consultant
Postcode
E10 9JT
Ward
Received
11 May 2026
Validated
2 Jun 2026
Target date
28 Jul 2026
Decision date
Decision route
Delegated (officer)
Status
Consultation/Publicity
Documents

What was filed?

Document
Published
View
19May2026-171A-B-Midland-Rd-Design-and-Access-Statement-v_4.
5 Jun 2026
19May2026-171A-B-Midland-Rd-Reasonable-Exception-Statement-v
5 Jun 2026
19May2026-171-A-B-Midland-Rd-Planning-Statement-1.pdf
5 Jun 2026
122511-154-Travel-Distance-Plan-Arches-171a-and-171b-Midland
5 Jun 2026
122511-154-Site-Plan-Arches-171a-and-171b-Midland-road-Londo
5 Jun 2026
122511-154-Proposed-Floor-Plans-Arches-171a-and-171b-Midland
5 Jun 2026
122511-154-Proposed-Elevations-and-Sections-Arches-171a-and-
5 Jun 2026
122511-154-Location-Plan-Arches-171a-and-171b-Midland-road-L
5 Jun 2026
122511-154-Existing-Floor-Plans-Arches-171a-and-171b-Midland
5 Jun 2026
122511-154-Existing-Elevations-Arches-171a-and-171b-Midland-
5 Jun 2026
19May2026-171A-B-Midland-Rd-Design-and-Access-Statement-v_4.
5 Jun 2026
19May2026-171A-B-Midland-Rd-Reasonable-Exception-Statement-v
5 Jun 2026
19May2026-171-A-B-Midland-Rd-Planning-Statement-1.pdf
5 Jun 2026
Show all 10 rows
122511-154-Travel-Distance-Plan-Arches-171a-and-171b-Midland
5 Jun 2026
122511-154-Site-Plan-Arches-171a-and-171b-Midland-road-Londo
5 Jun 2026
122511-154-Proposed-Floor-Plans-Arches-171a-and-171b-Midland
5 Jun 2026
122511-154-Proposed-Elevations-and-Sections-Arches-171a-and-
5 Jun 2026
122511-154-Location-Plan-Arches-171a-and-171b-Midland-road-L
5 Jun 2026
122511-154-Existing-Floor-Plans-Arches-171a-and-171b-Midland
5 Jun 2026
122511-154-Existing-Elevations-Arches-171a-and-171b-Midland-
5 Jun 2026

Documents open on the Waltham Forest portal. View the application page ↗

Decision

What happened?

Status: Consultation/Publicity. No decision is recorded yet.

Timeline

Date
Event
11 May 2026
Application received
2 Jun 2026
Application validated
28 Jul 2026
Statutory target date
11 May 2026
Application received
2 Jun 2026
Application validated
28 Jul 2026
Statutory target date

Public response

Comment counts were not captured for this application.

People

Who is involved?

Name
Role
Applicant — the party who applied, not necessarily the owner
Agent · consultant profile
Case officer — delegated decision
Applicant — the party who applied, not necessarily the owner
Agent · consultant profile
Case officer — delegated decision
Place

What affects it?

Context around the site — not part of this application. Designations over the site: use the map's designations filter (conservation areas, listed buildings, Article 4, flood risk …). Decisions within 250 metres of the site are listed below — context, not this application.

Other applications within 250 metres (context — nearby, not this application)

No other geocoded decision is recorded within 250 metres.