West Sussex
163 planning applications from West Sussex. 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. 12 pieces of information are filled in on at least 90% of records.
We hold only 163 applications here. Treat an absent record as "not published to us", never as "no such application".
West Sussex has approved 97.78% of the 135 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 — West Sussex 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 West Sussex handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Other | 163 | 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 West Sussex actually provides each one, across all 163 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 West Sussex actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
163 | 100.0% | |
Agent's nameagent_name |
163 | 100.0% | |
Case officercase_officer |
163 | 100.0% | |
Description of the worksdescription |
163 | 100.0% | |
Council referencereference |
163 | 100.0% | |
Statusstatus |
163 | 100.0% | |
Status (standardised wording)status_normalized |
163 | 100.0% | |
Applicant's nameapplicant_name |
162 | 99.4% | |
Postcodepostcode |
154 | 94.5% | |
Decisiondecision |
147 | 90.2% | |
Decision datedecision_date |
147 | 90.2% | |
Decision (standardised wording)decision_normalized |
147 | 90.2% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Wardward |
140 | 85.9% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Agent's companyagent_company |
5 | 3.1% | |
Agent's emailagent_email |
4 | 2.5% | |
Appeal decisionappeal_decision |
0 | 0.0% | |
Appeal decision (standardised wording)appeal_decision_normalized |
0 | 0.0% | |
Application typeapplication_type |
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% |
West Sussex'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 Type of development Officer's recommendation Date received
Connect it once with your email address, then ask questions like "which extensions were refused in West Sussex 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=473&limit=5"
Council id for West Sussex is 473.
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.