Kent
4,333 planning applications from Gravesham. 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. 14 pieces of information are filled in on at least 90% of records.
Gravesham has approved 77.75% of the 3,708 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%).
The mix of application types Gravesham handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Full | 1,084 | 25.0% |
| Householder | 1,038 | 24.0% |
| Other | 628 | 14.5% |
| Certificate | 544 | 12.6% |
| Conditions | 500 | 11.5% |
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 Gravesham actually provides each one, across all 4,333 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 Gravesham actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
4,333 | 100.0% | |
Description of the worksdescription |
4,333 | 100.0% | |
Date receivedreceived_date |
4,333 | 100.0% | |
Council referencereference |
4,333 | 100.0% | |
Application typeapplication_type |
4,330 | 99.9% | |
Applicant's nameapplicant_name |
4,303 | 99.3% | |
Case officercase_officer |
4,295 | 99.1% | |
Wardward |
4,294 | 99.1% | |
Agent's emailagent_email |
4,179 | 96.4% | |
Decisiondecision |
4,117 | 95.0% | |
Decision datedecision_date |
4,117 | 95.0% | |
Who decided it (officer or committee)decision_level |
3,973 | 91.7% | |
Decision (standardised wording)decision_normalized |
3,943 | 91.0% | |
Postcodepostcode |
3,912 | 90.3% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Statusstatus |
3,865 | 89.2% | |
Status (standardised wording)status_normalized |
3,825 | 88.3% | |
Alternative referencealternative_reference |
3,800 | 87.7% | |
Agent's phoneagent_phone |
3,436 | 79.3% | |
Agent's nameagent_name |
3,404 | 78.6% | |
Standardised typestandard_type |
1,354 | 31.2% | |
Agent's companyagent_company |
552 | 12.7% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Appeal decisionappeal_decision |
164 | 3.8% | |
Appeal decision (standardised wording)appeal_decision_normalized |
164 | 3.8% | |
Type of developmentdevelopment_type |
0 | 0.0% | |
Officer's recommendationofficer_recommendation |
0 | 0.0% |
Gravesham'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 Gravesham 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=271&limit=5"
Council id for Gravesham is 271.
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.