How to avoid counting the same construction project twice in planning research

Why duplicate planning leads happen

Duplicate planning leads usually appear when a team stores each planning reference as if it were a separate opportunity. That can inflate pipeline numbers, create repeat research and send sales staff back to the same site under different labels.

The GOV.UK guidance on making an application explains that there are two main types of application, full and outline, and that applications can also cover reserved matters, discharge of conditions, amendments to proposals with planning permission and non-planning consents. In practice, that means multiple records may exist for one development journey.

The same guidance also says applications for approval under outline permission may be made for all reserved matters at once or individually, and even fresh applications for alternative details can be made for the same reserved matter. For lead research, that is a clear warning: several records can sit under one broad scheme without being identical opportunities.

• One site may have an outline application first, then later reserved matters.
• A granted scheme may later produce amendment applications.
• A development may need separate non-planning consents as well as planning permission.
• Cross-boundary sites may involve identical applications submitted to more than one local planning authority.

Build two layers: project record and application record

A practical data model starts with two separate entities. First, create a project record. This is your team’s working view of the possible construction scheme at a site. Second, create an application record for every official planning reference you find on a council register.

Your project record should be broad enough to group related records, but cautious enough to avoid false merges. A useful rule is this: applications are evidence; projects are your interpretation of how those applications may relate commercially.

Because GOV.UK says a valid planning application includes a completed form and plans and drawings, and that a location plan must clearly identify the application site, those official documents can help you compare whether two records really concern the same land parcel. Still, similar location details do not always mean the same construction package.

• Project record fields: internal project ID, site name, normalised location, project summary, relationship confidence, current status, next check.
• Application record fields: planning reference, authority, application type, description, site wording from register, decision status, document checked, date checked, linked project ID.
• Relationship field between the two: confirmed link, probable link, uncertain link, or no link.
• Evidence note on every link: why your team linked or separated the records.

What to compare before linking records

Start with the planning authority and reference. Every public application should keep its own authority and reference intact. Never replace those with your internal project name.

Then compare the application type. According to GOV.UK, a full application concerns detailed proposals, while an outline application concerns the general principles of development and may be followed by reserved matters. If one record is outline and another is reserved matters on a matching site, a link may be sensible. If one is a discharge of conditions and another is a fresh full application, the relationship may be less obvious and should be checked from the documents.

Compare the site boundary, not just the postal address. GOV.UK says the location plan should show the exact application site, edged with a red line, and enough adjoining roads or buildings to identify it clearly. For deduplication, this is stronger evidence than a reused street address.

Finally, compare scope. A new school building, a car park change and a landscaping package could sit on adjoining land and share wording in the address while still representing different work packages.

• Match on red-line site area where documents are available.
• Check whether descriptions refer to the same scale and purpose of development.
• Note when one record appears to implement, amend or detail an earlier permission.
• Keep records separate when the evidence conflicts or remains incomplete.

Fictional worked example: one site, four records

Fictional example. Your team finds four planning records connected to ‘Riverside Works, Mill Lane’.

Record A is an outline application for mixed-use redevelopment. Record B is an application for approval of reserved matters for appearance, layout and scale on part of Riverside Works. Record C is a discharge of conditions application tied to the earlier permission. Record D is a full application for a stand-alone electricity substation on land beside Riverside Works.

A weak deduplication method would merge all four because the address is similar. A better method would create one project called ‘Riverside Works redevelopment’ and link Records A, B and C to it, with A and B probably or confirmed related once the documents match. Record C would stay as a separate application record linked to the same project because it is an additional procedural step, not a new project count. Record D would remain separate unless the documents show it is part of the same redevelopment package. Shared wording alone would not be enough.

In reporting, your team might count this as two possible projects under review and four application records monitored. That preserves accuracy. It also stops the same site inflating your lead totals.

• Project 1: Riverside Works redevelopment.
• Linked applications: Outline, reserved matters, discharge of conditions.
• Project 2 or uncertain link: adjacent substation application.
• Sales note: monitor both, but do not claim four separate projects.

A checklist for a small sales team

Use this short routine each time a new planning lead enters your pipeline. It works best when one person owns the project record and everyone else adds application evidence beneath it.

• Create a new application record for every official planning reference found.
• Search your database for matching or nearby sites before creating a new project record.
• Check the application type before linking anything.
• Read the register description, then inspect available plans, especially the location plan.
• If the site boundary and scope clearly align, link the application to an existing project as confirmed or probable.
• If the address matches but the boundary, scale or purpose is unclear, mark the relationship uncertain.
• If the record concerns a different package, phase or adjacent site, keep a separate project record.
• Store a brief evidence note explaining the decision.
• Report project counts separately from application counts.
• Review uncertain links on a regular watchlist instead of forcing an early merge.

Limitations and next checks

This method improves consistency, but it does not tell you whether work will proceed, when procurement will begin or whether one contractor package or several will reach the market. A planning register is evidence of a proposal and its administrative history, not a complete commercial picture.

There are also jurisdiction limits. The supplied GOV.UK register page says the register search is available in England and Wales. The supplied application guidance, including application types, reserved matters and validation detail, is specifically framed around England. If you research Welsh records, check the relevant local authority process and terminology before applying the same assumptions.

For difficult cases, the next sensible check is the original register entry and its documents. Where a site crosses local authority boundaries, GOV.UK says identical applications must be submitted to each local planning authority, so teams should watch for duplicate-looking records across more than one council. That is another reason to keep application references distinct even when you later group them into one project.

• Separate official evidence from your internal judgement.
• Do not merge records only because the address text matches.
• Use document-based checks, especially the location plan and application type.
• Keep uncertain relationships visible instead of hiding them.