Why a draft cites a superseded local plan policy

A superseded local plan policy turns up in a draft for a dull reason: policy numbers are recycled. Authorities adopt new plans that replace old ones, the new plan reuses familiar codes like H5, DM12 or CP3 for different subject matter, and a draft generated from general knowledge of an area has no reliable way to tell which document a number belongs to. The citation looks right. It points at the wrong plan.

For an architect producing supporting statements, this is a credibility problem rather than a validation problem. Nothing gets returned for it. The case officer simply stops trusting the rest of the document.

How plan policies are replaced

A local plan is adopted under the Planning and Compulsory Purchase Act 2004, and section 38(6) requires applications to be determined in accordance with the development plan unless material considerations indicate otherwise. The development plan for any site is the adopted local plan or plans, any neighbourhood plan that has been made for the area, and the relevant spatial development strategy in London.

When a new plan is adopted it does not silently overwrite the old one. The adopted document carries an appendix, usually titled a schedule of superseded policies or replaced policies, listing exactly which earlier policies it replaces. Policies not on that list survive. That appendix is the single most useful page in any local plan and almost nobody reads it.

The practical result is that most authorities have a layered development plan: a strategic plan from one date, a site allocations document from another, saved policies from a plan adopted before the 2004 Act reforms, and a made neighbourhood plan for some parishes but not others. Four documents, four numbering systems, one site.

Saved policies and the layered development plan

Saving arrangements are the main source of confusion. When the 2004 Act changed the plan-making system, policies in old-style local plans were saved for a transitional period, and many were then saved further by direction. Some of those policies are still in force today, twenty years on, because the authority has not yet adopted a replacement for that topic.

So an authority might be operating a core strategy adopted in the early 2010s containing policy CS7 on design, alongside saved policy D3 from a local plan adopted in the late 1990s dealing with residential extensions, because the core strategy never covered householder design. Both are part of the development plan. Both carry full weight under section 38(6), subject to consistency with national policy.

A draft that cites only the newest document is incomplete in a different way from one that cites a superseded policy, and both failures look the same to a reader: the author did not check.

Where an authority is mid-review, the position changes month by month. A plan adopted three weeks ago may have replaced the policy you have cited correctly for two years.

Why a policy number can exist twice

Three patterns account for most wrong citations.

The first is renumbering on review. A policy on parking standards sits at T4 in one plan and at DM23 in its replacement, with substantially the same content. Cite T4 and the officer knows you have an old copy.

The second is reuse with different content. A code like H2 might mean housing density in one plan and rural exception sites in its replacement. This is the dangerous case, because the citation looks plausible and the argument built on it is simply about the wrong thing.

The third is the composite reference. Drafts sometimes blend a policy number from one authority with a policy title from another, or attach a core strategy number to a text that came from a neighbouring borough. The giveaway is a policy title that reads slightly oddly for the authority in question.

Illustrative example

Take a householder scheme in a district that adopted a new local plan in 2023. This example is illustrative. The draft cites Policy BE12 on extensions in conservation areas, which was correct until adoption. The 2023 plan replaced BE12 with Policy HE4, and the new wording introduced a test about the proportion of the original dwelling that an extension may occupy, which the old policy did not contain. The design responds to the old test and not the new one. The officer's report assesses it against HE4, finds the proportion exceeded, and the application is refused on a point the applicant never addressed. Nothing in the draft was invented. It was out of date, which produced the same outcome.

Emerging plans and the weight question

A plan that has been published but not adopted is a material consideration, and the weight it carries depends on three things: the stage the plan has reached, the extent of unresolved objections to the relevant policies, and the degree to which those policies are consistent with national policy.

That means a policy in a submission-stage plan with no objections to it can carry real weight, while the same policy at regulation 18 consultation stage carries very little. Examination hearings and the inspector's main modifications change the picture again, and a policy the inspector has signalled will be modified should be cited with that qualification stated.

The useful habit is to cite both, explicitly. Set out the adopted policy, state its date, then note the emerging policy, its stage and the weight you say it carries, with a reason. That approach is defensible whichever way the plan goes, and it reads as the work of someone who has looked.

National policy moves too. The National Planning Policy Framework was reissued in December 2024 and again on 17 August 2026, and the current edition is organised by policy codes rather than by the paragraph numbers readers may remember. Any draft that cites a Framework paragraph number without naming an edition is working from an older copy, and the same discipline applies as to local policy: name the edition, then check it. This is the general problem that drafts get structure right and evidence wrong.

Checking the adopted plan and its policies map

Four sources, in order of reliability.

1. The authority's local plan page. Download the adopted plan itself rather than a summary, and go to the schedule of superseded policies at the back. Note the adoption date from the front cover.
2. The adopted policies map. This is a separate document from the written policies and it is what tells you which site-specific designations apply: settlement boundary, allocation, employment designation, local green space, conservation area. A policy argument that ignores the policies map is half an argument.
3. The national planning data service, which publishes datasets for conservation areas, article 4 directions, listed buildings, local plan boundaries and more, with the source authority and the date of the dataset recorded.
4. The authority's own interactive constraints map, which is usually the quickest way to get a site-specific answer but is not always the most current.

Where the authority has a local list or a validation checklist, download the current version at the same time. Validation requirements change with the plan, and a document list from an earlier project is one of the more common reasons applications come back.

Supplementary documents and their status

Supplementary planning documents are material considerations and are not part of the development plan. They cannot introduce new policy, only amplify what the plan already says, and they carry correspondingly less weight.

This matters when a draft cites a design guide or a parking standards document as though it were policy. The right formulation is that the proposal accords with policy X of the adopted plan, and that the approach is consistent with the guidance in the named supplementary document. Stated the other way round, it invites the officer to point out that a supplementary document cannot carry the argument.

Design codes prepared under the newer plan-making arrangements sit differently again depending on whether they have been adopted as part of a plan or as supplementary guidance, so check which route the authority used.

Neighbourhood plans are part of the development plan once made, and their policies carry the same statutory status as local plan policies. They also go out of date, and some made plans are now more than a decade old.

A verification routine that takes five minutes

Do this before any statement leaves the office.

• Open the adopted local plan and confirm the adoption date on the front cover.
• Check the schedule of superseded policies for every policy number cited in the draft.
• Confirm each policy's title and subject matter against the plan text, not against memory.
• Check the policies map for the site and list the designations that apply.
• Check whether a neighbourhood plan has been made for the parish or ward.
• Record the plan name, adoption date and policy number in the citation itself, in the form Policy HE4 of the adopted local plan (2023).
• Note the edition of the National Planning Policy Framework you are citing.

Where sections of a document are regenerated during drafting, policy citations are exactly the sort of detail that can revert to an earlier version without anyone noticing, so version control when sections are regenerated deserves its own discipline. Keep a single list of verified citations in the project file and check the final document against it.

Drafts produced by PlanScope are grounded in national policy and local plan text and insert a flag where a fact is missing rather than guessing, but the policy citations still need checking against the adopted plan before submission. A Planning Statement carries the policy argument, so a wrong citation there costs more than anywhere else in the pack. Where the pack is going to committee or to a client who will be cross-examined on it, having a reviewer check the policy references is time well spent.

This is general guidance rather than legal advice, so 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.