When to review, retain or archive a planning lead

What the official sources support

According to GOV.UK’s planning-register page, councils make public the plans for developments that need planning permission. That gives businesses a public starting point for research in England and Wales.

According to GOV.UK’s guidance on determining planning applications, once an application has been validated, the local planning authority should decide it as quickly as possible and within the statutory time limit unless a longer period is agreed in writing with the applicant. The same guidance sets out England timeframes of 13 weeks for major development, 10 weeks for technical details consent and certain public service infrastructure applications, and 8 weeks for other development, with 16 weeks where an application is subject to Environmental Impact Assessment.

The England guidance also says a longer timetable can be agreed in writing, for example through a planning performance agreement or an extension of time. It adds that an applicant may appeal for non-determination if the application has not been decided within the relevant period.

That matters for pipeline management because delay does not always mean disinterest or failure. The same GOV.UK guidance says planning history may be relevant to a later application, and that reasons why an earlier permission was not implemented can matter. For a research team, that is a reason to review context before discarding an older record.

A simple maintenance policy: review, retain or archive

A practical policy can use three statuses.

Review means the lead needs active checking because something material may have changed or an unanswered question now affects whether it deserves attention. Retain means keep the record on a watchlist because it still fits your market, but you do not yet have new evidence that justifies more effort. Archive means remove it from the active pipeline because, based on your current research purpose, it no longer offers enough value to monitor routinely.

These are business workflow decisions, not statements about the legal status or commercial outcome of the project.

• Review when a new decision, amendment, appeal, extension of time or other visible register update appears.
• Review when the application has reached a point where timing may have moved beyond your previous assumption, especially in England where official guidance sets normal determination periods but also allows written extensions.
• Review when your own service fit changes, for example if you stop taking a certain project size or geography.
• Retain when the project still matches your type of work, but the public record does not yet answer key delivery questions.
• Retain when the application history looks active but incomplete, so a later check may be more useful than immediate action.
• Archive when the lead clearly falls outside your service area, project type or commercial model.
• Archive when repeated checks produce no evidence that helps you move the lead forward and no realistic next research step remains.
• Archive when a newer record or better-matched project replaces it in your active shortlist, while keeping a note of why it was removed from day-to-day monitoring.

How to decide using changed evidence, fit and unanswered questions

A good planning lead pipeline management routine can be built around three tests.

First, changed evidence: has the council register shown something new since your last check? Because the public register is the evidence source, status changes should follow what the record now shows, not memory or guesswork.

Second, project fit: if the proposal were to proceed, would it still suit your geography, trade package, scale and capacity? A lead can be genuine and still be wrong for your business.

Third, unanswered questions: what do you still need to know before more effort makes sense? If the missing point is important but likely to become clearer on a later register check, retain it. If the missing point cannot be answered from the public record and the lead no longer justifies further monitoring, archive it.

This method helps avoid a common mistake: keeping a large pile of old planning records because they might matter one day. A smaller, better-labelled list is usually easier to maintain.

• Record the date you last checked the public register.
• Note exactly what changed, if anything.
• State whether the lead still fits your business profile.
• List the single most important unanswered question.
• Set one next action: review again, retain on watchlist, or archive from active tracking.

Fictional stale-record cases

Fictional example 1: A small contractor tracks an England application for a light industrial extension. Twelve weeks after validation there is still no decision on the register. A poor policy would mark it dead because the record feels old. A better policy would review it. GOV.UK’s England guidance says applications should usually be decided within statutory periods, but it also says longer periods can be agreed in writing and that non-determination can lead to appeal. The correct conclusion is not “abandoned”, but “timing uncertain: check for extension, appeal or later decision”.

Fictional example 2: A joinery firm kept a school-related record on its list for months. The register still shows a public proposal, but the firm has since narrowed its market to residential work only. Nothing is wrong with the project; it simply no longer fits. The lead should move to archive from the active pipeline because project fit changed, not because the application became invalid.

Fictional example 3: A civils business watches a site with an earlier permission and a newer, similar application. GOV.UK’s England guidance says planning history can be relevant and that reasons why an earlier permission was not implemented may matter. Instead of treating the older record as useless, the team reviews both records together. The output is a better evidence note: the site has repeat planning activity, but implementation remains unclear.

Checklist for routine maintenance

Use this short checklist each time you revisit a planning lead.

• Confirm the jurisdiction: England and Wales for the register search; England only for the determination guidance used here.
• Check the council register again rather than relying on an old export or screenshot.
• Write down any new decision, amendment, appeal-related information or timing change visible on the public record.
• Ask whether the project still fits your service area, work type and capacity.
• Separate verified facts from assumptions about delivery, budget or contractor selection.
• If the record is older than expected, do not label it abandoned without new evidence.
• Choose one status only: review, retain or archive.
• Add the next check you would make if the lead stayed in the pipeline. If you cannot name a useful next check, archiving may be the better workflow choice.

Limitations and next checks

These sources do not tell you whether a project will definitely be built, when site work will start, or whether a buyer is currently selecting suppliers. They also do not create a complete maintenance rule for every UK planning system. The register page cited here covers England and Wales, while the determination guidance supplied here is written for England.

For that reason, your policy should stay modest. Use public planning records to organise research and prioritise attention. Then check the original register entry and consider whether other public documents, council pages or project-specific information are needed before you spend more time on the lead.

If you use internal customer or contact data alongside planning records, set retention and privacy rules with appropriate internal or specialist advice. This guide does not prescribe personal-data retention periods.