South London

Richmond planning data

1,736 planning applications from Richmond. 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. 13 pieces of information are filled in on at least 90% of records.

1,736

Applications

—

Enforcement notices

1,424

Appeals

2023–2026

Date range

What Richmond decides

Richmond has approved 86.72% of the 806 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 below the middle of the pack (89.18%).

86.72%

Approved, of 806 decided

Median days to a decision

68.3

Average days

What it mostly decides

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

Application type	Applications	Share
Other	490	28.2%
Householder	471	27.1%
Tree	329	19.0%
Full	257	14.8%
Amendment	108	6.2%

How approval rates and decision times vary across the country →

What Richmond 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 Richmond actually provides each one, across all 1,736 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 Richmond 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`	1,736	100.0%
Description of the works `description`	1,736	100.0%
Date received `received_date`	1,736	100.0%
Council reference `reference`	1,736	100.0%
Status `status`	1,736	100.0%
Application type `application_type`	1,735	99.9%
Status (standardised wording) `status_normalized`	1,734	99.9%
Ward `ward`	1,734	99.9%
Case officer `case_officer`	1,732	99.8%
Map coordinates (easting) `easting`	1,727	99.5%
Map coordinates (northing) `northing`	1,727	99.5%
Alternative reference `alternative_reference`	1,637	94.3%
Postcode `postcode`	1,579	91.0%

Partial — use with care

Information	Records with it	Coverage
Agent's email `agent_email`	1,509	86.9%
Agent's name `agent_name`	1,508	86.9%
Agent's phone `agent_phone`	1,445	83.2%
Agent's company `agent_company`	1,363	78.5%
Who decided it (officer or committee) `decision_level`	1,198	69.0%
Decision (standardised wording) `decision_normalized`	1,055	60.8%
Decision `decision`	1,054	60.7%
Decision date `decision_date`	1,051	60.5%
Applicant's name `applicant_name`	621	35.8%
Standardised type `standard_type`	395	22.8%

Rarely or never published

Information	Records with it	Coverage
Appeal decision `appeal_decision`	1	0.1%
Appeal decision (standardised wording) `appeal_decision_normalized`	1	0.1%
Type of development `development_type`	0	0.0%

Not published by this council

Richmond's portal has been verified not to publish these fields at all — different from a field that exists but is rarely filled in.

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 Richmond 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=383&limit=5"

Council id for Richmond is 383. Full API reference for developers →

Get free access to Richmond data

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