Gloucestershire

Cheltenham planning data

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

6,751

Applications

Enforcement notices

274

Appeals

2003–2026

Date range

What Cheltenham decides

Cheltenham has approved 94.44% of the 4,244 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 at or above the middle of the pack (89.18%).

94.44%

Approved, of 4,244 decided

Median days to a decision

53.9

Average days

What it mostly decides

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

Application type	Applications	Share
Full	2,844	42.1%
Other	1,271	18.8%
Listed building	712	10.5%
Conditions	594	8.8%
Amendment	428	6.3%

How approval rates and decision times vary across the country →

What Cheltenham 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 Cheltenham actually provides each one, across all 6,751 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 Cheltenham 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,751	100.0%
Applicant's name `applicant_name`	6,751	100.0%
Application type `application_type`	6,751	100.0%
Who decided it (officer or committee) `decision_level`	6,751	100.0%
Description of the works `description`	6,751	100.0%
Council reference `reference`	6,751	100.0%
Ward `ward`	6,749	100.0%
Agent's email `agent_email`	6,736	99.8%
Case officer `case_officer`	6,734	99.7%
Status `status`	6,694	99.2%
Date received `received_date`	6,535	96.8%
Status (standardised wording) `status_normalized`	6,532	96.8%
Decision `decision`	6,530	96.7%
Decision date `decision_date`	6,530	96.7%
Decision (standardised wording) `decision_normalized`	6,511	96.4%
Agent's phone `agent_phone`	6,299	93.3%
Postcode `postcode`	6,160	91.2%

Partial — use with care

Information	Records with it	Coverage
Alternative reference `alternative_reference`	5,446	80.7%
Agent's name `agent_name`	5,233	77.5%
Agent's company `agent_company`	5,165	76.5%
Standardised type `standard_type`	2,223	32.9%

Rarely or never published

Information	Records with it	Coverage
Appeal decision `appeal_decision`	0	0.0%
Appeal decision (standardised wording) `appeal_decision_normalized`	0	0.0%
Type of development `development_type`	0	0.0%
Officer's recommendation `officer_recommendation`	0	0.0%

Not published by this council

Cheltenham'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 Cheltenham 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=200&limit=5"

Council id for Cheltenham is 200. Full API reference for developers →

Get free access to Cheltenham data

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