Which statement about the Project Charter is true?

Which statement about the Project Charter is true?

• A. It carries forward the information from the proposal and makes it more formal/detailed
• B. It creates the project budget and risk plan from scratch
• C. It defines only the end-state
• D. It is used to select vendors

Answer: (A)

The project charter is the formal authorization for a project and serves to translate what was proposed into an officially approved plan that assigns authority to the project manager and sets the initial direction. This document typically pulls content from the project proposal or business case—things like the project purpose, high-level objectives, key stakeholders, assumptions, constraints, and the overall scope—making them more formal and detailed so everyone has a clear, shared reference. That’s why the statement is true: it carries forward information from the proposal and elevates it into a formal document that authorizes the project and outlines its initial boundaries. The other aspects of planning—such as building a detailed budget and a full risk management plan—are developed in subsequent planning steps, not created from scratch in the charter. The charter may note a high-level budget and risks, but the detailed plans come later. It also isn’t solely about an end state, and vendor selection is typically handled later in procurement activities rather than being a function of the charter.

The project charter is the formal authorization for a project and serves to translate what was proposed into an officially approved plan that assigns authority to the project manager and sets the initial direction. This document typically pulls content from the project proposal or business case—things like the project purpose, high-level objectives, key stakeholders, assumptions, constraints, and the overall scope—making them more formal and detailed so everyone has a clear, shared reference.

That’s why the statement is true: it carries forward information from the proposal and elevates it into a formal document that authorizes the project and outlines its initial boundaries. The other aspects of planning—such as building a detailed budget and a full risk management plan—are developed in subsequent planning steps, not created from scratch in the charter. The charter may note a high-level budget and risks, but the detailed plans come later. It also isn’t solely about an end state, and vendor selection is typically handled later in procurement activities rather than being a function of the charter.