What it means
Contingency actions are prepared for defined triggers, fallback actions are alternatives when the primary response fails, and reserves provide time or money for recognized uncertainty.
Why it matters
Prepared responses reduce decision delay during disruption, but they must be governed so reserves and plans are used for the exposures they were intended to address.
Practical focus
- Define triggers, response steps, authority, communication, resources, and recovery objectives before the event.
- Separate contingency reserve for identified uncertainty from management reserve for broader unknown exposure.
- Test fallback feasibility and update plans when dependencies or response capability change.
- Retain the approved definitions, assumptions, decisions, ownership, exceptions, measures, and change history that demonstrate how Contingency, Fallback, and Reserves operates in real project work.
- Exercise this failure scenario: A trigger occurs, but the contingency requires unavailable staff and the reserve was already consumed by unrelated scope growth.
Common mistakes
- Using Contingency, Fallback, and Reserves as a label without defining its scope, owner, decision criteria, and expected evidence.
- Treating a template, meeting, tool screen, or status report as proof that Contingency, Fallback, and Reserves works consistently in normal delivery.
- Optimizing a single activity while ignoring dependencies, incentives, risk transfer, and the end-to-end outcome.
- Testing only the expected path and never rehearsing this failure condition: A trigger occurs, but the contingency requires unavailable staff and the reserve was already consumed by unrelated scope growth.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: