West Sussex

Mid Sussex planning data

8,466 planning applications from Mid 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. 16 pieces of information are filled in on at least 90% of records.

8,466

Applications

Enforcement notices

6,267

Appeals

1984–2026

Date range

What Mid Sussex decides

Mid Sussex has approved 92.5% of the 6,723 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%).

92.5%

Approved, of 6,723 decided

Median days to a decision

87.2

Average days

What it mostly decides

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

Application type	Applications	Share
Householder	2,598	30.7%
Tree	1,525	18.0%
Conditions	1,163	13.7%
Full	1,089	12.9%
Amendment	613	7.2%

How approval rates and decision times vary across the country →

What Mid Sussex 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 Mid Sussex actually provides each one, across all 8,466 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 Mid Sussex 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`	8,466	100.0%
Application type `application_type`	8,463	100.0%
Description of the works `description`	8,466	100.0%
Date received `received_date`	8,466	100.0%
Council reference `reference`	8,466	100.0%
Applicant's name `applicant_name`	8,442	99.7%
Status `status`	8,441	99.7%
Status (standardised wording) `status_normalized`	8,421	99.5%
Agent's email `agent_email`	8,407	99.3%
Case officer `case_officer`	8,410	99.3%
Ward `ward`	8,407	99.3%
Alternative reference `alternative_reference`	8,106	95.7%
Who decided it (officer or committee) `decision_level`	8,020	94.7%
Decision `decision`	7,887	93.2%
Decision date `decision_date`	7,887	93.2%
Decision (standardised wording) `decision_normalized`	7,866	92.9%

Partial — use with care

Information	Records with it	Coverage
Postcode `postcode`	7,497	88.6%
Agent's phone `agent_phone`	7,201	85.1%
Agent's name `agent_name`	6,585	77.8%
Appeal decision `appeal_decision`	5,504	65.0%
Standardised type `standard_type`	5,458	64.5%
Agent's company `agent_company`	4,488	53.0%

Rarely or never published

Information	Records with it	Coverage
Appeal decision (standardised wording) `appeal_decision_normalized`	160	1.9%
Type of development `development_type`	0	0.0%
Officer's recommendation `officer_recommendation`	0	0.0%

Not published by this council

Mid Sussex'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 Mid Sussex 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=329&limit=5"

Council id for Mid Sussex is 329. Full API reference for developers →

Get free access to Mid Sussex data

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