Structuring a planning statement so compliance is checkable

A planning statement works when the case officer can lift its structure straight into the officer report. That is the whole design brief. Section 38(6) of the Planning and Compulsory Purchase Act 2004 requires the decision to be made in accordance with the development plan unless material considerations indicate otherwise, and the officer report follows that sequence because it has to. A planning statement structured to policy compliance mirrors it, deals with each relevant policy in turn, and gives the officer a paragraph they can adopt at the end.

Why officers read statements in a particular order

The officer writing your report has a template, a caseload and a deadline. They need the site described, the proposal understood, the relevant policies identified, each one assessed, the objections addressed and a conclusion they can defend at committee or on appeal.

A statement that arrives as continuous prose, with the policy analysis distributed through it, forces the officer to do that sorting themselves. A statement organised the way the report is organised gets used.

This is not about writing the officer's decision for them. It is about making the reasoning easy to check, which is what a document of this kind is for.

Setting out the site and proposal without padding

Two short sections. The application site, its area, its current use, its boundaries, the buildings on it, the levels, access, trees and any designations that apply. Then the proposal: what is being built, its dimensions, its floorspace, its unit mix, parking, access and drainage.

Planning history belongs here too, briefly, with application references and outcomes. Where a previous refusal is relevant, say what has changed. Where a fallback position exists, such as an extant permission or a permitted development right, set it out plainly, because it can carry real weight in the balance.

Resist the urge to describe the surrounding area at length. Three paragraphs of townscape narrative that nobody disputes is three paragraphs the officer skims.

Running the development plan policies in sequence

This is the heart of the document. List the adopted development plan documents with their dates, identify the policies relevant to the application, and take each one in order.

For each policy: quote the operative requirement, state how the proposal responds, and reach a conclusion on compliance. Where the proposal does not comply with a policy, say so and explain why permission should still be granted. A statement that claims compliance with everything is less credible than one that concedes a point and explains it.

A policy compliance table at the front of the section helps, provided the text does the real work.

Neighbourhood plan policies sit in the development plan too, and applications are regularly refused on a neighbourhood plan policy the applicant never mentioned.

Check the plan's date and its status. A policy in an emerging local plan carries weight according to its stage and the extent of unresolved objections, and a statement that treats an emerging policy as adopted invites a correction in the officer report.

Dealing with national policy proportionately

National policy supports the development plan case, it does not replace it. Cite the current National Planning Policy Framework, state the edition, and use the policy references from that edition rather than paragraph numbers carried over from an older copy. The Framework was restructured in August 2026, so verify references at the time of writing.

Two or three well-chosen national policy points, tied to the actual issues, beat six pages of quotation. Where the tilted balance is engaged, that is a substantive argument and needs its own treatment with the evidence that supports it.

Planning Practice Guidance is useful for method rather than for principle: how a sequential test should be approached, what a viability assessment should contain, how conditions should be framed.

Addressing material considerations separately

Give them their own section so they are not confused with the plan-led assessment. Consultation responses and neighbour objections, answered on their planning merits. Appeal decisions, described as indicative of how inspectors have approached an issue rather than as binding. Site-specific matters such as contamination, flood risk or protected species, cross-referenced to the technical reports rather than summarised at length.

Planning obligations and any section 106 heads of terms go here as well, with the three tests for obligations addressed directly.

Keep the technical detail in the technical reports. The statement's job is to connect each report to the policy it answers.

Objections deserve more care than they usually get. Group them by theme, answer each theme on its planning merits, and say plainly where an objection raises a matter that is not a planning consideration, such as loss of a view or effect on property value. Dismissing the whole set in a sentence reads badly in a committee report, and the objectors will be in the room.

Writing a planning balance the officer can adopt

The final section does four things: identifies the harm, identifies the benefits, attaches weight to each, and states the conclusion under section 38(6).

1. Set out any conflict with the development plan, and its extent.
2. Set out the benefits, distinguishing those that carry weight in policy from those that do not.
3. Attach weight explicitly, using the language policy uses.
4. State whether the proposal accords with the development plan as a whole.
5. State whether any material considerations indicate a decision otherwise.

That is a paragraph an officer can use. A conclusion that asserts the scheme is acceptable in all respects is not. Nor is one that rehearses the benefits without ever naming the harm, because the officer has to name it and will then be writing against you.

On length, proportionality is the test. A householder extension needs a few pages. A major application with heritage, flood risk and viability issues needs more, and still benefits from brevity in the sections where nothing is contested. If a section exists only because the template has one, delete it.

One more discipline worth adopting. Keep a short schedule at the front listing every document submitted with the application and what each one addresses. Officers use it, objectors use it, and it exposes a gap in the pack before validation does.

PlanScope drafts planning statements structured to this sequence, with policy citations and with "[TO BE CONFIRMED]" markers wherever a site fact is missing rather than an invented figure. Drafts can be sent through the professional directory for review and sign-off by a qualified professional, and the pricing for single reports and for the Professional tier is set out on the pricing page.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it.

Enter your postcode on PlanScope to see which reports your site needs, then edit the draft against your own site facts.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.