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

The change log records all submitted change requests — tracking their ID, description, requester, date submitted, impact analysis, CCB decision (approved/rejected/deferred), date of decision, and implementation status. It provides an audit trail of all requested changes throughout the project.

**Why not B:** Documenting all project deliverables and their acceptance criteria belongs in the scope baseline, WBS dictionary, or requirements documentation. The change log specifically tracks change requests, not deliverable specifications or acceptance criteria.

**Why not C:** Documenting all project risks and their mitigation strategies belongs in the risk register. The change log and risk register serve entirely different purposes — one tracks changes, the other tracks risks and their planned responses.

**Why not D:** Documenting all team members and their assigned activities belongs in the responsibility assignment matrix (RAM) or resource management plan. The change log does not track resource assignments — it records the history of all change requests submitted during the project.