How a case officer reads your planning statement

A case officer reads your planning statement with a half-written report open beside it. They are not assessing your prose. They are looking for sentences they can lift into their own document, attributed to the applicant, that answer the policy tests they have to cover before they can sign a recommendation. Write with that in mind and your reasoning survives into the decision. Write a general essay about the merits of the scheme and the officer writes their own version, which is rarely as favourable as yours.

Most supporting statements are structured for the applicant. The useful ones are structured for the report.

What an officer is looking for

The officer has a fixed list of things to establish. Is the application valid and correctly described. What is the site, its planning history and its constraints. What is the development plan position and which policies apply. What did consultees and neighbours say. What are the material considerations, taken one by one. How does the balance come out under section 38(6) of the Planning and Compulsory Purchase Act 2004 and the relevant national policy.

Everything else is noise to them. A paragraph praising the client's commitment to quality does not help with any item on that list. A paragraph that identifies the correct development plan policy, states the test it sets, and then shows how the scheme meets it, helps with two.

They are also working under time pressure, with a determination period of eight weeks for a minor application and thirteen for a major, and a caseload running in parallel. Clarity is not a courtesy. It is the difference between your argument being used and being paraphrased badly.

How the officer report is structured

Delegated reports vary between authorities but the skeleton is remarkably consistent, and it is worth knowing in order.

1. Site description and the proposal.
2. Relevant planning history, with application references.
3. Consultation responses, usually summarised in a table.
4. Representations received, with the number and the main themes.
5. Policy framework, listing development plan policies and national policy.
6. Assessment, broken into headed sections such as principle of development, design and character, residential amenity, highways and parking, trees and landscaping, drainage, ecology.
7. Planning balance and conclusion.
8. Recommendation and conditions.

The assessment section is where your statement either appears or does not. Each headed subsection has a policy, a consultee position and an officer judgement. If your document has a section with the same heading, with the policy cited and the evidence named, the officer's job becomes transcription.

The paragraphs that get lifted

In practice, three kinds of sentence travel from applicant documents into officer reports.

One is a factual statement with a measurement attached. "The proposed rear extension projects 3m from the rear elevation of the host dwelling, 1.2m less than the adjoining extension at number 14." An officer can check it against the drawings and use it.

Another is a policy application sentence. "Policy DM12 requires development to respect the prevailing roofline, and the proposal retains the existing eaves and ridge heights, as shown on drawing 1042-P-04." That is the structure of the officer's own reasoning, handed over ready-made.

The last is a concession with mitigation attached. "The proposal would result in some loss of afternoon sunlight to the rear of number 14. The 45-degree assessment in Appendix C shows the effect is below the threshold in the council's householder design guide, and the extension has been set in 0.9m from the boundary to reduce it." Officers trust applicants who name the harm. It reads as an assessment rather than a sales document.

What never gets lifted: adjectives, assertions of compliance without a cited policy, and claims about how the scheme will benefit the area that have no policy hook.

Where an officer stops reading

Officers abandon documents in predictable places. A statement that spends three pages describing the application site before reaching the proposal. A policy section that quotes 14 policies in full and applies none. A section headed with a question that then restates the question. Any passage where the policy numbers belong to a superseded plan, because that signals the whole document may be recycled.

The NPPF problem is worth separating out. The Framework was renumbered in December 2024 and re-issued on 17 August 2026 with policy-coded chapters in place of paragraph numbers. A statement citing a paragraph number from an older edition tells the officer the document was not written for this application. Cite the edition and the policy code, and check the current text on gov.uk before you submit.

Length is its own signal. Nothing in validation requires a householder statement to run past four pages, and a long one invites the suspicion that the substance is thin.

A worked comparison with a report

Take a single-storey rear extension in a conservation area, decided under delegated powers. The officer's assessment section will carry headings for design and character, impact on the conservation area, and residential amenity.

A statement organised as introduction, site, proposal, policy, conclusion forces the officer to hunt through it for each of those three. A statement organised as design and character, conservation area impact, residential amenity, with the policy and the drawing reference inside each, maps onto the report directly. Same content, different order, materially different outcome in how much of your reasoning appears.

The illustrative case is instructive in one more way. Where the applicant's statement included a short paragraph acknowledging the loss of a modern lean-to and explaining why it made no contribution to the character of the area, the officer had something to quote in answer to the amenity society's objection. Without it, the officer would have had to construct the answer, and officers under pressure sometimes construct a refusal reason instead.

Writing so the report can quote you

Six habits do most of the work.

• Head your sections with the headings the officer will use: design, amenity, highways, trees, drainage, heritage. Not "Planning considerations".
• Name the policy, state the test it sets in one sentence, then answer it. Policy number alone is useless to a reader who has not got the plan open.
• Attach a drawing number or appendix reference to every factual claim. The officer has to verify it.
• Put the number in the sentence. "Projects 3m" rather than "a modest projection".
• Deal with the obvious objection explicitly, including the one the neighbour has already made. Officers read the representations before your statement.
• Keep one sentence per section that states the conclusion in terms the report can adopt.

Our note on where site judgement cannot be drafted in a design statement covers the parts of this that no template or draft can supply, and the discipline of structuring the bundle so assertions are traceable matters as much as the writing.

A final read-through method

Before submission, read the document once as the officer, with a blank sheet beside you. Write down, from the statement alone, the headings you would use in an assessment section, the policies you would cite under each, and the evidence reference you would check. If you cannot do that in ten minutes, the officer will not either.

Then do one pass for the things that cost you credibility: superseded policy numbers, the wrong NPPF edition, a claim with no drawing reference, a paragraph that could sit in any statement for any site. Cut the last of these without mercy. Generic paragraphs are the clearest signal that the author did not visit the site.

PlanScope drafts statements with the section structure and policy citations in place, and marks the site-specific facts it does not hold so you can fill them in rather than discover them missing at validation. The judgement about what the officer will find persuasive on a particular site is yours, or your reviewer's, and the professional directory is the route to a reviewer who can sign off a draft before it goes in. See pricing for the free report, the per-report option and the Professional tier.

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