Somerset
132 planning applications from Somerset. 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 132 applications here. Treat an absent record as "not published to us", never as "no such application".
We can't calculate an approval rate for Somerset: 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.
Decision times can't be measured here — Somerset 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 Somerset handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Other | 132 | 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 Somerset actually provides each one, across all 132 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 Somerset actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
132 | 100.0% | |
Description of the worksdescription |
132 | 100.0% | |
Council referencereference |
132 | 100.0% | |
Statusstatus |
132 | 100.0% | |
Status (standardised wording)status_normalized |
132 | 100.0% | |
Agent's nameagent_name |
126 | 95.5% | |
Applicant's nameapplicant_name |
122 | 92.4% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Decision datedecision_date |
112 | 84.8% | |
Postcodepostcode |
100 | 75.8% | |
Wardward |
92 | 69.7% | |
Decision (standardised wording)decision_normalized |
89 | 67.4% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Agent's companyagent_company |
13 | 9.8% | |
Agent's emailagent_email |
9 | 6.8% | |
Appeal decisionappeal_decision |
0 | 0.0% | |
Appeal decision (standardised wording)appeal_decision_normalized |
0 | 0.0% | |
Application typeapplication_type |
0 | 0.0% | |
Decisiondecision |
0 | 0.0% | |
Who decided it (officer or committee)decision_level |
0 | 0.0% | |
Map coordinates (easting)easting |
0 | 0.0% | |
Map coordinates (northing)northing |
0 | 0.0% | |
Standardised typestandard_type |
0 | 0.0% |
Somerset'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 Alternative reference Case officer Type of development Officer's recommendation Date received
Connect it once with your email address, then ask questions like "which extensions were refused in Somerset 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=400&limit=5"
Council id for Somerset is 400.
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.