Policy codes in the Framework and older paragraph numbers

Citing a National Planning Policy Framework paragraph number without naming the edition is now a mistake, because the number alone no longer identifies anything. The Framework was renumbered in December 2024 and restructured again on 17 August 2026, and the current edition uses policy codes such as GB6, DP2 and PM4 in place of sequential paragraph numbers. A statement that refers to "paragraph 11" tells the reader nothing about which test is meant.

The practical work is translation. You will be reading local plans, conditions, consultee advice and appeal decisions written against two or three earlier editions, and writing documents that have to be read against the current one. Doing that carefully takes a checking routine rather than a good memory.

Why the Framework was restructured

Sequential paragraph numbering is unstable by design. Insert a paragraph in chapter five and everything after it shifts, which is why the December 2024 edition broke thousands of citations in adopted plans, supplementary documents, section 106 agreements and standing advice.

Coded policies solve that. A code attaches to a policy rather than to its position in the document, so new material can be added without renumbering what already exists. The trade-off is a transition period in which two conventions are in circulation, and that period is where the errors happen.

For the reader of your document, the consequence is simple. Codes are stable and paragraph numbers were not, so from here on a citation should carry the code, the edition and, where the point is fine, the words themselves.

Mapping an old paragraph number to a current policy code

Do not look for a concordance table and trust it. Work from the substance.

1. Identify the test the old paragraph contained, in its own words, from the edition that document was written against
2. Search the current Framework for those operative words rather than for a number
3. Confirm which chapter the test now sits in, and read the whole policy rather than the sentence you were looking for
4. Compare the wording, not just the label, because restructuring has moved some tests and changed others
5. Record whether the old paragraph has become one policy, split across two, or disappeared

That fifth step is the one people skip. Restructuring is rarely a pure relabelling exercise. A test can survive with identical wording, survive with a changed threshold, be split between a strategic policy and a development management policy, or be dropped. Presenting a changed test as though only its number had moved is a substantive error, not a citation error.

Citing the edition every time

Adopt a house convention and apply it without exception. Name the Framework, give the edition by date, then the policy code: the Framework of 17 August 2026, policy GB6. For older material, cite the edition that applied at the time.

Three places where the discipline is worth the effort. In the policy compliance table, where a reader scanning the document needs to know which test is being applied. In any quotation, because a quotation attributed to the wrong edition is worse than a paraphrase. And in any statement that will be read at appeal, where the inspector may be working from a different copy than the one on your desk.

Verify the code against the published Framework on the day you write, rather than against your last submission. Our note on grey belt and what the term means in national policy shows how quickly the substance behind a label can move between editions.

Documents that still quote superseded numbering

Most of the documents you have to work with will never be updated. Adopted local plans quote the edition current at examination. Section 106 agreements and conditions quote whatever was live at completion. Consultee standing advice is updated on its own cycle.

Handle each in the same way: read the citation as it stood at the time, then state the current position alongside it. A sentence such as "policy DM12 of the adopted plan applies the test then in paragraph X of the December 2024 Framework, now carried in policy code Y" is longer than the alternative and stops an officer having to do the work themselves.

Conditions deserve particular care, because a condition citing a superseded paragraph is still binding as drafted. The national tests on necessity, relevance and precision apply regardless, as covered in our note on the national restrictions on drafting conditions.

Local plans made under earlier editions also raise the question of consistency with current national policy, which affects the weight their policies carry. That is a separate argument from the citation question, and it is worth keeping the two apart in the document.

Appeal decisions that predate the change

An inspector applied the wording in front of them on the day. That is the first thing to establish before relying on any decision.

State the edition the decision was made under, identify the test as it then stood, and say whether the same test survives in the current Framework. Where it does not, the decision may still be useful as an illustration of how a planning judgement was approached, but it cannot carry the weight of a decision on the current test.

Two cautions. Appeal decisions are indicative of how inspectors have approached an issue rather than binding precedent, so avoid presenting one as settling anything. And check the decision date against the edition dates rather than assuming, because a decision issued shortly after a new edition may have been determined under transitional arrangements or may record submissions made under the previous version.

A checking routine before submission

Make this a task with an owner, done on the finished document rather than during drafting.

• Extract every national policy citation into a list before checking any of them
• Confirm each code exists in the current Framework, on the day of the check
• Confirm the edition is stated at the first citation and in any quotation
• For each citation carried over from a precedent document, re-derive it from the substance rather than accepting the reference
• Flag any citation you could not verify, and rewrite the sentence so the argument stands without it
• Note the date of the check in the file

One specific warning for anyone working from drafted output. Automated drafting frequently reproduces national policy references from earlier editions, because that is what the underlying material contained. PlanScope's own generated text can include paragraph numbers written against the December 2023 edition, which is why a draft should never be submitted with a policy reference carried straight through. Check every one against the current published Framework and cite the edition. The planning law updates timeline is a reasonable place to follow reform news, and weight questions for locally made plans are covered in our note on neighbourhood plan weight, review and referendum.

As an illustrative example, a Green Belt statement drafted from a 2023 precedent cites two paragraph numbers and a phrase about very special circumstances. The reviewer re-derives both from the substance, finds the first now sits in a coded Green Belt policy with the same operative words, finds the second has been reworded, quotes the new wording, and adds the edition date at the first citation. Total time, twenty minutes. Value, a statement that an inspector can follow without cross-referencing an old copy.

The document types those policies sit inside are listed under the 66 report types by category. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it, and verify every policy code against the published Framework on the date you rely on it.