Essex
11,038 planning applications from Chelmsford. 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 can't calculate an approval rate for Chelmsford: it doesn't publish a usable decision on enough of its applications. That's a gap in what the council makes available, not a sign that nothing is decided — 9 of the councils we hold are in the same position.
The mix of application types Chelmsford handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Other | 11,038 | 100.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 Chelmsford actually provides each one, across all 11,038 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 Chelmsford actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
11,038 | 100.0% | |
Description of the worksdescription |
11,038 | 100.0% | |
Council referencereference |
11,038 | 100.0% | |
Date receivedreceived_date |
11,030 | 99.9% | |
Statusstatus |
10,899 | 98.7% | |
Status (standardised wording)status_normalized |
10,807 | 97.9% | |
Agent's emailagent_email |
10,797 | 97.8% | |
Decision datedecision_date |
10,553 | 95.6% | |
Alternative referencealternative_reference |
10,388 | 94.1% | |
Decision (standardised wording)decision_normalized |
10,347 | 93.7% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Postcodepostcode |
8,766 | 79.4% | |
Wardward |
8,239 | 74.6% | |
Agent's phoneagent_phone |
6,127 | 55.5% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Appeal decisionappeal_decision |
371 | 3.4% | |
Appeal decision (standardised wording)appeal_decision_normalized |
364 | 3.3% | |
Agent's companyagent_company |
0 | 0.0% | |
Agent's nameagent_name |
0 | 0.0% | |
Applicant's nameapplicant_name |
0 | 0.0% | |
Application typeapplication_type |
0 | 0.0% | |
Case officercase_officer |
0 | 0.0% | |
Decisiondecision |
0 | 0.0% | |
Who decided it (officer or committee)decision_level |
0 | 0.0% | |
Type of developmentdevelopment_type |
0 | 0.0% | |
Officer's recommendationofficer_recommendation |
0 | 0.0% | |
Standardised typestandard_type |
0 | 0.0% |
Chelmsford'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)
Connect it once with your email address, then ask questions like "which extensions were refused in Chelmsford 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=199&limit=5"
Council id for Chelmsford is 199.
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.