Why word count is no measure of a planning statement

A planning statement for a householder extension does not need to be long. Four pages that answer the council's design guide, the development plan policy and the neighbour's likely objection will beat forty pages of policy quotation every time. Nothing in the national validation requirements sets a word count, and no officer has ever recommended approval because a document was thick.

The reason people write long is anxiety. The document feels substantial, so the application feels safer. In practice the opposite happens, because a long statement buries the three sentences that mattered.

What proportionate means in practice

Validation requirements distinguish between what is needed nationally and what a local authority adds through its own validation list. Both are framed around providing enough information to determine the application, not around providing a particular volume.

Proportionate means the document covers each material consideration the officer must address, at the depth the issue deserves on this site. A single-storey rear extension on a 1930s semi has perhaps three: design and character, residential amenity, and whether any trees or drainage matters arise. A new dwelling in a conservation area in a flood zone has eight or nine. The statement grows because the number of issues grows, not because each issue needs more words.

There is a second test that is easier to apply. Could the officer, reading only your statement, draft the assessment section of their report? If yes, it is long enough. If they would have to go hunting through the drawings and the design guide, it is too short, whatever its length.

Where length actually helps

Some situations do need more pages, and it is worth being clear about which.

Where the development plan is out of date or the policy position is contested, the argument has to be set out properly, including the weight to be given to each policy and the operation of section 38(6) of the Planning and Compulsory Purchase Act 2004. Where there is relevant planning history, including a previous refusal, the statement has to explain what has changed. Where harm exists and is being weighed against benefits, the balance needs to be reasoned rather than asserted.

Appeals are different again. An appeal statement addresses the officer's reasons for refusal one by one, and it needs to engage with the reasoning in the decision notice and the officer report. Brevity still helps, but the scope is set by the refusal reasons rather than by the scheme.

And where a scheme is unusual, the explanation of why it is being done this way can be the most valuable part of the document. An officer who understands the constraint that drove an odd roof form is far more likely to accept it. Our note on where site judgement cannot be drafted in a design statement covers the material that has to come from the site visit rather than from a template.

Padding and how officers read it

Officers develop a fast filter for padding, and once it trips they skim. The usual forms:

• a page describing the application site in prose that the location plan already shows
• full quotation of policy text, sometimes several policies in a row, with no application to the scheme
• a national policy section summarising the Framework in general terms
• a restatement of the proposal that repeats the drawings
• a section asserting compliance with every policy listed, in a table of ticks
• a closing paragraph claiming the proposal is sustainable development without reference to any test

None of that is harmful in itself. The harm is what it does to the signal. When the officer reaches your actual argument on amenity, they are reading in skim mode, and the sentence that should have carried the decision goes past unnoticed.

Cut the policy quotations to the operative words. "Policy DM9 requires extensions to be subordinate to the host dwelling in height and projection" is worth more than three paragraphs of the policy reproduced in full.

Matching length to the application type

Rough guidance, based on what the issues normally are rather than on any published standard.

The right question is not which band you are in but which issues your site has. A householder extension next to a listed building can need more than an unconstrained new dwelling.

A worked householder example

Take a 4m single-storey rear extension to a semi-detached house, outside any designation, with a mature apple tree 6m from the proposed foundations and a neighbour who objected to a previous scheme.

An effective statement for that is about three pages. It states the proposal and its dimensions in one short paragraph with the drawing numbers. It deals with design in one section, naming the council's householder design guide requirement on subordinate roof form and showing the ridge is 600mm below the main ridge. It deals with amenity in a second section, giving the separation distance to the boundary, the 45-degree assessment result and the change from the previous refused scheme. It deals with the tree in a third short section, giving the species, the estimated stem diameter, the root protection area under BS 5837:2012 and the no-dig foundation detail proposed. It closes with the planning balance in four sentences.

The figures in that example are illustrative. The structure is not. Three issues, three sections, every claim tied to a drawing, and the previous refusal addressed head on. A forty-page version of the same application would contain the identical argument with another thirty-seven pages around it.

Cutting without losing substance

Four passes, in this order, remove most of the excess without touching the reasoning.

1. Delete every sentence that describes something a drawing shows. Replace with the drawing number.
2. Reduce each policy quotation to the operative requirement in your own words, keeping the policy reference.
3. Delete any paragraph that would sit unchanged in a statement for a different site. Generic text is the clearest signal that nobody visited.
4. Merge sections that address the same material consideration under different headings, which is common where a document has been assembled from a template.

What survives those passes is the document you should submit. If it comes out at two pages for a simple extension, submit two pages.

Judging the right length

Count the material considerations, not the words. Then check three things: every consideration has a section, every section names a policy and ends with a conclusion, and every factual claim has a drawing or appendix reference. A document that passes that check is the right length by definition.

The honest uncertainty worth admitting is that some officers do respond to volume, and a handful of authorities have validation lists that ask for content a short statement would omit. Check the local list before you cut, and keep the short document but add the sections the list requires.

PlanScope drafts statements with the section structure and policy framework in place and marks the site facts it does not hold as ones to be confirmed, which tends to produce a shorter document than a blank page does, because the structure stops you writing filler to reach a feeling of completeness. The judgement about what to keep is still yours or your reviewer's, and the professional directory is the route to review before submission. Our notes on explaining an AI-assisted draft to a client or a committee and on why applications are returned as invalid deal with the two places this most often goes wrong.

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

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