The 2026 NPPF: reading the new policy-coded structure

The National Planning Policy Framework published on 17 August 2026 replaced paragraph numbering with policy-coded chapters. A citation that used to read as a paragraph number now reads as a code such as GB6, DP2 or PM4. Nothing about the plan-led system changed, and section 38(6) of the Planning and Compulsory Purchase Act 2004 still requires determination in accordance with the development plan unless material considerations indicate otherwise. What changed is how you cite, and how quickly a reader can tell whether your submission is current. This note describes the position as at September 2026.

What the structure change does

Paragraph numbering was always fragile. Each revision renumbered the document, so a citation carried no information about which edition it came from, and a paragraph number in an old officer report could point at completely different policy after a re-issue.

Policy codes are stable identifiers attached to a policy rather than to its position in the running order. Inserting a new policy no longer shifts everything below it. A code also tells the reader which chapter the policy belongs to before they look it up, which is the practical gain in a committee report or a statement of case.

The trade-off is a transition period in which three numbering systems are in circulation: the December 2023 edition, the December 2024 edition and the current coded edition. Anyone working on a scheme that began before August 2026 will meet all three.

Converting an older citation

There is no shortcut that works reliably. Converting a citation means reading the old paragraph, finding the policy in the current edition that does the same job, and checking whether the wording actually survived intact.

Three failure modes are worth watching for.

1. The policy exists but the test has been tightened or relaxed, so the old paragraph supports a submission the new policy does not.
2. The policy has been split across two codes, and citing only one leaves out the qualification.
3. The paragraph was guidance rather than policy and now sits in Planning Practice Guidance instead, where it carries different weight.

Work from the current published text rather than a converted table someone circulated, and verify each code on gov.uk before it goes into a submission. Where a policy is central to the case, quote the sentence you are relying on as well as the code. A quoted sentence survives a later re-issue in a way that a bare code does not.

Documents that still cite superseded numbering

Adopted local plans, supplementary planning documents, validation checklists, committee reports and appeal decisions all contain frozen citations. So do many templates sitting in practice document management systems, and so does the output of any drafting tool built against an older edition.

None of that is a problem provided the citation is labelled. A statement that says "paragraph 11(d) of the 2023 Framework, now reflected in the current edition at code X" is honest and checkable. A statement that quotes a paragraph number with no edition is the one that draws a line in the officer's copy.

The same applies to anything produced with AI assistance. Drafts generated against an older edition will reproduce old paragraph numbers, which is why any draft needs the citations checked against the current Framework before submission. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.

Effect on appeals and committee reports

Inspectors decide appeals on the policy in force at the time of the decision, so an appeal lodged before August 2026 and determined afterwards will be decided against the current edition. Statements of case written against the old numbering need updating before the deadline for final comments, not after.

Committee reports are slower to catch up than appeal work, because report templates carry standing paragraphs that few officers revisit. Expect to see old numbering in reports for some months, and do not treat its appearance as evidence that the officer has applied superseded policy. Read what the report says about the test rather than the number attached to it.

Where a decision does rest on superseded policy, that is a point for the appeal or for representations before committee, and it needs to be put precisely: which policy, what the current edition says instead, and what difference it makes to the outcome.

What did not change

It is worth being clear about the limits of the change, because clients hear "new Framework" and assume the rules have moved. The Framework remains guidance, not statute. It is a material consideration of substantial weight, and it does not override an adopted development plan policy that is up to date and applies to the proposal.

Nor does the re-issue restart any local plan timetable, reopen an adopted policy, or alter a permission already granted. Conditions imposed under an earlier edition stay as they are. A scheme refused in July 2026 and appealed in September is argued on the current edition, but the reasons for refusal remain the council's reasons and the appeal is against that decision.

Checking the edition before you cite

Two habits prevent most of the trouble. Open the Framework from gov.uk each time rather than from a saved PDF, and record the edition date at the head of any policy section you write.

In a Planning Statement, that means a short policy context section naming the edition and date, followed by the codes relied on. Officers reading dozens of statements a month notice which ones do this, and it makes the rest of the document easier to trust.

For tracking what changes next, our planning law timeline is the place to follow reform news, and the Framework itself now signals amendments more clearly than a renumbered PDF ever did.

Keeping a citation table for a live project

On any scheme running more than a few months, keep a single table with four columns: the policy point, the code in the current edition, the wording relied on, and the date it was last checked.

It takes an hour to set up and it pays for itself the first time a re-issue lands mid-application. The alternative is a search through three versions of a statement to find out whether the sequential test paragraph you quoted in March is still the one in force.

Illustrative example: a Green Belt case begun in late 2025 under the December 2024 edition, submitted in September 2026. The statement carried both citations, labelled by edition, with the current codes in the main text and the superseded paragraph numbers in a footnote table for continuity with the pre-application correspondence. The officer report picked up the current codes without asking a question. The same scheme covered the grey belt analysis separately, which our note on what grey belt means in practice works through.

One honest uncertainty

Policy codes are new enough that the conventions around them are still settling. Whether inspectors will expect the chapter name alongside the code, and how sub-paragraphs within a coded policy will be referred to in decision letters, will become clear over the next few months of appeal decisions rather than from any guidance note.

Until then, over-identify rather than under-identify. Give the code, the chapter and the sentence. Nobody has ever lost an appeal for citing too precisely.

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 gov.uk at the time you write.