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.
- Every policy quotation is verified against the published NPPF (August 2026) text at build time. The build fails if any quote cannot be found. This build: 75 nodes and 74 quotations verified.
- Neutral, inspector-style register. Contested readings are shown both ways. Nothing application-specific is in the graph — it is the Framework, not a case for any one site.
- Case matching is by canonicalised policy code against the database below, grouped by finding, with a selection-bias note. Counts show how a test has been applied, never the odds of an outcome.
| Measure | Count | Source |
|---|---|---|
| Decisions read and summarised | 1064 | cases.json |
| by inspectors | 984 | cases.json |
| by the Secretary of State | 2 | cases.json |
| by councils (committee + delegated) | 78 | cases.json |
| Applying the 2026 Framework | 951 | nppf_applied = 2026-08 |
| Transitional (2024 Framework) | 47 | nppf_applied = 2024-12 |
| No Framework version cited | 66 | nppf_applied = not-cited |
| Decision letters in the corpus | 1508 | state.json |
| Awaiting distillation into the database | 0 | state.json |
| Newest decision | 2 October 2026 | state.json |
| Last harvest of new decisions | 2 October 2026 | manifest.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.
| Source | Relation | What it does and how it supports the method | Caveat or watch-point |
|---|---|---|---|
| GapSense analysis, published by The Intermediary (13 July 2026) | Same method | Coded 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-ups | Consistent | Reads 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 base | A 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 Chambers | Legal basis | Permission 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 database | Benchmark | Official 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 consultation | Government practice | The 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 base | Reads 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" | Comparator | A 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.
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.
| Proposition | Agrees | Qualifies | Disagrees | What we did | |
|---|---|---|---|---|---|
SH1 | A local settlement-hierarchy tier ("Local Service Village", "Key Service Centre") carries no weight of its own under the Framework. | 17 | 0 | 0 | Supported. |
SH2 | A village washed over by the Green Belt is not a "settlement" under Annex B, whatever its local tier. | 17 | 1 | 0 | Supported. One wording point taken: Green Belt land goes down the GB6–GB8 route; S5 applies only through S5(5). |
TR | On TR3 and GB7(1)(g)(iii) the quality of the walking route decides, not distance. | 21 | 3 | 0 | Supported. |
S5 | Outside settlements the S5(1) category is the whole case; S5(4) is almost always fatal. | 60 | 9 | 0 | Count corrected: 37 fail / 3 pass at appeal, adding Aston Clinton (6008253). |
SUP | A housing land supply shortfall opens the gate but rarely decides the case on its own. | 53 | 4 | 0 | Softened from "never decides" after Aston Clinton. |
GB | Grey belt is usually won at a village edge; passing GB7 is not approval. | 54 | 2 | 0 | Supported. |
A2 | Annex A ¶2 cuts only the inconsistent part of a plan policy. | 28 | 10 | 3 | Finding changed: spatial restrictions usually lose weight; heritage, design and access keep it (see below). |
DIV | On the same tests, councils pass what inspectors fail. | 4 | 2 | 0 | Little tested by anyone else. |
METH | Decision letters are the main evidence of how the Framework is applied. | 33 | 4 | 0 | Supported, with a caveat on reading outcome rates (see 2.1). |
Where the review changed our analysis#
- Annex A ¶2 (changed). Two Landmark Chambers silks expect the S4/S5 approach to make settlement-based restraint policies materially inconsistent: it is "likely to override all other settlement-based constraint policies" (Reed KC); plans are likely to be inconsistent on "the S4/S5 approach to acceptability in principle" (Warren KC). Livedin agrees: "Most restrictive rural housing policies adopted under earlier editions sit here." We recounted all 96 appeal letters that weigh a plan policy against the Framework. Spatial restrictions (settlement boundaries, countryside restraint) were cut in 30 of 45 letters: 16 for a named conflict with S4/S5, and 13 because housing supply was short, the 2024 "out of date" reasoning carried over. Heritage, design, amenity and access policies kept their weight in 38 of 39. The silks are right about spatial restrictions; the heritage and design half of our finding stands.
- S5(4) and supply (corrected). Aston Clinton (6008253, hearing, 66 homes) passed S5(4) on a substantial supply shortfall, 25% affordable housing and the council's own emerging allocation. Our headline count had not caught up with the case file. It is now 37 fail / 3 pass at appeal, and the supply proposition says "rarely", not "never".
- Reading outcome rates (caveat added). See 2.1: outcome rates reflect which cases reach appeal and by which procedure.
- Still open. Whether need for one type of housing (affordable, older people's) can open S5(1)(j) where five-year supply is met (Cornerstone; Garvey KC); the permissive "adjoining is enough" reading of "physically well-related" argued at the Colwell Farm inquiry (decision awaited); and HO12 giving traveller sites locational flexibility within GB7.
Common misreadings found in published guidance#
- Treating the Annex B "around 800 metres" reasonable walking distance as a test for all walking access. It applies only to the station policies (S5(1)(h), L3, GB7(1)(h)), not to TR3 or GB7(1)(g)(iii).
- Quoting the December 2025 draft as if final: the draft Annex A said "in any way inconsistent", the draft settlement definition had no Green Belt village exclusion, and the draft S5(1)(j) said "well related" without "physically".
- Reading the S5(5) "tilt in favour" after GB7 as approval. It is a presumption that the S5(2) "should be refused" policies can still defeat.
How councils are training officers and members#
- National support is thin. The Chief Planner's August 2026 newsletter says only: "I would encourage authorities to familiarise themselves with the new Framework." Planning Practice Guidance had not been re-keyed to the 2026 policy codes by 2 October. The Planning Advisory Service events we could verify covered the draft; autumn events on the final text are announced but we have not seen their material. Freedom of information releases show the Inspector Training Manual was updated about eight weeks after the December 2024 Framework ("Consolidated Inspector Training Manual on 10 February 2025"); we found no 2026 version in the public domain.
- Council briefings teach the draft. Of the 12 council documents found, only two were written after 17 August 2026. Every council briefing on Annex A that we found used the draft's whole-policy reading: King's Lynn and West Norfolk, policies "in any way inconsistent"; Gedling, inconsistent policies "will be considered out of date and be accorded little weight". The final text says "policies (or parts of those policies) which are materially inconsistent". Inspectors cut clauses; Stratford-on-Avon District Council, in our database, cut whole heritage (CS.8) and access (CS.26) policies.
- Settlements and supply. None of the council or parish training we found explains Annex B or the washed-over village exclusion. A parish handout says development "within settlement boundaries permitted in most circumstances" (Battle Town Council, on the draft). A September 2026 full-council report still frames supply in 2024 terms: "Not meeting the five-year supply means national planning policy takes precedence over local policy" (North East Lincolnshire).
- One council applying the final tests. Three Rivers' inquiry note treats route and topography, not the 800 metre line, as deciding reasonable walking distance, and runs the S5(5) balance with S5(2) after GB7: the approach inspectors take.
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.
| Issue | Arises | Consistent with the test | Differs (borderline) | Differs & allowed |
|---|---|---|---|---|
| 1. DP3(3) design as a "should be refused" policy | 264 | 248 (94%) | 16 (5) | 9 |
| named DP3(3) and asked the clear-justification question | 108 | |||
| found the design harm and dismissed without naming DP3(3) | 140 | |||
| used 2024 design wording | 9 (0) | 2 | ||
| found a design conflict, never asked for clear justification | 7 (5) | 7 | ||
| 2. Heritage harm method (HE6, HE4, HE7) | 236 | 202 (86%) | 34 (13) | 5 |
| 3. Weight given to plan policies (Annex A(2)) | 125 | 98 (78%) | 27 (11) | 8 |
| 4. Location shortcuts in the Green Belt | 137 | 107 (78%) | 30 (17) | 11 |
| 5. Walking routes, stations, access (TR3) | 148 | 112 (76%) | 36 (24) | 25 |
| 6. Which Framework is applied (Annex A(1)) | 905 | 815 (90%) +48 immaterial 2024 wording | 42 applied 2024 | 14 |
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:
- DP3(1) context — the history, character and features of the site and its setting, and integration with its surroundings.
- The relevant DP3(2) principles — (a) liveability, (b) climate, (c) nature and green infrastructure (tree cover), (d) movement, (e) built form, (f) public space, (g) identity and local character.
- An explicit design standard in the development plan — a Village Design Statement, design guide, code or masterplan; DP3(3) gives substantial weight to compliance (the clearest dataset example is 6010826).
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.
| How DP3(3) was handled | Appeals | Outcome |
|---|---|---|
| Named DP3(3) and asked the clear-justification question | 108 | the test applied as written |
| Same result, DP3(3) not named — weighed the design harm as ordinary harm | 92 | all dismissed |
| Same result, DP3(3) not named — dismissed on the local plan (s38(6)) | 48 | all dismissed |
| Differed — used 2024 design wording | 9 | 2 allowed |
| Differed in substance — conflict found, clear justification never asked | 7 | all allowed: Burnett 6005916 (borderline), Cople 6011253, Watlington 6007871 (borderline), Highbury 6005904, Buntingford 6008238 (borderline), West Wickham 6007183 (borderline), Hildenborough 6010459 (borderline) |
| Total | 264 | 9 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:
- Necessity — the conflict is justified only if it is unavoidable to deliver the development (Polegate 6008314 ¶43; at a hearing, Bilsborrow 6007133 ¶59 refused on this reading).
- Level balance — the conflict is justified if the benefits outweigh the harm (Didcot 6009340 ¶22; at a hearing, Aston Clinton 6008253 ¶86 allowed on this reading).
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.
| Issue | Within the Council | vs appeal decisions | What is at stake |
|---|---|---|---|
| 1. DP3(3) as a "should be refused" policy | Reasoning gap | Inconsistent | Alcester 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 Farm | Hard to reconcile | Differs in method | Forest 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.8 | Reasoning gap | Differs in method | Three 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 Belt | Reasoning gap | Differs in method | Tanworth 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 stations | Reasoning gap | Differs in method | None 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 Framework | Reasoning gap | Differs in method | Coverwell 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.