How to Check Planning Permissions Before Buying Property

Why Planning Data Matters More Than You Think

A couple fell in love with a Victorian terrace in south London. They planned to add a rear extension — the kind every other house on the street seemed to have. After purchasing, they discovered the property sits within a conservation area with an active Article 4 direction that removes permitted development rights for rear extensions. What would have been automatic on the next street over requires a full planning application here, with a 40% refusal rate from the local authority. The extension they budgeted at £45,000 now costs £52,000 including architect and planning fees — and might still be refused.

This scenario plays out across England every week. Planning constraints are invisible to anyone who doesn't know to check them. Conservation areas don't announce themselves with signs at the border. Article 4 directions aren't mentioned in estate agent listings. Green Belt boundaries, Tree Preservation Orders, and SSSI designations all restrict what you can do with a property, and none of them are obvious from a viewing. The data exists in government databases, but it's fragmented across 300+ local planning authorities, each with its own portal and data format.

What the Planning Intelligence Endpoint Returns

The Planning endpoint at /api/v1/planning/{postcode} returns a comprehensive planning profile in one call. The response includes named constraints — not just a boolean "conservation area: yes" but the actual name of the conservation area, plus named Article 4 directions, listed buildings with their grade, Green Belt status, and Tree Preservation Orders. You get planning application data with total applications found, approval rate, refusal rate, pending count, and withdrawn count. There's council performance metrics showing the local authority's determination speed and approval percentage.

The response also includes environmental designations (SSSIs, AONBs, National Parks), flood risk level, and a direct URL to the council's planning portal — so you can drill into specific applications without hunting for the right website. At the top of the response sits the Development Score (0-100), a proprietary rating that synthesises all of this data into a single viability metric.

Standard depth costs 12 credits. Summary (4 credits) gives you the score and key flags. Full (24 credits) adds brownfield site data and mining risk assessment.

Reading the Development Score

The Development Score rates a location from 0 to 100 based on seven weighted factors: constraint density (25%), development momentum (20%), environmental designations (15%), council efficiency (15%), brownfield opportunity (10%), flood risk (10%), and mining risk (5%). It maps to five bands — HIGHLY_CONSTRAINED (0-24), CONSTRAINED (25-39), MODERATE (40-59), FAVOURABLE (60-74), and HIGHLY_FAVOURABLE (75-100).

In practice, a greenbelt postcode within a conservation area near listed buildings might score 12 — development is possible but faces multiple barriers. A brownfield site in an area with 85% approval rate and no environmental designations might score 82 — the council is supportive and constraints are minimal.

The score is most useful for comparing locations. A developer evaluating ten potential sites can rank them by Development Score in seconds, filtering out anything below 40 and focusing due diligence on sites where the planning environment actually supports development. Without the score, this screening requires manually checking each site against half a dozen data sources.

A Practical Example: Checking Before You Build

Here's how you'd check a postcode before committing to a property or development site:

curl -H "Authorization: Bearer ukd_live_YOUR_KEY" "https://www.ukdatapi.com/api/v1/planning/SW1A1AA?depth=standard"

The response tells you immediately whether the postcode falls within a conservation area (and which one), whether Article 4 directions are in force (and what rights they remove), what the recent planning application approval rate is, and what Development Score the location gets. If the score is below 25 and you're planning significant alterations, that's a red flag worth investigating further before you make an offer.

The council_portal_url field gives you a direct link to the local authority's planning portal, so you can look at specific recent applications and their outcomes. If similar extensions or conversions have been approved nearby, your chances improve. If they've consistently been refused, you know the council's attitude before spending money on an architect.

Automating Planning Intelligence at Scale

For individual buyers, a single API call per postcode is enough. But for property developers, conveyancers, and investment platforms, the value compounds at scale. A developer evaluating 50 potential sites can screen all of them in under a minute, ranking by Development Score and filtering out postcodes with critical constraints. This replaces days of manual portal-checking with seconds of automated assessment.

Conveyancing firms can offer clients instant preliminary planning reports within minutes of instruction, rather than waiting days for formal local authority searches. The API doesn't replace the formal search (which carries specific legal protections), but it gives clients actionable information while the formal process runs in the background.

Property investment platforms can enrich every listing with planning context — showing whether a property has development potential or faces constraints that limit future use. At 12 credits per standard call, checking planning data for a hundred properties costs roughly £1.80. The data that would take a human researcher weeks to assemble manually takes the API milliseconds.