Which artifact should capture information about approved or rejected changes to avoid confusion among stakeholders?

Which artifact should capture information about approved or rejected changes to avoid confusion among stakeholders?

• A. the change log
• B. the issue log
• C. the risk register
• D. the configuration management plan

Answer: (A)

Tracking decisions on change requests is essential for stakeholder alignment and project governance. The change log is the artifact that records each change request and its outcome—whether it was approved or rejected—along with dates, who decided, and the rationale and impact. This centralized record lets everyone review the current baselines, understand why a change was accepted or not, and plan accordingly, preventing miscommunication and duplicated effort. The issue log tracks problems to resolve, the risk register catalogs potential risks and responses, and the configuration management plan outlines how configuration items and changes are managed, not the outcomes of individual change requests. Therefore, the change log is the right choice for capturing approved or rejected changes.

Tracking decisions on change requests is essential for stakeholder alignment and project governance. The change log is the artifact that records each change request and its outcome—whether it was approved or rejected—along with dates, who decided, and the rationale and impact. This centralized record lets everyone review the current baselines, understand why a change was accepted or not, and plan accordingly, preventing miscommunication and duplicated effort. The issue log tracks problems to resolve, the risk register catalogs potential risks and responses, and the configuration management plan outlines how configuration items and changes are managed, not the outcomes of individual change requests. Therefore, the change log is the right choice for capturing approved or rejected changes.