Home › Study guides › Risk responses: escalate, avoid, transfer, mitigate, accept
PMP Risk Response Strategies: Threats and Opportunities
Find uncertain events, rank them by probability and impact, plan responses with owners, then implement and monitor.
In simple words
For each serious risk, pick a response: avoid it, pass it to someone else (like insurance), make it smaller, or accept it. When a risk actually happens, use the plan you already made.
What the PMP exam wants
Risks can be threats or opportunities. The PM identifies them with the team and stakeholders, records them in the risk register, and performs qualitative analysis (probability × impact) to rank them. Quantitative analysis (such as Monte Carlo) is used on larger projects. Each important risk gets a response and an owner.
Threat responses: avoid, transfer, mitigate, accept, escalate (if outside the project's authority). Opportunity responses: exploit, share, enhance, accept, escalate. When a risk occurs, the owner implements the planned response; monitor risks tracks triggers and new risks. In agile, a risk burndown chart shows total risk exposure going down over iterations, and risky items are often done early.
Risk responses at a glance
| Threats (negative risks) | Opportunities (positive risks) | Idea |
|---|---|---|
| Escalate | Escalate | Outside the project's scope or authority: pass it to the right owner |
| Avoid | Exploit | Remove the threat completely / make sure the opportunity happens |
| Transfer | Share | Give ownership to a third party (insurance, contract / partnership) |
| Mitigate | Enhance | Reduce / increase the probability or impact |
| Accept | Accept | No action unless it occurs; active acceptance keeps a contingency reserve or plan |
Risk response strategies for threats
A threat is a risk that would hurt the project if it happens. For every important threat, the team chooses one strategy and names a risk owner, the person who watches the risk and carries out the response.
| Strategy | What you do | Example |
|---|---|---|
| Escalate | The threat is outside the project's authority or scope, so you pass it to the right owner (for example the program or portfolio manager). It is then not tracked by the project any more. | A company-wide software licence may be cancelled. The IT director decides, not the project. |
| Avoid | Change the plan so the threat cannot happen, or protect the project from its impact completely. | Use a proven supplier instead of a new one that has never delivered this part. |
| Transfer | Move the impact and ownership to a third party, usually for a fee. The risk still exists, but someone else carries it. | Insurance, a warranty, or a fixed-price contract. |
| Mitigate | Take early action to make the probability or the impact smaller. | Run a pilot test before the full rollout. |
| Accept | Acknowledge the threat and take no proactive action. Acceptance can be active or passive (see below). | A small risk of a one-day delay on a task with float. |
Risk response strategies for opportunities
An opportunity is a positive risk: something uncertain that would help the project. The opportunity strategies mirror the threat strategies.
| Strategy | What you do | Example |
|---|---|---|
| Escalate | The opportunity is bigger than the project, so you pass it to the right owner. | The new process could save money in every factory of the company. |
| Exploit | Make sure the opportunity definitely happens (opposite of avoid). | Assign your best engineer so the work finishes early and you get the early-finish bonus. |
| Share | Give part of the ownership to a partner who can capture it better (opposite of transfer). | A joint venture with a company that has the right equipment. |
| Enhance | Increase the probability or the impact (opposite of mitigate). | Add more testers to raise the chance of finishing a phase early. |
| Accept | Take the benefit if it comes, without actively chasing it. | Material prices may fall next quarter. |
Active vs passive risk acceptance
Both mean you accept the risk instead of changing the plan. The difference is preparation:
- Passive acceptance: you do nothing now. If the risk happens, you deal with it then. You only review the risk from time to time.
- Active acceptance: you prepare. The most common way is a contingency reserve of time, money or resources, and sometimes a contingency plan that says what to do if the risk happens.
Example: a supplier may deliver one week late. With passive acceptance, the team simply waits and re-plans if it happens. With active acceptance, the team adds one week of contingency reserve to the schedule and agrees in advance which tasks will move.
Implement risk responses: what to do when a risk happens
Many PMP questions describe a risk that has just occurred. If the risk was identified and a response was planned, the answer is almost always: the risk owner implements the planned response. You do not start a new analysis and you do not go to the sponsor first.
- The trigger (warning sign) appears, or the risk occurs.
- The risk owner carries out the agreed response, using the contingency reserve if one was planned.
- The team checks for secondary risks and residual risk.
- The risk register and other documents are updated. If the response changes a baseline, a change request goes through integrated change control.
Contingent response, workaround, residual and secondary risk
- Contingent response: a response that is used only if a trigger happens. Example: "If the prototype fails the first test, we switch to the backup design."
- Workaround: an unplanned response to a threat that has already happened, usually because it was never identified. An unidentified risk that occurs is an issue.
- Residual risk: the risk that is left after the response. Insurance pays for the damage, but the delay may still remain.
- Secondary risk: a new risk created by the response itself. Using a new supplier to avoid a strike creates the risk that the new supplier is slower.
Contingency reserve or management reserve?
The contingency reserve is for identified risks (known-unknowns). It is part of the cost baseline, and the project manager can use it as planned. The management reserve is for unidentified risks (unknown-unknowns). It is outside the cost baseline, and using it normally needs management approval and a change request. More in the contingency vs management reserve guide.
Non-event risks
Not every risk is a single event that happens or does not happen. Two kinds of non-event risks appear in PMI material:
- Variability risk: something that will happen, but you cannot know how much. Example: productivity may be higher or lower than planned, or the number of defects may vary. Teams use simulation (such as Monte Carlo analysis) and reserves.
- Ambiguity risk: uncertainty about what may happen in the future, for example new regulations or an unclear technology. Teams reduce it with expert input, prototypes, experiments and incremental delivery.
Risks nobody can see in advance are emergent risks. The project protects itself with resilience: management reserve, flexible processes and fast escalation.
Risk responses in agile projects
Agile teams handle risk inside the normal way of working: short iterations, frequent feedback, a risk-adjusted backlog (risk-reducing work is ordered early), spikes to test uncertain ideas, and a risk burndown chart that shows total risk exposure going down. The response strategies are the same; the team just applies them in every iteration.
Real example
Risk: the customer's production parts vary more than the samples. Response (mitigate): request 200 production parts for vision testing before FAT. Owner: controls lead.
The common trap
When an identified risk occurs, implement the planned response; don't start a new analysis. Buying insurance is transfer, not mitigation.
Remember: Threat: avoid, transfer, mitigate, accept. Opportunity: exploit, share, enhance, accept.
🗝 Words to notice in the question
“risk has occurred” → implement the planned response. “insurance” → transfer
Try 3 practice questions
Choose an answer, or open “Show the answer.”
Question 1 A risk identified during planning has just occurred. What should the PM do?
Show the answer
Answer: B. The response was already planned; the risk owner carries it out.
Question 2 The team uses a proven gripper instead of a new design to eliminate a technical risk. This response is:
Show the answer
Answer: C. Changing the plan to remove the threat is avoidance.
Question 3 A risk with a low probability and a small impact is in the risk register. The team decides not to take any action now, and to deal with it only if it happens. Which response is this?
Show the answer
Answer: B. Taking no action now and dealing with the risk only if it occurs is passive acceptance. Active acceptance would set aside a contingency reserve or prepare a contingency plan.
The free demo has this chapter with the key words, the PMP rule and every wrong answer explained. No sign-up, no card.
Open the free chapter → Practice more PMP questionsLearn more in PMCLEAR lessons
- Lesson: Risk process and the risk register
- Lesson: Risk analysis, probability, impact and EMV
- Lesson: Risk responses, threats, opportunities and escalation
- Study guide: Contingency reserve vs management reserve
Questions students ask
What are the risk response strategies for threats?
Escalate, avoid, transfer, mitigate and accept. Avoid removes the threat, transfer moves its impact to a third party, mitigate reduces probability or impact, accept takes no action unless it occurs, and escalate passes it to the right owner outside the project.
What are the risk response strategies for opportunities?
Escalate, exploit, share, enhance and accept. Exploit makes sure the opportunity happens, share gives ownership to a third party better able to capture it, and enhance increases its probability or impact.
What is the difference between active and passive acceptance?
Active acceptance sets aside a contingency reserve or prepares a contingency plan. Passive acceptance takes no action other than reviewing the risk periodically.
Does transfer remove the risk?
No. Transfer moves the ownership and financial impact to a third party, for example through insurance or a fixed-price contract. The event can still happen and still affect the project.