← All councils

Tees Valley

Redcar and Cleveland planning data

1,957 planning applications from Redcar and Cleveland. 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. 8 pieces of information are filled in on at least 90% of records.

1,957
Applications
—
Enforcement notices
142
Appeals
2022–2026
Date range

What Redcar and Cleveland decides

Redcar and Cleveland has approved 95.43% of the 1,531 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%).

95.43%
Approved, of 1,531 decided
56
Median days to a decision
74.5
Average days

What it mostly decides

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

Application typeApplications Share
Other 622 31.8%
Full 594 30.4%
Conditions 251 12.8%
Tree 207 10.6%
Amendment 92 4.7%

How approval rates and decision times vary across the country →

What Redcar and Cleveland 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 Redcar and Cleveland actually provides each one, across all 1,957 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 Redcar and Cleveland actually fill in?" and get these same numbers back. How to connect →

Reliable — 90% or more of records

InformationRecords with it Coverage
Address
address
1,957 100.0%
Application type
application_type
1,957 100.0%
Description of the works
description
1,957 100.0%
Council reference
reference
1,957 100.0%
Agent's name
agent_name
1,953 99.8%
Applicant's name
applicant_name
1,954 99.8%
Case officer
case_officer
1,909 97.5%
Date received
received_date
1,909 97.5%

Partial — use with care

InformationRecords with it Coverage
Decision
decision
1,743 89.1%
Decision date
decision_date
1,732 88.5%
Decision (standardised wording)
decision_normalized
1,713 87.5%
Status
status
1,631 83.3%
Status (standardised wording)
status_normalized
1,631 83.3%
Postcode
postcode
1,539 78.6%
Ward
ward
1,413 72.2%
Who decided it (officer or committee)
decision_level
400 20.4%

Rarely or never published

InformationRecords with it Coverage
Appeal decision
appeal_decision
19 1.0%
Appeal decision (standardised wording)
appeal_decision_normalized
19 1.0%
Agent's company
agent_company
0 0.0%
Agent's email
agent_email
0 0.0%
Map coordinates (easting)
easting
0 0.0%
Map coordinates (northing)
northing
0 0.0%
Standardised type
standard_type
0 0.0%

Not published by this council

Redcar and Cleveland'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 Redcar and Cleveland 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=81409&limit=5"

Council id for Redcar and Cleveland is 81409. Full API reference for developers →

Get free access to Redcar and Cleveland data

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