Site Analysis for Architects: A First-Week Workflow That Tests the Brief

Before opening a planning portal or drawing a boundary, write down the decision the project needs to make in the next two weeks. It is usually one of these:

• should we pursue this site?
• can the current brief survive the site conditions?
• which part of the site should carry the building, access, landscape, or servicing?
• what must the client commission next?

This sounds obvious, but it stops the research stage becoming a collection exercise. A flood layer matters because it changes access, ground-floor use, levels, cost, or all four. A listed building matters because it can change height, setting, and the planning route. The evidence should always be tied to a decision the team can act on.

For an early architectural review, organise the evidence into five groups:

1. Planning and policy context: allocation, designations, nearby decisions, and policy triggers.
2. Physical conditions: boundary, levels, existing buildings, access, utilities assumptions, and ground conditions that are already known.
3. Environmental and statutory constraints: flood, heritage, ecology, trees, contamination, and any other issue that needs specialist confirmation.
4. Movement and context: public transport, walking routes, servicing, neighbouring uses, street character, and arrival sequence.
5. Commercial reality: likely buildable area, abnormal cost risks, comparable evidence, and the assumptions that need testing before a land decision.

Keep the board readable. A client should be able to understand the important evidence in one conversation, while the design team should be able to trace every conclusion back to the map, source, or assumption behind it.

The useful findings appear where layers meet. A site can be policy-supportive but still weak because the accessible edge is flood-constrained. It can have a generous apparent footprint but lose usable area to levels, trees, or servicing geometry. It can be close to a station but unpleasant or indirect to reach on foot.

Use four labels for each finding:

• supportive. The condition helps the current brief;
• manageable with change. The condition is real but can be addressed by a revised layout, programme, or consultant input;
• material risk. The condition can change whether the current proposal should continue;
• not assessed / insufficient evidence. The source is missing, unavailable or too uncertain to support a judgement.

Record the source date, location and scope beside the label. Missing evidence must not be counted as a supportive finding.

This gives the team a way to judge rather than simply describe. It also makes an early review more honest: a material risk is not a failed project, but it is a reason not to spend the next month designing around an untested assumption.

The first output should be short enough to use in a live project meeting. It needs:

• the current brief and the question being tested;
• the three or four conditions most likely to change it;
• a mapped summary of the site opportunities and constraints;
• an explicit recommendation: proceed, proceed with changes, or pause pending a named check;
• the next specialist actions, with a clear distinction between early screening and formal sign-off.

That last distinction is essential. Early site analysis helps teams decide what to investigate and where to focus design effort. It does not replace a measured survey, planning advice, valuation, or any required specialist assessment.

Once the evidence is assembled, the team can make a better first move: position an entrance at the strongest arrival point, keep landscape on the constrained edge, test a smaller footprint, or ask whether the intended programme still fits the site.

Atlasly can help bring the early evidence into a shareable site-analysis workflow. For a fuller checklist, see the site feasibility study checklist. If the review is strong enough to continue, the next question is usually how to test the brief spatially; turn a site brief into a masterplan test sets out that step.