Pre-Construction Due Diligence Checklist for Architects: 15 Checks Before You Accept the Brief

The first pass should focus on the findings that can invalidate the client's assumptions immediately.

1. Planning status and allocation. In England, that means local plan allocations, settlement boundaries, conservation area context, Article 4 directions, and any policy wording that changes what the site is realistically for. In many urban sites, this is the fastest way to discover that the "obvious" use or density is not actually the likely one.

2. Flood and drainage risk. Environment Agency Flood Map for Planning, Risk of Flooding from Surface Water, and local drainage context should be checked before the first concept is trusted. Flood is not only a planning constraint. It is often a layout, ground-floor, and access problem.

3. Access and servicing geometry. A brief can fail because the parcel cannot handle servicing, refuse, fire access, or turning logic without losing far more buildable area than expected.

4. Topography and abnormal works. A site with a 4-metre level change across the buildable zone behaves differently from a flat parcel. Retaining, split levels, and access ramps can quietly remove budget and design freedom.

Those four checks are enough to stop a surprising number of weak briefs before they consume concept-design time.

Planning due diligence should be sequential rather than broad and vague.

First, identify the mapped designations and overlays. Second, read the controlling policy documents. Third, translate them into design consequences. That means:

• what uses are realistic
• what height or massing assumptions are plausible
• what evidence path is likely at pre-app or application stage
• what special review triggers the site creates

For an English site, the sources to review include the adopted development plan and relevant neighbourhood plan, national policy and material local guidance:

• local plan
• Current NPPF for England (check the official edition)
• conservation area appraisals where relevant
• local design guides or tall-buildings guidance
• flood-related policy triggers

Other UK nations need their own framework. Atlasly can help organise available references; verify the current edition and application to the proposal. This guide does not establish a measured speed advantage.

A serious due-diligence pass should include at least these physical and environmental checks:

5. Site boundary logic. Distinguish the study boundary, proposed application boundary and ownership extent. A Land Registry title plan normally shows general boundaries; resolve material uncertainty with legal and survey evidence.

6. Topography and slope. Use desktop terrain to flag potential level changes, then obtain suitable survey evidence before dimensions or costs depend on it.

7. Flood and surface-water risk. Not just whether the site "touches" a flood zone, but how much of the buildable area or access route is affected.

8. Heritage and ecology. Listed-building setting, conservation context, SSSI, local wildlife designations, or biodiversity constraints can all reshape the brief.

9. Solar orientation and overshadowing. A concept that depends on strong residential daylight or outdoor amenity should not be briefed blindly on a weakly oriented or heavily overshadowed site.

10. Neighbour interface. Privacy, overlooking, daylight sensitivity, and frontage context matter much earlier than many briefs assume.

These are possible evidence sources, not a guarantee that Atlasly retrieves every layer for every site. Environment Agency flood layers, Historic England records, local authority policy portals, Ordnance Survey terrain, and GTFS or public-transport data are all part of the real early-stage evidence stack.

This is where supposedly "minor" assumptions become expensive.

11. Transport access. The distance to the station is not enough. The route quality, severance, stop frequency, and daily-services catchment all affect the planning and viability story. In London, PTAL remains a useful shorthand, but route quality still matters.

12. Walkability and daily access. If the project narrative depends on low parking or active-travel logic, the team needs evidence for it. A 15-minute catchment and real street-network logic are much more useful than a generic "well connected" claim.

13. Utilities and infrastructure assumptions. Check available utility records and obtain network-operator enquiries where capacity or connection timing affects the brief. A mapped asset does not establish its depth, exact position, spare capacity or a right to connect. Commission detection and technical work where the decision needs it.

These items often sound less dramatic than flood or heritage, but they are some of the most common reasons an apparently straightforward brief begins to erode once design starts.

14. What does the evidence support? State the provisional use, scale and layout assumptions and the basis for them. Do not describe an early appraisal as planning permission or a complete legal search.

15. What risks and actions remain? Record missing evidence, specialist input, responsible people and the decisions dependent on each check. The brief can progress conditionally where the team understands those dependencies.

Keep reusable drawings and reports with their sources, units, coordinates and limitations. Test exports in the receiving application before treating them as a dependable handoff. These supporting questions complete the 15-check structure; they are not three additional numbered checks.