Using automatic constraint detection as a starting point

An automatic constraint check tells you what the national datasets say about your postcode in about the time it takes to type it. That is useful as a first pass, and it is not a substitute for the searches that follow. Automatic constraint detection draws on published national layers such as the Environment Agency flood maps, the National Heritage List for England and Natural England's designated site data. Those layers are authoritative for what they cover. The problem is everything they do not cover, and most of the constraints that stop a small scheme sit in that second category.

Which datasets a constraint check uses

The national layers are well established and, for the most part, free to view.

• The Flood Map for Planning, which shows Flood Zones 2 and 3 from modelled river and sea flooding.
• The long term flood risk service, which adds surface water and reservoir risk.
• The National Heritage List for England, covering listed buildings, scheduled monuments, registered parks and gardens and battlefields.
• MAGIC, which carries Natural England data including sites of special scientific interest, priority habitat inventory and ancient woodland.
• The national planning data platform, which brings together conservation areas, article 4 directions, tree preservation orders and other datasets supplied by councils.
• Defra air quality data for air quality management areas.

PlanScope checks flood data, listed buildings and conservation areas, and protected site layers, and feeds the result into a rule-based engine that suggests which reports a project is likely to need. The suggestions are a starting point for the application, and the council's validation list and the statutory position take precedence.

What these datasets are good at

Statutory designations with a single national owner are reliable. A listed building has an entry, a grade, a list entry number and a description, and the entry is definitive. Scheduled monuments and registered parks work the same way.

Flood Zones 2 and 3 are modelled nationally and updated periodically, and they decide whether a flood risk assessment is required. Reading them correctly is its own skill, and reading the Flood Map for Planning and what it leaves out covers the traps.

Site designations under nature conservation law are mapped consistently, and ancient woodland inventory polygons are a dependable prompt to commission ecological advice.

For triage, that is enough. You learn within a minute whether a site sits in a flood zone, next to a listed building or inside a designated site, which is exactly what you need before spending money.

The layers are also consistent over time, which matters when you are comparing two plots or explaining to a client why one costs more to develop than the other. Screenshots with the date visible are worth keeping in the project file, because datasets are updated and the map you relied on in March may look different in October.

What they miss, and why local records matter

The gaps are where applications come unstuck. National datasets are assembled from council submissions in many cases, and coverage is uneven.

A conservation area boundary drawn in the 1970s and never digitised is a real thing to trip over. So is an Article 4 direction that removes householder permitted development on an estate where every other house has a rear extension.

Boundary accuracy and the edge of a designation

Polygons are drawn at a scale, and that scale is rarely the scale of your site plan. Flood zone boundaries come from national modelling and should not be read to the metre. A conservation area boundary may follow a historic plot line that no longer matches the fence on the ground. A listed building entry is a point with a description, and the extent of curtilage listing is a legal question rather than a mapped one.

The practical rule is that if your site is near a boundary, treat it as inside until you have evidence otherwise. Ask the council for the boundary as it holds it. For flood risk, the Environment Agency supplies detailed modelled levels for a site on request, and that product, not the online map, is what a flood risk assessment is built on.

Verifying a detected constraint before relying on it

1. Check the council's own policies map and constraints layer for the site.
2. Ask the council directly about tree preservation orders and article 4 directions.
3. Order a Historic Environment Record search where anything suggests archaeology.
4. Contact the local environmental records centre for protected species records.
5. Request detailed flood data where a flood zone is anywhere near the site.
6. Ask the water undertaker about sewer capacity and connection points.

Each of those costs little and takes days rather than weeks. Doing them after a refusal costs a great deal more.

Constraint detection also misses the constraint that is not a designation at all: a restrictive covenant, a shared access, a right of light, an unadopted road with no maintenance agreement. Those come from the title, not from a map. Nor does a check tell you what your neighbours will say, which on a householder scheme is often the constraint that decides the outcome.

When to commission a professional search

Before purchase, always. Before committing to a design on any site with a watercourse, a mature tree, a basement, a neighbouring listed building or an unusual use history. And before a pre-application submission, since going in with an incomplete picture wastes the fee.

Where a constraint is confirmed, the report that follows should be prepared or reviewed by someone qualified for it. The professional directory is the route to a reviewer who can sign off a draft, and the pricing page sets out the single report and Professional options.

An illustrative example: a plot shown as Flood Zone 1 with no designations detected can still need a drainage strategy because it sits in a critical drainage area the council maps and the national layer does not. The automated check was not wrong. It was answering a narrower question than the one that mattered.

Treat the automated output as a list of questions rather than a list of answers. Each detected constraint becomes a check with the body that owns the data, and each blank space becomes a check that the blank is real. Enter your postcode on PlanScope to see the first pass, then work through the verification list above before you commission anything.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.