Remedial works to trees x 3
76 Cinnamon Lane, Poulton-with-fearnhead, Warrington, WA2 0AP
Planning application coverage
PlanWire tracks 1,406 planning records for Warrington Borough Council, spanning 9 Apr 2026 to 2 Sept 2026. Search the underlying applications and source links through one monitored API.
Live near Warrington Borough Council? Set up a planning alert and get an email when an application is submitted close to your postcode. Building a product instead? The same records are available through the API.
Records tracked
1,406
History begins
9 Apr 2026
Latest dated app
4 days ago
Source checked
2 days ago
Latest cached dated application: 2 Sept 2026. Use API date filters for exact recent counts.
Recent application preview
Five recent dated applications. API responses include fuller machine-readable fields and pagination.
76 Cinnamon Lane, Poulton-with-fearnhead, Warrington, WA2 0AP
93 Whitefield Road, Warrington, WA4 6ND
704 Warrington Road, Warrington, WA3 6AU
471, LEIGH END Warrington Road, Warrington, WA3 5NS
THE LODGE Old Pewterspear Lane, Appleton, Warrington, WA4 5NH
Local record profile
Warrington Borough Council is a focused local planning history, with 1,406 records tracked. The public record spans 2026, so the page is useful for recent monitoring as well as historic checks around sites and addresses.
Authority context
Warrington Borough Council is a borough planning authority, with local applications normalised for search, alerting and API workflows.
Recent activity pattern
Warrington Borough Council has a cached latest dated application of 4 days ago. Use API date filters for exact recent counts when sizing local monitoring or alerting workflows.
Monitoring fit
Warrington Borough Council has cached latest-date coverage in this public summary. API users can combine council filters, date filters and freshness metadata for exact operational checks.
Freshness status
Latest dated application is 4 days ago.
Completeness signal
Latest checked, latest dated application and API source metadata are published with the council record. Document metadata is exposed where the source supplies it.
Machine-readable access
Use GET /v1/councils for coverage metadata and GET /v1/applications?council_id=warrington for application records with an API key.