What it means
Project risk monitoring and closure track exposure, indicators, response progress, emerging risk, residual and secondary risk, and the evidence required to retire a risk responsibly.
Why it matters
Risk conditions change throughout delivery, so analysis and response decisions must be revisited rather than treated as one-time planning outputs.
Practical focus
- Review trends, triggers, response effectiveness, assumptions, new risks, and changes in overall exposure.
- Convert realized risks into issues while preserving their history and response learning.
- Close a risk only when the event window has passed, exposure is accepted or eliminated, or ownership has been formally transferred.
- Retain the approved definitions, assumptions, decisions, ownership, exceptions, measures, and change history that demonstrate how Project Risk Monitoring and Closure operates in real project work.
- Exercise this failure scenario: A risk is marked closed when an action completes, even though the action created a secondary dependency that is now driving the project’s exposure.
Common mistakes
- Using Project Risk Monitoring and Closure as a label without defining its scope, owner, decision criteria, and expected evidence.
- Treating a template, meeting, tool screen, or status report as proof that Project Risk Monitoring and Closure works consistently in normal delivery.
- Optimizing a single activity while ignoring dependencies, incentives, risk transfer, and the end-to-end outcome.
- Testing only the expected path and never rehearsing this failure condition: A risk is marked closed when an action completes, even though the action created a secondary dependency that is now driving the project’s exposure.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: