Project Charter
What It Is
A project charter is the founding document of a project. It formally authorises the work to begin, establishes the project manager's authority, and aligns sponsors and stakeholders on what is being done, why, and within what boundaries.
Without a charter, projects start with ambiguous mandates, contested scope, and unclear accountability.
When to Use It
- At project initiation, before planning begins
- When formal approval is needed from a sponsor or steering committee
- When multiple stakeholders need to agree on scope before resources are committed
- As a reset document when a project has drifted significantly from its original intent
What to Include
A well-formed charter captures the essentials without becoming a full project plan:
- Purpose — the business problem or opportunity driving the project
- Objectives — measurable outcomes that define success
- Scope — what is explicitly in and out of scope
- Deliverables — the tangible outputs the project will produce
- Milestones — key dates and decision points
- Risks — top-level threats to delivery with initial mitigations
- Approvals — signatures that formally authorise the project to proceed
Tips
- Keep it concise. A charter is an agreement, not a plan — one to three pages is the target.
- Define out-of-scope explicitly. Ambiguous scope always expands; naming exclusions prevents that.
- Get signatures before work starts. An unsigned charter is just a wish list.
- Treat it as a living document for scope changes, but require re-approval when it changes materially.