What makes a Planning Statement too long

A Planning Statement is too long when the case officer stops reading before reaching your conclusion, and that happens sooner than most agents assume. The document has one job: to give the decision maker the policy case in a form they can adopt. A householder statement that runs to twenty pages, or a major application statement that reproduces whole policies before commenting on them, works against itself.

Length is not the real problem. Proportionality is. A statement that is long because the scheme is complicated reads well. A statement that is long because nothing was left out reads like padding, and the officer will treat the whole document with the suspicion that padding earns.

Who reads it and how far they get

Three people read a Planning Statement, and they want different things. The case officer reads it to find the policy framework, the arguments and the conclusions. A statutory consultee reads only the section that touches their remit. A committee member, where the application goes that far, reads the officer's report and not your statement at all.

That shapes the writing. The officer is the audience, and the officer is drafting a report under time pressure, usually against a template with headings for policy, consultation, assessment and conclusion.

Write to be quoted. Where your statement gives a clear, defensible paragraph on a policy test, it can go into the report with light editing. Where it gives three pages of narrative around the same point, the officer writes their own paragraph and your framing is lost. Our page on a Planning Statement sets out the sections themselves.

Length proportionate to the application type

There is no published page limit, and local validation lists rarely specify one. The useful discipline is to set a target before writing.

Treat those as a sanity check rather than a rule. The test to apply is whether every section is doing work the decision needs, and whether the length is explained by the issues rather than by the drafting.

One honest observation: on householder applications the statement is often optional, and a short, well-aimed covering case can beat a long statement nobody asked for.

Material that belongs in another document

The most common cause of bloat is other people's work recited at length. The statement should refer to technical documents and state their conclusions, not restate their method.

Material to move out:

• design rationale, materials and layout justification, which belong in the Design and Access Statement
• survey results, modelling outputs and calculation methods, which belong in the technical reports and their appendices
• utility and capacity evidence, which has its own home, as our note on utilities capacity evidence for a residential scheme sets out
• site history recited application by application, where a short table does the same job
• planning history of other sites, unless closely comparable and used for a specific point

Where a technical report answers a policy test, say so in one sentence and cite the report and paragraph. "The sequential test is addressed in the flood risk assessment at section 6, which concludes that no reasonably available sites exist in a lower risk zone" is more useful than two pages reproducing the argument. The same applies to retail work, where the evidence sits in its own document, as our note on retail sequential test evidence explains.

Repeating policy text against summarising it

Block quotation of policy is the single clearest sign of a statement written to a word count. The officer has the development plan. They do not need it reprinted.

What they do need is the policy reference, the part of it that bites, and your analysis. A policy compliance table works well on schemes with many policies: policy reference, requirement in a few words, where the scheme addresses it, and compliance stated plainly. The analysis then sits in prose for the handful of policies that are actually in issue.

Three rules keep this honest. Quote only the words you are going to analyse. Never summarise a policy in a way that drops an inconvenient clause, because an officer who notices stops trusting the rest. And state the NPPF edition you have used, since the Framework has been renumbered and re-issued more than once and readers may hold an older copy.

Where a policy is out of date or carries reduced weight, that is an argument requiring evidence, not an assertion to be dropped into a list.

Writing so the officer can lift conclusions

Structure each substantive section the same way: the issue, the policy, the evidence, the conclusion. Put the conclusion in its own short paragraph and make it a sentence the officer could adopt.

Practical habits that help:

1. Give every section a heading that names the issue rather than the policy number.
2. Keep paragraphs numbered, so consultees and officers can cite them.
3. Put the planning balance in one section near the end, with the benefits and harms listed as you say they should be weighed.
4. Avoid advocacy adjectives. "The proposal would not materially harm the amenity of 14 and 16" carries further than "the proposal is entirely acceptable in amenity terms".
5. Cross-reference by document name and section, not by "see the accompanying reports".

Where the application turns on judgement, say so and explain why your view should prevail. An officer who has to construct your argument for you will usually construct a weaker version of it.

What to cut first

In order:

The history section, reduced to a table of relevant decisions. The description of the site, cut to what matters for the planning issues rather than a tour. Any passage summarising national policy at length. Repetition of consultation responses, since the officer has them. Design narrative duplicating the design statement. Appendices of material already submitted elsewhere in the application.

Then cut the paragraphs that assert rather than argue. Any sentence saying the scheme is appropriate, acceptable or in keeping, without a reason attached, can go without loss.

What should not be cut: the policy framework list, the planning balance, and the response to each likely objection. Those are the sections an officer cannot write without you.

A structure that scales

One skeleton works from two pages to forty. The sections stay the same and the depth changes.

Site and surroundings, reduced to the planning-relevant facts. The proposal, described precisely, with figures. Relevant planning history. The policy framework, listed. Assessment, one subsection per issue, each ending in a conclusion. Other matters, including obligations and conditions offered. Planning balance and conclusion.

On a householder application that skeleton produces three or four pages. On a major scheme the assessment section carries ten subsections and the planning balance runs to two pages. Nothing is added that is not an issue, and nothing that is an issue goes missing.

Last point. Offer draft conditions and heads of terms at the end. It is the shortest section in the document and often the most useful, because it tells the officer exactly what a recommendation would need to secure.

Browse the 66 report types by category to see which technical documents should be carrying the material you are tempted to put in the statement. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.