Risk Acceptance: Using Reserves & Accepting Scope/Quality Reduction
PMBOK v8 Definition
Risk acceptance is a risk response strategy that involves acknowledging the risk and taking no action unless it occurs. Acceptance of the risk's implication(s) usually means using schedule and/or cost reserves and accepting scope and/or quality reduction(s). This strategy applies to both threats and opportunities within project risk management.
Why It Matters for the Exam
Risk acceptance appears frequently in PMI exam questions testing your ability to distinguish between active and passive response strategies. It is commonly tested in scenario-based questions where the project manager decides to acknowledge a risk but take no proactive action, instead relying on contingency reserves. The exam often tests whether you understand that acceptance involves conscious decision-making, not neglect.
Key Points to Remember (for the Exam)
- Definition: Acknowledging the risk and taking no action unless it occurs
- Primary Mechanism: Using schedule reserves and/or cost reserves
- Secondary Consequence: Accepting scope reduction(s) and/or quality reduction(s)
- Key Distinction: Passive acceptance = no action unless risk occurs; Active acceptance = establishing contingency reserves
- Common Confusion: Risk acceptance is NOT the same as ignoring risks—it is a deliberate response strategy
- Reserve Type: Contingency reserves (not management reserves) are typically used for accepted risks
- When to Use: Low-priority risks, risks where response costs exceed potential impact, or when no other response is feasible
Typical PMI Exam Example
A project team identifies a risk that a critical supplier may deliver materials 2 weeks late. The probability is low (10%) and the impact is minor. The project manager decides to add a 2-week schedule reserve and accepts that if the delay occurs, the project may need to reduce scope slightly. This is an example of risk acceptance.
PMI Exam Traps
-
Trap: Confusing risk acceptance with risk avoidance Reality: Acceptance acknowledges the risk and prepares reserves; avoidance eliminates the threat entirely
-
Trap: Thinking acceptance means doing nothing Reality: Acceptance involves planned use of reserves and may include accepting scope/quality reductions
-
Trap: Confusing contingency reserves (for accepted risks) with management reserves (for unknown risks) Reality: Contingency reserves are for known risks; management reserves are for unknown risks
-
Trap: Believing acceptance only applies to threats Reality: Acceptance can apply to both threats and opportunities (though typically for threats)
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Risk Mitigation | Opposite strategy | Mitigation reduces probability/impact; acceptance does not |
| Risk Transference | Different strategy | Transference shifts impact to third party; acceptance retains it |
| Contingency Reserves | Key implementation tool | Reserves are the primary mechanism for risk acceptance |
| Risk Threshold | Decision criterion | Risks below threshold are often candidates for acceptance |
Quick Review Questions
-
What are the two primary reserves used when implementing risk acceptance?
-
A project manager identifies a risk but decides to take no action unless it occurs. Which risk response strategy is being used?
-
True or False: Risk acceptance means the project manager ignores the risk completely.
-
When a risk is accepted, what two project constraints might be reduced as a consequence?
-
What is the difference between contingency reserves and management reserves in the context of risk acceptance?
PMBOK v8 Reference
Section 11.5 - Plan Risk Responses (Risk Acceptance definition and application within the Risk Management knowledge area)