Demo environment — data may be reset without notice. Not for production use.
VanillaPM
Sign in Get started free Dashboard
B5 Business Environment · 26%

Plan and manage risk

In the app: Project → Risks (Overview · Risk register)

PMP ECO · Business Environment (26%) · Task B5. Find what could go wrong (and right), size it, plan a response with a trigger to watch, check the reserve can absorb what's left, and keep reviewing it until the risk is gone.

A risk register is a set of bets you keep checking — the short version

What it is

Risk management runs through the whole project:

  1. Plan the approach: the appetite, the scales, the score bands that count as high, how often risks are reviewed, and the reserves. That's the risk management plan.
  2. Identify risks, threats and opportunities, in the risk register.
  3. Qualitative analysis: probability × impact on a 1–5 scale, to rank them.
  4. Quantitative analysis for the ones that matter: a probability and a cost, so EMV = probability × impact in money. The sum of EMV across the threats is the expected loss the contingency reserve should cover.
  5. Plan responses, each with an owner and a trigger (the early warning that it's about to happen). Strategies for threats: avoid, transfer, mitigate, accept (or escalate). For opportunities: exploit, share, enhance, accept (or escalate).
  6. Implement the responses and monitor: review on a cadence, watch the triggers, and assess the residual risk (what's left after the response). A response that creates a new risk has created a secondary risk.

When a risk happens, it becomes an issue (B4).

Why it matters

  • Unfunded risk is a budget overrun waiting to happen. If expected loss is bigger than the contingency left, the project is planning to overspend. That's a decision for the sponsor now, not a surprise later.
  • A risk without a trigger is noticed too late. The trigger tells the owner when to act.
  • Registers decay. A risk last reviewed two months ago may already be an issue.
  • Opportunities are risks too. Managing the upside is how a project gets ahead of plan.

Where you do it in VanillaPM

  • Risks → Overview answers the review questions:
  • tiles: live risks, threat exposure (EMV, with how many risks aren't costed yet), contingency left after approved draws, exposure covered, and needs action;
  • Exposure vs reserves: expected loss against the contingency left and then the management reserve, and who has to decide if it doesn't fit; opportunities shown as upside, not netted off;
  • a probability × impact grid coloured by the bands in the risk management plan, Now and After response;
  • Needs action: risks that happened (with the issue they became), whose trigger fired, that score high with no response plan or no trigger, that are still high after the response, with no owner, or not reviewed within the plan's cadence;
  • Responses: the strategies in use, for threats and opportunities.
  • Risks → Risk register: P × I with the residual score, EMV, response, owner and status. Click a risk to see its response plan, trigger, fallback, impact, residual, the issue it became, and when it was last reviewed.
  • Planning → Risk Management Plan sets the appetite, the bands and the review cadence that the overview uses.

Free tools: Risk register template (Excel, CSV) · Decision tree and EMV calculator · Contingency reserve calculator.

Walked example — Coral Ridge Resort

Coral Ridge has 10 risks: 8 live threats, 1 opportunity, and 1 closed (soft ground at piling, dealt with by extra boreholes and load tests).

The money. The live threats carry USD 3.25M of expected loss. Contingency started at USD 2.4M, but USD 650k has gone to approved changes (the hurricane glazing and the marine-grade rebar), so USD 1.75M is left: 54% of the exposure. Even with the USD 1.2M management reserve, USD 295k has nothing behind it. That's the sponsor's call: add reserve, reduce the exposure, or accept it explicitly. It's also why the risk area of the status report is red (Pr9).

What needs action:

  • RISK-004, lifts at customs: the trigger fired and the risk happened. It's now ISS-006. The fallback (airfreight the guide rails) is ready.
  • RISK-007, community dispute over beach access: the trigger fired, because the fishers' association filed a complaint. The response is already in hand (the access plan in Bangla, a monthly town hall); the fallback is mediation through the Union Parishad.
  • RISK-010, rebar-fixer shortage: identified this week from ISS-007. It scores 12 (high) but has no response plan, no trigger, and no review, and it isn't costed, so it isn't in the USD 3.25M yet. This one's next.
  • Three more haven't been reviewed within the plan's 14 days, including the early-opening opportunity (enhance: fast-track the sea-view fit-out, USD 450k upside).

What the responses buy. On the After response grid, the cyclone drops from 3×5 to 2×4 (storm-season sequencing and all-risk insurance), and corrosion from 2×4 to 1×4 (epoxy rebar, 50 mm cover). The monsoon stays at 4×3: it's accepted, with float in the programme and its cost in contingency.

The workspace — the theory behind each screen

Every screenshot is the actual sample project, not a mock-up.


1 · Exposure, reserves, and where the risks sit

The theory: quantitative analysis and reserves. EMV turns each risk into an expected cost; the sum across threats is what the contingency reserve should cover. A probability-impact grid shows the shape of the risk, using thresholds from the risk management plan.

Coral Ridge — exposure vs reserves and the probability-impact grid
Coral Ridge — exposure vs reserves and the probability-impact grid

Reading the screenshot: 9 live risks (8 threats, 1 opportunity, 1 closed). Threat exposure USD 3.25M, 1 not costed. Contingency left USD 1.75M of USD 2.4M (USD 650k drawn). Exposure covered 54%, USD 1.5M not covered. Needs action 6. The bars: exposure against contingency, then contingency plus management reserve (USD 2.95M). In red: even with the management reserve, USD 295k of expected loss has no reserve. In green, the opportunity's USD 450k upside. The grid (Now): R001 (cyclone) at 3×5; R003, R004, R008 and the opportunity R009 at 3×4; R005 and R010 at 4×3. Bands from the plan: high ≥ 12, critical ≥ 20.

✅ Do compare expected loss with the contingency left, not the contingency you started with.
❌ Avoid netting opportunities off threats to make the reserve look sufficient.


2 · Needs action: the risk review agenda

The theory: monitor risks. Review on a cadence, watch the triggers, check every high risk has a response, and act when a risk happens.

Coral Ridge — risks that need action
Coral Ridge — risks that need action

Reading the screenshot: RISK-004 Imported facade/lifts stuck at customs (red): Happened: now ISS-006 in the issue log and Trigger fired: a shipment not released within five days of arrival. RISK-007 Community dispute over beach access (red): Trigger fired: the fishers' association files a formal complaint. Then amber: the opportunity (RISK-009, not reviewed for 50 days), the loan rate (20 days), corrosion (40 days), and RISK-010 Rebar-fixer shortage: scores high with no response plan, no trigger to watch for, never reviewed.

✅ Do give every high risk a response, an owner and a trigger.
❌ Avoid a register that's reviewed only when someone audits it.


3 · The register: response, trigger, fallback, residual

The theory: the risk register. Each entry records the risk, its analysis, the response and owner, the trigger, the fallback, and the residual risk after the response.

Coral Ridge — the risk register with RISK-004 open
Coral Ridge — the risk register with RISK-004 open

Reading the screenshot: each row: P × I and the score after the response, EMV, the response strategy, owner and status. RISK-004 is open: response plan: pre-clearance with the freight forwarder, HS codes agreed before shipping; trigger: a shipment not released within five days (fired); fallback: airfreight the guide rails; impact if it happens: USD 900k, 21 days, 45% likely; after the response: 2×3 = 6; became: ISS-006. The monsoon (RISK-005, accept) also became ISS-002 in March and stays on monitoring. RISK-009 shows its +USD 450k in green.

✅ Do write the fallback before you need it.
❌ Avoid "mitigate" with no plan behind it. A strategy isn't a response.


4 · After the response: residual risk

The theory: residual risk. A response rarely removes a risk. What's left should be inside the appetite, or accepted on purpose.

Coral Ridge — the grid after the planned responses
Coral Ridge — the grid after the planned responses

Reading the screenshot: After response: the cyclone (R001) and the ECA risk (R003) move to 2×4; R004 and R007 to 2×3; corrosion (R006) to 1×4; the loan rate (R008) to 3×2 once it's transferred to the rate cap. The monsoon (R005) stays at 4×3, because accepting a risk doesn't make it smaller. The note below names the risks with no residual assessment yet: the opportunity (R009) and the new rebar-fixer risk (R010).

✅ Do assess the residual for every risk you respond to.
❌ Avoid assuming a response brings the risk to zero.

Best practices & pitfalls

  • Do manage opportunities as well as threats.
  • Do keep the reserve honest: compare the exposure with what's left after the draws.
  • Do watch for secondary risks that your responses create.
  • Pitfall: a register written at kick-off and never reviewed.
  • Pitfall: "accept" used as "ignore". Active acceptance means a reserve and a plan for when it happens.

On the PMP exam

Know the risk management processes (plan, identify, qualitative, quantitative, plan responses, implement, monitor), the response strategies for threats and opportunities (and escalate when it's outside the project's authority), EMV, probability-impact analysis, triggers, residual and secondary risk, risk appetite and thresholds, and the difference between contingency reserve (for identified risks, the PM's to use within the rules) and management reserve (for unknown unknowns, released by management). When a risk occurs, the right answer is usually to implement the planned response, then update the register and the issue log.

Check your understanding a short quiz — pass to mark the task complete