Why an adopted local plan still has to be read in full

A policy citation proves that a policy exists. It does not prove that the proposal complies with it. That gap is the whole of the local plan policy ai drafting problem, and it matters because section 38(6) of the Planning and Compulsory Purchase Act 2004 requires the determination to be made in accordance with the development plan unless material considerations indicate otherwise. The plan is the starting point, so a document that quotes it accurately and applies it loosely will read as competent and persuade nobody.

Four things sit inside an adopted plan that no quotation reaches: the supporting text, the policies map, the site allocation, and the parts of the plan that have been superseded.

What a citation proves and what it does not

A drafted paragraph that says the proposal accords with Policy DM5 because it respects the character of the area has done one useful thing, which is identify the right policy. Everything after "because" is an assertion.

What the officer needs is the chain. The policy requires X, the proposal does Y, here is the measurement or the drawing that shows Y satisfies X, and here is the point on which judgement is required. A planning statement that makes that chain visible for each engaged policy is worth more than one covering twice as many policies in general terms.

The test I apply to a draft is simple. Take any compliance sentence, delete the policy reference, and ask whether anything is left that could be checked. If not, the sentence is decoration.

Supporting text, and where the numbers live

Adopted policies are usually short. The reasoned justification underneath them is where the standards sit, and that text is part of the plan.

An amenity policy might say two sentences about protecting the living conditions of neighbours. The paragraphs beneath it can set a separation distance, refer to a supplementary planning document, or specify a garden size per unit. Officers assess against those, and an applicant who has read only the policy is arguing a different case.

Supplementary planning documents are the next layer. They are not part of the development plan and they carry weight as material considerations where they have been adopted following consultation. Parking standards, householder design guidance and affordable housing guidance usually live there.

The policies map and the allocation

The policies map is the part of the plan a text-based draft cannot see. It tells you which designations touch the site, and it is the difference between a generic policy table and a site-specific one.

Work through it systematically for each application:

1. Is the site inside or outside the settlement boundary
2. Is it allocated, and if so for what use and at what indicative capacity
3. Which overlays apply, including conservation areas, Green Belt, local green space, employment areas, flood zones, critical drainage areas and areas of search for minerals
4. What sits within the distances the policies refer to, such as a listed building, an ancient woodland or a SSSI

Where the site is allocated, the allocation usually carries its own requirements: a quantum of development, an access point, a buffer, a contribution towards infrastructure, a phasing expectation. Those requirements are policy, and a scheme that ignores one of them is in conflict with the plan however well it performs against the generic policies.

Saved policies and partial supersession

Plans are rarely replaced cleanly. An authority adopting a new local plan will often save a list of policies from the previous plan, and the saved list is published with the new plan rather than inside it.

So the question "what is the development plan for this site" can have an awkward answer: a core strategy from one year, a site allocations document from another, a handful of saved policies from a plan two decades old, a minerals and waste plan from the county, and a neighbourhood plan. All of it is the development plan, and all of it attracts section 38(6).

Check the authority's own statement of the current development plan, and check the date. A policy quoted from a superseded plan is the error that damages a submission most, because it tells the officer the author has not looked.

Neighbourhood plans

Where a neighbourhood plan has been made, it forms part of the development plan for that area and its policies are applied with the same statutory starting point. They are frequently more specific than the local plan: a named site protected as local green space, a design code for a village, a limit on dwelling size, a requirement for frontage parking to be avoided.

They are also easy to miss, because a site can sit inside a designated neighbourhood area whose plan is at examination rather than made. An emerging neighbourhood plan carries weight as a material consideration according to its stage, and a made one carries the full statutory weight.

Where a drafted document will be generic

Honest about the limits: a drafting tool working from policy text can structure a planning statement, identify the policies likely to be engaged and summarise them accurately, and it will produce generic reasoning wherever the answer depends on the site.

That is why PlanScope's drafts insert "[TO BE CONFIRMED]" markers where site-specific facts are missing rather than filling the gap with plausible text. The marker is the useful output. A draft that quietly invented a separation distance would be worse than one that admits it does not know.

The parts that need a person are the judgement calls: whether the character of the area is what the policy assumes, whether a harm is less than substantial, whether the housing land supply position shifts the balance, and what the site's planning history tells you about how the authority has approached it before. Where site judgement cannot be drafted in a design statement deals with the equivalent problem for design, and what drafts get right about structure and wrong about evidence sets out the general pattern.

An illustrative example

A site allocated for around 30 dwellings, with the allocation requiring vehicular access from a named road, a 15 metre landscape buffer to the eastern boundary and the retention of a hedgerow. The scheme proposes 38 dwellings, access from a different road and a 5 metre buffer. The figures are illustrative.

A policy table generated from the plan's text would show compliance with the housing policy, the design policy and the biodiversity policy, and might be right on all three. The scheme is still in conflict with the plan, because the allocation's own requirements are policy and three of them are not met. The conflict might be justified, and the statement has to argue that rather than not notice it.

Building a policy table that earns its place

• One row per engaged policy, with the policy number, the requirement in your own words, what the proposal does, and the evidence reference
• A separate section for allocation requirements, each addressed individually
• A column recording where judgement is involved, so the officer can see you have identified the contested points
• The plan name and adoption date at the top, with the saved policy position stated
• Nothing in the table that the submitted drawings or reports do not support

Keep the table short and let it carry the weight. Thirty rows of partial compliance is a weaker document than eight rows that engage properly with what the plan asks.

Where a draft is going to be used on a submission, it should be reviewed by someone who can make those judgement calls, and the professional directory is the route to a reviewer who can sign off a draft. The pricing page sets out what editing and version control cost on each tier, which matters when a policy table is regenerated several times during an application.

This is general guidance, not legal advice. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.