Project Charter Template_1
Reference model
Mobilisation runs from charter to kick-off to tracking. The charter is the baseline every later change is measured against.
About this model
A project charter is a short document, completed by the project manager and approved by the sponsor. It sets out why the project exists, what is in and out of scope, how success is measured, the budget and timeline, the main risks and who decides. It is the agreed starting baseline for delivery and change control.
Originator not stated.
How to read it
- Read the objective and success measures first: they say why the project exists.
- Check scope in and out together; gaps between them cause later disputes.
- Use the risk scores to see which risk needs an owner before kick-off.
What this does
Captures the facts a sponsor needs to approve a project at kick-off: objective, scope, success measures, budget, timeline, key risks and the first actions.
When to use it
Use it when mobilising a new project, before the formal kick-off, so the sponsor and team agree one baseline.
Not when: Do not use it for routine operational work, or as a detailed schedule or a full risk register for a large programme.
What happens next
Once the sponsor approves, move to a detailed work plan and a weekly status report built on this baseline.
Golden thread
Builds on ←
- Business case
- Stakeholder map
Feeds into →
- Detailed work plan
- Weekly status report
- Risk register
Use this tool, free
Sign in to open the worksheet. Your work saves as you type, the AI can draft the parts you have not filled in, and you finish with an analysis and a 30/60/90-day action plan.
Drafted with AI and reviewed by Eccellere on 05/11/2026. Guidance, not advice: apply your own judgement.