Derbyshire
460 planning applications from Erewash. 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. 7 pieces of information are filled in on at least 90% of records.
We hold only 460 applications here. Treat an absent record as "not published to us", never as "no such application".
Erewash has approved 93.29% of the 343 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%).
Decision times can't be measured here — Erewash doesn't publish both a received and a decision date on enough records. The nationwide range across councils that do is 31 to 299 days.
The mix of application types Erewash handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Householder | 167 | 36.3% |
| Certificate | 83 | 18.0% |
| Tree | 79 | 17.2% |
| Full | 61 | 13.3% |
| Other | 34 | 7.4% |
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 Erewash actually provides each one, across all 460 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 Erewash actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Application typeapplication_type |
460 | 100.0% | |
Description of the worksdescription |
460 | 100.0% | |
Council referencereference |
460 | 100.0% | |
Addressaddress |
459 | 99.8% | |
Applicant's nameapplicant_name |
448 | 97.4% | |
Postcodepostcode |
441 | 95.9% | |
Wardward |
432 | 93.9% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Decisiondecision |
401 | 87.2% | |
Decision (standardised wording)decision_normalized |
384 | 83.5% | |
Decision datedecision_date |
377 | 82.0% | |
Agent's nameagent_name |
350 | 76.1% | |
Standardised typestandard_type |
188 | 40.9% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Alternative referencealternative_reference |
0 | 0.0% | |
Appeal decision (standardised wording)appeal_decision_normalized |
0 | 0.0% | |
Who decided it (officer or committee)decision_level |
0 | 0.0% | |
Status (standardised wording)status_normalized |
0 | 0.0% |
Erewash'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 Case officer Type of development Map coordinates (easting) Map coordinates (northing) Officer's recommendation Date received Status
Connect it once with your email address, then ask questions like "which extensions were refused in Erewash 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=254&limit=5"
Council id for Erewash is 254.
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.