Structuring a planning statement so drafting tools help
Officers lift the site description, the policy list and the conclusion straight into the delegated report when those sections are clean. Structure the statement so they can.
A planning statement structure that works is one a case officer can navigate without reading it end to end. Officers write delegated reports under time pressure, and they lift the site description, the policy list and the balance from your document if those sections are clean. Build the statement so those three parts can be extracted intact and you have done most of the job. Build it as a continuous essay and the officer rewrites everything, which means your framing of the case does not survive into the report.
That is also the test for where drafting tools help. They are good at the parts with a fixed shape and poor at the parts that need judgement about a particular site.
The sections a case officer reads first
Three, in this order. The description of development, because it has to match the application form exactly. The list of development plan policies engaged, because the report has a section that needs filling. And the conclusion, because that is where the officer looks for the argument they will either accept or answer.
So put a short numbered contents page at the front, keep the description of development on its own at the start of section one, and make the conclusion a standalone section that repeats the case rather than gesturing back at it. A conclusion that says "for the reasons set out above" is useless to a reader who has skipped to it.
Give every section a number and every paragraph a number. Officers and inspectors cite paragraph numbers, and a document without them invites paraphrase.
Describing the site and the proposal precisely
The site description carries more weight than its length suggests, because it establishes the facts that everything else rests on. Cover the address and area in hectares, the existing use and its Use Classes Order position, the built form and its condition, the boundaries and what lies beyond each one, access and parking, levels and trees, and every designation that applies.
Designations need a source and a date. Flood zone from the Environment Agency map, checked on a stated date. Listing grade and entry number from the National Heritage List. Conservation area name and the date it was designated. Tree Preservation Order reference. An officer who has to check each of these from scratch is an officer writing a slower report.
The proposal description should describe what is proposed, not sell it. Floorspace in square metres by use, unit numbers by size and tenure, storey heights, materials, parking numbers, and what is being demolished. The place for the case is the assessment, and mixing the two makes both weaker. This is also where a Design and Access Statement takes over, so cross-refer rather than duplicating, and the approach in drafting a design and access statement an officer can use applies to the split.
Setting out the development plan
Section 38(6) of the Planning and Compulsory Purchase Act 2004 requires the application to be determined in accordance with the development plan unless material considerations indicate otherwise. So the statement has to say what the development plan is, by name and adoption date, including any neighbourhood plan.
List the policies engaged in a table with the policy reference, its title and a one-line statement of what it requires. Then assess against each one in the same order later. A reader who can match the policy list to the assessment headings can follow the argument; a reader who cannot will assume something has been skipped.
Two things to get right. Where a plan is out of date or a policy is inconsistent with national policy, say so and explain the consequence rather than ignoring it. And state the National Planning Policy Framework edition you are working from, since the Framework has been re-issued more than once and readers may hold an older copy with different numbering.
Assessing each material consideration
One heading per issue, in the order the policies appear, with the same structure inside each: what the policy requires, what the proposal does, what the evidence shows, and the conclusion on that issue.
| Section | What it must contain |
|---|---|
| Principle of development | Land use policy, allocation or settlement boundary position |
| Design and character | Response to context, scale, materials, the design policy tests |
| Amenity | Daylight, outlook, privacy, noise, with reference to the technical reports |
| Highways and parking | Access, trip generation, parking standards |
| Environment | Flood risk, drainage, ecology, biodiversity gain, trees, contamination |
| Heritage | Significance, harm, the statutory duties and the policy balance |
| Infrastructure | Obligations, levy position, what is offered |
Cross-refer to the technical reports rather than restating them. A planning statement that summarises the flood risk assessment in two paragraphs and cites it is doing its job. One that reproduces four pages of it has buried the planning argument in someone else's evidence.
Writing the planning balance
This is the section that decides whether the statement is any good, and it is the section that cannot be templated.
Set out the harms identified, honestly, including the ones an objector will raise. Set out the benefits, with weight attributed and a reason for each weighting. Then state the conclusion in the terms the relevant policy test uses, whether that is the presumption in favour of sustainable development, the heritage balance, very special circumstances in the Green Belt, or simple accordance with the development plan.
Weight is where consultants earn their fee. Saying a benefit carries significant weight without explaining why reads as assertion. Saying that a scheme delivers a policy-compliant proportion of affordable housing in an authority that cannot demonstrate a five year supply, and that the benefit therefore carries substantial weight, is an argument.
Acknowledge one weakness. An officer who finds the statement has dealt candidly with the difficult issue trusts the rest of it.
Appendices and what belongs there
Keep the main document short enough to read in twenty minutes and push the evidence into appendices. Site photographs with a key plan. The planning history schedule with application references and decision dates. Policy extracts where a policy is long and central. Pre-application correspondence. Consultee correspondence obtained before submission.
What does not belong: the technical reports themselves, which are submitted as separate documents, and anything the reader cannot act on. An appendix nobody opens is a page count, not evidence.
Where automated drafting adds least value
Drafting tools are strong on the parts with a fixed shape: the structure itself, the site description once the facts are supplied, the policy list, the statutory framework, the standard sections on infrastructure and obligations, and the internal consistency checking that catches a floor area quoted differently in two places.
They are weak in three places. Local plan interpretation, because a policy's meaning often depends on its supporting text and on how the authority has applied it. The weighting exercise in the balance, which is a judgement about a specific decision maker and a specific set of facts. And anything relying on appeal decisions or committee history, where an assertion without a reference is worse than no assertion at all.
PlanScope drafts insert a [TO BE CONFIRMED] flag wherever a site-specific fact is missing rather than filling the gap, which is the behaviour you want: the flags show exactly where the judgement work has to happen. Treat them as a task list. The related habit of scanning a draft for factual errors to look for in a drafted planning document catches the rest, and a draft is also a useful agenda for a pre-application meeting.
Where the report type needs a licensed or competent professional, the professional directory is the route to a reviewer who will sign off.
Draft a Planning Statement on PlanScope by entering the postcode, then write the balance yourself.
PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.
Frequently asked questions
Which sections does a case officer read first?
The description of development, which must match the application form exactly, the list of development plan policies engaged, because the delegated report has a section needing it, and the conclusion. Make each one standalone, number every section and paragraph, and repeat the case in the conclusion rather than referring back to it.
How much technical detail belongs in a planning statement?
Enough to make the planning argument and no more. Summarise each technical report in a paragraph or two and cite it by title and date. Reproducing pages of a flood risk assessment or ecology report buries the planning case inside someone else's evidence and makes the statement harder to extract from.
How should development plan policies be presented?
In a table with the policy reference, its title and a one-line statement of what it requires, naming the plan and its adoption date, including any neighbourhood plan. Then assess against those policies in the same order later, so a reader can match the list to the assessment headings without wondering what was skipped.
What makes a planning balance section convincing?
Attributed weight with reasons. Listing harms honestly, including those an objector will raise, then stating each benefit with the weight claimed and why that weight follows. Conclude in the terms the applicable policy test uses, and acknowledge one weakness, because candour about the difficult issue buys credibility for the rest.
Where do drafting tools add least value?
Local plan interpretation, where meaning depends on supporting text and how the authority has applied a policy. The weighting exercise in the planning balance, which is judgement about a particular decision maker. And anything relying on appeal decisions or committee history, where an unreferenced assertion is worse than silence.
What belongs in the appendices?
Site photographs with a key plan, the planning history schedule with references and decision dates, extracts from long and central policies, pre-application correspondence and any consultee responses obtained before submission. Technical reports are submitted as separate documents rather than appended, and anything a reader cannot act on should be left out.
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.