Project Charter
A one-page project charter covering purpose, scope, timeline, and sign-off.
About Project Charter
A project charter is a short document that formally defines a project: why it exists, what it will and will not deliver, when it will happen and who has agreed to it. It is the reference point everyone returns to when questions of direction come up.
The one-page format summarises the essentials so that scope, timeline and sign-off can each be read at a glance. It gives the team, the sponsor and stakeholders a shared understanding before work begins.
At a glance
- Category
- Planning
How it is structured
A charter typically covers the purpose and background, objectives, scope and exclusions, key deliverables, timeline and milestones, and the people involved, including the sponsor and the team. It ends with sign-off, where the sponsor and key stakeholders confirm they agree.
The purpose statement sits at the centre and says in a few lines what the project is for and why it matters. Scope, timing and approvals are then kept in separate sections so each can be read on its own.
Use cases
Starting a project
Agree what the project is for and get formal authority to proceed before resources are committed.
Controlling scope
Refer back to the agreed scope and exclusions when new requests arrive.
Onboarding people
Give new team members and stakeholders a quick, authoritative summary of the project.
How to use it
Tips and common mistakes
- Keep it to one page. If it needs more, the project is not yet clear enough.
- Write the exclusions down. They prevent more arguments than the inclusions.
- Update the charter through a formal change process if scope, budget or dates change materially.
More Planning planning frameworks
Build better plans, faster
Join the waitlist for early access to curated insights, flexible templates, and rapid iteration across strategy, planning, and project management.