Oct 13, 2026
How to combine flood, wildfire, and landslide scores into one supplier ranking

Risk managers often end up with three separate exposure numbers per site: a flood score from one vendor, a wildfire fuel-load score from another, and a landslide terrain rating from a third. Each uses its own scale and its own thresholds. Getting the three scores is easy. Turning them into one register that tells you which site to call first is the harder part.
Why a simple average gets you the wrong ranking
The instinct is to average the three scores, or sum them, and sort. That fails for a specific reason: a site scoring low across three independent hazards isn't equivalent to a site scoring high in one. A supplier plant sitting inside a 100-year flood plain with negligible wildfire and landslide exposure should outrank, for most procurement purposes, a site with moderate scores across all three. Averaging buries one severe exposure under two low ones.
Most risk teams land on a "worst hazard governs" rule instead. The site's overall ranking is set by its highest individual hazard level, not the mean. A site counts as high-exposure if any one hazard is high-exposure, full stop. You carry the other two hazards as flags on the entry, not as inputs that dilute the top-line number. That keeps a flood-plain supplier from reading as "medium" just because its wildfire and landslide scores happen to be low that year.
Normalizing scales before you combine anything
None of this works if the underlying scores aren't on the same scale to begin with. A flood score built off FEMA-style zone categories, a wildfire score built off fuel-load classes, and a landslide score built off slope-and-soil terrain classes rarely line up on a shared tier scheme by accident. Before combining anything, convert each hazard to the same structure, low, elevated, high, and write down what each tier means for that specific hazard. A "high" flood tier might mean sitting inside an annual-chance flood plain. A "high" wildfire tier might mean dense fuel load within a set buffer of the structure. The tiers need to be comparable in severity, not just matching in label.
Once the three scores share a common scale, the composite step is straightforward. Take the highest tier across the three hazards as the headline ranking, and list every hazard that landed at or near that level. Sort the supplier list by that ranking first, then by how many hazards are flagged as a tiebreaker. A site with one high-tier hazard and two low ones sits above a site with three moderate-exposure hazards, but below a site with two hazards at the top level. That ordering matches how a procurement team argues it internally: one serious exposure is one too many, and several compounding exposures strengthen the case for relocation or an insurance review.
What the register entry needs to carry
A ranked list by itself doesn't hold up in a board review. Each entry needs the hazard type driving the ranking, the imagery or data basis the call was made from, and the date the assessment ran. Annual re-screening matters here too. Fuel load around a site changes year to year as vegetation grows back after clearing, and flood plain delineations get revised on their own schedule. A composite score from three years ago, on a site whose tree line has since crept back toward the fence, isn't the number you want sitting in a current register.
If you're building this register by hand from spreadsheets and generic hazard-zone PDFs, the part that usually breaks first is confirming a hazard zone overlaps the supplier's physical footprint instead of just the zip code or city it's filed under. Supply Chain Hazard Mapping runs that check against your full supplier list once a year and returns the ranked register with the imagery basis already attached, tying each tier to where the supplier's buildings actually sit on the ground.
If your supplier list needs this kind of annual, site-level recheck, get in touch.