Finding appeal decisions that are actually relevant

Most appeal decisions you find are useless to you, and the reason is almost always the same: they turned on facts that are not your facts. A decision allowing a rear extension in a conservation area tells you very little unless the roof form, the boundary relationship, the character appraisal and the policy wording are close to yours. Searching well means filtering hard, and filtering hard means knowing what to filter on before you start.

The Planning Inspectorate publishes decisions through its casework portal, and everything below assumes that as the source.

Where decisions are published

Appeal decisions and the associated documents are published on the Planning Inspectorate's appeals casework portal. Cases are searchable by appeal reference, by local planning authority, by appeal type and by decision date, and the decision letter itself is available as a document on the case record.

The appeal reference carries information worth reading. It identifies the authority, the appeal type, the year and the case number, so a reference beginning with a householder appeal type tells you at a glance that the decision was reached on the shorter householder procedure with limited evidence.

What the portal does not offer is a strong full-text search across the body of decision letters. That is the practical limitation, and it shapes the method: filter by authority, type and date to get a manageable set, then read.

Searching by inspector, issue and authority

Three filters do most of the work.

Filter by authority first where the policy question is local, because a decision applying the same adopted plan policy is worth more than a better-reasoned decision applying someone else's. Filter by appeal type second, because a written representations householder decision and a called-in inquiry decision carry very different weight and depth. Filter by date third, and be ruthless: a decision applying a superseded edition of the national Framework or a since-replaced local plan may state a conclusion you cannot rely on.

Searching by inspector is a legitimate technique for understanding how a particular decision-maker has approached an issue, but it should not appear in your statement. Citing an inspector's previous decisions at them reads as an attempt to bind, which is not how the system works and does not go down well.

Where the issue is technical rather than policy, widen the authority filter and narrow the topic. A decision on the adequacy of a bat survey scope, or on the weight given to a parking stress survey, travels better across authority boundaries than a decision about local character.

Filtering out decisions that turn on their facts

Read the "main issues" paragraphs first and stop reading if they do not match. Inspectors set out the main issues early, in a numbered list, and that list tells you in thirty seconds whether the decision is about your question.

Then check four things before you invest in the rest:

• The policy framework applied, including the edition of the national Framework and the status of the local plan at the time
• Whether the authority could demonstrate a five-year housing land supply, since that changes the balance applied
• Whether the decision rests on a site-specific feature, such as an existing boundary structure or a particular topography
• Whether evidence was unchallenged, because an inspector accepting unopposed evidence is not making a finding of general application

A decision reached because the council put in no evidence on a point is a weak citation, and the other side will say so.

Reading a decision for the reasoning

The useful part is rarely the outcome. It is the route.

Look for how the inspector characterised the harm, what weight was given to it, and what tipped the balance. Look for the language used about policy compliance, because a finding of conflict with a specific policy is more portable than a general conclusion. Look for what the inspector said about evidence: which report was found adequate, which was not, and why.

Conditions are underrated. The schedule at the end of a decision letter shows what an inspector thought was necessary to make a scheme acceptable, and lifting a well-drafted condition into your own application is often more useful than quoting the reasoning.

Where an inspector dismissed an appeal but indicated that a modified scheme could succeed, that passage is worth quoting in a pre-application submission.

Pay attention to how the inspector treated the officer report. Where a scheme was refused against officer advice, the decision often sets out in terms why the members' reasoning did not hold, and that analysis is transferable to a scheme facing the same committee. Where the officer recommended refusal and the inspector agreed, the useful material is usually the description of what evidence was missing.

Costs decisions and what they reveal

Costs decisions are published alongside the appeal decision where an application was made, and they are the most candid documents the system produces.

They say plainly when an authority behaved unreasonably: refusing contrary to officer advice without evidence, failing to substantiate a reason for refusal, introducing a new objection late, or requiring information that was not necessary. For an applicant in a dispute about validation or about an unreasonable information request, a costs decision from the same authority on a comparable point is a useful thing to have in the file.

Use them carefully in correspondence. Attaching a costs decision to a letter is a signal, and it should be a deliberate one.

Citing a decision properly

1. Give the full appeal reference, the decision date and the site address.
2. State the appeal type and procedure, so the reader knows the depth of evidence.
3. Cite the paragraph number, not just the decision.
4. Quote the passage you rely on rather than characterising it.
5. Attach the decision letter as an appendix.
6. Say, in one sentence, why the facts are comparable to yours.

That last step is the one that separates a useful citation from a decorative one. An officer reading a statement that asserts relevance without showing it will treat the citation as noise. A Planning Statement that spends two sentences establishing comparability before quoting is doing the work properly.

Why decisions are indicative rather than binding

Appeal decisions are not precedent in the legal sense. Each case is determined on its own facts and on the development plan in force at the time.

What the courts have recognised is that consistency in decision-making matters, and that a previous appeal decision on the same or closely comparable facts is a material consideration which a decision-maker should address, giving reasons for departing from it. That is a different and more modest proposition than precedent, and describing it accurately in a statement is more persuasive than overstating it.

So the right framing in a submission is that the earlier decision indicates how the issue has been approached, and that the reasoning applies here for stated reasons. Not that the council is bound.

Keep the decisions you rely on in a dated folder with the version of policy they applied, because policy churn is what invalidates a good citation. Keeping constraint data current over a long project makes the same point about mapping, and reusing planning data under the Open Government Licence covers the attribution position for material you reproduce. For reform news that changes the policy backdrop, the planning law timeline is the place to follow updates.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it.