A new stakeholder has joined a project and has a different vision of the scope.

The sponsor wants the document where the initial scope is defined, and the best place to confirm that baseline is the project charter. The charter authorizes the project and typically includes the high-level purpose, objectives, high-level scope, key stakeholders, and success criteria. CompTIA Project+ emphasizes reviewing and using existing project artifacts to maintain alignment; when a stakeholder’s view of scope differs, the PM should first reference the authoritative initiation artifact that establishes the original agreement.

Creating a new project management plan (A) is premature and could worsen confusion if the baseline is not reconfirmed. Meeting minutes (B) can provide context, but they are not the formal scope authorization document the sponsor is asking for. “Perform project scope management” (C) is important as an ongoing process, but the question is asking what to do next to clarify differences and provide the initial scope document—reviewing the charter is the fastest and most correct step.

After reviewing the charter, the PM can facilitate alignment with the new stakeholder, and if scope truly needs to change, route it through formal change control and update scope artifacts accordingly.