Drafting a design and access statement an officer can use

A design and access statement is required by article 9 of the Development Management Procedure Order 2015, and the statutory design and access statement content is narrower than most people assume. The order asks you to explain the design principles and concepts applied, show how the context was appraised and reflected, set out the access policy adopted, record any consultation on access and say what came of it, and explain how specific access issues have been addressed. That is the whole list.

Everything else in a statement is there because a validation list asks for it, because the officer needs it to write the report, or because somebody in the practice has always done it that way.

When a statement is actually required

The requirement does not apply to every application. A statement is needed for major development, and for development in a conservation area or World Heritage Site where the proposal is for one or more dwellings or for a building of 100 m² or more of floorspace. Applications for listed building consent need one as well.

Householder applications outside designated areas do not need a statement. Neither do applications for a material change of use alone, engineering or mining operations, or works to waste development, subject to the exceptions in the order.

That leaves a large middle ground where a statement is not required but is still useful. A short one on a contested minor application gives the case officer the reasoning behind the design, which is otherwise reconstructed from the drawings and the objections. Check the local validation list first, because many councils require a statement on applications the order would exempt, and a missing document is an invalidation letter rather than a refusal.

The design headings and what each should cover

The old six-part structure of use, amount, layout, scale, appearance and landscaping came from the 2006 regime. The current order does not require those headings, though plenty of validation lists still list them and they remain a sensible skeleton, particularly on outline applications where scale and layout parameters are being fixed.

Used well, each heading answers a question the officer has to answer in the report:

• Use: what the building will be used for and why that use belongs here, referenced to the development plan allocation or policy.
• Amount: how much floorspace or how many units, and what determined that quantum, whether density policy, site capacity or an overshadowing constraint.
• Layout: how buildings, routes, parking, private space and boundaries sit together, and how the arrangement responds to aspect, levels and existing features.
• Scale: height, width and depth in metres relative to what is around it, with a street elevation comparison rather than an adjective.
• Appearance: materials, fenestration rhythm, roof form and detailing, explained against the local character evidence rather than a mood board.
• Landscaping: hard and soft surfaces, planting, levels, drainage interaction and long-term management.

Give numbers. "A modest increase in height" tells the officer nothing. "A ridge 800 mm above the adjoining terrace, which itself steps up 600 mm across four plots" is checkable against the elevations.

Explaining design evolution without self congratulation

Design evolution sections are usually the weakest part of a statement, because they read as a portfolio piece. The useful version is short and factual: what was proposed at pre-application, what the officer or the conservation officer objected to, what changed and why.

Include the option you rejected. A statement that shows a two-storey rear extension was tested and dropped in favour of a single storey with rooflights, because of the 45 degree line to the neighbouring window, does two jobs at once. It demonstrates the constraint was understood, and it pre-empts the objection.

Where there was no pre-application engagement, say so plainly rather than inventing a process. Officers read a lot of these and they can tell.

Access as inclusive access, not vehicles alone

The access section is misread more often than any other. The order is concerned with how people reach and use the development, which means inclusive access for everyone, with vehicular access as one part of it.

Cover the approach from the public highway and from public transport, level or ramped thresholds, door and corridor widths, lift provision and the internal circulation for wheelchair users, accessible parking bays and their distance to entrances, drop-off arrangements, wayfinding and lighting, and the accessible and adaptable dwelling standards where local policy applies them. Anchor it to the public sector equality duty under the Equality Act 2010 where the scheme is public-facing.

Then record consultation. If you spoke to an access group, a disabled user or the council's access officer, say who, when and what changed as a result. If you did not consult anyone, the order still requires you to state the position.

Emergency and servicing access belongs here too. Refuse vehicle tracking, fire appliance access and the carry distance for bins are the details that generate late consultee objections.

Relating the design to local character evidence

"The proposal respects the character of the area" is the sentence officers skip. What they read is evidence.

Build the character section from things that can be checked: a conservation area appraisal, a published design guide or design code, the local plan's design policy, a townscape analysis of the street with plot widths and building lines measured from the survey, and photographs keyed to a location plan. Where the council has adopted a design code under the national model, use its terms, because the officer will assess against them.

The National Design Guide's ten characteristics give a vocabulary that officers recognise, and mapping your reasoning onto them costs nothing. Where your scheme departs from a local design guide, name the departure and justify it. A statement that quietly ignores a requirement invites an objection that frames the whole scheme as non-compliant.

Drawings the statement should reference

A statement is a companion to the drawings, and it should be legible next to them. Reference drawing numbers and revisions in the text rather than reproducing images at low resolution. Where you do include images, use the site location plan, the existing and proposed street elevations at the same scale, and a contextual section showing levels.

Three things repeatedly missing from statements, and asked for during determination: a plan showing the relationship to neighbouring windows and gardens, a materials schedule naming products or reference standards, and existing and proposed site sections where the ground slopes.

Length, and what officers skip

Proportionate means proportionate. A householder statement in a conservation area might run to three or four pages. A statement for a hundred dwelling scheme might run to forty, with parameter plans. A twelve page statement for a single dwelling, ten pages of which describe national policy, is worse than a two page one that engages with the site.

What gets skipped: practice biographies, general sustainability narrative that repeats the energy statement, restated national policy, and any paragraph beginning with an assertion about quality. What gets read: the context appraisal, the access section, the design evolution, and the specific response to the constraints the officer already knows about.

AI-assisted drafting helps with the parts that are structural. It can set out the required headings, pull in the relevant development plan policies, keep the tone consistent and mark every place a site-specific fact is still missing, which PlanScope does by inserting a to-be-confirmed flag rather than inventing a number. The design reasoning still has to come from the designer, and the draft has to be read and corrected before it goes anywhere near a portal. The Design and Access Statement page sets out what the generated document covers, and the professional directory is the route to a reviewer where one is wanted. Practices producing these at volume can compare the per-report and subscription options on pricing.

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

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. To see the full set of supporting documents a scheme needs, enter your postcode on PlanScope.