How to write a project charter
A project charter is the one-page agreement that launches a project. Done well, it heads off the two biggest risks — scope creep and unclear ownership — by getting everyone to agree on the essentials before anyone starts building.
- Purpose & objectives — why it exists and what success looks like.
- Scope & deliverables — what's in, what's out, what you'll produce.
- Milestones & risks — the checkpoints and what could derail them.
Frequently asked questions
- What is a project charter?
- A project charter is a short document that formally kicks off a project. It states why the project exists, what it will deliver, who is involved, and what success looks like — aligning everyone before work starts.
- What should a project charter include?
- At minimum: a purpose, clear objectives, scope (what is and isn’t included), key deliverables, milestones, and the main risks. This tool drafts all of those.
- Why do you need a project charter?
- It prevents scope creep and misalignment. When everyone agrees up front on purpose, scope, and success criteria, the project is far less likely to drift.
- Project charter vs project plan?
- A charter is the high-level "why and what" that authorizes the project. A project plan is the detailed "how and when" you build afterward.