Leicestershire

Leicester planning data

282 planning applications from Leicester. 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.

282

Applications

2,964

Enforcement notices

547

Appeals

2025–2026

Date range

Limited data for this council.

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

What Leicester decides

We can't calculate an approval rate for Leicester: it doesn't publish a usable decision on enough of its applications. That's a gap in what the council makes available, not a sign that nothing is decided — 9 of the councils we hold are in the same position.

Median days to a decision

54.1

Average days

What it mostly decides

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

Application type	Applications	Share
Full	162	57.4%
Other	35	12.4%
Certificate	29	10.3%
Conditions	24	8.5%
Tree	11	3.9%

How approval rates and decision times vary across the country →

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

Reliable — 90% or more of records

Information	Records with it	Coverage
Application type `application_type`	282	100.0%
Case officer `case_officer`	282	100.0%
Description of the works `description`	282	100.0%
Date received `received_date`	282	100.0%
Council reference `reference`	282	100.0%
Status `status`	282	100.0%
Status (standardised wording) `status_normalized`	282	100.0%
Ward `ward`	282	100.0%
Address `address`	281	99.6%
Who decided it (officer or committee) `decision_level`	281	99.6%
Agent's name `agent_name`	280	99.3%

Partial — use with care

Information	Records with it	Coverage
Decision date `decision_date`	141	50.0%

Rarely or never published

Information	Records with it	Coverage
Decision (standardised wording) `decision_normalized`	23	8.2%
Appeal decision `appeal_decision`	20	7.1%
Appeal decision (standardised wording) `appeal_decision_normalized`	20	7.1%
Agent's company `agent_company`	11	3.9%
Agent's email `agent_email`	11	3.9%
Applicant's name `applicant_name`	0	0.0%
Decision `decision`	0	0.0%
Map coordinates (easting) `easting`	0	0.0%
Map coordinates (northing) `northing`	0	0.0%
Postcode `postcode`	0	0.0%
Standardised type `standard_type`	0	0.0%

Not published by this council

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

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 Leicester 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=74&limit=5"

Council id for Leicester is 74. Full API reference for developers →

Get free access to Leicester data

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