Errors on a policies map and how to deal with them

A policies map error is fixable, but rarely quickly, and the route depends on whether the map or the written statement defines the boundary. Under the Town and Country Planning (Local Planning) (England) Regulations 2012, the adopted policies map illustrates geographically the application of the policies in the adopted development plan. Illustrates. Where a policy defines its own boundary in words, the words govern and the map is a drawing of them. Where the policy says nothing and relies on the map, the line on the map is the designation, mistake and all.

Start by working out which of those two situations you are in. Everything else follows from it.

Common causes of mapping error

Most errors are clerical rather than policy-driven, and knowing the mechanism helps you argue the point.

Digitising from paper is the largest single source. Boundaries drawn by hand on a 1:10,000 paper plan in the 1990s were traced into a geographic information system at a scale the original never supported, and a pencil line 0.5 mm wide covers five metres on the ground.

Base map drift is the second. Ordnance Survey data is revised, buildings are demolished and rebuilt on slightly different footprints, and a designation boundary snapped to a wall that no longer exists ends up floating. Field boundaries that have been grubbed out cause the same problem on rural sites.

Then there is the plan-making process itself. Examination main modifications change allocation boundaries, and the modification schedule is text. If the map was not revised to match, the two documents disagree from the day of adoption. Saved policies inherited from a superseded plan are the other recurring culprit, because the map for the new plan sometimes carries the old lines forward without anyone checking them.

Clipping and topology errors round out the list: slivers between adjoining designations, a conservation area boundary that runs down the centre of a road rather than the back of the pavement, and polygons that were never closed.

Digitising errors against genuine policy boundaries

Do not assume an odd line is a mistake. Settlement boundaries are frequently drawn to historic field boundaries, drainage ditches or the rear of curtilages rather than to anything visible today, and that can be entirely deliberate.

Three tests separate the two. First, does the line follow a feature that existed at the date of the plan it came from, even if it has gone now? Second, is the anomaly consistent across the whole plan area, which points to a systematic transformation error, or is it confined to your site, which points to a deliberate decision? Third, does the supporting evidence base, the site assessment or the inspector's report say anything about where the boundary was intended to run?

A boundary that excludes precisely the part of a garden a previous applicant wanted to develop is usually intentional. A boundary that misses every building on the street by the same four metres in the same direction is a projection problem.

What the adopted written statement governs

This is where a careful reading pays. Some policies are self-defining: a policy protecting employment land at sites listed in an appendix, or a policy applying within 400 metres of a designated habitat, carries its own boundary in the text. The map is then evidence of where the authority thinks the text applies, and it can be wrong without changing the policy.

Other policies are map-dependent. Green Belt inner boundaries, settlement limits and allocation boundaries normally exist only as lines. There is no text to fall back on, and the line is the designation.

The interpretation of development plan policy is a matter of law rather than planning judgement, as the Supreme Court held in Tesco Stores Ltd v Dundee City Council [2012] UKSC 13. That principle is what lets you argue that the written statement prevails over the drawing where the two conflict. It does not help you where the drawing is the policy.

Evidence to assemble before raising it

Build the file before you write to anyone. Officers respond to a documented anomaly and ignore an assertion.

1. The adopted policy wording in full, with the reasoned justification and any glossary definition of the designation.
2. The adopted policies map extract at a usable scale, plus the published spatial data layer if the authority releases one. Check what is published as authoritative on the national planning data service as well as on the council's own map.
3. The equivalent extract from the previous plan and any saved policies map, to trace where the line came from.
4. The submission version map, the schedule of main modifications and the inspector's report, to test whether the map was updated to match the examination outcome.
5. A topographical survey or measured title plan for the site, georeferenced, showing the actual position of the features the boundary appears to follow.
6. Historic mapping and aerial imagery at the date of the earlier plan.

Present it as a single note with an overlay drawing. One page of reasoning, one drawing, one ask.

Who to approach and in what order

Go to the planning policy team first, not development management. The case officer cannot change the map and has no mandate to interpret it against the council's published position.

Ask the policy team for a written view on which document governs the boundary at your site, and for confirmation of what the council treats as the definitive spatial dataset. That written view is the thing you actually need, because it can go in front of the case officer, a committee or an inspector.

If the policy team will not engage, escalate to the head of planning, and raise it formally through the council's corrections or feedback process where one exists. The Monitoring Officer becomes relevant only where the council is proceeding on a basis it knows to be wrong. Keep all of it in writing and keep it civil, because you may be back next year on a different site.

There is also a hard deadline worth knowing. A challenge to the adoption of a plan under section 113 of the Planning and Compulsory Purchase Act 2004 has to be brought within six weeks of adoption. Miss it and the plan, including its map, is not open to that kind of attack.

Correction at review against immediate resolution

Formal correction usually waits for the next plan or a focused review, because the policies map is revised when a development plan document is adopted. That is years, not weeks.

The interim options are narrower than clients expect. An authority can publish a correction or erratum note acknowledging a drafting error, it can confirm in writing that the written statement governs, or it can simply determine applications on the correct basis and record why in the officer report. None of these changes the map, and all of them are within the council's gift rather than yours.

Accept that distinction early. Your realistic objective is a written council position you can rely on for this application, with the map correction as a separate, slower piece of work.

How to proceed with an application meanwhile

Run the application on the correct interpretation and evidence the alternative. Set out in the Planning Statement why the written statement governs, what the boundary should be, and how the proposal performs against the policy even if the council's line is taken at face value. Arguing only the interpretation point leaves you with nothing if you lose it.

Ask for the officer report to record the mapping issue expressly. If the application is refused on the designation, the interpretation question goes to the inspector as a matter of law, and a documented pre-decision exchange with the policy team is worth more than a late submission.

Constraint checking at the acquisition stage prevents most of this, which is the subject of our note on checking a site for constraints before you make an offer. Mapped designations with no written definition behave the same way, whether the line is a safeguarded transport route or a green corridor in a local plan. Where the designation triggers technical evidence, the full list of report types is the quickest way to scope it.

This is general guidance rather than legal advice. Development plan interpretation and plan challenges need advice on the facts, so check the position with the local planning authority and take legal advice before relying on any of it.

Working out which reports a constrained site needs? Enter your postcode on PlanScope and answer a few questions to see the likely list. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.