PMP · Question #1407
A project manager works for a large manufacturing company with diversified domains. The project team often participates in change requests. Recently, the change control board (CCB) deferred some…
The correct answer is C. Change log. The project manager should use the change log to communicate the status of change requests to stakeholders, as this document specifically records all submitted change requests, their status, and the decisions made by the Change Control Board (CCB).
Question
A project manager works for a large manufacturing company with diversified domains. The project team often participates in change requests. Recently, the change control board (CCB) deferred some requests and the project manager wants to communicate these requests to the stakeholders. What document should the project manager use to communicate these requests?
Options
- ARisk log
- BBacklog
- CChange log
- DIssue log
How the community answered
(50 responses)- A6% (3)
- B2% (1)
- C90% (45)
- D2% (1)
Why each option
The project manager should use the change log to communicate the status of change requests to stakeholders, as this document specifically records all submitted change requests, their status, and the decisions made by the Change Control Board (CCB).
A risk log (or risk register) is used to document potential future events that may impact the project, not the status of formal change requests.
A backlog is commonly used in agile methodologies to list features, requirements, or tasks that need to be completed, not to track the status of formal change control requests.
The change log is the dedicated project document that records all change requests, their status, and the decisions made regarding them by the Change Control Board (CCB). It serves as the official record for communicating the disposition of change requests to all relevant stakeholders.
An issue log (or issue register) tracks actual problems or roadblocks that have occurred in the project and require resolution, not pending or deferred change requests.
Concept tested: Change control documentation
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/integration-management
Topics
Community Discussion
5Confirmed C on exam last week. The change log is the single source of truth for all change requests, including their current status like approved, rejected, or deferred. You use it to communicate those updates to stakeholders so everyone knows where things stand without digging through meeting notes. D trips people up because deferred changes feel like problems, but they are still changes, not issues.
Good call on C, and worth a card that pairs change log with current status specifically, since the exam loves testing whether you know it tracks state transitions, not just that it exists.
C is right, but why not the issue log for deferred items?
Leaned toward B thinking deferred items go to backlog, but change log tracks all CCB decisions.
B is correct but the key distinction is that the backlog holds deferred items awaiting future action, while the change log simply records that the CCB chose to defer them.