The limits of automatic planning constraint detection

An automatic constraint check tells you what the national datasets hold about a point on a map. It does not tell you what applies to your site. Those are different statements, and the gap between them is where self-builders lose money. PlanScope checks a site against Environment Agency flood data, Historic England listed buildings and conservation areas and Natural England designations, and feeds the results into a rule-based engine that flags which reports a project is likely to need. That is a useful first pass. Treating it as a land search is the mistake.

Three kinds of limit matter: how precisely a boundary is drawn, which designations are held locally rather than nationally, and how recently each dataset was refreshed.

What positional datasets can tell you

Open constraint data is good at answers of the form: this point falls inside a published polygon, or this point lies a measured distance from a published record. Flood zones, conservation areas, national park boundaries, sites of special scientific interest and local plan boundaries that have been published as data all behave that way, and a check against them is reliable to the precision of the polygon.

The useful output is a shortlist of questions. If the site sits in Flood Zone 2, a Flood Risk Assessment is almost certainly required and the drainage strategy becomes a live issue. If a conservation area polygon covers the plot, design and materials move to the front of the application. The flag is the prompt, and the work follows.

Boundary precision and the edge case

Polygons have edges, and the edge is where the arithmetic stops helping. Conservation area boundaries were drawn on paper plans, sometimes decades ago, and digitised later. A boundary that follows the back of a garden wall can sit a metre or two either side of where the wall actually stands. A plot shown as 3 metres outside may be inside on the adopted map.

Listed buildings are worse, because the National Heritage List records a grid reference for each entry. A distance to the nearest listed building is a distance to that point. It is not a distance to the building's curtilage, to its boundary wall, or to the listed railings that may be covered by the same entry. And setting has no boundary at all. The duty under section 66 of the Planning (Listed Buildings and Conservation Areas) Act 1990 applies to the setting of a listed building, which is a matter of judgement about views, approach and historic relationship, so no dataset can draw it for you. Where a designated asset is anywhere near, a Heritage Statement is the document that tests the question properly.

Designations held locally

A national dataset only contains what has been published nationally. Several of the constraints that most often change an application are made and held by the council:

• Tree preservation orders, which are made by the local authority and in many areas are not published as open data at all.
• Article 4 directions, which withdraw permitted development rights for a defined area. Coverage on the national planning data platform has improved and remains incomplete.
• Locally listed heritage assets and conservation area appraisals with character sub-areas.
• Local wildlife sites, local green space allocations and protected open space.
• Critical drainage areas identified by the lead local flood authority.
• Historic environment record entries and archaeological priority areas.
• Settlement boundaries and site allocations in an emerging plan that has not yet been published as data.

An automatic check that returns no constraints on a plot inside an Article 4 area is not wrong about the data. It is silent about the one fact that removes your permitted development rights.

Data currency

Designations are made continuously. A tree preservation order can be served in a week. A conservation area can be extended at committee. New listings are added to the national list regularly, and flood mapping is updated as modelling improves.

Each dataset has its own refresh cycle, and a cached copy in any tool is a snapshot. The practical rule is to re-check anything time-sensitive at the point you rely on it rather than at the point you first looked, and to check again before submission if months have passed. Applications returned as invalid often turn on exactly this kind of staleness, and our note on why planning applications are returned as invalid covers the commonest causes.

An illustrative conservation area edge example

Illustrative example. A self-builder buys an infill plot at the end of a terrace. An automatic check reports the plot as outside the conservation area, with the boundary running along the rear of the terrace about 4 metres from the plot edge, and the nearest listed building 80 metres away.

Three things turn out to be true on the adopted map. The boundary follows the garden wall, which was rebuilt in a different position in the 1980s, putting a corner of the plot inside the area. The listed building 80 metres away is a former chapel whose grid reference sits at its centre, and its listed boundary railings run along the far side of the lane, 30 metres from the plot. And the terrace is covered by an Article 4 direction removing householder rights, made two years ago and not present in the national data.

None of those is a failure of arithmetic. All three change the application: design review on materials and fenestration, an assessment of effect on the setting of a designated asset, and no permitted development fallback to argue from.

Why a search is still needed

The authoritative record of what affects a site sits with the council and with the statutory registers. A local land charges search, a constraints enquiry to the planning department, and a look at the council's own interactive map together give you what a national dataset cannot. Pre-application advice is the other route, and on a site with heritage or flood issues it is usually worth the published fee.

Ordering a search also creates a record of what you were told and when, which matters if a dispute arises later.

Verifying each flagged constraint

Work through the flags one at a time against the primary source.

1. Flood zone: check the Flood Map for Planning for the planning zone, and the long term flood risk service for surface water and reservoir risk, which are separate datasets.
2. Listed buildings and scheduled monuments: open the National Heritage List entry and read the description, because it tells you what is actually listed.
3. Conservation area: ask the council for the adopted boundary map rather than relying on a digitised polygon.
4. Protected trees: ask the council directly for tree preservation orders affecting the site and adjoining land.
5. Permitted development rights: ask whether an Article 4 direction applies, and whether any previous permission removed rights by condition.
6. Ecology and designated sites: check the national mapping, then ask the local record centre for species and local site records.

A draft report built on top of unverified flags inherits every one of their limits, which is why PlanScope inserts a TO BE CONFIRMED marker rather than inventing site data, and why the drafting is described as AI-assisted. Where a constraint turns on judgement rather than data, a reviewer from the professional directory is the right person to settle it.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it.