Storm surge vs. flood plain exposure: why your supplier register needs both

A risk manager we talked to last year had a supplier site in coastal Louisiana marked "flood risk: low" on the register. The FEMA flood map showed it sitting just outside the 100-year riverine flood plain. Eighteen months later a tropical storm pushed six feet of water through the loading dock. The site sat in the surge zone, a hazard nobody had checked separately from the flood plain map.

This mix-up shows up constantly in supplier risk registers, and it's worth untangling because the two hazards don't behave the same way, don't show up on the same maps, and don't get mitigated the same way.

What flood plain exposure actually measures

Flood plain exposure is about water that comes from rain and rivers. A site's flood plain designation, the familiar 100-year or 500-year zone, is built from rainfall records, watershed modeling, and how fast a river or stormwater system can move water away before it backs up. It's a function of elevation relative to a channel, drainage capacity, and how much rain falls upstream.

This is inland logic. A supplier's warehouse forty miles from any coastline can sit in a flood plain because a creek behind the property floods every spring. It has nothing to do with tides, wind, or the ocean.

What storm surge exposure actually measures

Storm surge is a coastal phenomenon with a completely different cause: wind from a tropical storm or hurricane physically pushes a mound of ocean water onto the shore, on top of the normal tide. Surge height depends on storm intensity and track, the shape of the coastline, and the slope of the seafloor just offshore (shallow, gently sloping bathymetry funnels more water inland than a steep drop-off does).

A site can have excellent drainage, sit on high enough ground to never flood from rain, and still take on several feet of surge water because it's low relative to sea level and exposed to open coastline or a wide bay. That's why coastal flood maps often carry a separate category, sometimes labeled a V zone, for coastal high-hazard areas where wave action and surge, not rainfall runoff, do the damage.

Why one hazard layer isn't enough for the register

Here's the practical problem for anyone building a supplier hazard register: a standard flood plain check and a storm surge check are two different exposure tests, run against two different drivers, and a site can fail one without failing the other. A distribution center set back from a river might score clean on flood plain exposure and still sit directly in a Category 3 surge path. A tier-two supplier's coastal plant might be well above any riverine flood line and still be the first building to take on water when a hurricane makes landfall.

Treating "flood" as one line item on a register flattens two hazards that call for different questions. For flood plain exposure, you're asking: how close is this site to a waterway or low-lying drainage basin, and what's its elevation relative to the channel. For storm surge, you're asking: how far is this site from open coast or a tidal estuary, what's the local bathymetry, and what surge height has that stretch of coastline seen historically.

A register that lists both hazards separately, with its own exposure tier for each, shows whether the risk at a given site is rainfall-driven, storm-driven, or both. A site flagged for storm surge calls for a hurricane shutdown protocol. A site flagged for flood plain exposure calls for better stormwater pumps and drainage work upstream. Those are two different lines in a capital plan, and a single "flood zone: yes/no" entry can't tell you which one to write.

For procurement teams working through a supplier footprint with sites on both river deltas and open coastline, the fix isn't a smarter spreadsheet column, it's checking each site against each hazard type on its own terms. A ranked hazard register built from imagery rather than a generic flood-zone PDF keeps storm surge and flood plain exposure as separate entries, each with the exposure tier and the imagery basis for the call, so a site gets flagged for the hazard that's actually going to hit it.

If your supplier list has coastal sites you've only ever checked against a flood plain map, that's worth a second look before the next storm season.