Policies map notations that are not designations

A line on a policies map is not a designation. It illustrates the geographical application of a policy, and the policy text is what has legal effect. Regulation 9 of the Town and Country Planning (Local Planning) (England) Regulations 2012 requires a local plan to contain a policies map illustrating geographically the application of the policies in the plan, reproduced from or based on an Ordnance Survey base. That word, illustrating, is doing a lot of work.

Which matters when an officer tells you that the site is "within a green infrastructure corridor" and the policy text turns out to say nothing that bites on a householder extension.

What the policies map must show

The map has to show, on an ordnance base at an identified scale with a national grid reference, where each policy applies. It is adopted with the plan and revised when the plan is revised, which is why a submission version is normally accompanied by a schedule of policies map changes.

It will also carry a good deal of material that is there for information. Conservation area boundaries, listed buildings, flood zones, scheduled monuments and safeguarding directions appear on many policies maps even though they are made under other legislation and would apply whether the map showed them or not. Those are designations with their own statutory source, and an error in how the map draws them does not alter the designation itself. The questions worth asking about rail safeguarding directions illustrate the point, since a direction binds through its own instrument rather than through the plan.

So the first job with any notation is to establish which of three things you are looking at: a boundary that defines where a plan policy applies, a designation made elsewhere and reproduced for convenience, or an indicative annotation that defines nothing.

Where a notation gets its force

Trace it to the policy. Open the written policy that the legend attributes the notation to, and read the operative words. A policy that says "development within the X area will not be permitted unless" gives the boundary real effect. A policy that says "the council will work with partners to improve connectivity across the X network" gives the same line on the map almost none.

The courts have held that the interpretation of development plan policy is a matter of law, to be approached objectively and in its context, which is the principle established in Tesco Stores Ltd v Dundee City Council in the Supreme Court. That cuts both ways. You cannot read a restriction into a policy that is not there, and you cannot read one out because it is inconvenient.

Where the map and the policy text appear to conflict, the text generally governs, because the regulation makes the map an illustration of the policy rather than a free-standing instrument. That is not a licence to ignore a boundary. It is a reason to build the argument around the policy rather than around the line.

Indicative and diagrammatic notations

Local plans carry a long tail of annotations that look like designations and are not. Common ones include:

• Broad locations for growth, shown as a blob or an arrow rather than a boundary.
• Indicative access points on an allocation, which are illustrative and not a requirement to use that point.
• Green infrastructure or wildlife corridors drawn as bands across multiple ownerships.
• Areas of search for minerals, which indicate where resource may exist rather than where extraction is acceptable.
• Safeguarded land, where the policy effect is usually to resist development that would prejudice a future use rather than to prohibit all development.
• Town centre boundaries and primary shopping frontages, where the policy effect depends heavily on which of the two a site sits in.

Several of these are drawn from third-party datasets at a resolution never intended for plot-level decisions, and the caution appropriate to a priority habitat inventory record applies to a corridor drawn on a plan.

The practical test is whether the notation has a boundary that can be measured on the ground. If it cannot, treating it as a constraint on a particular plot is an error of approach.

Strategic diagrams and deliberate imprecision

Many plans open with a diagram showing the spatial strategy: settlements as circles, corridors as arrows, broad directions of growth. A diagram of this kind, often labelled a key diagram, is deliberately not to scale and deliberately without defined boundaries. It is there to communicate strategy.

Reading a site-specific constraint off such a diagram is the most common misuse. An arrow passing across a parcel is not an allocation, a safeguarding or a restriction. If the strategy is to be given effect at a particular site, it will appear in a policy with a boundary, and if it does not appear there, the plan has not yet done the work.

Be careful about the reverse argument too. The absence of a site from a strategic diagram does not make development acceptable, because the plan's development management policies apply across the whole area.

How officers read an unclear notation

Honestly, with variation. A case officer with a GIS system that reports "site intersects: green corridor" will usually ask the applicant to address it, whether or not the underlying policy requires anything. That is a reasonable response to an automated flag and it is not an interpretation.

What helps is doing the work for them. Set out, in two or three sentences in the planning statement, which notation the site intersects, which policy the legend attributes it to, what that policy requires, and how the scheme responds or why the policy is not engaged. Officers are not looking for an argument that the map is wrong. They are looking for a reason they can put in the report.

Where a notation derives from a separate record rather than from the plan, say so and cite the record. An Historic Environment Record search will often explain an archaeological notation better than the map legend does.

Challenging the application of a notation

Four routes, in descending order of usefulness.

1. Argue at application stage that the policy is not engaged on the facts, with the policy text quoted and the site circumstances set out. This resolves most cases.
2. Ask the authority to correct a mapping error. Authorities do make and publish corrections, particularly where a boundary was digitised from a paper plan. Provide the evidence rather than the assertion.
3. Make representations through plan-making. A boundary can be tested at examination, and this is the only route that changes the line itself.
4. Challenge the adoption of the plan under section 113 of the Planning and Compulsory Purchase Act 2004, which has a six-week window and is a high bar. This is rarely the answer for a single boundary.

Appeals are worth noting separately. Inspectors frequently deal with the engagement of a notation as a matter of interpretation, and those decisions indicate how the issue tends to be approached rather than settling it, so present them as such.

Recording the interpretation you relied on

Mapped data changes without announcement, and a dataset that showed a corridor in March may show a different alignment in September. Build a short evidence pack at the start of every project:

1. The adopted policies map extract, with the adoption date, the legend and the sheet or inset reference.
2. A dated screenshot of any online map or dataset used, with the dataset name and version where it is published.
3. The text of each policy the legend attributes a relevant notation to, quoted in full.
4. A one-page note of your interpretation and the reasons for it.

Where a national dataset is the source, the published planning data service is a better record than a council viewer, because it carries provenance and a version. And if you change your interpretation later, keep the earlier note. Explaining the change is easier than explaining its absence.

For the documents an application against a constrained site needs, browse the 66 PlanScope report types and enter your postcode to see which the site is likely to trigger. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.