Berkshire

Reading planning data

6,201 planning applications from Reading. 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. 6 pieces of information are filled in on at least 90% of records.

6,201

Applications

Enforcement notices

456

Appeals

2022–2026

Date range

What Reading decides

Reading has approved 88.31% of the 3,525 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%).

88.31%

Approved, of 3,525 decided

Median days to a decision

95.7

Average days

What it mostly decides

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

Application type	Applications	Share
Householder	1,238	20.0%
Other	1,045	16.9%
Full	975	15.7%
Tree	797	12.9%
Conditions	763	12.3%

How approval rates and decision times vary across the country →

What Reading 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 Reading actually provides each one, across all 6,201 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 Reading 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`	6,200	100.0%
Application type `application_type`	6,199	100.0%
Council reference `reference`	6,201	100.0%
Status `status`	6,201	100.0%
Ward `ward`	6,186	99.8%
Status (standardised wording) `status_normalized`	6,185	99.7%

Partial — use with care

Information	Records with it	Coverage
Case officer `case_officer`	5,446	87.8%
Who decided it (officer or committee) `decision_level`	5,446	87.8%
Description of the works `description`	5,447	87.8%
Date received `received_date`	5,444	87.8%
Applicant's name `applicant_name`	5,367	86.6%
Decision date `decision_date`	5,121	82.6%
Standardised type `standard_type`	5,004	80.7%
Decision `decision`	4,998	80.6%
Alternative reference `alternative_reference`	4,804	77.5%
Decision (standardised wording) `decision_normalized`	4,523	72.9%
Agent's name `agent_name`	4,398	70.9%
Postcode `postcode`	3,848	62.1%

Rarely or never published

Information	Records with it	Coverage
Appeal decision (standardised wording) `appeal_decision_normalized`	0	0.0%

Not published by this council

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

Agent's company Agent's email Agent's phone Appeal decision Type of development Map coordinates (easting) Map coordinates (northing) Officer's recommendation

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 Reading 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=378&limit=5"

Council id for Reading is 378. Full API reference for developers →

Get free access to Reading data

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