Planning application coverage

Gedling Borough Council planning applications and history.

PlanWire tracks 4,548 planning records for Gedling Borough Council, spanning 5 Jan 1990 to 2 Sept 2026. Search the underlying applications and source links through one monitored API.

Get planning alerts for Gedling Borough Council Get this data via API Coverage overview
planning applications API planning alerts API planning data API postcode planning data API planning webhooks proptech planning API planning application leads API MCP planning data server

Live near Gedling Borough Council? Set up a planning alert and get an email when an application is submitted close to your postcode. Building a product instead? The same records are available through the API.

Records tracked

4,548

History begins

5 Jan 1990

Latest dated app

4 days ago

Source checked

yesterday

Latest cached dated application: 2 Sept 2026. Use API date filters for exact recent counts.

Recent application preview

Latest public records from Gedling Borough Council

Five recent dated applications. API responses include fuller machine-readable fields and pagination.

Proposed replacement dwelling

Brackendale Ricket Lane Ravenshead Nottinghamshire NG21 0NF

Planning application · Status: Awaiting decision

27 Aug 2026 2026/0587

Local record profile

Gedling Borough Council is a focused local planning history, with 4,548 records tracked. The public record spans 1990 to 2026, so the page is useful for recent monitoring as well as historic checks around sites and addresses.

Authority context

Gedling Borough Council is a borough planning authority, with local applications normalised for search, alerting and API workflows.

Recent activity pattern

Gedling Borough Council has a cached latest dated application of 4 days ago. Use API date filters for exact recent counts when sizing local monitoring or alerting workflows.

Monitoring fit

Gedling Borough Council has cached latest-date coverage in this public summary. API users can combine council filters, date filters and freshness metadata for exact operational checks.

Freshness status

Fresh in last 7 days

Latest dated application is 4 days ago.

Completeness signal

No open source caveat

Latest checked, latest dated application and API source metadata are published with the council record. Document metadata is exposed where the source supplies it.

Machine-readable access

Use GET /v1/councils for coverage metadata and GET /v1/applications?council_id=gedling for application records with an API key.

Try this exact query Query docs