A structure for a design and access statement that works

A design and access statement structure that works follows the way an officer reads it, not the way a practice files its drawings. The reader is writing a committee or delegated report under time pressure and wants four things they can lift: what the site and its context are, how the design responds to them, what changed during the design process and why, and how people get in and move around. A statement that delivers those in the first eight pages gets quoted. One that opens with a history of the practice gets skimmed.

When a statement is actually required

Article 9 of the Town and Country Planning (Development Management Procedure) (England) Order 2015 sets the requirement. In outline, a statement is needed for major development, for applications for listed building consent, and for development in a conservation area or World Heritage Site where the proposal involves one or more dwellings or 100 m² or more of floorspace.

Several categories are excluded, including engineering and mining operations and applications for a material change of use alone. Householder applications outside designated areas do not need one.

Check the current Order rather than relying on a memory of it, and check the council's local validation list, because some authorities ask for a statement in circumstances the national requirement does not cover. Where one is not required, a short version is still worth writing on any scheme where design is contested. It is the only document in the pack where the architect speaks directly.

Context analysis that earns its space

Context analysis fails in two directions. Too little, and the design looks arbitrary. Too much, and forty pages of history and photographs bury the argument.

The test is whether each piece of analysis leads to a design decision later in the document. A page on prevailing roof pitches belongs there if the proposal picks up a roof pitch. A page on the medieval street pattern belongs there if the layout responds to it. Anything that does not connect forward is padding.

Cover the physical context, the movement network, the designations affecting the site, and the character of the immediate street rather than the whole settlement. Where the site sits in a conservation area or near a listed building, the significance argument belongs in a Heritage Statement and the design statement should reference it rather than repeat it.

Use the National Design Guide's characteristics as an organising frame if your authority works to it. Many do, and matching their vocabulary makes the officer's job easier.

Design evolution, and showing what was tested

This is the section that changes outcomes and the section most often missing.

Officers and inspectors respond to evidence that alternatives were considered. Three or four small diagrams showing options tested, with a sentence on why each was set aside, does more than any amount of describing the final scheme. A rejected option showing a taller block that was cut back after a daylight study is worth a page.

Be specific about what drove each change. Pre-application comments, a root protection area, a sightline, a level difference, an overlooking distance, a viability constraint. Naming the driver makes the change credible, and a change attributed to nothing reads as decoration.

Where the scheme has been through a design review panel, summarise the comments and the response honestly, including the comments you did not act on and why. Panels publish their letters, and officers read them.

Amount, layout, scale, appearance and landscaping

The five headings still work as a structure for the design description, partly because they map onto the reserved matters and partly because officers are used to them.

• Amount: floorspace, unit numbers and mix, density expressed in the same units as the local plan policy.
• Layout: the relationship between buildings, routes, private and public space, aspect and orientation, and the frontage treatment.
• Scale: heights in metres and storeys, related to something existing and measurable on the street.
• Appearance: materials, fenestration proportions, roof form, detailing at ground level, with a materials schedule rather than a mood board.
• Landscaping: hard and soft treatment, trees retained and proposed, boundary treatments, and how the planting is maintained.

Give the numbers in this section. A design statement that describes a building as respecting the prevailing scale, without stating the ridge height against the neighbour's, invites the objection it was trying to avoid.

Access and inclusive design

Access means more than step free entry, and the Order asks for the approach to access and what account has been taken of relevant policies, plus any consultation undertaken on access and what came of it.

Cover approach and arrival from the public highway, level access at entrances, movement within and between buildings, lift provision, accessible parking and its distance to entrances, wayfinding, and accessible or adaptable dwellings where local policy sets a proportion.

Where the building has a public function, say who was consulted. An access group, an occupier's accessibility lead, or a specialist consultant. Consultation that happened should be recorded, since the Order asks for it directly and a blank answer is noticed.

Do not conflate this section with building regulations compliance. Approved Document M sets the construction standard. The statement explains the design approach and the policy response, which is a planning matter.

Responding to pre-application advice

If the council gave written advice, deal with it explicitly, point by point, in a table.

Set out the officer's comment, the response, and where in the drawings or documents the response can be found. Where advice was not followed, say so and give the reason. Officers check this more carefully than any other part of the document, because it tells them whether the application is likely to be recommended for approval.

This table also protects the applicant. Advice given informally at a meeting and then reinterpreted later is a familiar problem, and a written record in the submitted statement fixes the position at the time of submission.

Drawings that carry the argument

The statement should be built around drawings and diagrams rather than photographs of finished buildings elsewhere.

Site analysis diagrams, a constraints plan, the options tested, street elevations including the neighbouring buildings at the same scale, sections through the site showing levels, and a materials schedule keyed to the elevations. Where the setting is sensitive, verified views belong in a Townscape and Visual Impact Assessment rather than being approximated here.

Keep the same drawing numbers used in the application. A statement referring to figures that do not match the submitted drawing schedule creates work for the case officer, and work for the case officer is time on your determination period.

Length, and what to leave out

Thirty pages is generous for most schemes. Twelve is enough for many.

Leave out the practice profile, the client's aspirations, the sustainability marketing that belongs in a Planning Statement or an energy assessment, the repetition of local plan policy text, and the photographs of precedent buildings in other countries that the site cannot reproduce.

What stays is the analysis that leads somewhere, the evolution that shows judgement, the description with numbers in it, the access approach, and the response to advice. Write the summary of design principles last, on one page, in language the officer can quote without editing. That page is the one that ends up in the committee report.

Browse all 66 PlanScope report types to see which supporting documents your application needs alongside the design statement.

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