Cheshire
803 planning applications from Chester. 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. 10 pieces of information are filled in on at least 90% of records.
We don't yet have Chester's full history back to 2023 — it's loading now. The figures below cover what we already hold, so treat them as a minimum rather than the full picture. Alerts for new day-to-day changes start once loading is complete.
Chester has approved 94.66% of the 337 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 Chester handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Full | 315 | 39.2% |
| Other | 228 | 28.4% |
| Tree | 74 | 9.2% |
| Conditions | 69 | 8.6% |
| Certificate | 48 | 6.0% |
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 Chester actually provides each one, across all 803 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 Chester actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
803 | 100.0% | |
Description of the worksdescription |
803 | 100.0% | |
Council referencereference |
803 | 100.0% | |
Statusstatus |
802 | 99.9% | |
Status (standardised wording)status_normalized |
802 | 99.9% | |
Date receivedreceived_date |
793 | 98.8% | |
Wardward |
792 | 98.6% | |
Applicant's nameapplicant_name |
750 | 93.4% | |
Application typeapplication_type |
750 | 93.4% | |
Standardised typestandard_type |
750 | 93.4% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Postcodepostcode |
664 | 82.7% | |
Alternative referencealternative_reference |
651 | 81.1% | |
Case officercase_officer |
562 | 70.0% | |
Agent's emailagent_email |
530 | 66.0% | |
Agent's nameagent_name |
530 | 66.0% | |
Decision datedecision_date |
447 | 55.7% | |
Decisiondecision |
424 | 52.8% | |
Decision (standardised wording)decision_normalized |
408 | 50.8% | |
Agent's companyagent_company |
296 | 36.9% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Appeal decisionappeal_decision |
7 | 0.9% | |
Appeal decision (standardised wording)appeal_decision_normalized |
7 | 0.9% | |
Agent's phoneagent_phone |
0 | 0.0% | |
Who decided it (officer or committee)decision_level |
0 | 0.0% | |
Type of developmentdevelopment_type |
0 | 0.0% | |
Map coordinates (easting)easting |
0 | 0.0% | |
Map coordinates (northing)northing |
0 | 0.0% | |
Officer's recommendationofficer_recommendation |
0 | 0.0% |
Connect it once with your email address, then ask questions like "which extensions were refused in Chester 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=202&limit=5"
Council id for Chester is 202.
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.