Design & Access Statements in London

Drawings show what is proposed; a design and access statement explains why. It sets out the context analysis, the design rationale, how the proposal responds to local character and policy, and how access and movement work. For listed buildings, conservation areas and larger applications — where these statements are commonly required — a clear, well-evidenced narrative can be decisive in how a case officer reads a scheme, because it lets you frame the proposal rather than leaving the officer to interpret it unaided.

A proper statement works through the design under recognised headings — the amount of development, the layout, the scale, the appearance and the landscaping — explaining the reasoning behind each rather than simply describing the drawings. It then deals with access: not just vehicular access, but inclusive access into and through the building for everyone, and how the proposal connects to its surroundings. The discipline of writing to these headings is itself useful, because it exposes any part of a design that cannot be justified before the council does.

Design and access statements are not needed for everything. They are generally required for major development and for works to a listed building or development in a conservation area above modest thresholds, while most straightforward householder applications do not need one. Over-documenting a simple scheme wastes money and buries the case; under-documenting a sensitive one weakens it. We advise honestly on whether your application genuinely needs a statement, and scale its depth to the scheme.

On listed buildings and in conservation areas, the statement has to do heritage work as well as design work: it must identify the significance of what is there and justify the impact of the proposal against it, in line with national heritage policy. In practice this overlaps with a heritage statement, and for many smaller heritage applications the two are combined into a single coherent document. We make sure the heritage case is explicit, because a planning officer dealing with a designated asset will look for it first.

The fastest way to undermine an application is a statement that contradicts the drawings — a different number of windows, a material described but not shown, an access arrangement that does not match the plan. We write the statement as part of a coherent submission, consistent with the drawings and any other supporting documents and pitched to the specific borough’s guidance, so the application reads as one clear, persuasive case rather than a collection of unrelated parts.

A useful DAS covers amount, layout, scale, appearance, landscaping and access with reasons tied to context and policy. It should match the drawings exactly. Statements that invent materials or window counts not shown on elevations undermine the whole submission.

On heritage assets the DAS often overlaps a heritage statement; we keep one coherent narrative rather than two conflicting documents.

Inclusive access into and through the building, level thresholds where relevant, and connection to the surroundings belong in the statement when required. For householder schemes the access section is proportionate but still honest.

We write for the case officer’s time: clear structure, short paragraphs, and drawings cross-referenced rather than repeated in prose.

The DAS sits with planning drawings, forms, fees and any specialist reports. We coordinate the package so validation is not delayed by a missing or contradictory statement.

Where a full DAS is not required, we do not invent one to pad fees. Proportionate documentation is part of professional service.

The most persuasive statements read as a record of decisions rather than a justification written after the event, and case officers can tell the difference. A statement that explains which options were considered, what the site's constraints ruled out and why the submitted scheme emerged as the answer carries far more weight than one that simply asserts the design is appropriate. Where early feasibility work tested alternatives, we say so; where a massing was reduced or a material changed in response to a constraint, the statement shows the reasoning.

This matters most where the council has already seen the scheme. If you have been through pre-application advice, the statement should set out what the officer said and how the design responded, point by point. Case officers sometimes change mid-application, and a statement that documents the pre-application dialogue means whoever inherits the file gets the full history rather than starting cold. Ignoring pre-application feedback in the statement, or quietly hoping the officer forgets it, is one of the quickest ways to lose an officer's confidence in the whole submission.

The case officer is the primary reader, but rarely the only one. On sensitive schemes the statement is read by conservation and design officers, sometimes by highways or access officers, and on applications that reach committee it is read by councillors who may know the street well but not the policy. Neighbours read it too, because it is published with the application. Each audience takes something different from it, and a statement written purely as a technical policy exercise can fail the non-specialist readers whose views still shape the outcome.

We write accordingly. The structure follows the recognised headings, but the language stays plain, the argument can be followed without the drawings open, and claims about the existing building are made with care. Describing a neighbour's street as having little character, or dismissing the building being altered as worthless, invites objections the application then has to overcome. A statement can be honest about a site's weaknesses while remaining respectful of the people who live around it, and that tone tends to keep the discussion on planning merits rather than turning it into a defence of the neighbourhood.

A design and access statement outlives the decision it was written for. If the application is refused, the statement becomes part of the appeal record, and an inspector will read it alongside the refusal reasons to understand what was argued first time round. A statement that anticipated the difficult questions and answered them squarely gives a planning appeal a solid foundation; one that glossed over the scheme's hardest point leaves the appeal trying to make an argument the original submission never made, and inspectors notice the gap.

For that reason we write statements with refusal in mind even when we expect approval. If the genuinely contentious issue is scale, the statement addresses scale directly rather than burying it under landscaping. An officer's report may quote the statement when setting out the applicant's case, so the words chosen are the words the decision is partly written from. None of this guarantees an outcome, and no statement can rescue a scheme with a genuine policy conflict at its heart. What a well-judged statement does is put the strongest available version of your case on the record from the start, whichever route the application ends up taking.