In risk management, where are likelihood and consequence thresholds defined?

In risk management, where are likelihood and consequence thresholds defined?

• A. Risk Register
• B. Program Risk Process (PRP) Document
• C. Stockpile Plan
• D. Technical Risk Log

Answer: (B)

Likelihood and consequence thresholds are defined in the Program Risk Process Document because it sets the formal framework for how risks are assessed across the program. This document specifies the scales for likelihood and impact and the thresholds that separate different risk levels (for example, what counts as low, medium, or high risk) and the escalation or acceptance actions tied to those levels. Having these thresholds in one authoritative source ensures everyone evaluates risks consistently and uses the same criteria when updating the Risk Register and deciding on mitigations. The Risk Register is the place where individual risks are recorded and tracked, but it relies on the thresholds defined in the PRP rather than defining them itself. A Stockpile Plan deals with logistics and materials, not risk rating, while a Technical Risk Log focuses on technical risks but does not establish the overall program-wide risk rating framework.

Likelihood and consequence thresholds are defined in the Program Risk Process Document because it sets the formal framework for how risks are assessed across the program. This document specifies the scales for likelihood and impact and the thresholds that separate different risk levels (for example, what counts as low, medium, or high risk) and the escalation or acceptance actions tied to those levels. Having these thresholds in one authoritative source ensures everyone evaluates risks consistently and uses the same criteria when updating the Risk Register and deciding on mitigations. The Risk Register is the place where individual risks are recorded and tracked, but it relies on the thresholds defined in the PRP rather than defining them itself. A Stockpile Plan deals with logistics and materials, not risk rating, while a Technical Risk Log focuses on technical risks but does not establish the overall program-wide risk rating framework.