This Risk Management Plan example shows how Alex Morgan, PMP, structured the risk approach for Project Phoenix — a $72,250 website launch managed using the PMBOK Guide 8th Edition. Project Phoenix identified 12 risks at kickoff, 7 of which materialized as issues during execution — and the project was still delivered on time and under budget. That outcome was not luck; it was the direct result of a well-designed risk management plan that was actually followed.

What Is a Risk Management Plan?

A Risk Management Plan is a subsidiary component of the Project Management Plan that defines how risk management activities will be conducted throughout the project. It describes the risk identification approach, the probability and impact assessment methodology, the risk tolerance thresholds, the response strategy options, the roles and responsibilities for risk ownership, and the monitoring and review cadence. In PMBOK 8, risk management is addressed primarily within the Uncertainty Performance Domain, which emphasizes that uncertainty is a natural feature of projects — and that the goal of risk management is not to eliminate uncertainty but to navigate it with confidence. The Risk Management Plan is the operational guide for doing exactly that.

What's Inside This Risk Management Plan Example

This Risk Management Plan example for Project Phoenix includes:

• Risk identification methods: structured brainstorming session at kickoff (March 17), assumption analysis using the approved Assumption Log, and checklist review based on MCG's previous web project (2022)
• Probability and impact assessment: 5×5 matrix with defined scales — probability rated 1 (Very Low) to 5 (Very High), impact rated 1 (Negligible) to 5 (Critical) on cost, schedule, scope, and quality dimensions
• Risk Breakdown Structure (RBS): four categories — Technical risks (performance, integration), External risks (vendor delivery, IT coordination), Organizational risks (resource availability, scope change), and Project Management risks (estimating accuracy, communication)
• Risk thresholds: risks with a combined score of 12 or above are classified as High and escalated to Riley Park (Sponsor); risks scoring 6–11 are Medium and managed by the PM; risks scoring 1–5 are Low and monitored passively
• Response strategies: documented options for avoid (eliminate the cause), mitigate (reduce probability or impact), transfer (vendor SLAs, insurance), and accept (active acceptance with contingency, or passive acceptance for low-priority risks)
• Monitoring cadence: risk review as a standing agenda item in every weekly status meeting; full risk register review at each milestone gate

How Alex Morgan Used This Risk Management Plan

Alex Morgan used the Risk Management Plan's thresholds to determine exactly when to escalate risk events to Riley Park — a protocol that prevented both under-communication (surprises) and over-communication (noise). When ISS-005 (hosting migration delay) elevated the schedule risk score above 12, Alex escalated immediately and brought a recovery plan to the same conversation. Riley Park later commented in the project retrospective that she always felt informed without feeling bombarded — a reflection of the plan's tiered threshold system. The 7-out-of-12 risk occurrence rate was high, but the 0-critical-impact outcome was the proof that the response strategies worked.

Download and Customize

This Risk Management Plan example is available as a free download. Use it as a reference to build your own plan, or start with the blank template and fill it in for your project.

• Download the Risk Management Plan Template — PMBOK 8 (blank, ready to use)
• Read the article: Risk Management Plan in PMBOK 8 — Guide and Best Practices

Risk Management Plan Example: Key Takeaways

The standout lesson from this Risk Management Plan example is that risk thresholds and escalation criteria must be agreed before any risk materializes — not negotiated in the moment of a crisis. By establishing the 12-point escalation threshold with Riley Park at kickoff, Alex Morgan created a shared understanding of when the sponsor needed to be brought into a risk conversation. This removed the subjective, relationship-dependent judgment call from escalation decisions and replaced it with an objective, pre-agreed rule. That single element of the Risk Management Plan is arguably the most important governance innovation in Project Phoenix, and it is replicable on any project of any size.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.