Stockertim Dictionary · Project management
Project charter
Also called project initiation document, PID, project mandate
In short
A short document that formally authorises a project and names its sponsor, manager, purpose, high-level scope, budget and success criteria.
- Beginner
- Document
- Checked
In detail
The project charter is the birth certificate of a project. It records why the project exists, what it is expected to achieve, who sponsors it, who manages it and how much authority that manager has to spend money and use people. Once the sponsor signs it, the project formally exists and the team can start planning in detail.
A good charter is brief, usually a few pages. It sets out the business need, measurable objectives and success criteria, the main deliverables, known assumptions and constraints, major risks, a summary budget and milestone dates, and the key stakeholders. It points to the business case for the full justification rather than repeating it.
The charter's value lies in agreement. Writing it forces the sponsor and the project manager to settle what success looks like before money is spent, and it gives later decisions a reference point. When scope disputes arise, the team can go back to what was authorised.
In practice
Many organisations use a one-page charter template signed at the first gate. Improvement teams in health services use a charter to fix the aim, scope, team and timescale before testing changes.
Watch out
- A charter authorises the project; it is not the detailed plan, which comes later.
- Vague objectives in the charter become arguments at acceptance.
Learn it properly
Official sources
- Define your project charter · NHS England (Quality, Service Improvement and Redesign tools)
- Government Functional Standard GovS 002: Project Delivery · UK Government (Cabinet Office)
Facts last checked on 3 November 2026.
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.