Charter Fundamentals
A project charter is the document that says: we are doing this project, here is what it covers, here is what it does not cover, and here is who has authority to make decisions. It is typically 1 to 5 pages, created in 2 to 8 hours, and signed by the project sponsor.
Updated 11 April 2026
A project charter is a formal document that authorises a project's existence, defines its scope boundaries, establishes success criteria, and grants the project manager authority to apply organisational resources. It is the contract between the project sponsor (who funds the work) and the project manager (who delivers it). Without a signed charter, the project has no formal authority, no defined boundaries, and no mechanism to prevent scope creep.
The charter comes after the business case is approved and before the team is assembled. This is the most common point of confusion: the charter is not part of project planning. It happens before planning begins.
The project manager writes 80 to 90% of the content, typically after a 30-minute conversation with the sponsor. The PM translates the sponsor's intent into structured sections.
The sponsor's signature is the formal grant of authority and budget. Without it, the PM cannot assemble a team, commit resources, or make decisions.
Key stakeholders review the draft and provide input on scope boundaries and success criteria. Their feedback shapes what is in and out of scope.
Every charter format, from a lean 1-pager to a full PMO 12-section document, contains these four core sections. Everything else is optional.
What business problem the project solves, with current metrics and cost of inaction.
3 to 5 measurable outcomes that define what 'done' looks like. Use the SMART framework.
What is included and, more importantly, what is explicitly excluded. The out-of-scope column prevents 52% of scope disputes.
Who can approve budget, scope changes, and timeline shifts. Names, not roles.
39%
of projects without charters exceed budget by 25% or more (PMI 2024 Pulse of the Profession)
52%
experience significant scope creep when scope boundaries are not documented in a charter
The causal mechanism is simple: without documented scope boundaries, every stakeholder adds "just one more thing." Each addition seems reasonable in isolation. In aggregate, they push the project 30 to 50% beyond its original intent. The charter prevents this by creating a written record of what was agreed before work began.
| Methodology | Charter Name | Key Difference | Guide |
|---|---|---|---|
| Traditional (PMBOK) | Project Charter | Full 12-section format with formal governance | View → |
| Agile / Scrum | Lean Charter or Product Brief | Product vision, Definition of Done, sprint boundaries | View → |
| Six Sigma | DMAIC Project Charter | Process metrics, sigma-level targets, SIPOC boundaries | View → |
| PRINCE2 | Project Brief + PID | Two-document approach: brief (like charter) + Project Initiation Document | View → |
"A charter is just a formality."
PMI data: projects without charters are 39% more likely to exceed budget by 25% or more. The charter forces alignment before money is spent.
"Agile projects do not need charters."
They need lean charters. The Scrum Guide does not mention charters, but without documented product vision and sprint boundaries, backlogs grow without constraint.
"The charter should include the project plan."
These are separate documents. The charter says what the project covers. The plan says how to execute it. Combining them produces a 15-page document that nobody reads and sponsors reject.
"Only large projects need charters."
Even a $10K project benefits from a half-page charter. The charter takes 30 minutes to write for a small project and prevents 3 weeks of scope disputes.