According to the PMBOK® Guide, the Project Charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

Key Elements of a Project Charter: The charter contains high-level information including the project purpose, measurable objectives, high-level requirements, high-level project description, overall project risk, summary milestone schedule, and preapproved financial resources. Crucially, it includes a Key Stakeholder List.

Stakeholder List vs. Register: At the time the charter is being developed (during the Develop Project Charter process), the project manager identifies the main stakeholders involved in or influenced by the project. This initial list is a high-level component of the charter. The formal, detailed Stakeholder Register is actually an output of the Identify Stakeholders process, which typically occurs immediately after the charter is signed.

Comparison with other options:

A. Management reserves: These are part of the project ' s total budget but are determined during the Determine Budget process (Planning Phase), not during the initiation phase when the charter is created.

B. Work breakdown structure (WBS): The WBS is a detailed decomposition of the project scope created during the Create WBS process in the Planning Phase. It is far too granular for the high-level Project Charter.

D. Stakeholder register: While similar to a stakeholder list, the Stakeholder Register is a specific, detailed project document that is an output of the Identify Stakeholders process. The Charter contains the initial list used to kickstart the identification process.