Inner London

Tower Hamlets planning data

8,315 planning applications from Tower Hamlets. Ask questions about them in plain English from ChatGPT or Claude — no coding, about two minutes to set up — or pull them straight into your own software. 13 pieces of information are filled in on at least 90% of records.

8,315

Applications

Enforcement notices

1,259

Appeals

1986–2026

Date range

What Tower Hamlets decides

Tower Hamlets has approved 89.01% of the 7,270 applications it has decided since January 2023. Across the 225 councils with a comparable caseload the range is 71.37% to 99.14%, so this is below the middle of the pack (89.18%).

89.01%

Approved, of 7,270 decided

Decision times can't be measured here — Tower Hamlets doesn't publish both a received and a decision date on enough records. The nationwide range across councils that do is 31 to 299 days.

What it mostly decides

The mix of application types Tower Hamlets handles — useful for telling whether your kind of application is routine here or unusual.

Application type	Applications	Share
Full	2,787	33.5%
Conditions	1,891	22.7%
Other	1,383	16.6%
Amendment	681	8.2%
Listed building	635	7.6%

How approval rates and decision times vary across the country →

What Tower Hamlets actually fills in

A "field" is one piece of information on an application — the decision date, the applicant's name, the address. Councils fill these in inconsistently, so this table measures how often Tower Hamlets actually provides each one, across all 8,315 records. Anything listed as reliable you can count on; anything lower, check the council's own record before relying on it.

Once this data is connected to ChatGPT or Claude you can just ask "what information does Tower Hamlets actually fill in?" and get these same numbers back. How to connect →

Reliable — 90% or more of records

Information	Records with it	Coverage
Address `address`	8,315	100.0%
Description of the works `description`	8,315	100.0%
Council reference `reference`	8,315	100.0%
Application type `application_type`	8,306	99.9%
Case officer `case_officer`	8,301	99.8%
Applicant's name `applicant_name`	8,253	99.3%
Status `status`	8,245	99.2%
Status (standardised wording) `status_normalized`	8,245	99.2%
Who decided it (officer or committee) `decision_level`	8,229	99.0%
Ward `ward`	8,162	98.2%
Decision `decision`	7,762	93.3%
Decision date `decision_date`	7,762	93.3%
Decision (standardised wording) `decision_normalized`	7,697	92.6%

Partial — use with care

Information	Records with it	Coverage
Agent's name `agent_name`	6,639	79.8%
Postcode `postcode`	6,523	78.4%
Agent's company `agent_company`	6,337	76.2%
Standardised type `standard_type`	5,460	65.7%

Rarely or never published

Information	Records with it	Coverage
Appeal decision `appeal_decision`	185	2.2%
Appeal decision (standardised wording) `appeal_decision_normalized`	181	2.2%
Agent's email `agent_email`	58	0.7%
Alternative reference `alternative_reference`	6	0.1%
Agent's phone `agent_phone`	0	0.0%
Type of development `development_type`	0	0.0%
Officer's recommendation `officer_recommendation`	0	0.0%
Date received `received_date`	0	0.0%

Not published by this council

Tower Hamlets's portal has been verified not to publish these fields at all — different from a field that exists but is rarely filled in.

Map coordinates (easting) Map coordinates (northing)

Get this data

Ask it in ChatGPT or Claude

Connect it once with your email address, then ask questions like "which extensions were refused in Tower Hamlets last year?" or "what's the planning history of this address?" — no coding, about two minutes to set up. Setup guide →

Or call it from your own code

curl -H "X-Api-Key: pk_..." \
  "https://ukplanningapi.co.uk/v1/applications?council_id=120&limit=5"

Council id for Tower Hamlets is 120. Full API reference for developers →

Get free access to Tower Hamlets data

500 lookups a month, free. No card, no password — we email you a sign-in link and you're in.