Kent
8,956 planning applications from Tunbridge Wells. 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. 7 pieces of information are filled in on at least 90% of records.
We don't yet have Tunbridge Wells's full history back to 2023 — it's loading now. The figures below cover what we already hold, so treat them as a minimum rather than the full picture. Alerts for new day-to-day changes start once loading is complete.
Tunbridge Wells has approved 93.95% of the 1,752 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%).
The mix of application types Tunbridge Wells handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Other | 6,797 | 75.9% |
| Full | 1,069 | 11.9% |
| Tree | 671 | 7.5% |
| Listed building | 189 | 2.1% |
| Certificate | 128 | 1.4% |
How approval rates and decision times vary across the country →
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 Tunbridge Wells actually provides each one, across all 8,956 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 Tunbridge Wells actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
8,956 | 100.0% | |
Description of the worksdescription |
8,956 | 100.0% | |
Date receivedreceived_date |
8,956 | 100.0% | |
Council referencereference |
8,956 | 100.0% | |
Statusstatus |
8,851 | 98.8% | |
Status (standardised wording)status_normalized |
8,851 | 98.8% | |
Postcodepostcode |
8,163 | 91.1% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Wardward |
4,037 | 45.1% | |
Applicant's nameapplicant_name |
2,672 | 29.8% | |
Application typeapplication_type |
2,672 | 29.8% | |
Who decided it (officer or committee)decision_level |
2,672 | 29.8% | |
Agent's emailagent_email |
2,642 | 29.5% | |
Case officercase_officer |
2,434 | 27.2% | |
Alternative referencealternative_reference |
2,345 | 26.2% | |
Decisiondecision |
2,275 | 25.4% | |
Decision datedecision_date |
2,274 | 25.4% | |
Decision (standardised wording)decision_normalized |
2,258 | 25.2% | |
Agent's nameagent_name |
1,988 | 22.2% | |
Agent's phoneagent_phone |
1,895 | 21.2% | |
Agent's companyagent_company |
1,869 | 20.9% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Standardised typestandard_type |
183 | 2.0% | |
Appeal decisionappeal_decision |
20 | 0.2% | |
Appeal decision (standardised wording)appeal_decision_normalized |
20 | 0.2% | |
Type of developmentdevelopment_type |
0 | 0.0% | |
Officer's recommendationofficer_recommendation |
0 | 0.0% |
Tunbridge Wells'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)
Connect it once with your email address, then ask questions like "which extensions were refused in Tunbridge Wells last year?" or "what's the planning history of this address?" — no coding, about two minutes to set up. Setup guide →
curl -H "X-Api-Key: pk_..." \ "https://ukplanningapi.co.uk/v1/applications?council_id=448&limit=5"
Council id for Tunbridge Wells is 448.
Full API reference for developers →
500 lookups a month, free. No card, no password — we email you a sign-in link and you're in.