Nottinghamshire

Gedling planning data

2,842 planning applications from Gedling. 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.

2,842

Applications

—

Enforcement notices

2,834

Appeals

1993–2026

Date range

What Gedling decides

Gedling has approved 92.47% of the 2,152 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.47%

Approved, of 2,152 decided

Median days to a decision

96.4

Average days

What it mostly decides

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

Application type	Applications	Share
Householder	1,007	35.4%
Full	581	20.4%
Other	356	12.5%
Conditions	295	10.4%
Tree	283	10.0%

How approval rates and decision times vary across the country →

What Gedling 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 Gedling actually provides each one, across all 2,842 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 Gedling 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`	2,842	100.0%
Description of the works `description`	2,842	100.0%
Date received `received_date`	2,842	100.0%
Council reference `reference`	2,842	100.0%
Application type `application_type`	2,838	99.9%
Ward `ward`	2,817	99.1%
Agent's email `agent_email`	2,797	98.4%
Applicant's name `applicant_name`	2,794	98.3%
Decision `decision`	2,573	90.5%
Decision date `decision_date`	2,573	90.5%
Who decided it (officer or committee) `decision_level`	2,568	90.4%
Decision (standardised wording) `decision_normalized`	2,564	90.2%

Partial — use with care

Information	Records with it	Coverage
Agent's phone `agent_phone`	2,555	89.9%
Postcode `postcode`	2,549	89.7%
Alternative reference `alternative_reference`	2,506	88.2%
Case officer `case_officer`	2,451	86.2%
Agent's name `agent_name`	2,128	74.9%
Agent's company `agent_company`	1,881	66.2%
Status `status`	434	15.3%
Status (standardised wording) `status_normalized`	434	15.3%
Standardised type `standard_type`	317	11.2%

Rarely or never published

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

Not published by this council

Gedling'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 Gedling 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=266&limit=5"

Council id for Gedling is 266. Full API reference for developers →

Get free access to Gedling data

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