🧠 Refusal Pattern Browser
Planning officers reuse language. Councils share boilerplate. This page surfaces the patterns mined from 18,321 PINS appeal decisions — what phrases get reused, which policies get cited, and which cross-council templates dominate refusals.
⚖️ Your right to challenge generic refusals — the rules that bind the planner
Planning officers using generic catchphrases ("character and appearance of...", "contrary to policy", "harm to the openness of...") without identifying the specific feature, evidence, or measurable harm is challengeable. The system has rules — most planners assume applicants won't read them.
📜 What the rules actually require
- Statutory duty to give reasons — Article 35(1)(b) of the Town and Country Planning (Development Management Procedure) Order 2015: refusal notices must state "clearly and precisely" the full reasons. Generic phrases without specificity fail this test.
- NPPF para 135 — "Decisions should not refuse otherwise acceptable development on design grounds." Quote this back whenever the refusal hides behind vague design language.
- NPPF para 38 — Decision-makers must "approach decisions in a positive and creative way" and "work proactively with applicants to secure developments". Refusing without engagement breaches this.
- PINS Costs Guidance — Costs can be awarded against an LPA where its refusal is "unreasonable" (PPG Reference ID 16-049). Includes: vague refusal reasons, no evidence base, refusing contrary to officer's own assessment, refusing on grounds not raised at consultation.
- Probity / Bias — Lord Nolan's Standards in Public Life principles (selflessness, objectivity, openness, accountability) apply to planning officers. A refusal grounded in template language rather than site-specific evidence undermines objectivity.
- Case law: Save Britain's Heritage v SoS [2018] EWCA Civ 2137 — reasons must enable the reader to understand why a decision was made on each principal controversial issue. "Why" requires evidence + reasoning, not assertion.
🛡 How to push back
- Demand specificity in writing before the decision is made. "Which feature? Compared to what local character? Which paragraph of which policy?"
- If refused on vague grounds, appeal under s.78 — the Inspector applies a higher evidential bar than the LPA.
- Apply for costs at the same time as the appeal. Vague refusal is one of the explicitly listed "unreasonable behaviour" grounds in PPG.
- Use the patterns below — when this LPA's officer cites "character and appearance of" in 73 different refusals, that's a template, not site-specific reasoning. Hold them to the requirement that each refusal be evidenced on its own facts.
The patterns surfaced on this page are the platform's contribution to that fight. Every phrase the LPA reuses is statistical evidence it's not site-specific reasoning. Quote it back.
🐑 Cross-LPA boilerplate phrases — the "sheep" signal
📘 What this means + how to address it
What it means: Generic design-theme catchphrase — refusal officer cites this when alleging visual harm.
Evidence needed: Officer must identify the specific feature harming character. "Out of keeping" alone is not enough — they need to point at scale, materials, or proportion.
How to address: Challenge the specificity: which feature? Compared to what local character? If officer can't name the feature, the ground is weak. NPPF 135 says don't refuse otherwise acceptable development on design grounds.
NPPF: NPPF para 135
📘 What this means + how to address it
What it means: Same as above — variant phrasing. Generic design-theme boilerplate.
Evidence needed: Specific feature of the proposal that conflicts with a specific feature of the surrounding character.
How to address: Quote the officer back: "the report says character is harmed by X — but X is also present at [comparator], which was approved." Force them to be specific.
📘 What this means + how to address it
What it means: Design-theme boilerplate variant — alleges harm to the area's appearance.
Evidence needed: Same as "character and appearance of".
How to address: Challenge specificity. Provide a character study showing the area is varied / has multiple types of building. NPPF 135.
NPPF: NPPF para 135
📘 What this means + how to address it
What it means: Generic reference to the NPPF — usually with a paragraph number after. Not a refusal ground by itself.
Evidence needed: Look at the specific NPPF paragraph cited and engage with its substance.
How to address: Identify which NPPF paragraph the officer is leaning on. The Framework as a whole isn't a refusal ground — only specific paragraphs are. Hold the officer to specificity.
📘 What this means + how to address it
What it means: Generic NPPF reference — see above.
Evidence needed: —
How to address: Demand the specific paragraph reference. Generic NPPF citations are not refusal grounds.
📘 What this means + how to address it
What it means: Statutory duty wording — s.72 of the Planning (LB&CA) Act 1990 phrases the Conservation Area duty exactly this way. Strong ground.
Evidence needed: Heritage Impact Assessment specific to the Conservation Area. Significance statement. Comparison with NPPF less-than-substantial-harm tests.
How to address: This is the statutory duty wording — it's strong but specific. Address the public benefits balance (NPPF 208). Note: only triggers if site is IN a Conservation Area (check planning.data.gov.uk).
NPPF: NPPF para 207-208
Case law: South Lakeland DC v SoS [1992] 2 WLR 204 — "preserve" means "do no harm"
📘 What this means + how to address it
What it means: Green Belt harm — heavy lift. Triggers the inappropriate-development / Very Special Circumstances framework.
Evidence needed: Openness assessment (spatial + visual). VSC statement if scheme is inappropriate. Identification of any "grey belt" status under NPPF 2024 reforms.
How to address: First determine if scheme is "inappropriate". If yes, prove VSC clearly outweighs harm. If site is "grey belt" (previously developed within GB), much lower bar.
NPPF: NPPF paras 142-156
📊 Data sources & freshness
Patterns surface what officers actually write. Lower thresholds = more noise; we filter n-grams to phrases containing at least one refusal-vocabulary token (harm, adverse, contrary, character, amenity, etc.) so the signal is concentrated on refusal language.
- lib_documents.plain_text ↗ (updated Mined daily via cron)
PINS appeal decisions with full Inspector text. Currently 401 of 57,920 have plain_text extracted; backfill scrape in progress. - Pattern detector ↗
n-grams (4-6 words) with refusal-y vocab filter · policy-citation regex (NPPF para, Policy X.Y, s.66/s.72) · theme classifier (9 themes) · cross-LPA boilerplate (phrases used by 2+ LPAs). - LPA name resolution
Internal ONS code → name map; covers the NE councils + a handful of London / High Peak. National rollout pending LPA scaleout.