- Project Management Plan
- Change Management Plan
- Project Roadmap
- Scope Management Plan
- Requirements Management Plan
- Requirements Documentation
- Requirements raceability Matrix
- Project Scope Statement
- Work Breakdown Structure
- WBS Dictionary
- Schedule Management Plan
- Activity list
- Activity attributes
- Milestone list
- Network diagram
- Duration estimates
- Duration estimates worksheet
- Project schedule
- Cost management plan
- Cost estimates
- Cost estimating worksheet
- Cost baseline
- Quality management plan
- Quality metrics
- Responsibility assignment matrix (RAM)
- Resource management plan
- Team charter
- Resource requirements
- Resource breakdown structure
- Communications management plan
- Risk management plan
- Risk register
- Risk report
- Probability and impact assessment
- Probability and impact matrix
- Risk data sheet
- Procurement management plan
- Procurement strategy
- Source selection criteria
- Stakeholder engagement plan
Risk register
The risk register captures the details of identified individual risks. It documents the results of risk analysis, risk response planning, response implementation, and current status. It is used to track information about identified risks over the course of the project. Typical information includes:
- Risk identifier
- Risk statement
- Risk owner
- Probability of occurring
- Impact on objectives if the risk occurs
- Risk score
- Response strategies
- Revised probability
- Revised impact
- Revised score
- Actions
- Status
- Comments
The risk register can receive information from anywhere in the project environment. Some documents that should be specifically reviewed for input include:
- Assumption log
- Issue log
- Lessons learned register
- Requirements management plan
- Requirements documentation
- Scope baseline
- Schedule management plan
- Duration estimates
- Schedule baseline
- Cost management plan
- Cost estimates
- Cost baseline
- Quality management plan
- Resource management plan
- Resource requirements
- Risk management plan
- Procurement documents
- Agreements
- Stakeholder register
The risk register provides information to:
- Scope statement
- Duration estimates
- Cost estimates
- Quality management plan
- Resource requirements
- Risk report
- Procurement management plan
- Stakeholder engagement plan
- Lessons learned register
- Project closeout
The risk register is an output from process 11.2 Identify Risks in the PMBOK® Guide – Sixth Edition. It is developed at the start of the project and is updated throughout the project.
Document element | Description |
Risk ID | Enter a unique risk identifier. |
Risk statement | Describe the risk event or condition. A risk statement is usually phrased as “EVENT may occur, causing IMPACT” or “If CONDITION exists, EVENT may occur, leading to EFFECT.” |
Risk owner | The person responsible for managing and tracking the risk |
Probability | Determine the likelihood of the event or condition occurring. |
Impact | Describe the impact on one or more of the project objectives. |
Score | If you are using numeric scoring, multiply the probability times the impact to deter- mine the risk score. If you are using relative scoring then combine the two scores (e.g., high-low or medium-high). |
Response | Describe the planned response strategy to the risk or condition. |
Revised probability | Determine the likelihood of the event or condition occurring after the response has been implemented. |
Revised impact | Describe the impact once the response has been implemented. |
Revised score | Enter the revised risk score once the response has been implemented. |
Actions | Describe any actions that need to be taken to respond to the risk. |
Status | Enter the status as open or closed. |
Comments | Provide any comments or additional helpful information about the risk event or condition. |