What is the purpose of a project charter?

It authorizes a project and gives everyone the same starting point: why the project exists, what it must achieve, its boundaries, who the sponsor and lead are, and what authority the lead has. It is the reference for deciding whether a later request belongs in the project.

Who writes and signs the project charter?

The project lead or the person proposing the project usually drafts it, working with the sponsor. The sponsor signs it, because the sponsor is the person accountable for the business case and the one who approves changes to scope, budget or deadline.

How long should a project charter be?

Short enough that the sponsor reads all of it: one to three pages is typical. If it runs longer, detail that belongs in the project plan, such as the task list, has probably crept in.

What is the difference between a project charter and a statement of work?

A charter is an internal agreement that starts a project and sets its boundaries. A statement of work is usually a contractual document between a client and a supplier that specifies the work, deliverables, timeline and payment terms. A client project often has both.

Can a project charter change after it is approved?

Yes, but only through the sponsor. When scope, budget or the deadline changes materially, update the charter, record what changed and why, and get it approved again so the document still describes the project people are actually running.

Why include a section on what the project must not do?

Because objectives can be hit in ways nobody wants: cutting a corner, breaking a policy or harming another team. Writing down the ruled-out approaches makes those limits explicit for people and for any automated tools working on the project.

Free template · no sign-up

Project charter template

A project charter is a short document that formally starts a project. It states why the project exists, what it must achieve, what is in and out of bounds, who the sponsor and lead are, and what authority the lead has. Once the sponsor signs it, the project is real and the team can spend time and money on it.

Write the charter before the detailed project plan. Its job is agreement, not scheduling: it gives everyone the same answer to "what are we doing and why", and it is the document you return to when a request arrives that might not belong in the project.

The CSV is the “Stakeholders and roles” table; it opens in Excel, Google Sheets or Numbers.

#When to use it

When to use a project charter template

A project needs approval or funding before work starts.
Several departments or a client are involved and need the same written starting point.
The goal is clear to the person proposing it but not yet to the people doing it.
You want a reference to settle scope arguments later.

#The template

The project charter template

Fill in the blanks and replace the example rows with your own. Everything below is what the copy and download buttons give you.

Purpose

The problem or opportunity, in two or three sentences:
Why now (what happens if we do nothing):

Objectives and success measures

Each objective should be checkable at the end of the project: met or not met.

Objective 1 — measure of success:
Objective 2 — measure of success:
Objective 3 — measure of success:

Scope

In scope:
Out of scope:
Main deliverables:

Stakeholders and roles

Name people, not departments. The sponsor is the one person who can approve a change to this charter.

Role	Responsibility	Decision rights
Sponsor	Owns the business case; approves the charter and any change to scope, budget or deadline	Final approval
Project lead	Runs the project day to day; reports status; raises risks and issues	Assigns work within the approved scope and budget
Core team member	Delivers assigned work and reports progress	Decides how to do assigned tasks
Key stakeholder	Is affected by the outcome; reviews deliverables	Consulted before scope changes
Client or end-user contact	Represents the people who will use the result; accepts deliverables	Accepts or rejects deliverables

Milestones and deadline

Target start:
Key milestones and dates:
Target finish:
Is the deadline fixed or flexible? Why?

Budget and resources

Approved budget:
People and time committed:
Tools, vendors or other resources:

Assumptions, constraints and risks

Assumptions we are making:
Constraints we must work within:
Top risks and their owners:

What this project must not do

Optional, but the line that saves the most arguments: approaches or outcomes that are ruled out even if they would hit the objective.

Ruled out:

Approval

Sponsor signature and date:
Project lead signature and date:

#How to fill it in

How to fill it in

01
Start with the purpose
Describe the problem or opportunity in plain words and say what happens if nothing is done. If the case is weak here, it will not get stronger in later sections.
02
Turn the purpose into objectives you can check
Write two to four objectives, each with a measure that will be clearly met or missed at the end.
03
Draw the boundaries
List the main deliverables, what is explicitly out of scope, and the assumptions and constraints the team is working under.
04
Name the people and their authority
Fill in the stakeholder table with real names, and say who can approve what. Most charter disputes are really disputes about decision rights.
05
Add dates, budget and top risks
Give the target dates and approved budget, and list the few risks most likely to hurt the project, each with an owner.
06
Get it signed
Walk the sponsor through it and get a signature or written approval. From then on, any change to scope, budget or deadline goes back to the sponsor.

Common mistakes

Writing a full project plan instead of a charter: keep it to what needs agreement, not every task.
Objectives nobody can check, such as "improve the customer experience" with no measure.
A sponsor who is a committee: one named person must be able to say yes or no.
Skipping sign-off, which leaves the charter as a suggestion rather than an agreement.

#In Kavanah

Kavanah keeps a charter on every project

In Kavanah each project's Overview carries a project charter built on the KVN method, and it is not just a document people file away: the AI agent reads it before it acts on that project.

Know-How, Vision, Negation

The project charter records the know-how the work depends on, the vision of the finished result, and the negation: what the project must never do. It matches the last section of this template.

Learn more

False friends

The charter can also list false friends: approaches that look right but are wrong for this project, each with the reason why, so the next person or agent does not try them.

Learn more

Enforced on the agent

When a workspace writes a negation, Kavanah checks the AI agent's task-creating actions against it and refuses work that contradicts it. Human task creation is not filtered.

Learn more

One place for the project's context

The same Overview holds the project's description, linked client, goals, documents and recent activity, next to the tasks, discussions and files.

Learn more

#Questions

Project charter template questions

What is the purpose of a project charter?: It authorizes a project and gives everyone the same starting point: why the project exists, what it must achieve, its boundaries, who the sponsor and lead are, and what authority the lead has. It is the reference for deciding whether a later request belongs in the project.
Who writes and signs the project charter?: The project lead or the person proposing the project usually drafts it, working with the sponsor. The sponsor signs it, because the sponsor is the person accountable for the business case and the one who approves changes to scope, budget or deadline.
How long should a project charter be?: Short enough that the sponsor reads all of it: one to three pages is typical. If it runs longer, detail that belongs in the project plan, such as the task list, has probably crept in.
What is the difference between a project charter and a statement of work?: A charter is an internal agreement that starts a project and sets its boundaries. A statement of work is usually a contractual document between a client and a supplier that specifies the work, deliverables, timeline and payment terms. A client project often has both.
Can a project charter change after it is approved?: Yes, but only through the sponsor. When scope, budget or the deadline changes materially, update the charter, record what changed and why, and get it approved again so the document still describes the project people are actually running.
Why include a section on what the project must not do?: Because objectives can be hit in ways nobody wants: cutting a corner, breaking a policy or harming another team. Writing down the ruled-out approaches makes those limits explicit for people and for any automated tools working on the project.

More free templates

Run the work, not just the template.

Free to start, priced per seat from $3 a month with AI usage metered in credits.

Start free See pricing

Project charter template

The CSV is the “Stakeholders and roles” table; it opens in Excel, Google Sheets or Numbers.

Role

Name

Responsibility

Decision rights

Sponsor

Owns the business case; approves the charter and any change to scope, budget or deadline

Final approval

Project lead

Runs the project day to day; reports status; raises risks and issues

Assigns work within the approved scope and budget

Core team member

Delivers assigned work and reports progress

Decides how to do assigned tasks

Key stakeholder

Is affected by the outcome; reviews deliverables

Consulted before scope changes

Client or end-user contact

Represents the people who will use the result; accepts deliverables

Accepts or rejects deliverables