Of all the documents in a planning application, the Design and Access Statement (DAS) is the one the developer most wants you to like. It's the glossy one. The one with the CGI renders showing happy people walking through sunlit plazas. The one that explains, in the developer's own words, what they're building and why it's wonderful.
It's also the one most likely to tell you what the developer doesn't want you to notice. You just have to know where to look.
What a DAS is
A Design and Access Statement is a document that explains the design thinking behind a development and how people will access it. It's required for most major planning applications, for developments in conservation areas, and for applications involving listed buildings. The developer's architect or planning agent writes it.
Its purpose is to show that the design is well-considered, responds to its surroundings, and meets the needs of the people who'll use it and the people who live nearby. In theory, it's where the developer demonstrates they've thought carefully about context, character, and community impact. In practice, the quality varies wildly.
The structure: what each section means
Most DAS documents follow a standard structure based on six considerations established by government guidance:
1. Use
What the buildings will be used for — residential, commercial, mixed-use, community space. This section tells you the basic purpose of the development. Look for the breakdown: how many homes, how many are affordable, what the commercial units are, whether there's genuinely public space or just "publicly accessible" private land.
2. Amount
How much is being built. The numbers: total floor area, number of units, number of bedrooms, parking spaces. This is where you find out the actual scale. Compare these numbers to the existing site. If there are currently 20 homes and the proposal is for 400, the amount section will tell you that — though it may present it in square metres rather than a multiple that makes the contrast obvious.
3. Layout
How the buildings are arranged on the site. Where the blocks sit, where the roads go, where the open space is (if any). Look at the layout plans carefully. Where are the tallest elements? Are they positioned at the edge of the site nearest your home, or set back? Is the "amenity space" a meaningful garden or a strip of grass between a bin store and a car park?
4. Scale
How big the buildings are — height, width, massing. This is where you find out if the proposed building is 4 storeys or 24. Look for actual measurements in metres, not just descriptions like "appropriate scale" or "broadly consistent with the surrounding area". If the tallest existing building nearby is 12 metres and the proposal is 72 metres, the scale section should acknowledge that gap — and explain why it's acceptable.
5. Appearance
What the buildings will look like. Materials, facade treatments, window patterns, the relationship between solid wall and glazing. The renders in this section are the developer's best-case scenario — perfect light, no weather, landscaping at full maturity. Look past the prettiness and ask: what will this actually look like from your kitchen window in February?
6. Access
How people get in and out. Vehicular access, pedestrian routes, cycle storage, accessibility for disabled users, servicing arrangements. Will construction traffic use your street? Will the main entrance create a bottleneck on a road that's already congested? The access section should address these questions. If it doesn't, that's a gap.
What "responding to context" should look like
A good DAS includes a thorough context analysis: photographs of the surrounding streets, analysis of the existing building heights and character, identification of heritage assets nearby, consideration of important views. The developer should demonstrate they've actually visited the site, walked around the neighbourhood, and designed something that fits.
A bad DAS has two paragraphs saying the area is "characterised by a mix of building types and heights" and then proposes something completely unlike anything within half a mile. Watch for generic descriptions that could apply to any site in any city. If the context analysis doesn't mention your street by name and you're within the direct impact zone, the developer hasn't done the work.
How to read the height and massing
The height information in a DAS can be presented in ways that minimise the apparent impact:
- Storeys vs metres — a "6-storey" building might be 18 metres or 24 metres depending on floor-to-ceiling heights. Always look for the height in metres above ground level (AOD — Above Ordnance Datum).
- Relative height descriptions — "stepping down towards the edges" sounds sympathetic, but if the building steps down from 25 storeys to 15 storeys at the edge nearest your home, that's still a 15-storey wall.
- Cross-section drawings — these show the building in profile alongside neighbouring buildings. If the DAS includes cross-sections that show your street, they're the most revealing drawings in the document. If it doesn't include them, ask yourself why not.
Spotting vague language
Here are the phrases that should make your antenna twitch:
- "Where practicable" — translation: we'll do it if it's easy and skip it if it isn't.
- "Subject to detailed design" — translation: we haven't decided yet and want approval before we do.
- "In keeping with the surrounding area" — check this against reality. If the surrounding area is Victorian terraces and the proposal is a glass tower, "in keeping" needs some serious justification.
- "Appropriate" or "suitable" — without defining what appropriate or suitable means, these words are empty. Appropriate to whom?
- "The proposal will not have a significant impact" — significant is doing a lot of work in this sentence. Demand the evidence.
- "High-quality materials" — which materials, specifically? Until they're named, this is a promise written in sand.
What a good DAS looks like
A good Design and Access Statement is specific, measured, and evidenced. It includes actual photographs of the site and surroundings (not just aerial views). It gives dimensions in metres. It explains how the design addresses specific impacts on neighbours. It references the relevant local plan policies and shows how the design complies with them. It includes shadow studies or refers to the separate daylight report. It feels like it was written for this site, not copied from another project.
What a bad one looks like
A bad DAS is generic, vague, and evasive. The photography is limited to the site itself with no context. Heights are described in storeys not metres. The words "appropriate" and "high-quality" appear on every page without substantiation. There's no mention of neighbouring homes. The renders show the building from flattering angles that hide its relationship to your street. If you swapped the site name for another development and the document still made sense, it's a bad DAS.
Common omissions
- No mention of neighbours — the DAS should acknowledge the existing residential properties nearby and explain how the design minimises impact on them. If it doesn't mention your street at all, that's a significant omission.
- No shadow or daylight reference — the DAS should cross-reference the daylight and sunlight report and explain how the design has been shaped to minimise light loss. If the two documents don't speak to each other, the design process was siloed.
- No heritage context — if there are listed buildings or a conservation area nearby, the DAS must explain how the design preserves or enhances their setting. Ignoring heritage assets is a planning policy breach.
- No pedestrian experience — a street-level perspective of what the building will feel like to walk past. Aerial views and bird's-eye renders hide the experience of being a human standing next to a 20-storey wall.
How to reference the DAS in your objection
When you write your objection, cite the DAS specifically:
- Quote the page number and the exact phrase you're challenging
- Point out contradictions between the DAS and other documents (the daylight report says one thing, the DAS says another)
- Identify what's missing — "The DAS makes no reference to the impact on [your street]"
- Challenge vague commitments — "The DAS states materials will be 'high-quality' but does not specify them"
Tips for first-time readers
- Use the table of contents — jump to the sections about scale, height, and impact on neighbouring properties first.
- Search for your street name — if you're reading a PDF, hit Ctrl+F and type your street. If your street doesn't appear, that's itself a finding.
- Look at the site photos — do they include views from your direction? If not, the developer may be avoiding showing the most impactful perspectives.
- Compare the numbers to what you know — you know how tall your house is. If the proposal is ten times that height and the DAS calls it "sympathetic to its surroundings", trust your instinct.
- Upload it to Hit The Roof — our AI will read every page and help you find the parts that matter for your home. Ask questions in plain English and get answers with page references.