Risk Register
DE: Risikoregister
A document recording identified risks, their analysis, and planned responses.
Detailed Explanation
The risk register is a comprehensive document recording the results of risk identification, qualitative and quantitative risk analysis, and risk response planning. It is the central repository for all risk-related information on the project.
For each risk, the register typically contains: unique ID, description, category, probability, impact, risk score (P x I), risk owner, trigger conditions, response strategy, contingency plan, fallback plan, residual risk, and current status.
The risk register is a living document updated throughout the project. New risks are added, closed risks are archived, and risk responses are monitored for effectiveness. Regular risk review meetings use the register as their primary working document.
Key Points
- Central repository for all project risk information
- Records risk ID, description, probability, impact, owner, response
- Maintained as a living document throughout the project
- Updated at regular risk review meetings
- Includes both threats and opportunities
- Key input for contingency reserve calculation
Practical Example
A project risk register has 35 entries. Risk R-012: 'Key developer leaves mid-project' — probability: Medium, impact: High, risk score: 15, owner: PM, response: Mitigate (cross-train team, document knowledge), trigger: developer gives notice, contingency: engage contract developer within 1 week. The PM reviews all 35 risks biweekly, updating statuses and scores.
Tips for Learning and Applying
Start the risk register during planning and update it throughout
Assign a risk owner to every risk — unowned risks are unmanaged risks
Include both threats and opportunities in the register
Review and update the register at regular intervals, not just when problems occur
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.