Using planning application search to find precedents

To find similar planning applications near your site, search the council's own public register by street rather than by house number, filter by application type, and then read the officer reports rather than the decision notices. The decision notice tells you what happened. The officer report tells you why, and the why is what you can use. Every local planning authority has to keep a public register of applications, and almost all of them now publish it online with the documents attached, so this research costs nothing but time.

For a self-builder assembling a first application, three or four well-chosen local decisions with the reasoning extracted are worth more than any amount of general guidance about what councils usually accept.

Searching a council's register effectively

Start wide and narrow down. Searching the exact address of your plot usually returns only its own history, which is useful and tells you nothing about how the council treats schemes like yours.

The searches worth running, in order:

1. The street name with no house number, which returns every application on the road and lets you see the pattern across a terrace or a cul-de-sac.
2. The map search, drawing a box around the immediate area, which catches applications on adjoining streets that share the same character.
3. A keyword search of the proposal description, using the words the council itself would use. Two storey rear extension, loft conversion with rear dormer, new dwelling, garage conversion, change of use.
4. The postcode, which most systems accept and which picks up the immediate cluster.
5. The weekly or monthly lists of validated applications and decisions, which are the fastest way to see what is coming forward now.

Then search the plot itself properly. Every application, refusal, withdrawal, appeal, prior approval, certificate and condition discharge for the site and its neighbours, back as far as the register goes.

Be aware of the digitisation limit. Many registers hold full documents only from the late 1990s or the early 2000s, with earlier entries reduced to a reference, a description and a decision. Where an older application matters, ask the council whether the file can be retrieved from microfiche or paper storage. It is usually possible and it sometimes carries a fee.

Filtering by application type and date

Comparability is the whole point, so filter deliberately.

Match the application type. A householder application, a full application for a new dwelling, an outline application, a prior approval and a certificate of lawfulness are assessed against different tests, and a permission granted on a prior approval tells you nothing about how a full application would be judged.

Match the period. A permission granted a decade ago was assessed against a different local plan, a different edition of the National Planning Policy Framework, and often a different design guide. Applications decided in the last three to five years carry the most weight, and anything from before the current local plan was adopted needs a caveat.

Then read the outcomes in groups. Approvals tell you what the council accepts. Refusals tell you where the line is, and they are usually more informative. Withdrawals often mean an officer indicated a refusal was coming, so a cluster of withdrawn applications for the same thing on the same street is a warning worth heeding.

Our note on searching planning decision data across authorities covers the wider datasets when you need comparisons beyond one council area.

Reading an officer report for the reasoning

The officer report, sometimes called the delegated report or the committee report, is the document that repays reading. Its structure is fairly standard.

Site description and planning history. The list of policies the officer considered relevant, which is a free policy list for your own application. Consultation responses, including the highway authority, the tree officer, the conservation officer and any statutory consultee. Neighbour representations and how the officer dealt with them. Then the appraisal, which is where the reasoning sits. Then conditions and the recommendation.

Read the appraisal closely and extract the standards actually applied. How the officer described a subordinate extension. What separation distance was used and whether it came from a design guide. Whether a first floor side window was acceptable with obscure glazing. How the officer weighed the loss of a garden tree. What was said about parking provision and on-street stress. These are the council's working thresholds, expressed in its own words, and quoting them back in your own statement is legitimate and effective.

Delegated reports on small applications are sometimes only a page long. Even then, the appraisal paragraph is worth having, and a run of five short reports on similar schemes gives you the pattern.

Where the report refers to a supplementary planning document or a design guide, download that document too. The officer is applying it, so you should be reading it.

Conditions as evidence of what is acceptable

Conditions are an underused source. They record the precise mitigation the council needed before it could say yes, which tells you the threshold more exactly than the appraisal often does.

Look for obscure glazing and non-opening window conditions, which tell you which windows the council treats as a privacy problem and at what cill height. Materials conditions, which tell you whether matching brick and tile is expected or whether contrast is accepted. Conditions removing permitted development rights, which flag where the council was worried about future additions. Tree protection conditions referencing a method statement. Landscaping and boundary treatment conditions. Restrictions on use of a flat roof as a terrace, which appear wherever overlooking was in issue.

Copy the wording. Offering the same condition in your own application, with the same wording the council has used before, makes approval administratively easy and signals that you have done the work.

Also note what was not conditioned. Where three similar permissions carry no drainage condition, the council is probably content with the standard arrangement in that area.

Appeal decisions on the same street

Appeal decisions carry more weight than council decisions because they come from an independent inspector applying national policy and the development plan, with reasons given.

Search the Planning Inspectorate's appeals records by postcode or by local authority, and cross-reference against the council's register, which usually notes whether an appeal was lodged and its outcome. Read the whole decision letter, not the final paragraph, because the reasoning is where the value lies.

A dismissed appeal on a neighbouring property for a scheme like yours is a serious warning. An allowed appeal is a strong card, particularly where the inspector expressly disagreed with the council's application of a local standard. That kind of finding is worth quoting in full, with the appeal reference and date.

Where a previous appeal decision concerns the same site or closely similar circumstances, the courts have long held that consistency is a material consideration and that a decision maker who departs from an earlier decision has to give reasons for doing so. That is a useful argument and it is not a guarantee.

Recording references so they survive

Councils reorganise their websites, and links break. Save the documents rather than the addresses.

For each precedent, record the application reference, the full site address, the proposal description exactly as the council wrote it, the decision and the decision date, the officer report reference and the paragraph you are relying on, and any relevant condition number and wording. Then download and file the decision notice, the officer report, and the key drawing.

Keep them in one folder per application with the reference as the folder name. When you come to cite a precedent eighteen months later in an appeal statement, having the PDF is the difference between an argument and an assertion.

The same principle applies to historic evidence generally, and our note on historic maps as former land use evidence covers the archival side of this work.

Why a precedent is persuasive rather than binding

Each application is determined on its own merits, in accordance with the development plan unless material considerations indicate otherwise. There is no doctrine of precedent in planning, and a council is entitled to reach a different view from the one it reached on the house next door.

What a precedent does is shift the burden of explanation. Where you can show that the council granted permission for a materially similar scheme nearby within the current plan period, and the officer applied a particular standard in doing so, the council has to explain why your case is different. That is a real advantage and it is frequently enough.

Four cautions. A permission granted under a superseded plan carries less weight. An unimplemented permission carries less weight than one that was built. A permission granted in error is not a foundation to build on, and councils will say so. And the fact that something exists on a street does not mean it was ever permitted, so check the register before relying on it.

Cite two or three precedents properly rather than ten loosely. In the Planning Statement, give the reference, the date, the description and the specific finding you rely on, and explain the similarity in one sentence. The design reasoning that responds to local character belongs in the Design and Access Statement.

This is general guidance rather than legal advice, so check the position with your local planning authority or a qualified professional before relying on it. PlanScope can draft your supporting documents around the precedents and policies you have gathered, flagging where a reference still needs confirming. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. Browse the 66 report types to see what your application is likely to need alongside them.