Nottinghamshire

Nottingham planning data

6,616 planning applications from Nottingham. 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.

6,616

Applications

—

Enforcement notices

530

Appeals

1990–2026

Date range

What Nottingham decides

Nottingham has approved 93.08% of the 5,190 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.08%

Approved, of 5,190 decided

Median days to a decision

96.8

Average days

What it mostly decides

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

Application type	Applications	Share
Full	2,945	44.5%
Tree	1,108	16.7%
Conditions	695	10.5%
Certificate	623	9.4%
Other	383	5.8%

How approval rates and decision times vary across the country →

What Nottingham 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 Nottingham actually provides each one, across all 6,616 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 Nottingham 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`	6,616	100.0%
Description of the works `description`	6,616	100.0%
Date received `received_date`	6,616	100.0%
Council reference `reference`	6,616	100.0%
Ward `ward`	6,615	100.0%
Application type `application_type`	6,612	99.9%
Status `status`	6,575	99.4%
Status (standardised wording) `status_normalized`	6,575	99.4%
Agent's email `agent_email`	6,541	98.9%
Applicant's name `applicant_name`	6,535	98.8%
Alternative reference `alternative_reference`	6,089	92.0%
Postcode `postcode`	5,957	90.0%

Partial — use with care

Information	Records with it	Coverage
Case officer `case_officer`	5,934	89.7%
Decision `decision`	5,888	89.0%
Decision date `decision_date`	5,891	89.0%
Decision (standardised wording) `decision_normalized`	5,852	88.5%
Who decided it (officer or committee) `decision_level`	5,661	85.6%
Agent's name `agent_name`	4,865	73.5%
Agent's company `agent_company`	3,259	49.3%

Rarely or never published

Information	Records with it	Coverage
Standardised type `standard_type`	534	8.1%
Appeal decision `appeal_decision`	113	1.7%
Appeal decision (standardised wording) `appeal_decision_normalized`	113	1.7%
Agent's phone `agent_phone`	0	0.0%
Type of development `development_type`	0	0.0%
Officer's recommendation `officer_recommendation`	0	0.0%

Not published by this council

Nottingham'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 Nottingham 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=73&limit=5"

Council id for Nottingham is 73. Full API reference for developers →

Get free access to Nottingham data

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