Summarising an adopted local plan for a site appraisal
The development plan is narrower than most appraisals assume. How to identify every document, read the policies map, weigh supplementary guidance and build a policy schedule.
Before any policy summary means anything, you need to know which documents make up the development plan for the site. That list is narrower than most appraisals assume, and getting it wrong undermines everything built on top of it. Under section 38 of the Planning and Compulsory Purchase Act 2004, the development plan for an area in England comprises the adopted development plan documents taken as a whole, the spatial development strategy in Greater London, and any neighbourhood plan made for the area. Nothing else.
So a supplementary planning document is not part of the development plan. Neither is a design guide, an evidence base study, a masterplan the council commissioned, or a draft plan at examination. Each may be a material consideration. None of them carries the weight that section 38(6) gives the plan itself.
Identifying every document in the development plan
Start with the authority's own published statement of what its development plan consists of. Most publish one, and it is the only reliable starting point, because the composition varies enormously between authorities.
A typical combination:
- A local plan, sometimes split into a strategy part and a detailed policies part adopted years apart
- A site allocations document, which may be separate or folded into the local plan
- A development management policies document in older plan structures
- An area action plan or neighbourhood-scale document for a regeneration area
- The minerals and waste local plan, usually prepared by the county in two-tier areas
- Any made neighbourhood plan covering the site
- In Greater London, the spatial development strategy
Note the adoption date of each, and check the superseded policy schedule in the most recent adoption. Plans routinely save a handful of policies from earlier documents, and those saved policies remain part of the plan while the rest of the old document has gone.
One nuance that catches people out. The adopted policies map illustrates the policies. It is not itself a development plan document. Where the map and the written policy appear to conflict, the written policy governs, and you should say so rather than relying on the shading.
Using the policies map for the site
Work outwards from the red line. For the site itself, record whether it is allocated and for what, whether it sits inside or outside any settlement boundary, and which designations cover it. Then do the same for land within influencing distance, because a designation next door can be as important as one on the site.
The national planning data platform is useful for a first pass on designations with consistent national datasets, but for allocations and local boundaries the authority's own map is the source. Check the scale at which the boundary was drawn, and be careful about a red line that appears to clip an allocation edge by a few metres.
Record what you looked at and when. Designations change, and an appraisal without dates is hard to defend a year later.
Allocations, designations and boundaries
Each of these has a different consequence for the appraisal, and lumping them together produces a weak document.
| Finding | Practical consequence |
|---|---|
| Site allocated for the proposed use | Principle broadly established; policy sets the detailed requirements |
| Site allocated for a different use | Conflict with the plan that needs a material considerations case |
| Inside the settlement boundary, unallocated | Judged against general development management policies |
| Outside the settlement boundary | Countryside policies apply, often restrictive |
| Green Belt, National Landscape or similar | A specific policy test applies before any balance |
| Local designation such as a green space or frontage | Usually a criteria-based policy with an exception route |
Where a site is allocated, read the allocation text closely and treat its requirements as a specification: unit numbers, access points, infrastructure, phasing, open space, and anything the allocation says must be provided. Those requirements will appear in the officer's report whether or not your appraisal mentions them.
Strategic policies against detailed ones
The Framework distinguishes strategic policies, which set the overall approach and housing requirement, from non-strategic policies dealing with detail and local character. Neighbourhood plans can only contain non-strategic policies.
The distinction matters when you test consistency. A detailed local policy that conflicts with a strategic policy in the same plan is a point you can make, and where a policy is out of date the Framework provides its own consequences. Be precise about which policies are most important for determining the application, because that phrase does real work in the balance.
Supplementary documents and their weight
Supplementary planning documents can carry real influence while remaining outside the plan. They cannot introduce new policy, only add detail to adopted policy, and that limit is a useful argument where an authority treats a design guide as though it were a policy requirement.
Read them anyway. Parking standards, householder design guidance, affordable housing and space standards guidance all shape what officers ask for, and pretending they do not exist makes an appraisal less useful even if it makes it technically pure.
Emerging plans and how much weight they carry
The Framework sets out how to approach emerging plans: the stage the plan has reached, the extent of unresolved objections to the relevant policies, and the degree of consistency with national policy. Weight rises as those factors settle.
State the position rather than asserting a weight. An emerging policy at pre-submission consultation stage with heavy objection carries little. The same policy after an inspector's main modifications, unopposed, carries a good deal more. And a plan adopted between your appraisal and the decision changes the basis of assessment, which is one reason the appraisal needs a review date.
Turning the summary into an appraisal
A policy summary is not an appraisal. The appraisal is the document that tells the client what the plan means for their scheme, and it needs four things: a policy schedule, a compliance assessment, a document schedule and a risk list.
- List each relevant policy by number and title, with its source document and adoption date
- Against each, state what it requires of a scheme of this type, in the plan's own terms
- Assess the proposal against it, and mark where compliance is uncertain rather than smoothing it over
- Derive the evidence base from that assessment, naming each report the requirements imply
- Set out the three or four risks that could change the recommendation, with the trigger for each
Drafted summaries are a reasonable way to produce the first version of steps one and two, and they save real time on a plan running to several hundred pages. The discipline is that every policy number, every quoted phrase and every threshold gets checked against the adopted document before it leaves the office. Never quote policy wording from a summary, and never carry a policy number into a submission without opening the plan. Our notes on factual errors to look for in a drafted document and on building an internal review checklist set out how that check is organised, and a good appraisal is also the best preparation for a pre-application meeting, as covered in using a draft to prepare for a pre-application meeting.
As an illustrative example, a 2.5 hectare site might sit inside a settlement boundary, unallocated, in a borough whose plan comprises a 2019 strategy document, a 2022 site allocations document that saved four policies from a 2011 plan, and a made neighbourhood plan from 2021 with a local green space designation 30 metres away. That is four documents and three adoption dates before a single policy is read. An appraisal that names them all, with dates, is already more useful than most.
The report types those policies imply are listed under the 66 planning documents by category, and drafting costs are set out on the pricing page. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.
This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it.
Frequently asked questions
What counts as the development plan for a site?
Under section 38 of the Planning and Compulsory Purchase Act 2004, the adopted development plan documents taken as a whole, the spatial development strategy in Greater London, and any neighbourhood plan made for the area. Supplementary planning documents, design guides, evidence base studies and emerging plans are material considerations but are not part of the plan.
Is the policies map part of the development plan?
The adopted policies map illustrates the policies rather than forming a development plan document in its own right. Where the map and the written policy appear to conflict, the written policy governs. Say so in the appraisal instead of relying on shading, and note the scale at which a boundary was drawn before treating it as precise.
How much weight does a supplementary planning document carry?
It can be influential as a material consideration but cannot introduce new policy, only add detail to adopted policy. That limit is a useful argument where an authority applies a design guide as though it were a requirement. Read them regardless, because parking standards and design guidance shape what officers ask for.
How do I weigh an emerging local plan?
Use the factors in the Framework: the stage the plan has reached, the extent of unresolved objections to the relevant policies, and the degree of consistency with national policy. State the position rather than asserting a weight, and remember that adoption between appraisal and decision changes the basis on which the application is judged.
Can a drafted summary be used in a submission?
Use it as a first draft of the policy schedule, then verify every policy number, threshold and quoted phrase against the adopted document. Never quote policy wording from a summary and never carry a policy number into a submission without opening the plan. Summaries frequently conflate a superseded policy with its replacement.
Sources and further reading
This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.