Quick answer

Before concept design begins, architects should screen a site against statutory flood maps, surface-water data, topography, and access routes to understand whether flood risk affects the buildable area, safe access, ground-floor use, drainage strategy, and planning route. The goal is not to replace a formal FRA. It is to stop the design starting from the wrong assumptions.

Flood risk is rarely just a red overlay on a plan. It is a layout problem, a ground-floor problem, an access problem, and sometimes a viability problem.

That is why it belongs in the first site review rather than in a consultant appendix weeks later. By the time a team discovers that the access road performs badly in flood conditions, or that the southern edge of the site should really be attenuation landscape rather than building footprint, the concept design has already drifted onto the wrong track.

Which flood maps should architects check first?

Start with the public statutory layers that change the planning conversation fastest.

In England, that usually means the Environment Agency Flood Map for Planning, Risk of Flooding from Surface Water, and where relevant reservoir or groundwater information. In the US, the equivalent first pass is usually FEMA FIRM mapping plus local stormwater or drainage overlays where they exist.

The first screening note should answer:

  • does the site intersect a statutory flood zone?
  • what type of flooding is indicated?
  • how much of the parcel is affected?
  • is the only problem the footprint, or is access affected too?

Flood Zone 1, 2, and 3 are not design instructions on their own, but they immediately change how much caution the team should apply.

How do different flood types change the design response?

River and coastal risk often change the planning route first because they trigger more formal scrutiny. Surface-water risk often changes the layout first because it reveals where the site naturally wants to hold or move water. Groundwater and local drainage issues can be less visible at first pass, but still expensive once substructure and drainage design are costed.

Architects should not compress these into one generic "flood issue".

  • River and coastal risk often affect vulnerability classification, sequential reasoning, and resilience measures.
  • Surface-water risk often affects open-space strategy, lower-ground assumptions, and overland flow routes.
  • Groundwater or drainage constraints often affect basement ambition, foundation approach, and attenuation requirements.

Treating every flood issue as the same is how teams get surprised twice.

When does flood risk affect access, not just the footprint?

More often than teams expect.

A site can appear buildable on the parcel itself and still be weak if the route in and out performs badly in flood conditions. That matters for residents, servicing, and emergency access. It also matters to planning officers who are reading the proposal as a whole rather than as a neat footprint diagram.

This is why flood data should be checked alongside topography, movement routes, and the broader site feasibility checklist. The map answer alone is not enough.

What should the early-stage flood note say before an FRA is commissioned?

It should be short and brutally practical.

  • where the flood issue is
  • what type of flood issue it is
  • whether access is affected
  • whether the issue changes the likely layout, use, or viability
  • what specialist input is likely to be needed next

For example: "Southern third of site intersects Flood Zone 2 and high surface-water risk. Western access route remains clear. Likely response is to keep built footprint north, reserve south for landscape and attenuation, and confirm detailed implications with formal FRA before fixing ground-floor uses."

That is useful. "Flood risk present" is not.

Conclusion

Flood risk should not arrive after the concept. It should shape the concept, or stop it, before design time is wasted. The value of early screening is not that it answers every technical question. It is that it tells the team whether the site still supports the brief they think they have.

If you want flood risk read in context with topography, access, and planning from the start, that is exactly where Atlasly fits.

About the author

Shatakshi Patil – Architect writing about pre-construction due diligence, planning context, and site intelligence workflows for design teams using Atlasly.