Norfolk
327 planning applications from Norfolk. 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 hold only 327 applications here. Treat an absent record as "not published to us", never as "no such application".
Norfolk has approved 97.3% of the 148 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%).
Decision times can't be measured here — Norfolk doesn't publish both a received and a decision date on enough records. The nationwide range across councils that do is 31 to 299 days.
The mix of application types Norfolk handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Full | 158 | 48.3% |
| Conditions | 116 | 35.5% |
| Amendment | 29 | 8.9% |
| Other | 21 | 6.4% |
| Certificate | 2 | 0.6% |
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 Norfolk actually provides each one, across all 327 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 Norfolk actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
327 | 100.0% | |
Application typeapplication_type |
327 | 100.0% | |
Council referencereference |
327 | 100.0% | |
Statusstatus |
327 | 100.0% | |
Agent's nameagent_name |
326 | 99.7% | |
Applicant's nameapplicant_name |
326 | 99.7% | |
Description of the worksdescription |
326 | 99.7% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Postcodepostcode |
277 | 84.7% | |
Decisiondecision |
270 | 82.6% | |
Decision datedecision_date |
269 | 82.3% | |
Standardised typestandard_type |
260 | 79.5% | |
Decision (standardised wording)decision_normalized |
257 | 78.6% | |
Wardward |
257 | 78.6% | |
Map coordinates (easting)easting |
248 | 75.8% | |
Map coordinates (northing)northing |
248 | 75.8% | |
Status (standardised wording)status_normalized |
213 | 65.1% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Appeal decisionappeal_decision |
4 | 1.2% | |
Appeal decision (standardised wording)appeal_decision_normalized |
4 | 1.2% | |
Agent's emailagent_email |
3 | 0.9% | |
Agent's companyagent_company |
2 | 0.6% | |
Who decided it (officer or committee)decision_level |
0 | 0.0% |
Norfolk'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 Case officer Type of development Officer's recommendation Date received
Connect it once with your email address, then ask questions like "which extensions were refused in Norfolk 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=342&limit=5"
Council id for Norfolk is 342.
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.