While reviewing lessons learned from a past project, a project manager discovers the client's engineer insisted on reviewing every change, even changes not specified in the contract. How should the project manager address this when planning the project?

The correct answer is to ensure the change management plan clearly documents this requirement. The change management plan defines the process for managing changes, including who has authority to approve them. Documenting this specific client requirement in the plan ensures all stakeholders are aware of it from the outset, preventing future misunderstandings and delays. Updating the project charter is incorrect because the charter provides a high-level overview and authorization; detailed process requirements belong in subsidiary plans. Discussing the process with the client is a good step but insufficient on its own; formal documentation is needed. Recording it as a risk is incorrect because this is a known, specific requirement, not an uncertain event. It's a condition to be managed, not a risk to be mitigated.