Lancashire

Pendle planning data

2,952 planning applications from Pendle. 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.

2,952

Applications

133

Enforcement notices

427

Appeals

2000–2026

Date range

What Pendle decides

Pendle has approved 85.28% of the 2,120 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%).

85.28%

Approved, of 2,120 decided

Median days to a decision

62.4

Average days

What it mostly decides

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

Application type	Applications	Share
Householder	812	27.5%
Full	730	24.7%
Tree	416	14.1%
Conditions	343	11.6%
Other	259	8.8%

How approval rates and decision times vary across the country →

What Pendle 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 Pendle actually provides each one, across all 2,952 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 Pendle 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`	2,952	100.0%
Description of the works `description`	2,952	100.0%
Date received `received_date`	2,952	100.0%
Council reference `reference`	2,952	100.0%
Ward `ward`	2,948	99.9%
Application type `application_type`	2,947	99.8%
Case officer `case_officer`	2,944	99.7%
Status `status`	2,942	99.7%
Status (standardised wording) `status_normalized`	2,942	99.7%
Applicant's name `applicant_name`	2,927	99.2%
Decision `decision`	2,796	94.7%
Decision date `decision_date`	2,796	94.7%
Decision (standardised wording) `decision_normalized`	2,727	92.4%
Who decided it (officer or committee) `decision_level`	2,658	90.0%

Partial — use with care

Information	Records with it	Coverage
Agent's name `agent_name`	2,379	80.6%
Agent's email `agent_email`	2,356	79.8%
Postcode `postcode`	2,344	79.4%
Agent's phone `agent_phone`	2,305	78.1%
Agent's company `agent_company`	2,055	69.6%
Alternative reference `alternative_reference`	1,817	61.6%
Standardised type `standard_type`	797	27.0%

Rarely or never published

Information	Records with it	Coverage
Appeal decision `appeal_decision`	77	2.6%
Appeal decision (standardised wording) `appeal_decision_normalized`	77	2.6%
Type of development `development_type`	0	0.0%
Officer's recommendation `officer_recommendation`	0	0.0%

Not published by this council

Pendle'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)

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 Pendle 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=23&limit=5"

Council id for Pendle is 23. Full API reference for developers →

Get free access to Pendle data

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