Do you need a Design and Access Statement — or a Planning Statement?

Most architects write a Design and Access Statement out of habit. For the majority of householder and small-residential schemes, the regulations do not ask for one — and the document that does the work at the decision is a Planning Statement: the argument for why the scheme should be approved, tested against the policies the case officer will actually apply.

This guide sets out what article 9 really requires, what it exempts, and what to submit when nothing triggers it.

What a Design and Access Statement is

A Design and Access Statement is a prescribed document. Where article 9 of the Town and Country Planning (Development Management Procedure) (England) Order 2015 bites, the statement must explain the design principles and concepts applied, appraise the site’s context, set out the approach to access, and describe any consultation undertaken. The content is defined by the regulations, not by the case you want to make.

A Planning Statement is different. It is non-statutory, its content is yours to choose, and its whole job is to argue the application: how the scheme meets the development plan, why the harms alleged in the local plan’s design and amenity policies do not arise here, and what weight the benefits carry.

When article 9 actually applies

Under article 9 a Design and Access Statement is mandatory in two cases only:

• Major development. Ten or more dwellings, or 1,000m² or more of floorspace to be created.
• Development in a conservation area or World Heritage Site that provides one or more dwellings, or 100m² or more of floorspace.

And there are express exemptions that apply even when one of those limbs is met: applications under section 73 to vary or remove a condition, engineering and mining operations, waste development, and — the one that catches most conversions — any material change of use.

The change-of-use exemption surprises people. A garage converted into three flats inside a conservation area triggers no statutory duty at all, because article 9 is disapplied for a material change in the use of land or buildings. If operational development is proposed alongside the conversion, the building works can still bring the 100m² limb into play — that is worth checking on the drawings rather than assuming either way.

So what do councils actually ask for?

Not much, and not consistently. Across the ten authorities Buildwise has read validation lists for, a Planning Statement is a validation requirement for major applications only in four of them; one asks for it wherever the context and justification need demonstrating; three do not list it at all; one publishes no local list; and one says in terms that a planning statement is optional.

For a householder extension, a small residential scheme, or a conversion, the honest position is that no statement is compulsory anywhere on that list. Which is exactly why writing one well matters: it is not a validation box, it is the only place you get to make the argument, and the officer’s recommendation is written from what is in front of them.

What a good Planning Statement covers

• Site and context — what is there now, what surrounds it, what character the area actually has.
• The proposal — scale, layout, materials, described precisely enough to be checked against the drawings.
• Policy compliance — the adopted local plan policies engaged, by code, with the compliance argued rather than asserted.
• Neighbour amenity — daylight, outlook and privacy, assessed per neighbouring property.
• Planning history — previous refusals answered directly, and revisions described honestly.
• Design and access — the article 9 material, where article 9 applies.

That last line is the whole point. A Planning Statement with a design and access section where the regulations require one covers both cases; a Design and Access Statement on a scheme that never triggered article 9 spends its pages on prescribed content instead of on the argument.

How long should it be?

• Householder applications — typically 4 to 8 pages. Conservation areas and listed buildings warrant more detail.
• Small residential (fewer than 10 units) — typically 8 to 15 pages, with detailed policy sections and site analysis.
• Major applications — typically 20 to 50 pages or more, often accompanied by separate heritage statements, transport assessments, and sustainability reports.

Length is less important than quality. A concise, well-argued 8-page statement will usually outperform a generic 20-page document that simply describes the proposal without making a case for it.

Common mistakes to avoid

• Describing rather than arguing. “The extension will be single storey and constructed in brick” is a description. “The single storey form and matching brickwork reflect the domestic scale and material palette of the street scene, consistent with policy DEN1” is an argument. Every sentence should advance the case for approval.
• Generic policy citations. Citing NPPF paragraphs without connecting them to the specific proposal is unconvincing. Officers want to see that you have read the relevant policies and understand how they apply to your site.
• Ignoring constraints. If the site is in a flood zone, conservation area, or near a listed building, the statement must address this directly. Failing to mention a significant constraint suggests the applicant has not considered it.
• Wrong NPPF paragraph numbers. The NPPF has been revised several times. For example, the paragraph on well-designed places is now §135 — citing the old 2019 number (§130) will undermine confidence in the statement.
• No neighbour impact analysis. For residential extensions and new dwellings, officers want to see that daylight, outlook, and privacy impacts on neighbouring properties have been properly assessed — ideally on a per-property basis.

How Buildwise can help

Buildwise generates a Planning Statement — with a design and access section where the regulations require one — cited to your council’s actual adopted local plan policies and tailored to your site’s specific constraints. Every statement is structured around the sections planning officers read, with a site-specific argument for every policy.

Rather than starting from a blank page, architects use Buildwise to generate a complete, submission-ready first draft in minutes — then review and edit it before submission. The platform handles policy research, constraint analysis, and document structure automatically.

£95 per document — no subscription needed, with a free Permitted Development check available to all users.

Generate your Planning Statement in minutes

AI-written, policy-referenced Planning Statements — cited to your council's actual local plan policies, tailored to your site's specific constraints. Every statement is written to the standard planning officers expect.