VanillaPM
Sign in Get started free Dashboard
Free template

Project charter template

A free project charter template in Word and Markdown — purpose, measurable objectives, scope, milestones, budget, stakeholders, risks and the project manager's authority, with guidance under every heading.

Download Word (.docx) Download Markdown (.md) Free · no sign-up · opens in Word, Excel, Google Docs/Sheets and LibreOffice

What's inside

  1. Project title and sponsorThe project name, the sponsor who authorises it, and the date.
  2. Purpose and business needWhy the organisation is doing this, and the problem or opportunity it answers. Link the business case.
  3. Measurable objectives and success criteriaEach objective with a number and a date: what will be true, by when, and how you will know.
  4. High-level requirementsThe few conditions the result must meet for the sponsor to accept it.
  5. High-level scopeWhat is in, and just as important, what is out.
  6. Key deliverablesThe main things the project hands over.
  7. Summary milestonesThe handful of dates that matter, with the one that cannot move marked.
  8. Budget summaryThe approved figure, and any reserve held above it.
  9. Key stakeholdersWho is affected or has a say, and their role.
  10. Assumptions and constraintsWhat you are taking as true without proof, and the limits you must work inside.
  11. High-level risksThe few uncertainties that could change the project most.
  12. Project manager and authorityWho manages the project, and what they can decide alone: budget, staffing, changes.
  13. ApprovalName, role, signature and date for the sponsor (and anyone else who must approve).

What a project charter is

The project charter is the document that formally starts a project. It records why the project exists, what it has to achieve, the limits it works inside, and who the project manager is and what they're allowed to decide. The sponsor signs it; from that moment the project manager can spend money and use people on the project's behalf.

It's short on purpose. Detailed plans come later (the project management plan); the charter is the agreement those plans have to honour.

When to use it

  • At the very start, once the business case says the project is worth doing.
  • When a project has been running informally and needs a clear owner and mandate.
  • When the scope or the sponsor changes so much that the original agreement no longer holds.

How to fill it in

Work through the sections in order and keep each one brief. Three of them matter most:

  1. Measurable objectives. Every objective needs a number and a date. "A high-quality resort" can't be checked; "220 keys, practical completion by 31 August 2028, within USD 45.8M, LEED Gold" can.
  2. Scope, including what's out. Saying what is not included prevents the most arguments later. On Coral Ridge, the public access road is the municipality's job, and the charter says so.
  3. The project manager's authority. Write it as numbers: "contingency draws up to USD 250k per change". A vague "manages the project" leaves everyone guessing who can decide what.

The Word file has a sign-off table at the end. Don't start spending until it's signed.

Common mistakes

  • Objectives with no date or number. If you can't tell whether it's been met, it isn't an objective.
  • Writing the whole plan into the charter. Keep the detail for the plans; the charter should fit on two or three pages.
  • No signature. A charter nobody signed hasn't authorised anything.
  • Never revisiting it. If the sponsor or the business case changes, the charter needs to change too.

See it used on a real project: P1 · Develop a common vision