Leicestershire

Blaby planning data

3,173 planning applications from Blaby. 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.

3,173

Applications

—

Enforcement notices

269

Appeals

1995–2026

Date range

What Blaby decides

Blaby has approved 93.78% of the 2,765 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%).

93.78%

Approved, of 2,765 decided

Median days to a decision

97.4

Average days

What it mostly decides

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

Application type	Applications	Share
Householder	1,156	36.4%
Full	592	18.7%
Tree	443	14.0%
Conditions	331	10.4%
Amendment	222	7.0%

How approval rates and decision times vary across the country →

What Blaby 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 Blaby actually provides each one, across all 3,173 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 Blaby 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`	3,173	100.0%
Description of the works `description`	3,173	100.0%
Date received `received_date`	3,173	100.0%
Council reference `reference`	3,173	100.0%
Application type `application_type`	3,169	99.9%
Who decided it (officer or committee) `decision_level`	3,155	99.4%
Applicant's name `applicant_name`	3,142	99.0%
Ward `ward`	3,116	98.2%
Status `status`	3,098	97.6%
Status (standardised wording) `status_normalized`	3,098	97.6%
Agent's email `agent_email`	3,019	95.1%
Agent's phone `agent_phone`	2,971	93.6%
Decision date `decision_date`	2,929	92.3%
Decision `decision`	2,926	92.2%
Decision (standardised wording) `decision_normalized`	2,906	91.6%
Alternative reference `alternative_reference`	2,882	90.8%

Partial — use with care

Information	Records with it	Coverage
Postcode `postcode`	2,823	89.0%
Case officer `case_officer`	2,606	82.1%
Agent's name `agent_name`	2,561	80.7%
Standardised type `standard_type`	1,192	37.6%
Agent's company `agent_company`	900	28.4%

Rarely or never published

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

Not published by this council

Blaby'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 Blaby 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=167&limit=5"

Council id for Blaby is 167. Full API reference for developers →

Get free access to Blaby data

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