Improve planning application search keywords by reviewing rejected results

Start with scope and limits

The first step is to define where your keyword audit applies. According to GOV.UK’s register-search page, councils make plans for developments needing planning permission public, and that register search is available in England and Wales. That is the public-record scope for this workflow.

Your keyword choices also need to reflect what kinds of planning records you want to find. GOV.UK’s guidance on making an application explains that there are two main types of application, full and outline, and that other records can include reserved matters, discharge of conditions, amendments, lawful development certificates, prior approval and some non-planning consents. In practice, that means a search for a project type may surface records at different stages, or records that are not the main planning permission you expected.

A useful limitation to note is that councils may use different register interfaces and labels. This article does not assume any unsupported search operators, filters or field rules on a council’s site. Instead, it gives a review method you can apply to whatever search options are actually available.

• Jurisdiction for register access: England and Wales.
• Application-type guidance cited here: England-specific.
• Do not assume one keyword behaves the same way on every council register.

Build a rejection log before changing keywords

Many teams reject poor matches mentally and then immediately try another search. That makes improvement difficult because you lose the evidence of what went wrong. A simple rejection log creates a trail you can review.

For each result you discard, record the search term used, the application reference, the visible description, the application type if shown, and a short rejection reason. Keep the rejection reason specific. For example, reject because the record is a discharge of conditions rather than a new build proposal, or because the term matched a location name rather than the project scope.

This matters because the GOV.UK application guidance shows that planning records are not one uniform category. If your search pulls in reserved matters, amendments or non-planning consents, the problem may not be the keyword alone. It may be that you need a separate review rule for application type.

• Suggested rejection reasons: wrong project type, wrong scale, wrong geography, wrong application stage, non-planning consent, keyword matched unrelated wording.
• Keep evidence and judgement separate: record what the register says, then your reason for exclusion.
• Review the log after a small batch, such as 20 to 30 results, before editing the query.

Test synonyms in small, controlled rounds

Once you have a rejection log, look for patterns. If many false matches come from one ambiguous word, replace or narrow that word. If relevant records use different terminology, add a synonym test.

Run synonym tests one change at a time. For instance, test one term on Monday and a second on Tuesday against the same area and date range. If you change several variables together, you will not know which keyword caused the difference.

Use application-type awareness when choosing synonyms. The GOV.UK guidance lists records such as outline applications, reserved matters and prior approval. A term that works well for full applications may miss useful outline records, while a broad term may pull in later-stage approvals that do not fit your research purpose.

• Compare the exact result mix, not just the number of results.
• Note terms found in official descriptions and document titles, but do not assume every council uses identical wording.
• Create a small synonym table: preferred term, alternative term, common false-match term, notes.

Check a sample of excluded records

A search audit is incomplete if you only study what appeared in the results. You also need to test what your method excluded. The aim is to spot false negatives: records you would have wanted but did not capture.

One practical method is to take a small sample from nearby dates, neighbouring categories if the register provides them, or a manual page review of records that sit just outside your current query. Then ask two questions. First, would this record have been useful to your business research? Second, if yes, which word or rule caused you to miss it?

This sampling step is especially important because planning records can represent different stages of the same development journey. GOV.UK explains that outline permission deals with general principles, while reserved matters cover later detail. If your search only finds detailed terms, you may miss early-stage records that still matter for research.

• Sample excluded records in a fixed number, such as 10 at a time.
• Log missed records separately from false matches.
• If several missed records share the same wording, add that wording to your next keyword test.

Fictional worked example: before and after review

Fictional example. A contractor researching small commercial schemes searches one council register for the term “extension”. The initial result list contains household side extensions, time-extension wording in documents and some condition-discharge records. The team rejects many results but has not recorded why.

After creating a rejection log, the team notices three repeated issues. First, “extension” is capturing domestic household work outside its target market. Second, some records are not new planning proposals but later-stage condition or amendment records. Third, useful commercial schemes sometimes use wording such as “rear addition” or refer to a change of use combined with alterations rather than “extension” alone.

In the next round, the team keeps the geography the same, notes the visible application type where available, and tests “extension” against “alterations”, then reviews a sample of excluded records. That sample shows one relevant record described mainly as outline redevelopment and another as reserved matters for commercial floorspace details. The team does not assume every council supports advanced operators. Instead, it updates its worksheet: search term used, application type seen, likely project fit, and reason for keeping or rejecting.

The improvement is not a promise of better results everywhere. The benefit is a cleaner, evidence-based search routine that can be repeated on other council registers with appropriate local checking.

• Fictional before: one broad term, no rejection reasons, mixed record types.
• Fictional after: rejection log, synonym tests, excluded-record sampling, application-type notes.
• Outcome: a more disciplined review process, not a guaranteed uplift.

A practical checklist for your next keyword audit

Use this checklist when you next review planning application search keywords. It is designed for research teams that want a repeatable method rather than one-off tinkering.

• Define scope: council area, date range, and the project types you want to research.
• Record the current search term exactly as used.
• Review an initial batch and log every rejection with a specific reason.
• Separate keyword problems from application-type problems.
• Test one synonym or wording change at a time.
• Review a small sample of excluded records to identify missed opportunities.
• Keep a note of any council-specific filter or label that you have actually verified on the register.
• Repeat the process on another area only after checking that the register behaves similarly.
• Store links or references to the original records so you can re-check them later.
• Flag uncertainty where the visible description is too vague to classify confidently.

What this method cannot tell you

A keyword audit improves your research process, but it does not confirm that a project will proceed, that a contractor is being chosen, or that all relevant records are captured. Public planning information is only one part of opportunity research.

It also cannot standardise the underlying register systems. GOV.UK confirms the public-register position in England and Wales, but individual council interfaces still vary. And while the application guidance helps explain record types, the supplied detailed guidance is England-specific, so terminology and process should be checked carefully if you work across borders.

Your next check should always be the original council record. If a result looks promising, verify the application type, description and available documents on the source page before using it in a shortlist.

• Public record does not equal project certainty.
• Keyword logic does not replace manual checking.
• Cross-area consistency should be tested, not assumed.