Derbyshire

Derbyshire planning data

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

298

Applications

—

Enforcement notices

Appeals

1997–2026

Date range

Limited data for this council.

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

What Derbyshire decides

Derbyshire has approved 92.16% of the 255 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.16%

Approved, of 255 decided

Median days to a decision

82.6

Average days

What it mostly decides

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

Application type	Applications	Share
Tree	220	73.8%
Other	77	25.8%
Certificate	1	0.3%

How approval rates and decision times vary across the country →

What Derbyshire 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 Derbyshire actually provides each one, across all 298 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 Derbyshire 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`	298	100.0%
Application type `application_type`	298	100.0%
Description of the works `description`	298	100.0%
Date received `received_date`	298	100.0%
Council reference `reference`	298	100.0%
Status `status`	298	100.0%
Applicant's name `applicant_name`	292	98.0%
Agent's name `agent_name`	290	97.3%
Status (standardised wording) `status_normalized`	288	96.6%
Postcode `postcode`	287	96.3%
Case officer `case_officer`	276	92.6%
Decision `decision`	276	92.6%

Partial — use with care

Information	Records with it	Coverage
Decision (standardised wording) `decision_normalized`	267	89.6%
Decision date `decision_date`	263	88.3%
Ward `ward`	229	76.8%
Standardised type `standard_type`	194	65.1%

Rarely or never published

Information	Records with it	Coverage
Who decided it (officer or committee) `decision_level`	20	6.7%
Agent's company `agent_company`	2	0.7%
Agent's email `agent_email`	2	0.7%
Appeal decision `appeal_decision`	0	0.0%
Appeal decision (standardised wording) `appeal_decision_normalized`	0	0.0%
Map coordinates (easting) `easting`	0	0.0%
Map coordinates (northing) `northing`	0	0.0%

Not published by this council

Derbyshire'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 Derbyshire 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=222&limit=5"

Council id for Derbyshire is 222. Full API reference for developers →

Get free access to Derbyshire data

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