Staffordshire
2,960 planning applications from Stoke on Trent. 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.
Stoke on Trent has approved 79.97% of the 2,421 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%).
The mix of application types Stoke on Trent handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Full | 1,454 | 49.1% |
| Other | 503 | 17.0% |
| Conditions | 257 | 8.7% |
| Householder | 198 | 6.7% |
| Certificate | 186 | 6.3% |
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 Stoke on Trent actually provides each one, across all 2,960 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 Stoke on Trent actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
2,960 | 100.0% | |
Application typeapplication_type |
2,960 | 100.0% | |
Case officercase_officer |
2,959 | 100.0% | |
Date receivedreceived_date |
2,960 | 100.0% | |
Council referencereference |
2,960 | 100.0% | |
Description of the worksdescription |
2,955 | 99.8% | |
Statusstatus |
2,953 | 99.8% | |
Status (standardised wording)status_normalized |
2,953 | 99.8% | |
Applicant's nameapplicant_name |
2,950 | 99.7% | |
Wardward |
2,916 | 98.5% | |
Who decided it (officer or committee)decision_level |
2,851 | 96.3% | |
Decisiondecision |
2,778 | 93.9% | |
Decision datedecision_date |
2,773 | 93.7% | |
Postcodepostcode |
2,773 | 93.7% | |
Decision (standardised wording)decision_normalized |
2,757 | 93.1% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Agent's nameagent_name |
2,606 | 88.0% | |
Standardised typestandard_type |
2,408 | 81.4% | |
Agent's companyagent_company |
2,373 | 80.2% | |
Map coordinates (easting)easting |
2,229 | 75.3% | |
Map coordinates (northing)northing |
2,229 | 75.3% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Alternative referencealternative_reference |
47 | 1.6% | |
Appeal decisionappeal_decision |
48 | 1.6% | |
Appeal decision (standardised wording)appeal_decision_normalized |
48 | 1.6% | |
Agent's emailagent_email |
0 | 0.0% |
Stoke on Trent'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 Stoke on Trent 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=426&limit=5"
Council id for Stoke on Trent is 426.
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.