Method & cross-references

How the Navigator was built, the decisions behind it, the external sources its notes have been checked against, and a summary of the inconsistencies the research has found. Counts as of 5 October 2026.

← Back to the NPPF 2026 Navigator

1. How the Navigator was built#

The Navigator is a typed decision graph, authored in TypeScript and compiled to a single graph.json. Each node carries the verbatim policy text, the facts or planning judgements the step needs, and a query into the decisions database. A small pure evaluation engine derives the visible route, the next question, the triggers and harms, and an indicative outcome from the answers entered — it makes no judgement silently; where the Framework leaves a question to the decision-maker, the tool asks it and shows how others have answered.

1064decisions in the database
951apply the 2026 Framework
1508decision letters in the corpus
75 / 74graph nodes / verified quotes
The decisions database (source: index/cases.json, harvest-log/state.json, built manifest.json).
MeasureCountSource
Decisions read and summarised1064cases.json
  by inspectors984cases.json
  by the Secretary of State2cases.json
  by councils (committee + delegated)78cases.json
Applying the 2026 Framework951nppf_applied = 2026-08
Transitional (2024 Framework)47nppf_applied = 2024-12
No Framework version cited66nppf_applied = not-cited
Decision letters in the corpus1508state.json
Awaiting distillation into the database0state.json
Newest decision2 October 2026state.json
Last harvest of new decisions2 October 2026manifest.json

2. External cross-references#

Independent sources our notes have been checked against, and the outcome.

2.1 Sources that support reading decisions as evidence#

Few published sources look at decisions at all; most read the policy text. These are the ones that do, or that back doing so. They are the strongest outside support for the Navigator's method, and each comes with the caveat it raises.

SourceRelationWhat it does and how it supports the methodCaveat or watch-point
GapSense analysis, published by The Intermediary (13 July 2026)Same methodCoded 726 Planning Inspectorate decision letters that mention grey belt (December 2024 Framework) against a fixed frame and derived outcome rates: "Planning policy has to be understood at the level of individual decisions, not ministerial announcements." Like us, it finds that location decides grey belt appeals.Warns that outcome rates reflect which cases reach appeal: "stronger cases reach inquiry in the first place." We now say our route rates are associations across many appeals, not forecasts for one.
Planning Geek — "Presumption in favour of sustainable development" and appeal write-upsConsistentReads individual decisions under the August 2026 Framework almost daily. Every write-up we compared agrees with our coding. Its Aston Clinton note ("It is an individual appeal decision on its own evidence") caught our stale S5(4) count, now corrected.The presumption page slightly overstates how decisive a housing shortfall is (it only opens S5(1)(j); about 40% of (j) passes are allowed), and omits "up-to-date" from the S3(1)(c) route.
Burges Salmon — "The New NPPF: One Month On" (17 September 2026)Same evidence baseA law-firm note built on the first month of appeal decisions: "we are now seeing appeal decisions published which refer to the new NPPF and grapple with its policies."Five hand-picked cases, no counts. Its 6005108 report (spatial-policy conflict reduced to moderate weight because of S5(1)(j)) is one of our Annex A cut cases.
High Court, R (Old Chiswick Protection Society) v LB Hounslow [2026] EWHC 2278 (Admin), reported by Landmark ChambersLegal basisPermission quashed because the officer report did not engage with an inspector's earlier findings. The court: "It benefits no one for officers to give advice or convey judgments, particularly as to material considerations, that they know to have been rejected by a planning inspector."Concerns a previous decision on the same site, not counts across many sites. Appeal decisions are material, not binding precedent.
Planning Inspectorate — "Is your appeal decision written in the stars?" (19 August 2026) and casework databaseBenchmarkOfficial allowed rates for 2025/26 section 78 appeals: 31% overall, 30% by written representations, 53% at hearings, 72% at inquiries. Our inspector permit rate under the August 2026 Framework is about 32%.PINS explains "why headline rates of allowed appeals don’t tell the full story" and warns that small samples per inspector or area can show 100% either way. We show denominators and flag small samples.
Ministry of Housing, Communities and Local Government — December 2025 consultationGovernment practiceThe government itself uses appeal outcomes as evidence of how policy is working: "Since the current Framework was updated in December 2024, an unprecedented 80% of major residential appeals located on grey belt land have been approved".A headline rate with no discussion of selection, the caveat GapSense and PINS raise.
Urbanist Architecture — grey belt appeal digests (updated March 2026)Same evidence baseReads grey belt appeals for lessons and finds "inspectors are applying the Grey Belt policy with growing consistency". Same conclusions as ours on grey belt not being approval and on route safety deciding.Written under the December 2024 Framework. It proposes a distance threshold to a bus stop that we do not adopt: every failure it cites is a route-quality failure.
Livedin — "NPPF 2026 policy test"ComparatorA rules engine built from the 2026 policy text, the nearest public comparator to the Navigator. It checks its readings against appeals: "no decision has had to decide the point, because a supply shortfall was present in every appeal read".Agrees with us on washed-over villages and S5; disagrees on Annex A ¶2, where our recount now largely agrees with it on spatial policies.

All quotations above were checked word for word against saved copies of the sources. All 315 sources reviewed are on the published guidance sources page.

2.2 Review of published guidance (snapshot 2 October 2026)#

We collected the public guidance on applying the August 2026 Framework: government and Planning Inspectorate material, council committee reports and member briefings, barristers' chambers, law firms, planning consultancies, sector and campaign bodies, the trade press and independent writers. Each source was saved, read in full and coded against the nine propositions the Navigator rests on. Every claimed disagreement or qualification was then given to a second reviewer told to knock it down: check the quotation word for word against the saved text, read the context, and recode it if it did not hold.

315sources found
286read in full (262 checked against a saved copy)
37training or briefing material
93about the December 2025 draft

Result. Published guidance broadly supports the propositions. About 211 disagreements or qualifications were coded at first reading; 21 survived the check, and only 3 are outright disagreements, all on Annex A ¶2. Almost all the guidance reads the policy text rather than decisions, so "agrees" usually means agreement with the text, not with our counts. 29 sources were found but could not be read (paywalls or blocked downloads); they are listed but not coded.

Sources taking a position on each proposition, after the check. Sources silent on a proposition are not counted.
PropositionAgreesQualifiesDisagreesWhat we did
SH1A local settlement-hierarchy tier ("Local Service Village", "Key Service Centre") carries no weight of its own under the Framework.1700Supported.
SH2A village washed over by the Green Belt is not a "settlement" under Annex B, whatever its local tier.1710Supported. One wording point taken: Green Belt land goes down the GB6–GB8 route; S5 applies only through S5(5).
TROn TR3 and GB7(1)(g)(iii) the quality of the walking route decides, not distance.2130Supported.
S5Outside settlements the S5(1) category is the whole case; S5(4) is almost always fatal.6090Count corrected: 37 fail / 3 pass at appeal, adding Aston Clinton (6008253).
SUPA housing land supply shortfall opens the gate but rarely decides the case on its own.5340Softened from "never decides" after Aston Clinton.
GBGrey belt is usually won at a village edge; passing GB7 is not approval.5420Supported.
A2Annex A ¶2 cuts only the inconsistent part of a plan policy.28103Finding changed: spatial restrictions usually lose weight; heritage, design and access keep it (see below).
DIVOn the same tests, councils pass what inspectors fail.420Little tested by anyone else.
METHDecision letters are the main evidence of how the Framework is applied.3340Supported, with a caveat on reading outcome rates (see 2.1).

Where the review changed our analysis#

Common misreadings found in published guidance#

How councils are training officers and members#

Others analysing decisions#

See 2.1. We found no one else counting findings test by test under the August 2026 text, or comparing councils with inspectors on the same tests.

3. Inconsistencies found#

Two strands of work. The first tests every appeal decision in the database against the Framework. The second compares Stratford-on-Avon District Council's own decisions — both against each other and against appeal decisions.

Across all appeal decisions#

Every appeal in the database — 984 Planning Inspectorate and 2 Secretary of State decisions — was tested against six issues drawn from the Stratford note. All 1027 quotations in the per-case tables were machine-checked against the letters, and all matched. "Differs" mostly means a different route to the same result; it changes the outcome only where the appeal was allowed. Issue 1 is broken out: a letter that finds the design harm and dismisses has done what DP3(3) directs ("should be refused") whether or not it names the policy, so it counts as consistent and is shown on its own line. Full detail: the Council-decisions review page.

Source: analysis/appeals-consistency-review.md and appeals-review/issue-1..6.tsv.
IssueArisesConsistent with the testDiffers (borderline)Differs & allowed
1. DP3(3) design as a "should be refused" policy264248 (94%)16 (5)9
named DP3(3) and asked the clear-justification question108
found the design harm and dismissed without naming DP3(3)140
used 2024 design wording9 (0)2
found a design conflict, never asked for clear justification7 (5)7
2. Heritage harm method (HE6, HE4, HE7)236202 (86%)34 (13)5
3. Weight given to plan policies (Annex A(2))12598 (78%)27 (11)8
4. Location shortcuts in the Green Belt137107 (78%)30 (17)11
5. Walking routes, stations, access (TR3)148112 (76%)36 (24)25
6. Which Framework is applied (Annex A(1))905815 (90%) +48 immaterial 2024 wording42 applied 202414

Borderline cases are marked where the required step is missing but the result would plainly be the same (e.g. Lydiard Millicent 6001260 on TR3, issue 5).

Issue 1 — DP3(3), broken down#

DP3(3) makes a proposal "should be refused" if, without clear justification, it conflicts with any one of three things:

Of the 264 appeals where design harm arose, 248 (94%) are consistent with DP3(3): 108 name it and ask the clear-justification question, and 140 find the design harm and dismiss by another route. The full split is below. Only the last two rows change an outcome; the middle two reach the result DP3(3) directs and are not errors.

Source: analysis/appeals-consistency-review.md, issue 1.
How DP3(3) was handledAppealsOutcome
Named DP3(3) and asked the clear-justification question108the test applied as written
Same result, DP3(3) not named — weighed the design harm as ordinary harm92all dismissed
Same result, DP3(3) not named — dismissed on the local plan (s38(6))48all dismissed
Differed — used 2024 design wording92 allowed
Differed in substance — conflict found, clear justification never asked7all allowed: Burnett 6005916 (borderline), Cople 6011253, Watlington 6007871 (borderline), Highbury 6005904, Buntingford 6008238 (borderline), West Wickham 6007183 (borderline), Hildenborough 6010459 (borderline)
Total2649 allowed where it differed

What "clear justification" means is unsettled; inspectors read it two ways, and no Secretary of State or court decision has settled which is right:

Either reading is stricter than the S4/S5 "substantially outweighed" test, which favours approval. The Navigator now takes this in two steps — a checklist of what the scheme conflicts with, then the clear-justification call — mirroring this breakdown.

Stratford-on-Avon District Council's own decisions#

The Stratford note works through six issues, each looked at two ways: whether the Council is consistent with itself, and whether it matches how inspectors decide the same question. The sharpest contrast is on walking routes: Alcester ✓ treated a policy failure as a "should be refused" trigger and refused, while Snitterfield ✗ found character harm but granted without asking whether there was clear justification.

Source: pages/authority/stratford-dc/nppf-decisions/build/note.md.
IssueWithin the Councilvs appeal decisionsWhat is at stake
1. DP3(3) as a "should be refused" policyReasoning gapInconsistentAlcester refused on a flood trigger; Snitterfield (granted) found "significant harm to the character of the area" but cited DP3(3) only for weight, never asking whether there was clear justification. Inspectors (Kings Langley, Hook-a-Gate, Ware) treat a DP3 design conflict as engaging DP3(3) and refuse.
2. Heritage harm at Forest FarmHard to reconcileDiffers in methodForest Farm found HE6 and 1990 Act conflict then granted in the S4 balance; Ilmington weighed the harm and refused. Inspectors (Hunmanby, Bagnall, Smarden) weigh heritage harm on its own terms.
3. Reason given for discounting CS.8Reasoning gapDiffers in methodThree reports declared CS.8 "materially inconsistent" without saying which part conflicts, then relied on CS.8 anyway. Annex A(2) reduces weight only for the conflicting part.
4. Location shortcuts in the Green BeltReasoning gapDiffers in methodTanworth ran the S5(1)(j) "well-related to a settlement" test on a washed-over village; Earlswood passed GB7(1)(g)(iii) on a boundary line. S5 does not decide Green Belt cases (S5(5)); Annex B excludes washed-over villages from "settlement".
5. Walking routes and stationsReasoning gapDiffers in methodNone of the reports uses the Connectivity Tool or tests the actual route; both lean on Local Service Village status as proof of sustainability. Inspectors decide on the route: a 350 m station did not save Hatton, a named service village did not save Findon.
6. Reports written under the 2024 FrameworkReasoning gapDiffers in methodCoverwell Farm applied the 2024 Framework on 17 August; Kineton and Oxhill kept the 2024 balance. Annex A(1): the 2026 policies apply from the day of publication.

What the labels mean. Inconsistent: comparable facts, opposite answers to the same Framework question. Hard to reconcile: the conclusion does not follow from the decision's own findings. Reasoning gap: a required step is missing or the stated reason is wrong (the result may still be defensible). Differs in method: the Council applies a different test from the one inspectors apply — refusals reasoned this way risk being overturned at appeal; grants are open to challenge.