Planning records describe a process, not a contractor's order book. Understanding the stage can help you interpret a record, but it cannot tell you on its own whether someone needs a builder or when work will begin.
The labels and documents you see can vary between council systems. Use this article as a research framework and check the current source record for each proposal. It is not advice on whether a particular development can proceed.
An application is a proposal
An application records proposed development. At this stage, the information may help you assess whether the type of work and location fit your business.
It does not establish that the proposal will be approved or built. It also does not show that the applicant is inviting quotations. Keep those distinctions visible when you add a record to your research list.
Validation and publication are not buying signals
Council records may show receipt, validation or publication information. These relate to the handling and visibility of an application. They should not be translated into a claim that the project is “ready for a builder”.
Before comparing dates from different sources, check what each field means. A record newly found by an app can be different from an application newly published by a council. Our planning-record reading guide explains this distinction in more detail.
Consultation can produce more information
During consideration, additional material or revisions may appear. If a proposal remains on your shortlist, revisit the source when you have a reason to do so and check whether the information you originally reviewed still applies.
Do not assume that an earlier drawing is the final version. Equally, do not treat every new document as a new project. One proposal can generate several records and revisions.
A decision needs to be read in context
If the register shows a decision, inspect the available decision document where it matters to your assessment. A short “approved” label is not a complete explanation of the permission or any conditions.
GOV.UK explains the general planning-permission application process. For the position on an individual project, use the council's documents and appropriate professional advice.
A decision does not confirm the client's budget, contractor appointment, technical readiness or programme. Those are separate matters to establish through the normal project process.
Conditions and other requirements are not a research shortcut
Do not infer that construction can start simply because permission has been granted. The relevant permissions, conditions and other requirements need to be understood for that specific project.
The Planning Portal distinguishes planning permission from building regulations. Neither a lead summary nor this article is a substitute for checking the applicable requirements.
Use stages to frame questions, not promises
For a proposal under consideration, your question might be whether its scope fits your services. For a decided application, your question might be whether the current documents change that assessment. For an old record, the first question may simply be whether the project remains relevant.
In every case, write down what is known and what remains unknown. Do not infer an available contract from a planning stage.
Give each record a review outcome
Use a small set of decisions in your own notes: investigate, revisit with a reason, or set aside. A review date is useful only when you know what you intend to check.
Trade Watch Alerts supports discovery; your business still qualifies opportunities and checks source information. Follow the weekly review routine to keep that work manageable, and check current app coverage before choosing paid access.
Continue your research
Read the complete guide to planning leads for the wider workflow, or browse all practical guides.
