CAPM Practice: Determine how to document project controls of predictive, plan-based projects

A risk register typically includes: Risk ID (unique identifier), description (what could happen), probability (likelihood), impact (consequences if it occurs), risk score (probability × impact), response plan (avoidance/mitigation/transfer/acceptance), risk owner (responsible party), and status. This structured format enables systematic risk monitoring and response.

**Why not A:** While risk description and mitigation plan are valid fields, including "lessons learned" as a key field is incorrect. Lessons learned are captured in a separate register and are not a standard field within the risk register itself. The risk register focuses on active risk management, not retrospective learning.

**Why not B:** While cost and schedule impact may be assessed as part of the impact analysis, "stakeholder name" is not a standard risk register field. The correct field is "risk owner" — the person responsible for monitoring and responding to the risk, which may or may not be a stakeholder.

**Why not C:** "Risk category" is a valid field, but "risk tool" and "risk technique" are not standard risk register fields. The risk register documents specific risks and their management details, not the tools and techniques used in the risk management process.