Risk Etc Updates: Project Document Register & Report Changes
PMBOK v8 Definition
Risk Etc Updates refers to the continuous updates made to project documents—specifically the Risk Register and Risk Report—throughout multiple project management processes. These updates occur as outputs of processes including Manage Project Execution, Monitor Risks, Perform Risk Analysis, and Plan Risk Responses. The Risk Register documents identified risks, their analysis, and response plans, while the Risk Report summarizes overall project risk exposure and trends. Both documents are updated whenever new information emerges from risk analysis, monitoring activities, or approved change requests.
Why It Matters for the Exam
The PMI exam frequently tests your ability to identify which project documents are updated in each process and what specific content changes. Questions often present a scenario where risk information changes and ask you to select the correct document update. Expect situational questions where you must distinguish between updating the Risk Register versus the Risk Report, or recognize that both are updated simultaneously in certain processes.
Key Points to Remember (for the exam)
- Main Inputs to Monitor Risks: Risk management plan, Issue log, Lessons learned register, Risk register, Risk report, Work performance data, Work performance reports
- Main Outputs from Monitor Risks: Change requests, Project document updates (Issue log, Lessons learned register, Risk register, Risk report)
- Key Tool for Risk Analysis: Data analysis techniques including Technical performance analysis, Reserve analysis, Audits, and Meetings
- Common Confusion: The Risk Register tracks individual risks while the Risk Report tracks overall project risk—they are updated together but contain different information
- Critical Output from Perform Risk Analysis: Project document updates specifically to Assumption log, Issue log, Risk register, and Risk report
- Approved Change Requests Connection: Approved change requests are inputs to Manage Project Execution and trigger updates to the Risk Register and Risk Report
- Work Performance Data vs. Reports: Work performance data is input to Monitor Risks; Work performance reports are outputs from Monitor Work that feed into risk monitoring
Typical PMI Exam Example
During project execution, a team member identifies a new risk that could delay the critical path by two weeks. The project manager performs qualitative analysis and determines the risk has high probability and high impact. What should the project manager update FIRST?
Answer: The Risk Register (to document the new risk with its probability and impact assessment) and then the Risk Report (to update overall project risk exposure).
PMI Exam Traps
-
Trap: Thinking the Risk Register is only updated during risk identification
-
Reality: The Risk Register is updated in Manage Project Execution, Monitor Risks, Perform Risk Analysis, and Plan Risk Responses—every process that deals with risk
-
Trap: Confusing Work Performance Data with Work Performance Reports as inputs
-
Reality: Work Performance Data is input to Monitor Risks; Work Performance Reports are outputs from Monitor Work that provide analyzed performance information
-
Trap: Assuming the Risk Report is only created once during planning
-
Reality: The Risk Report is continuously updated as an output of Monitor Risks and Perform Risk Analysis processes
-
Trap: Forgetting that Approved Change Requests trigger Risk Register updates
-
Reality: Approved change requests are inputs to Manage Project Execution, which produces updates to the Risk Register and Risk Report as project document updates
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Issue Log | Updated alongside Risk Register | Both are project document updates in Monitor Risks and Manage Project Execution |
| Lessons Learned Register | Updated simultaneously | Lessons learned register is updated with risk-related lessons in the same processes |
| Assumption Log | Input to and updated by Perform Risk Analysis | Assumptions are validated during risk analysis; invalid assumptions become risks |
| Approved Change Requests | Input that triggers Risk Register updates | Approved changes may introduce new risks or modify existing risk responses |
Quick Review Questions
- Which project documents are updated as outputs of Monitor Risks?
- What is the difference between the Risk Register and the Risk Report in terms of the type of risk information they contain?
- When approved change requests are implemented during Manage Project Execution, which risk-related documents must be updated?
- What data analysis technique is specifically listed under Monitor Risks for evaluating risk responses?
- In Perform Risk Analysis, which four project documents receive updates as outputs?
PMBOK v8 Reference
Section 2.7.2 - Perform Risk Analysis Inputs, Tools and Techniques, and Outputs (Figure 2-50) Section 2.6 - Manage Project Execution Inputs, Tools and Techniques, and Outputs (Figure 2-6) Section 2.9 - Monitor Risks Inputs, Tools and Techniques, and Outputs (Figure 2-9 context) Section 2.7.3 - Plan Risk Responses (Figure 2-51)