Finding development sites

A developer search is defined by the sites it rejects as much as the sites it keeps. Minimum frontage, access, existing use, policy, flood risk, utilities and owner control need to be recorded consistently across the target area.

I build that longlist, keep the source and rejection reason, and separate ownership clues from a verified title. The development team chooses which sites deserve planning, design and appraisal work before an owner approach.

What changes the search

• Development use, target authorities and minimum gross and developable area.
• Access geometry, frontage, highway context and servicing.
• Current use, occupation, buildings and relocation issues.
• Local-plan status, planning history and nearby constraints.
• Flood mapping, surface water, drainage and topography.
• Habitats, trees and biodiversity net gain questions in England.
• Registered title information, owner entity and the route for a direct approach.
• A red-line area is not the same as developable area.
• Ownership clues from company records or mapping do not prove title.
• Policy and planning history do not replace an appraisal or pre-application advice.

What I record on the first pass

• Mapped longlist with site boundary and source date.
• Planning, policy, flood and environmental links.
• Ownership source and legal-verification status.
• Reason kept or rejected against the search filters.
• Approved owner message and contact result.

What to send me

• Use, geography and site-size range.
• Access, frontage and constraint filters.
• Land-control or acquisition preference.
• Known sites and previous approaches.
• Internal approval and owner-contact rules.

Further reading

• Making effective use of landCurrent national planning-policy context.
• Environment Agency Flood Map for PlanningInitial flood-risk screening for England.
• HM Land Registry property informationRegistered title information for ownership checks.

Common questions