Create a Detailed Risk Register Template for Project Risk Management
Build a complete risk register with scored risks, mitigation strategies, probability-impact matrix, and escalation criteria.
📝 The Prompt
Act as a risk management specialist with deep expertise in enterprise project delivery and PMI risk management frameworks. Create a comprehensive risk register for [PROJECT NAME], a [PROJECT TYPE, e.g., software implementation, product launch, infrastructure upgrade] at [ORGANIZATION NAME].
Project context:
- Industry: [INDUSTRY]
- Project duration: [DURATION]
- Team size: [TEAM SIZE]
- Key dependencies: [EXTERNAL DEPENDENCIES, e.g., third-party vendors, regulatory approvals]
- Known constraints: [BUDGET, TIMELINE, OR RESOURCE CONSTRAINTS]
Generate a risk register that includes:
1. **Risk Register Table** with the following columns for each risk:
- Risk ID (sequential numbering)
- Risk Category (Technical, Financial, Operational, Legal/Compliance, Resource, External)
- Risk Description (clear, specific statement using 'If [cause], then [effect]' format)
- Probability (1-5 scale with definitions)
- Impact (1-5 scale with definitions)
- Risk Score (Probability × Impact)
- Risk Priority (Critical / High / Medium / Low)
- Risk Owner (role responsible)
- Mitigation Strategy (specific preventive actions)
- Contingency Plan (response if risk materializes)
- Status (Open / Mitigating / Closed / Accepted)
- Target Resolution Date
2. **Probability & Impact Matrix** – A 5×5 scoring matrix with color-coded risk zones and threshold definitions
3. **Risk Categories Taxonomy** – Define each category with 2-3 example risk types
4. **Escalation Criteria** – Define when a risk must be escalated to the project sponsor or steering committee
5. **Review Cadence** – Recommended frequency and process for risk review meetings
Populate the register with [NUMBER, e.g., 10-15] realistic, industry-relevant risks based on the project context provided. Ensure a mix of categories and severity levels. Include at least 2 risks rated as Critical.
💡 Tips for Better Results
Write risks in the 'If-Then' format (e.g., 'If the vendor delays API delivery, then integration testing will be pushed back by 2 weeks') to make them specific and actionable. Review and re-score risks at least biweekly — a stale risk register is worse than no register at all. Assign a single risk owner per risk to ensure clear accountability rather than shared responsibility.
🎯 Use Cases
Project managers, PMO leads, and risk analysts who need to systematically identify, assess, and track risks throughout the project lifecycle.