PMP · Question #1308
A project manager is reviewing the lessons learned for an historical project. The review identifies that the client's engineer was adamant that they review all changes, even those not identified in th
The correct answer is C. Ensure the change management plan highlights this requirement to prevent future issues.. Given lessons learned that a client's engineer reviewed all changes regardless of contract, the project manager should ensure the project's change management plan explicitly highlights this requirement.
Question
Options
- AUpdate the project charter with this information regarding change management.
- BTalk with the client to ensure they are aware of the change management procedure.
- CEnsure the change management plan highlights this requirement to prevent future issues.
- DUpdate the project risk register to identify this risk and describe how to mitigate the issue.
How the community answered
(59 responses)- A8% (5)
- B3% (2)
- C83% (49)
- D5% (3)
Why each option
Given lessons learned that a client's engineer reviewed all changes regardless of contract, the project manager should ensure the project's change management plan explicitly highlights this requirement.
The project charter is a high-level document; detailed procedures for change management, including specific stakeholder review requirements, belong in the change management plan, not the charter.
Talking with the client is reactive. The proactive and more robust solution is to formalize this known behavior within the project's official change management plan for the current project.
Lessons learned are valuable for future planning. Since it's a known stakeholder behavior, the project's change management plan should be updated proactively to formally include this requirement for comprehensive review by the client's engineer. This prevents future disputes by setting clear expectations and incorporating the observed practice into the project's formal change control process.
While this behavior could be linked to scope or schedule risk, it's more accurately an identified, recurring stakeholder *expectation* related to change control that needs to be managed within the change management process itself, rather than solely as an uncertain risk.
Concept tested: Lessons learned integration into change management
Source: https://www.pmi.org/pmbok-guide-standards/foundations/pmi-lexicon#change-management-plan
Topics
Community Discussion
4
Bao N.Jul 3, 2026Confirmed C on my last practice run. The lessons learned input feeds straight into the change management plan, so documenting the client's review requirement there ensures the process accounts for it before issues surface.
Samuel O.Jul 5, 2026Saw this exact scenario on my exam last month and went with C because the change management plan is where procedural requirements get documented so the team knows the rules of engagement before work starts. In my consulting days we had a client who insisted on reviewing every minor field change, and having it spelled out in the change management plan upfront saved us from constant scope arguments later.
Hiroshi T.Jul 5, 2026Going with D. Per the PMBOK Guide, historical information and lessons learned are inputs to Identify Risks, and a client who insists on reviewing changes outside the contract scope is a future issue that belongs in the risk register with a documented mitigation strategy.
Samuel O.Jul 8, 2026Actually C, Hiroshi. A client pushing for out-of-scope reviews is a scope issue you handle through change control, not a future risk to log in the register. Two decades of consulting taught me that conflating scope creep with risk management just muddies the change request trail.