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

A well-documented change request includes: what change is being requested (description); why it's needed (justification/business case); and the full impact assessment across all affected knowledge areas (scope, schedule, cost, quality, risks). This comprehensive information allows the CCB to make an informed decision.

**Why not A:** A description alone is insufficient for the CCB to make an informed decision. Without justification and impact analysis, decision-makers cannot evaluate whether the change is worth the cost, schedule, and risk trade-offs it entails.

**Why not C:** Historical changes from similar projects may provide useful context but are not required elements of a change request. The change request must focus on the specific change being proposed, its justification, and its impacts on the current project.

**Why not D:** Identifying who caused the need for the change is not a standard element of a change request and shifts focus from problem-solving to blame. Change requests should focus on the what, why, and impact of the proposed change, not on assigning fault.