Risk Management

PMP PMP · Business Environment

By Abu Anns · Last updated 20 November 2026Exam version: July 2026 ECO (current since 9 July 2026)

Risk is now a Business Environment topic

In the July 2026 ECO, risk management moved from the Process domain to Business Environment, where it is one of eight tasks: plan and manage risk. The move reflects how PMI now sees risk — not just as a technical planning exercise, but as a business discipline that connects the project to the organization's strategy, appetite for risk, and governance. The content itself is largely unchanged: risk is an uncertain event that, if it occurs, has a positive or negative effect on project objectives. Negative risks are threats; positive risks are opportunities. The exam tests both, and it tests the full risk management process — from planning how risk will be handled, through identifying and analyzing risks, to planning and implementing responses and monitoring risks throughout the project.

The first step is planning risk management: deciding how risk will be handled on this project, and recording it in the risk management plan. This includes the methodology, the roles and responsibilities, the timing of risk activities, the risk categories (often organized in a risk breakdown structure, or RBS), and — critically — the definitions of probability and impact that the project will use. Without agreed definitions, one person's "high probability" is another person's "medium," and the risk analysis is meaningless. The plan also records the organization's risk appetite (how much risk it is willing to accept) and risk thresholds (the level at which a risk becomes unacceptable and must be escalated).

Identifying and analyzing risks

Risk identification is the process of finding the risks that could affect the project, and it involves the whole team and key stakeholders — the people closest to the work know the risks best. Techniques include brainstorming, interviews, checklists, root cause analysis, assumption and constraint analysis, and reviewing lessons learned from past projects. The results go into the risk register, which records each risk, its cause, its potential effect, its probability and impact, its owner, and its planned response. The exam expects you to know that risk identification is continuous: new risks emerge throughout the project, and the register is a living document, not a one-time deliverable.

Qualitative risk analysis prioritizes risks by assessing their probability and impact, usually on a scale (for example, very low to very high) and often visualized on a probability and impact matrix. A risk with high probability and high impact is a top priority; a risk with low probability and low impact can be watched. The exam tests the matrix directly: given a risk's probability and impact ratings, you should be able to say whether it is high, medium, or low priority. Qualitative analysis is fast, cheap, and done for all identified risks; it is the main prioritization tool on most projects.

Quantitative risk analysis goes further: it puts numbers on the overall effect of risk on the project's objectives, usually through techniques such as expected monetary value (EMV) analysis, decision tree analysis, and Monte Carlo simulation. EMV is the most tested: the expected monetary value of a risk is its probability multiplied by its impact in money terms. A risk with a 30% probability of costing $20,000 has an EMV of $6,000 (a threat, so negative). An opportunity with a 40% probability of saving $15,000 has an EMV of $6,000 (positive). Decision trees extend EMV to choices: each branch of the tree has a probability and a payoff, and the best choice is the one with the highest expected value. Monte Carlo simulation runs thousands of random scenarios to produce a probability distribution of possible project outcomes — for example, "there is an 80% chance the project finishes within 12 months." The exam rarely asks for Monte Carlo calculations, but it does expect you to know what the technique produces.

Risk responses: threats and opportunities

Risk response planning is where the exam's situational questions concentrate, and it requires knowing the response strategies for threats and for opportunities. For threats (negative risks), there are five strategies:

Threat strategyMeaning
AvoidEliminate the risk entirely — change the plan so the threat cannot occur (for example, remove the risky part of the scope).
MitigateReduce the probability or the impact of the risk (for example, add testing, use a more experienced team, build a prototype).
TransferShift the risk to a third party (for example, buy insurance, or use a fixed-price contract so the seller bears the cost risk).
AcceptAcknowledge the risk and take no action unless it occurs — either actively (with a contingency plan and reserve) or passively (with no plan).
EscalateRaise the risk to a higher level, because it is beyond the project manager's authority or the project's scope (for example, an organizational or regulatory risk).

For opportunities (positive risks), the strategies mirror the threats: exploit (ensure the opportunity happens), enhance (increase its probability or impact), share (partner with a third party to capture it), accept (take it if it happens), and escalate. The exam tests the distinction between strategies by scenario: a question describing a project manager buying insurance is testing transfer; a question describing a prototype to reduce technical uncertainty is testing mitigate; a question describing a decision to remove a risky feature is testing avoid. The most common confusion is between mitigate and transfer (mitigation reduces the risk itself; transfer moves it to someone else) and between accept and ignore (acceptance is a deliberate decision, often with a contingency plan; ignoring a risk is not a strategy at all).

Reserves, triggers, and secondary risks

Risk responses connect to the project's reserves. The contingency reserve is the budget (and schedule allowance) held for known risks — risks that have been identified and analyzed. It is part of the cost baseline. The management reserve is held for unknown risks (sometimes called "unknown unknowns") and sits outside the baseline, controlled by the sponsor. The exam tests this distinction: a question asking where the money for an identified risk's response comes from is asking about the contingency reserve.

Every risk response should have a risk owner — the person responsible for monitoring the risk and implementing the response — and a trigger: the event or condition that signals the risk is about to occur or has occurred, and that activates the contingency plan. A fallback plan is a backup response, used when the primary response proves ineffective. A secondary risk is a new risk created by implementing a risk response — for example, fast tracking to avoid a schedule risk creates a new quality risk. The exam expects you to know that responses must be checked for secondary risks, and that residual risks (risks that remain after a response) must be monitored.

Monitoring risks

Risk monitoring is continuous: the project manager tracks identified risks, watches for triggers, identifies new risks, and evaluates whether the responses are working. Risk reassessment happens at regular intervals and at major milestones, and the risk register is updated throughout. Risk audits check whether the risk management process itself is effective. The exam tests monitoring through scenarios where a risk's probability or impact has changed: the correct response is to update the risk register, reassess the priority, and adjust the response — not to leave the original assessment in place.

One special case is the risk that has already occurred — it is no longer a risk, it is an issue. Issues are managed through issue management (covered in the change and issues guide), not through risk responses. The exam tests this transition: a question describing an event that has already happened and asking for the risk response is a trap — the correct answer is to manage it as an issue.

Exam mindset for risk

For risk questions, the pattern is: identify early and continuously, prioritize by probability and impact, choose the response that fits the strategy (avoid, mitigate, transfer, accept, escalate for threats; exploit, enhance, share, accept, escalate for opportunities), and monitor throughout. For calculation questions, EMV is probability times impact. And remember the reserves: contingency for known risks (in the baseline), management reserve for unknown risks (outside the baseline, sponsor-controlled).

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A project has identified a risk: there is a 30% probability that a key supplier will fail, which would cost the project $20,000. What is the expected monetary value (EMV) of this risk?

Report an error

Q2.A project manager learns that a critical component may be delayed by a supplier. The project manager decides to order the component from a second supplier as a backup, so that if the first supplier fails, the project is not delayed. Which risk response strategy is this?

Report an error

Q3.A construction project faces the risk of damage from severe weather. The project manager buys insurance to cover weather-related damage. Which risk response strategy is this?

Report an error

Q4.A risk with high probability and high impact has been identified, but it is caused by a pending government regulation that is outside the project manager's authority and affects the whole organization. What should the project manager do?

Report an error

Q5.A project manager is deciding how much contingency reserve to include in the cost baseline. The project has identified 10 risks with a total expected monetary value of $45,000. What is the MOST appropriate basis for the contingency reserve?

Report an error

Q6.A risk response plan states: 'If the supplier's delivery is more than 5 days late, activate the backup supplier.' What is the 'more than 5 days late' condition called?

Report an error

Q7.A project manager fast-tracks two activities to recover schedule. The overlapping work introduces a new risk: the second activity may need rework if the first activity's output changes. What is this new risk called?

Report an error