A planning-lead qualification checklist for busy teams

Start with what the public record can and cannot tell you

According to GOV.UK’s register-of-planning-decisions guidance, plans for developments that need planning permission are made public by the council. That makes planning records a strong starting point for research. It also means your team can review proposed building plans before deciding whether the lead is worth further investigation.

That same GOV.UK page says the council register service is available in England and Wales only. This article uses England as the main context because the second source, GOV.UK guidance on making an application, explains the English planning application process in detail. If you review Welsh records, check the relevant Welsh rules and terminology separately.

The key limit is simple: a public planning record shows that an application or proposal exists in the planning system. It does not confirm builder procurement, programme certainty, live budget, tender route or whether the project will proceed to site.

• Evidence from the register: there is a proposal in the public planning system.
• Not evidence from the register alone: contractor demand, start date, buying route or affordability.

Use three statuses: yes, monitor or decline

A good qualification workflow should be fast enough for first review and strict enough to protect estimator and pre-construction time. The three-status model works well for that.

Yes means the lead matches your service area and project type, the planning evidence is detailed enough to understand the likely works, and the unknowns are acceptable for further research. Monitor means the record looks relevant but is still too early, too vague or too incomplete. Decline means there is a clear reason not to spend more time.

• Yes: good fit, adequate evidence, acceptable unknowns.
• Monitor: possible fit, but important questions remain unanswered.
• Decline: poor fit, wrong geography, unclear scope, or application type too early for your process.

The qualification checklist: evidence first, then fit, then commercial gaps

The GOV.UK guidance on making an application says there are two main application types: full planning permission and outline planning permission. It also lists related application routes including approval of reserved matters, discharge of conditions, amending proposals, lawful development certificates, prior approval for some permitted development rights and several non-planning consents. For lead qualification, that matters because different application types give different amounts of usable detail.

GOV.UK explains that full planning permission results in a decision on detailed proposals, while outline planning permission is about the general principles of development and leaves one or more reserved matters for later approval. For a busy contractor, that usually means a full application may be easier to assess quickly than an outline application.

GOV.UK also says a valid planning application requires a completed form, national information requirements, the correct fee and local information requirements. National information requirements include plans and drawings, ownership and agricultural declarations, and in some cases a design and access statement or fire statement. As a practical recommendation, teams can use the presence or absence of these materials as a quick evidence-quality test, while remembering that validation rules are official requirements for applicants rather than a direct instruction for contractors.

• 1. Geography: Is the site inside your active service area? If no, decline.
• 2. Project type: Does the proposal match the work you actually deliver? If no, decline.
• 3. Application type: Is this full, outline, reserved matters, discharge of conditions, prior approval or another route? Full or reserved-matters submissions may offer more workable detail than outline cases.
• 4. Scope clarity: Are there enough plans or drawings to understand likely works? GOV.UK says applications must include plans and drawings, with a minimum location plan.
• 5. Site understanding: Can your team identify access, layout or scale issues from the available material? GOV.UK defines reserved matters such as access, appearance, landscaping, layout and scale.
• 6. Stage of certainty: Is the project detailed enough for your current pipeline, or is it still at principle stage only?
• 7. Procurement unknowns: Is there any evidence at all about whether a contractor is being considered now? If not, this is usually a monitor, not an automatic yes.
• 8. Timing unknowns: Can you see any clue that the project may move within a timeframe you can serve? If timing is entirely unclear, record that gap explicitly.
• 9. Delivery constraints: Are there obvious reasons the project may sit outside your risk appetite, such as unusual consent complexity or missing core documents?
• 10. Decision rule: Mark yes, monitor or decline, and write one sentence explaining why.

Suggested rejection reasons for a reusable team list

Standard decline reasons reduce repeat work. They also help future reporting, because the team can see whether weak leads are being filtered out early enough.

These are recommendations for internal workflow, not official planning categories.

• Outside service area.
• Wrong project type for our business.
• Too early: outline principles only, insufficient detail for our current process.
• Insufficient documents to understand scope from the public record.
• Scale mismatch: too small or too large for our team.
• Specialist consent or complexity outside our delivery model.
• Commercial route unknown and not worth further research at this stage.
• Duplicate of an existing lead record.
• No clear next step after review.

Fictional worked example with a simple score

Fictional example: your firm delivers shell-and-core and fit-out packages for small commercial and mixed-use schemes in two adjoining English counties. A council register shows an application for redevelopment of a town-centre site.

Scoring can keep first review consistent. For example, score each category from 0 to 2: geography fit, project-type fit, scope clarity, stage certainty and commercial attractiveness based on what is visible in the public record. Total possible score: 10.

In this fictional case, geography fit scores 2 because the site is inside your core area. Project-type fit scores 2 because the proposal matches your normal work. Scope clarity scores 1 because there are plans, but the procurement route is unknown. Stage certainty scores 1 because the application is full planning permission, which GOV.UK describes as dealing with detailed proposals, but permission is not yet the same as a live construction package. Commercial attractiveness scores 0 because no budget, programme or buying route is evidenced. Total score: 6 out of 10.

Outcome: monitor, not yes. The lead is real and relevant, but the unanswered commercial questions are still too large. The record should stay on a watchlist for later checks such as decision status, revised submissions or more detailed documents.

• Example threshold only: 8 to 10 = yes, 5 to 7 = monitor, 0 to 4 = decline.
• Keep the score secondary to the written reason. A lead with a fair score can still be declined if it clearly falls outside your business model.

Limitations and next checks

This checklist is designed for early research, not final bid selection. It relies on what is visible in public planning materials and therefore cannot answer every commercial question.

Official sources explain application routes and validation basics, but they do not tell you whether a project suits your capacity, margin expectations or delivery risk. Those are internal business judgements.

A practical next step is to keep one evidence note per lead: application type, location, visible documents, what appears to be proposed, the main unknowns and the reason for yes, monitor or decline. That gives your team a repeatable audit trail without assuming more certainty than the record supports.

• Check the original council record before acting on any lead.
• Treat outline and other early-stage applications cautiously if your team needs detailed scope.
• Separate verified facts from assumptions in your CRM or lead sheet.
• Review monitored leads on a schedule so they do not disappear into a backlog.