Writing the design evolution section of a DAS

The design evolution section of a design and access statement exists to answer one question: why does the scheme look like this and not like something else. A case officer writing a report needs to say that the design has been properly considered, and the design evolution section is where they get the material to say it. Design and access statement design evolution is therefore an argument, not a diary. It shows the constraints, the options tested against them, and the reasoning that led to the submitted scheme.

What the design evolution section is for

Article 9 of the Development Management Procedure Order 2015 requires a design and access statement for major development and, in a conservation area or World Heritage Site, for one or more dwellings or a building with 100 m² or more of floorspace. Listed building consent applications need one too.

The Order asks the statement to explain the design principles and concepts applied, to explain how the development plan's design policies have been taken into account, to say what consultation has been undertaken on design and access and what account was taken of it, and to explain how access issues have been addressed.

Read that list again and notice what it does not ask for. It does not ask for a description of the proposal, which the drawings already give. The consultation limb is the statutory hook for the design evolution section, and it is the one most statements answer with a single sentence.

The headings a case officer still looks for

The 2015 Order dropped the prescribed sub-headings that earlier regulations used, but officers were trained on them and most local validation lists still expect them. Use them, because a familiar structure is read faster and quoted more readily in a report.

Amount, meaning how much development and why that quantum. Layout, meaning the relationship between buildings, spaces, routes and boundaries. Scale, meaning height, width and depth relative to context. Landscaping, meaning the treatment of external space, planting and boundaries. And appearance, meaning materials, fenestration, detail and the way the building meets the ground and the sky.

Write each as a decision rather than a description. "Scale: three storeys" is a fact from the drawings. "Scale: three storeys to the street frontage, matching the parapet height of the terrace to the north, dropping to two storeys at the rear boundary to hold the 45-degree line from the neighbouring rear windows" is a decision with a reason and a test.

Showing constraints as the driver

The strongest design evolution sections start with the constraints, because a constraint is an argument the officer cannot easily dismiss.

Set them out as a plan and a short list: site levels, existing trees and their root protection areas, daylight and overshadowing of neighbours, noise sources, drainage and flood levels, sight lines at the access, heritage assets and their setting, ecology, and any protected view. Then show, sketch by sketch, how the scheme responded.

That sequence turns a subjective conversation into a technical one. A layout that steps away from a boundary because the root protection area of a category A oak sits there is a layout the tree officer has already agreed. Settling the BS 5837 tree categories before the layout is drawn is what makes that argument available.

The same applies to daylight. Where massing was reduced or set back to protect a neighbour's amenity, say which test drove it and what the result was, because the numbers from a sun on ground and transient overshadowing study make a much better case than an assertion that the impact is acceptable.

Using rejected options honestly

Three or four earlier options, drawn at the same scale and presented side by side with the submitted scheme, do more for an application than any amount of prose.

The trap is fake alternatives. Officers recognise the pattern where option one is a slab block nobody proposed, option two is a pastiche nobody wanted, and option three is the scheme. It reads as a sales technique and it undermines the rest of the statement.

Real options are the ones the design team actually argued about. A courtyard layout that was rejected because it put habitable windows within 12 m of each other. A pitched roof that was rejected because it pushed the ridge above the neighbouring eaves. A dual-aspect arrangement abandoned because the flood level forced the entrance to the other side of the building.

For each, state the option, the reason it was tested, the reason it was rejected, and what carried forward from it. That last part matters. Design evolution is cumulative, and showing that a rejected option contributed something makes the narrative credible.

Where pre-application advice or neighbour comment changed the scheme, say so plainly and specifically. "Following the pre-application meeting on 14 March, the second floor was set back 2 m from the front elevation and the balcony to plot 3 was removed" is worth more than a paragraph about a constructive dialogue.

Illustrative example

An illustrative case: a backland scheme of four houses behind a Victorian terrace. The constraints plan shows two mature limes with overlapping root protection areas across the middle of the site, a 1.8 m level fall to the rear, and rear windows of the terrace 21 m from the northern boundary. Option A put a terrace of four across the site and failed on the root protection areas. Option B moved to two pairs either side of the trees and failed on the access geometry. The submitted scheme keeps the paired arrangement but rotates the northern pair by 15 degrees, which clears the root protection areas, holds a 21 m back-to-back separation and lets the access run on the existing level. Three drawings and 300 words.

Linking the narrative to the National Design Guide

The National Design Guide sets out ten characteristics of well-designed places, covering context, identity, built form, movement, nature, public spaces, uses, homes and buildings, resources and lifespan. Many local plans now require design to be assessed against them, and some authorities have a design code that does the same job locally.

Do not write ten sub-sections. Pick the four or five characteristics that the scheme really engages with and answer those properly, then say why the others are not material at this scale. A statement that gives equal weight to all ten on a five-house infill scheme signals that nobody made a judgement.

Where the authority has adopted a design code or a householder design guide as supplementary planning document, quote the specific requirement and show compliance, or explain the departure. Officers check codes line by line, and an unexplained departure is a refusal reason waiting to be written.

Where these sections read as marketing

Some habits mark a statement as written for the client rather than the officer.

Adjectives without dimensions. A "generous" garden, a "sensitive" response, a "high-quality" material palette. Replace each with a number, a name or a comparison.

Present-tense description of the finished scheme, with no account of how it was arrived at. That is a brochure.

Images without captions or scales, and montages that flatten a five-storey block into the middle distance.

Claims about need or demand that belong in the planning statement and are unevidenced in the design one.

And retrospective justification, where every constraint turns out to have been satisfied by the scheme the client always wanted. Concede something. A statement that says the rear elevation is compromised by the retained chimney stack, and explains why keeping the stack was worth it, reads as honest and makes the rest more persuasive.

The access element without repeating Part M

The access half of the statement is not a compliance schedule for Approved Document M, and copying one in is the commonest way to waste four pages.

Access in planning terms means how people reach and move through the site: the approach from the street and from public transport, the arrival point, level changes and how they are handled, the clarity of the route, the position of parking including accessible bays, and how servicing and refuse collection work without conflicting with pedestrians.

Where the site imposes a conflict, name it and explain the resolution. A raised finished floor level for flood resistance and a level entrance are in tension, and the statement should show the ramp or the internal level change that reconciles them. On a listed building, the tension is between the statutory duty to preserve special interest and the duty to provide inclusive access, and the answer is usually a reversible intervention with the reasoning set out.

Say what consultation informed the access approach, including any access group or occupier input. Article 9 asks for it, and hardly anyone answers it.

Scoping the technical work that will feed the statement, against the full list of report types, before the first sketch is what makes a design evolution section possible to write at all.

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

Draft your design and access statement on PlanScope, then edit the design evolution section around your own sketches.

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