The project charter formally starts a project. It is short, high level, and signed by the sponsor. Once signed, the project exists and the project manager has authority to use the organization's resources on it.
A charter usually holds:
- the purpose: why the project exists, the problem or opportunity;
- measurable objectives and the high-level scope;
- key milestones and the summary budget;
- major risks, assumptions and constraints;
- the stakeholders, the project manager and their authority (for example, a spending limit);
- the approval: the sponsor's signature.
What it leaves out is detail: task lists, technical designs, the full schedule. Those come later, in the project management plan, once the project is authorized. A charter crowded with design detail commits to a solution before anyone has planned the work.
What a charter holds.