The hazard ranking the council already published
Following a consultant-led risk assessment, your jurisdiction has published a hazard ranking used to set grant priorities. Each hazard was scored by multiplying a 1–5 likelihood by a 1–5 consequence, with both scales assigned by the consultant. The results put dam failure first, winter storm second, pandemic third, and wildfire fourth - even though the wildland–urban interface holds roughly 9,000 structures, the county has recorded three significant ignitions in five years, and the dam is a high-hazard-potential structure with a current inspection record and a functioning emergency action plan. The dam's consequence score of 5 came from an assumption of full failure at maximum pool. The council has already cited the ranking in a public meeting.
1. Diagnose why the ranking conflicts with local operational experience. Name the specific methodological defects.
Read the worked answer
The arithmetic is doing something the analysis never intended. Multiplying two ordinal scales produces a number with no meaning - a 5x4 and a 4x5 are not equivalent statements, and the product implies a precision the inputs do not have.
Single-scenario consequence. Dam failure scores 5 on consequence because the scenario was defined as full failure at maximum pool. That is one point in a distribution, and it was paired with a likelihood estimate that may or may not describe that same scenario. Risk requires the scenario, its frequency, and its consequences to describe the same event.
Wildfire's likelihood was compressed. Three ignitions in five years, with 9,000 structures exposed, is a high-frequency, high-exposure combination. A 1–5 scale has no room to express 'likely within the planning horizon' separately from 'has occurred repeatedly,' so a genuinely recurrent hazard gets flattened next to a rare one.
No vulnerability or capability dimension. Nothing in the method asks how many people cannot evacuate, which structures are unmitigated, or whether the county can actually respond. A well-maintained dam with a tested EAP and a deteriorating WUI with one-lane roads are not comparable on consequence alone.
No uncertainty, no assumptions register. Every score is a point estimate with no range and no stated basis, so the ranking cannot be examined or defended - only repeated.
2. The ranking is already public and tied to grant priorities. What revision can you complete with existing staff, and how do you handle the political exposure?
Read the worked answer
Method you can run in-house: move to scenario-based assessment. For each hazard, define two or three named planning scenarios with a stated magnitude and geography, then estimate frequency, consequences across life safety, property, economic, environmental and continuity-of-operations categories, and - separately - the jurisdiction's current capability against that scenario. Report ranges and write down every assumption. Risk is then a function of scenario, frequency, consequence, and capability gap, not a product of two consultant-assigned integers.
Time-box it: five hazards, two scenarios each, a facilitated workshop with the agencies that would actually respond, and a one-page assumption log per scenario. Two staff can do this in six to eight weeks.
Handle the politics by not reversing the ranking - refining it. Go to the council with: 'the published ranking used a screening method; screening is a first pass, and we are now doing the second pass. Here is what the second pass shows and why it matters for where we spend the match dollars.' You are not contradicting them; you are completing the work they endorsed. Give them the language to describe the change as an upgrade.
Critical: do not let the refinement drop dam failure from consideration. It stays a plan priority - EAP testing, evacuation routes, population at risk - even if its probability-weighted rank falls. If the council reads your revision as 'the dam is fine now,' you have created a new and worse misrepresentation.
3. What would you change about the ranking's use in grant prioritization specifically, and what would you advise against?
Read the worked answer
Change: decouple the two uses. A hazard ranking answers 'what should we worry about'; grant prioritization answers 'which funded project buys the most risk reduction per dollar, within eligibility.' Those are different questions and the second needs the capability-gap column. A hazard that ranks low in probability but has a discrete, fundable, high-leverage mitigation - a levee freeboard project, a WUI fuel break - can and should outrank a higher-probability hazard with no actionable project.
Also change: build the ranking to survive the loss of the consultant. Document the method, keep the assumption log, and make the next update reproducible in-house.
Advise against: republishing a new ordinal score that merely reorders the old one. That invites a comparison the method cannot support and reads as score-shopping to fit a preferred outcome. Present the second-pass results as scenario profiles with ranges and a separate capability-gap summary.
Advise against: using the ranking to justify not funding anything for a hazard because it 'ranked fourth.' Rankings are prioritization within a budget, not a claim that unranked hazards will not occur. Say that explicitly in the transmittal, because a low rank is the first thing a budget office will quote when a hazard materializes.