Project Charter (Word)
The project charter is the one-to-three-page document that starts a project: why it exists, what it will deliver and what it will not, by when, for how much, who is in charge, and the sponsor's signature authorising the work. This template has every section with a short prompt in brackets explaining what to write, and examples you can overwrite.
Free · no sign-up · opens in Microsoft Word, Google Docs, LibreOffice and WPS Office. Files contain no macros.
Preview
Real view of the file with its sample data (yellow cells are where you type).
PROJECT CHARTER
[Project name]
| Project name | [ ] | Version / date | [1.0] · [DD-MMM-YYYY] |
| Sponsor | [Name, role] | Project manager | [Name, role] |
| Start date | [DD-MMM-YYYY] | Target finish | [DD-MMM-YYYY] |
| Department / client | [ ] | Budget | [Currency] [ ] |
1. Background and purpose
Two or three sentences: what is wrong or missing today, and what will be better when the project is done.
[Example: Our website is eight years old, does not work well on phones and brings in about 40 enquiries a month. A new, mobile-friendly website will make it easier for customers to find us and contact us.]
2. Objectives
Three to five objectives. Each needs a measure and a target so you can check it at the end.
| # | Objective | Measure | Target and date |
| 1 | [Example: More enquiries from the website] | [Enquiries per month] | [From 40 to 70 by DD-MMM-YYYY] |
| 2 | [Example: Site works well on phones] | [Mobile speed score] | [90 or more at launch] |
| 3 | [ ] | [ ] | [ ] |
3. Scope
| In scope (we will do) | Out of scope (we will not do) |
| • [Example: Design and build of 25 pages] • [Content for the main pages] • [Contact form and analytics] • [ ] | • [Example: Online shop or payments] • [Mobile app] • [Translation into other languages] • [ ] |
4. Deliverables
The things that will exist at the end, which someone can see, test or sign for.
| Deliverable | Description | Accepted by |
| [Example: Live website] | [25 pages on the new design, on our domain] | [Sponsor] |
| [ ] | [ ] | [ ] |
5. Key milestones
| Milestone | Target date |
| Charter approved | [DD-MMM-YYYY] |
| [Design approved] | [DD-MMM-YYYY] |
| [Testing complete] | [DD-MMM-YYYY] |
| [Go-live] | [DD-MMM-YYYY] |
| Project closed (lessons learned done) | [DD-MMM-YYYY] |
6. Budget
| Item | Amount ([currency]) | Notes |
| [Labour / internal time] | [ ] | |
| [Suppliers and services] | [ ] | |
| [Software, equipment, other] | [ ] | |
| Contingency ([10]%) | [ ] | Released by the sponsor only |
| Total | [ ] |
Funding source: [department budget / client / grant]. Spending limit the project manager can approve alone: [currency] [ ].
7. Team and roles
| Role | Name | Responsibility | Time on project |
| Sponsor | [ ] | Provides money and authority; approves scope, changes and go-live | [ ] |
| Project manager | [ ] | Plans, coordinates and reports; manages risks and issues | [ ] |
| [Team member] | [ ] | [ ] | [ ] |
…
What's inside
- Project details: name, sponsor, project manager, start and target finish dates, version
- Background and purpose: the problem or opportunity in two or three sentences
- Objectives table with a measure and a target for each, written to be checked at the end
- Scope: in scope and out of scope lists, side by side
- Deliverables, key milestones with dates, high-level budget and funding source
- Team and roles, stakeholders, top risks, assumptions and constraints
- How the project will be governed and reported, and a sign-off table for sponsor and project manager
How to use it
- Fill in the project details table at the top.
- Write the background in plain words: what is wrong or missing today and what changes when the project is done.
- Write three to five objectives that can be measured, for example "Online enquiries up from 40 to 70 a month by June".
- List what is in scope, and just as carefully what is out of scope. The out-of-scope list prevents most later arguments.
- Add the milestones, budget, team and the top five risks. Use the other files in this toolkit for the detail.
- Send it to the sponsor for review, agree changes, and get it signed before work starts.
Tips
- Keep it short. A charter is read by busy sponsors; detail belongs in the plan and the registers.
- Replace every [bracket] or delete the line: a charter with leftover prompts looks unfinished.
- Save the signed copy as PDF and keep it with the project records. If the scope changes later, raise a change request rather than editing the signed charter.
Questions and answers
Who writes the project charter?
Usually the project manager, with the sponsor. The sponsor signs it because the sponsor provides the money and the authority.
What is the difference between a charter and a project plan?
The charter authorises the project and fixes its purpose, scope and limits. The plan explains how the work will be done, task by task, and changes more often.
Is it a contract?
No. It is an internal agreement. For work done for a client, use a proper contract or statement of work and check it with a legal professional.