West Sussex

Chichester planning data

6,541 planning applications from Chichester. 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. 4 pieces of information are filled in on at least 90% of records.

6,541

Applications

Enforcement notices

872

Appeals

1996–2026

Date range

We're still loading this council's older records.

We don't yet have Chichester's full history back to 2023 — it's loading now. The figures below cover what we already hold, so treat them as a minimum rather than the full picture. Alerts for new day-to-day changes start once loading is complete.

What Chichester decides

Chichester has approved 89.78% of the 1,018 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%).

89.78%

Approved, of 1,018 decided

Median days to a decision

86.4

Average days

What it mostly decides

The mix of application types Chichester handles — useful for telling whether your kind of application is routine here or unusual.

Application type	Applications	Share
Other	5,382	82.3%
Householder	294	4.5%
Conditions	268	4.1%
Full	228	3.5%
Tree	190	2.9%

How approval rates and decision times vary across the country →

What Chichester actually fills in

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 Chichester actually provides each one, across all 6,541 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 Chichester actually fill in?" and get these same numbers back. How to connect →

Reliable — 90% or more of records

Information	Records with it	Coverage
Address `address`	6,541	100.0%
Description of the works `description`	6,541	100.0%
Council reference `reference`	6,541	100.0%
Status `status`	6,030	92.2%

Partial — use with care

Information	Records with it	Coverage
Postcode `postcode`	5,746	87.8%
Status (standardised wording) `status_normalized`	5,558	85.0%
Decision (standardised wording) `decision_normalized`	5,005	76.5%
Ward `ward`	2,997	45.8%
Date received `received_date`	1,721	26.3%
Application type `application_type`	1,273	19.5%
Case officer `case_officer`	1,273	19.5%
Who decided it (officer or committee) `decision_level`	1,272	19.4%
Applicant's name `applicant_name`	1,253	19.2%
Agent's email `agent_email`	1,239	18.9%
Agent's phone `agent_phone`	1,205	18.4%
Decision `decision`	1,155	17.7%
Decision date `decision_date`	1,155	17.7%
Alternative reference `alternative_reference`	1,127	17.2%
Agent's name `agent_name`	1,011	15.5%
Agent's company `agent_company`	919	14.0%

Rarely or never published

Information	Records with it	Coverage
Standardised type `standard_type`	116	1.8%
Appeal decision `appeal_decision`	30	0.5%
Appeal decision (standardised wording) `appeal_decision_normalized`	30	0.5%
Type of development `development_type`	0	0.0%
Officer's recommendation `officer_recommendation`	0	0.0%

Not published by this council

Chichester'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)

Get this data

Ask it in ChatGPT or Claude

Connect it once with your email address, then ask questions like "which extensions were refused in Chichester last year?" or "what's the planning history of this address?" — no coding, about two minutes to set up. Setup guide →

Or call it from your own code

curl -H "X-Api-Key: pk_..." \
  "https://ukplanningapi.co.uk/v1/applications?council_id=204&limit=5"

Council id for Chichester is 204. Full API reference for developers →

Get free access to Chichester data

500 lookups a month, free. No card, no password — we email you a sign-in link and you're in.