Section 406 hazard mitigation is one of the most underused levers in FEMA Public Assistance. Tied directly to the repair of disaster-damaged facilities, it lets applicants harden infrastructure against future events — and capture additional federal dollars on the same project — when the measures are cost-effective and proportionate to the damage.
Done well, 406 mitigation turns a like-for-like repair into a resilience investment. Done carelessly, it invites scope disputes and de-obligation. Here is how to stay on the right side of that line.
Confirm eligibility first
Section 406 mitigation must be applied to the damaged element of a facility and directly reduce the potential of future, similar damage. It is evaluated per project, and the proposed measures must be cost-effective under FEMA-accepted methods.
- The measure addresses the component that was actually damaged.
- It reduces the risk of future similar damage from the same hazard.
- It is cost-effective using approved pre-calculated benefits or a benefit-cost analysis.
- It meets applicable codes and standards without being a deferred maintenance fix.
Cost-effectiveness strategies
FEMA provides pre-calculated benefit thresholds for certain common mitigation measures, which can streamline approval when your proposed cost falls within them. For larger or more complex measures, a benefit-cost analysis (BCA) demonstrates the long-term value.
The key is to scope mitigation while the project is being formulated — not after obligation. Retrofitting mitigation into an already-obligated project is far harder and often triggers a scope change review.
Avoid the common traps
The most frequent mistakes we see: proposing mitigation on undamaged portions of a facility, conflating mitigation with an upgrade unrelated to the hazard, or failing to document cost-effectiveness. Each of these is a de-obligation risk. Pair every 406 proposal with the engineering rationale and the cost-effectiveness evidence in the project file.
