Why refusals are the underused signal
Approved applications tell you what's already happening. Refused applications tell you where the friction is — and friction is where opportunity and risk both live. Yet most investors and data tools only surface grants, partly because refusal data is genuinely harder to capture cleanly from council portals (councils word refusals dozens of ways). That gap is the edge: if you can see refusals reliably, you see things your competition doesn't.
Three things a refusal tells you
1. A motivated owner
Someone applied to develop or extend, and was turned down. That owner now holds a property that's harder to improve than they hoped. Some will resubmit; some will decide to sell and move on. A refused application is one of the few public signals of a frustrated owner — months before any for-sale listing.
2. The site's real constraints
The refusal reasons are a free due-diligence report. Was it scale and massing (fixable with a better scheme)? Or a fundamental constraint — conservation area, highways, flood risk, green belt — that no design solves? Reading refusal reasons across a street tells you which sites are genuinely developable and which are traps.
3. How strict the council actually is
Two neighbouring councils can have very different appetites. A council refusing 25% of applications is a different risk profile than one refusing 6%. Knowing a council's real refusal rate — and for which application types — lets you price planning risk into an acquisition before you bid.
UK councils refuse roughly 10–15% of decided applications on average — but the range by council and application type is wide. That variance is exactly what you want to underwrite *before* committing to a site.
Using refusal data in practice
With coverage across every UK planning authority, you can filter directly for refusals in your target markets:
curl "https://api.planwire.io/v1/applications\ ?council=guildford\ &status=Refused\ &date_from=2026-03-13\ &limit=100" \ -H "X-API-Key: your_api_key"
Each result carries the address, coordinates, the proposed works, and a link to the council record with the full decision notice and refusal reasons. Pull it per district, score the reasons, and you have a ranked list of approachable owners and constraint-mapped sites.
The compounding use case: monitor refusals continuously
A one-off pull is useful; a standing feed is a pipeline. Investors running this seriously monitor refusals across their whole target geography on a schedule (or via webhook), so a relevant refusal lands the day it's published — not when an agent eventually circulates the site. That's the difference between reacting to the market and moving ahead of it. See our guides on finding sites with planning data and setting up planning alerts.
From signal to decision
Refusal data doesn't make the decision — it sharpens it. Combine it with the full planning history of a site, ownership from Land Registry, and the council's track record, and you're underwriting planning risk with evidence instead of optimism. The investors who win on planning aren't the ones chasing approvals — they're the ones reading the refusals.