HKSM
Risk Threshold
The risk threshold is the amount of risk exposure a business stakeholder's organization is willing to tolerate. Each risk is compared to this cutoff: if it is below the threshold, acceptance is more likely; if it is above, the organization is less likely to accept it.
Key Points
- Specifies how much risk the stakeholder's organization will accept.
- Acts as the boundary between accepting a risk and requiring a response.
- Can vary by project, risk category, or phase and is documented in the risk management approach.
- Guides prioritization of risk responses and allocation of mitigation effort.
Example
On an agile software project, the product sponsor states that schedule slippage up to 2 weeks is tolerable, but anything beyond that must trigger corrective action. A risk forecasted to cause a 1-week delay is below the threshold and is accepted; a risk that could delay delivery by 3 weeks exceeds the threshold and requires mitigation.
PMP Example Question
Which statement best describes a risk threshold?
- The organization's general attitude toward risk across all projects.
- The point at which a specific risk changes from acceptable to requiring action.
- The probability that a risk event will occur before any response is applied.
- Funds set aside to address known risks during the project.
Correct Answer: B — The cutoff where a particular risk becomes unacceptable and needs action
Explanation: A risk threshold is a specific limit for acceptability of an individual risk. It differs from overall risk appetite (A) and from reserves (D), and it is not a probability measure (C).
