What is the primary purpose of the Risk Register?

• A. To document identified risks, their characteristics, and planned responses.
• B. To log stakeholder feedback
• C. To track issues as they arise
• D. To record accepted changes

Answer: (A)

Risks are uncertainties that could affect project objectives, and the Risk Register is the centralized record of those uncertainties, their details, and how the team plans to respond. It captures identified risks with what could happen, why it might occur (the cause), the potential impact on objectives, the assigned owner, and the probability and impact. It also includes the chosen response strategy (avoid, transfer, mitigate, or accept) and the planned actions or triggers for implementing those responses. This makes the Risk Register the living hub for risk information, guiding monitoring, control, and communication about risk throughout the project.

Logging stakeholder feedback belongs to stakeholder management and requirements or communications activities; tracking issues is handled in an issue log and focuses on problems that have already manifested; recording accepted changes belongs to change control and the change log. Each serves a different purpose and does not replace the central repository used to manage all risk information.