Most design and access statements are written at the wrong time, by the wrong person, for the wrong reader. They are produced in the fortnight before submission, assembled from marketing renders and a description of what the drawings already show, and read by an officer who is looking for something else entirely. The result is a document that costs money to make and does no work.
It is worth being precise about what the document is for, because when it is done properly it is one of the few pieces of an application that can change an outcome.
It is an argument, not a description
The single most common failure is descriptive drift. The statement explains that the building is seven storeys, that the materials are brick and metal, that the entrance is on the corner. All of this is visible on the drawings. Restating it adds nothing and signals to the reader that there is nothing else to say.
The document’s job is to explain why the scheme is the shape it is. Every building of any complexity is the resolution of a set of competing pressures: site geometry, daylight to neighbours, an awkward level change, a retained structure, a required floorplate, an access constraint, a policy expectation about height. The design is the answer somebody arrived at. The statement is where you show your working.
An officer writing a report has to justify a recommendation in terms that survive challenge. If your statement gives them a clear, honest account of the constraints and the reasoning, you have written part of their report for them. If it gives them adjectives, they must construct the reasoning themselves, and they will construct it less generously than you would.
Show the options you rejected
The most persuasive statements include the alternatives that did not proceed. A massing study showing four configurations, with a short explanation of why three were discarded, does something no amount of visualisation can: it demonstrates that the submitted scheme is a choice rather than a default.
Practices resist this because it feels like handing over ammunition. In practice the opposite is true. If you do not show the obvious alternative, somebody at consultation will propose it, and you will be answering it from a defensive position late in the process with no evidence prepared. If you show it and explain why it fails, you have taken the question off the table and established that you considered the neighbours’ likely concern before they raised it.
This is particularly powerful on height and massing, where the objection is almost always why not lower. A statement that answers that question with quantified consequences, on daylight, on the viability of the ground floor, on the retention of a tree, is far harder to argue with than one that asserts the proposal responds to its context.
The access half is not a compliance annexe
The access content is routinely treated as a paragraph confirming that the scheme complies with the Building Regulations. That is a misunderstanding of both the document and the regulations. Building Regulations approval is a separate process with a separate assessor. What the planning system wants to know is different: how does a person arrive, understand where to go, and get in, given the way this site actually works.
The interesting access questions are almost always site-specific and unglamorous. Where is the level threshold when the pavement falls a metre across the frontage. How does someone using a wheelchair reach the refuse store without going out onto the carriageway. Is the accessible parking bay adjacent to the entrance it serves or across a service yard. Does the step-free route into the building pass through the same door as everyone else, or is it the discreet side entrance that everyone claims to have abandoned and many schemes still contain.
These are design decisions with visible consequences, and they are frequently unresolved at submission because they were left to a later stage. Setting them out honestly, including where a compromise has been made and why, is more credible than a blanket assertion of inclusive design.
Write it early or it cannot help you
A statement written after the drawings are frozen can only rationalise. A statement started at the point of first massing does something more useful: it forces the team to articulate the constraint hierarchy while there is still time to act on it. Teams that draft the constraints section at concept stage regularly discover that two of the constraints they were designing around were assumptions nobody had tested.
There is also a pre-application benefit. If you can hand an officer a five-page constraints and options document before you have committed to a scheme, the conversation you get is materially better than the one that follows a finished proposal. Officers are far more willing to engage with a genuine question than with a request to endorse a decision already made.
What the good ones have in common
- A site analysis with conclusions. Not a catalogue of observations, but a short statement of what the analysis means for the design: the frontage that must be active, the boundary that governs height, the aspect that cannot be compromised.
- An explicit constraints hierarchy. When constraints conflict, which one wins and why. Every real site has at least one such conflict.
- Rejected options with reasons. Two or three, honestly described.
- Consequence, not intention. The claim is not that the scheme respects the townscape. The claim is that the parapet aligns with the neighbouring cornice and the setback above is not visible from the two key views, with the views shown.
- Honest treatment of the weak points. Every scheme has one. Naming it and explaining the mitigation is more persuasive than hoping nobody notices, because somebody will.
- Brevity. A document nobody finishes has no persuasive power. Length is not thoroughness.
What they avoid
Vocabulary that carries no information is the main offender. Words like vibrant, sensitive, contextual, high quality and celebrates describe an aspiration rather than a property of the building. If a sentence would remain true when applied to a different scheme on a different site, it is not doing any work.
Renders substituted for argument are the second. A sunlit perspective with figures on a terrace tells the reader nothing about how the building behaves in the round. Officers develop a strong resistance to imagery used in place of reasoning, and the resistance transfers to the rest of the document.
The third is inconsistency with the rest of the submission. If the statement describes a landscape strategy the drawings do not show, or an entrance arrangement the transport assessment contradicts, the reader stops trusting all of it. Cross-checking the statement against every other submitted document is a dull hour that repeatedly saves weeks.
The underlying point
Planning decisions are judgements made by people who must be able to explain them. A design and access statement is the one document in the application where the applicant speaks directly to that judgement rather than presenting evidence for it. Used as an argument, it is leverage. Used as a description, it is print.
