Correcting an error in a published constraints layer

Constraints layer error correction runs through the body that holds the primary record, not through the local planning authority. That is the single thing worth knowing before you spend a week emailing the wrong people. A case officer cannot amend a listed building's extent, move a flood zone boundary or redraw an SSSI. The custodian of the record can, and each designation has a different one.

What a council can do is accept your evidence for the purposes of your application. Those are two separate pieces of work, and on a live application you usually want both: the submission dealt with on the correct facts now, and the dataset fixed so the next application on the street does not repeat the argument.

How constraints data is compiled and why it drifts

Published constraints layers are aggregations. A national platform pulls datasets from national bodies and from hundreds of local authorities, normalises them and publishes them together. Commercial search reports do the same thing with a different interface.

Drift comes from four places. Digitisation, where a boundary drawn on a paper plan at 1:10,000 was traced into a geographic information system and gained or lost several metres. Latency, where a designation was amended but the published layer still carries the old version. Attribute errors, where a grade, a date or a reference number was transcribed wrongly. And generalisation, where a point has been used to represent an area, which is how a listed building's curtilage ends up looking like a 10 metre circle.

None of these are unusual, and none of them mean anyone was careless. A national dataset assembled from hundreds of sources at different vintages will contain errors, and the published platforms say as much.

Spotting an error against the primary source

The test is always the same: compare the layer against the record it was derived from. If you have not looked at the primary record, you do not yet know there is an error.

Two details catch people out. A listed building's record describes the building, and the law extends protection to structures within the curtilage that pre-date 1 July 1948, so the mapped point or polygon is not the legal extent. And a conservation area boundary is defined by the designating resolution and its plan, so a later appraisal that shows a different line may itself be the error.

Which body holds each dataset

Having identified the custodian, find the right route in. These differ in formality and in speed.

Historic England operates a process for amending list entries, used for factual corrections, clarifications of extent and changes to a description. It is evidence-led and slow. It does produce an amended entry, which then flows into the published layers.

The Environment Agency will review a Flood Map for Planning boundary where you submit hydraulic modelling or survey evidence showing the mapped extent is wrong at the site. In practice this is done through a site-specific flood risk assessment that the Agency then accepts, and the published map may be updated at the next modelling refresh rather than immediately.

Natural England holds SSSI boundaries and the Ancient Woodland Inventory, and both have correction routes requiring ecological or documentary evidence.

For council-held data, the route depends on the designation. A Tree Preservation Order error is corrected by inspecting the sealed Order, which is the definitive document; if the Order's own plan is wrong the council may need to make a new Order. A policies map error needs the plan-making process, and getting an error on the policies map corrected is a long route that is still worth starting.

Aggregator platforms generally publish a route to report a data issue, and reporting it there is useful because it flags the discrepancy for other users. It does not change the underlying record.

The route to request a correction

A correction request that succeeds looks much the same whichever custodian receives it.

1. State precisely what the published layer says, with a dated screenshot or extract and the dataset name.
2. State what the primary record says, with the entry reference, the resolution date or the model reference.
3. Provide survey evidence: a topographical survey with the asserted boundary plotted from coordinates, referenced to a datum.
4. Explain the mechanism of the error, whether digitisation, latency, attribute or generalisation.
5. Say what you are asking for in one sentence.
6. Say whether an application is pending and when it is due to be determined.

That last point matters. Custodians prioritise differently when a live decision depends on the answer, and the request should be honest about the interest rather than presenting itself as disinterested public service.

An illustrative example

Illustrative only: an architect finds a published layer showing a Grade II listed building polygon overlapping the rear 2 metres of a client's garden, where the building itself is 40 metres away across a lane. The National Heritage List for England entry describes the building alone and its map shows a point, with the polygon generated by a buffer. The architect submits a topographical survey plotting the lane, the list entry text and a dated extract of the layer, asks Historic England to confirm the extent of the listing and asks the council to determine the application on the basis that the garden is not within the curtilage. The application proceeds. The layer is corrected at a later release.

Proceeding while a correction is pending

Do not wait. Corrections take months and your client has a programme.

The approach that works is to submit on the correct facts, show your working, and deal with the published layer explicitly. Put the survey overlay in the application documents. State in the planning statement that the published layer is inconsistent with the primary record, identify which, and set out the correction request and its date. Where the constraint would have triggered a report, consider submitting a short version of that report anyway as a precaution, because it costs less than a re-consultation.

Where flood zone mapping is the issue, a site-specific Flood Risk Assessment is the orthodox answer: national guidance expects site-specific assessment to refine the mapped position, so you are using the intended mechanism rather than arguing with a map. Where heritage extent is the issue, a Heritage Statement that addresses significance on the correct basis, with a fallback assessment if the wider extent were right, closes the point either way.

Recording the discrepancy in the submission

Write it down in the documents, not in an email to the case officer. Emails do not survive a change of officer and they do not appear in the committee report.

A short paragraph naming the dataset, the date of the extract, the primary record and the asserted position is enough. Add the correction request reference once you have one. If the application later goes to appeal, that paragraph is the evidence that the point was raised and reasoned from the start.

Browse the index of report types if you are working out which documents the corrected constraint position changes.

When an error becomes a ground of appeal

A refusal based on a constraint that does not apply is a refusal based on an error of fact, and that is a strong appeal case. It is strongest where you raised the discrepancy with evidence before determination and the authority did not engage with it.

It is much weaker where the point is raised for the first time at appeal. Inspectors deal with the planning merits on the evidence before them, and an applicant who discovers the error after refusal has to explain why the survey was not commissioned earlier. Raise it early, in writing, in the application documents.

Enter your postcode on PlanScope to see the constraints detected at a site and which reports they are likely to trigger, then check each against its primary record before you rely on it.

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.