Kent

Kent planning data

407 planning applications from Kent. 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. 11 pieces of information are filled in on at least 90% of records.

407

Applications

—

Enforcement notices

Appeals

2023–2026

Date range

Limited data for this council.

We hold only 407 applications here. Treat an absent record as "not published to us", never as "no such application".

What Kent decides

Kent has approved 99.15% of the 354 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%).

99.15%

Approved, of 354 decided

Decision times can't be measured here — Kent 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.

What it mostly decides

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

Application type	Applications	Share
Other	407	100.0%

How approval rates and decision times vary across the country →

What Kent 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 Kent actually provides each one, across all 407 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 Kent 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`	407	100.0%
Applicant's name `applicant_name`	407	100.0%
Description of the works `description`	407	100.0%
Council reference `reference`	407	100.0%
Status `status`	407	100.0%
Status (standardised wording) `status_normalized`	407	100.0%
Decision `decision`	375	92.1%
Agent's name `agent_name`	373	91.6%
Decision date `decision_date`	371	91.2%
Postcode `postcode`	371	91.2%
Decision (standardised wording) `decision_normalized`	369	90.7%

Partial — use with care

Information	Records with it	Coverage
Ward `ward`	332	81.6%

Rarely or never published

Information	Records with it	Coverage
Agent's company `agent_company`	4	1.0%
Agent's email `agent_email`	3	0.7%
Appeal decision `appeal_decision`	1	0.2%
Appeal decision (standardised wording) `appeal_decision_normalized`	1	0.2%
Application type `application_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 type `standard_type`	0	0.0%

Not published by this council

Kent'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

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 Kent 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=300&limit=5"

Council id for Kent is 300. Full API reference for developers →

Get free access to Kent data

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