SHELAA, Allocation or Permission? What Each Status Actually Tells a Land Team
The commercial and planning difference between evidence-base inclusion, local-plan allocation and planning permission.
5 min
SHELAA inclusion, local-plan allocation and planning permission are three different things. Treating them as interchangeable creates bad acquisitions, misleading landowner conversations and appraisals built on the wrong probability.
SHELAA inclusion
A Strategic Housing and Economic Land Availability Assessment is evidence. It helps an authority understand land that may be suitable, available and achievable for development.
Inclusion does not decide that development should proceed. It does not create policy support equivalent to an allocation, and it does not grant permission. Oxford City Council’s January 2026 SHLAA states the distinction plainly: the assessment identifies possible sites but does not allocate them.
The useful questions are:
Was the site assessed or merely submitted?
What conclusion and capacity did the authority record?
Which constraints or dependencies were identified?
When was the assessment produced?
Has the evidence changed since then?
Local-plan allocation
An allocation is a policy proposal or decision in an emerging or adopted plan identifying land for a particular form of development. Its weight depends on the plan’s status, the wording of the policy and the progress of the emerging plan.
An allocation may establish the principle of development, but it can still carry substantial requirements covering access, infrastructure, affordable housing, phasing, design, ecology and other matters.
For a plan progressing under the legacy system, record the stage precisely: Regulation 18 consultation, Regulation 19 publication, submission, examination, main modifications or adoption. Government plan-making guidance distinguishes the early Regulation 18 work from the proposed-submission documents published under Regulation 19. England is transitioning to a new plan-making system in 2026, so do not assume every new plan will use the same labels.
Planning permission
Permission authorises development subject to its conditions, approved plans, legal obligations and time limits. Outline and full permissions carry different levels of resolved detail. Under government guidance on outline applications, reserved matters are normally submitted within three years of outline permission. Conditions may also control what must be approved before work begins; the planning-conditions guidance explains that permissions normally carry a commencement time limit.
Even then, commercial due diligence continues:
Are pre-commencement conditions capable of being discharged on acceptable terms?
Is the Section 106 agreement workable?
Is reserved-matters approval required?
Has the permission been implemented?
Are access and third-party rights secured?
Does the consented scheme still appraise?
A better pipeline status
Do not use one field called “planning status” to carry the whole story. Keep separate fields for:
evidence-base treatment;
adopted-plan status;
emerging-plan status and stage;
application status;
permission type and date;
conditions and obligations;
appeal or legal challenge;
next planning milestone.
That structure lets a land director compare sites without reading every note and stops an old SHELAA reference being mistaken for current policy support.
What to say to a landowner
These distinctions are easiest to lose when a complex planning position has to be explained in one conversation.
If a site appears in a SHELAA, say that the authority has assessed it as part of its evidence base and then explain the recorded conclusion. Do not describe it as allocated unless the plan actually does so.
If it is proposed for allocation in an emerging plan, name the stage and the remaining process. Consultation, examination and modification can still change the policy.
If it is allocated in an adopted plan, explain that this is meaningful policy support but not a permission to build. The site-specific requirements and application process remain.
If it has permission, explain the type of consent, the conditions, obligations and expiry position. “Consented” does not mean “ready to start tomorrow”.
Accurate language protects the relationship. It also prevents the commercial appraisal from silently assuming a planning certainty that does not exist.
A status should always have a date and source
Planning status decays. An emerging allocation can be removed. A permission can lapse if it is not implemented within the applicable time limit. A SHELAA can be replaced. A legal challenge can alter the position.
Every status field should therefore retain:
the source document or decision;
its publication or decision date;
the relevant policy, paragraph or site reference;
the date the team last checked it;
the person responsible for the interpretation;
the next expected milestone.
This makes it possible to distinguish a current status from an inherited label copied across several appraisals.
The role of AI
AI is useful here because the evidence is dispersed. It can locate the latest assessment, compare it with earlier versions, extract the authority’s conclusion and flag a mismatch with the pipeline.
It should not upgrade a site from “submitted” to “suitable”, or from “emerging allocation” to “allocated”, because a keyword appeared in a new PDF. Harold keeps the source beside the extracted status and routes uncertain changes for review. The value is not a more confident label. It is a traceable one.
Why the distinction matters commercially
Each stage changes risk, timing and value differently.
A favourable SHELAA conclusion may justify continued promotion. An emerging allocation may justify greater technical spend while still carrying examination risk. An adopted allocation can materially strengthen the principle but may bring expensive policy requirements. A permission can still be commercially unattractive.
The right question is not “Does the site have planning?” It is:
What exactly has been established, what remains unresolved, and what evidence changes the next decision?
Sources
Article written by
