Gloucestershire
230 planning applications from Gloucestershire. 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. 15 pieces of information are filled in on at least 90% of records.
We hold only 230 applications here. Treat an absent record as "not published to us", never as "no such application".
Gloucestershire has approved 98.02% of the 101 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%).
The mix of application types Gloucestershire handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Other | 195 | 84.8% |
| Amendment | 21 | 9.1% |
| Certificate | 9 | 3.9% |
| Conditions | 5 | 2.2% |
How approval rates and decision times vary across the country →
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 Gloucestershire actually provides each one, across all 230 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 Gloucestershire actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
230 | 100.0% | |
Application typeapplication_type |
230 | 100.0% | |
Case officercase_officer |
230 | 100.0% | |
Date receivedreceived_date |
230 | 100.0% | |
Council referencereference |
230 | 100.0% | |
Description of the worksdescription |
229 | 99.6% | |
Statusstatus |
229 | 99.6% | |
Status (standardised wording)status_normalized |
229 | 99.6% | |
Applicant's nameapplicant_name |
227 | 98.7% | |
Agent's nameagent_name |
223 | 97.0% | |
Wardward |
220 | 95.7% | |
Agent's companyagent_company |
219 | 95.2% | |
Map coordinates (easting)easting |
210 | 91.3% | |
Map coordinates (northing)northing |
210 | 91.3% | |
Who decided it (officer or committee)decision_level |
208 | 90.4% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Decision datedecision_date |
176 | 76.5% | |
Decisiondecision |
175 | 76.1% | |
Standardised typestandard_type |
165 | 71.7% | |
Postcodepostcode |
161 | 70.0% | |
Decision (standardised wording)decision_normalized |
111 | 48.3% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Agent's emailagent_email |
0 | 0.0% | |
Alternative referencealternative_reference |
0 | 0.0% | |
Appeal decisionappeal_decision |
0 | 0.0% | |
Appeal decision (standardised wording)appeal_decision_normalized |
0 | 0.0% |
Gloucestershire'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 phone Type of development Officer's recommendation
Connect it once with your email address, then ask questions like "which extensions were refused in Gloucestershire last year?" or "what's the planning history of this address?" — no coding, about two minutes to set up. Setup guide →
curl -H "X-Api-Key: pk_..." \ "https://ukplanningapi.co.uk/v1/applications?council_id=269&limit=5"
Council id for Gloucestershire is 269.
Full API reference for developers →
500 lookups a month, free. No card, no password — we email you a sign-in link and you're in.