East Sussex

Rother planning data

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

4,453

Applications

—

Enforcement notices

763

Appeals

2023–2026

Date range

What Rother decides

Rother has approved 85.29% of the 3,358 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 below the middle of the pack (89.18%).

85.29%

Approved, of 3,358 decided

Median days to a decision

94.4

Average days

What it mostly decides

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

Application type	Applications	Share
Full	2,184	49.0%
Other	523	11.7%
Listed building	406	9.1%
Certificate	397	8.9%
Tree	394	8.8%

How approval rates and decision times vary across the country →

What Rother 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 Rother actually provides each one, across all 4,453 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 Rother 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`	4,453	100.0%
Applicant's name `applicant_name`	4,452	100.0%
Application type `application_type`	4,452	100.0%
Case officer `case_officer`	4,453	100.0%
Description of the works `description`	4,453	100.0%
Date received `received_date`	4,453	100.0%
Council reference `reference`	4,453	100.0%
Status `status`	4,433	99.6%
Status (standardised wording) `status_normalized`	4,433	99.6%
Ward `ward`	4,424	99.3%
Postcode `postcode`	4,336	97.4%
Agent's name `agent_name`	4,266	95.8%
Decision date `decision_date`	4,249	95.4%
Decision `decision`	4,235	95.1%
Decision (standardised wording) `decision_normalized`	4,081	91.6%

Partial — use with care

Information	Records with it	Coverage
Who decided it (officer or committee) `decision_level`	3,968	89.1%
Agent's company `agent_company`	3,435	77.1%
Standardised type `standard_type`	3,430	77.0%
Map coordinates (easting) `easting`	1,041	23.4%
Map coordinates (northing) `northing`	1,041	23.4%

Rarely or never published

Information	Records with it	Coverage
Alternative reference `alternative_reference`	129	2.9%
Appeal decision `appeal_decision`	126	2.8%
Appeal decision (standardised wording) `appeal_decision_normalized`	126	2.8%
Agent's email `agent_email`	0	0.0%

Not published by this council

Rother'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 Type of development Officer's recommendation

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 Rother 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=385&limit=5"

Council id for Rother is 385. Full API reference for developers →

Get free access to Rother data

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