All posts
Vincent Chen
CEO, AFFiNE·Published Oct 19, 2026
Project charter template open in an AFFiNE doc next to an edgeless whiteboard scope map

Free Project Charter Template 2026 (With Full Example)

Last updated: October 2026

A project charter is a short document that formally authorizes a project, names the sponsor and project manager, and records the goal, scope, success criteria, budget, and major risks before work begins. Write it in a shared workspace such as AFFiNE so the sponsor, team, and stakeholders all sign off on one live version.

Key takeaways

  • A charter answers one question: "Is this project approved, and what exactly did we agree to?" It is not a schedule or a task list.
  • The best charters fit on one or two pages. Add detail in the project plan, not the charter, and show the timeline in a project roadmap.
  • Every charter needs a named sponsor with authority to approve budget and resolve conflicts. If you cannot name one, you are not ready to start.
  • Write measurable success criteria and explicit out-of-scope items. These two sections prevent most scope arguments later.

What is a project charter?

PMI's PMBOK Guide has long defined the project charter as a document issued by the project initiator or sponsor that formally authorizes the existence of a project and gives the project manager authority to apply organizational resources to project activities. Recent editions (the principle-based 7th edition from 2021 and the newer 8th edition) organize the guide differently, but the charter's role as the authorizing document has not changed. PRINCE2, now owned by PeopleCert, has no document called a charter. Its closest equivalents are the project brief, approved before initiation, and the Project Initiation Documentation (PID), which sets the baseline for how the project will be run.

In practice, a charter does three jobs:

  1. Authorizes. It shows that someone with budget authority said yes.
  2. Aligns. It gives everyone the same one-paragraph answer to "why are we doing this?"
  3. Bounds. It records what is in scope, what is out, and what "done" means.

Project charter vs project plan

People often merge these two documents, and the result is a 30-page charter nobody reads. Keep them separate.

Project charterProject plan
PurposeAuthorize the project and set boundariesExplain how the work will be delivered
When writtenBefore kickoff, during initiationAfter the charter is approved
OwnerSponsor approves, PM draftsProject manager and team
ContentsGoal, scope, success criteria, budget range, key risks, rolesWork breakdown, schedule, resource plan, communication plan, risk register
How often it changesRarely, only through formal change controlRegularly, as the team learns

Charter vs business case vs project brief vs PID vs SOW

You may be handed any of five related documents. This matrix shows which one you need.

DocumentMain questionWho signsUse it when
Business caseIs this worth the money?Investment or budget ownerFunding must be justified before anyone commits
Project charterIs the project approved, and within what limits?SponsorAlmost every project, PMI-style or not
Project brief (PRINCE2)Is it worth initiating?Project boardYour organization runs PRINCE2
PID (PRINCE2)How will the project be controlled?Project boardPRINCE2 projects after initiation
Statement of work (SOW)What will a supplier deliver, for how much?Client and vendorOutside parties do the work under contract

If a business case already exists, link it from the charter instead of copying it. If you still need to write one, start from our business case template. If a vendor is involved, the charter sets your internal limits and the SOW sets the contract; keep the scope wording consistent between them.

If the funding decision still needs numbers, a cost-benefit analysis template shows how to calculate NPV, the benefit-cost ratio, and payback before the charter is written. Detailed requirements belong in their own document, such as a business requirements document template, rather than in the charter.

Once the charter is signed, the plan gets built on top of it: a step-by-step work plan, a project timeline, and a project communication plan.

Project charter format: what every project charter template needs

Most charter formats share the same core sections. The table below lists each one, the question it answers, and a practitioner tip from real kickoff meetings.

SectionQuestion it answersPractitioner tip
Background and problemWhy now?Describe the current pain in one paragraph, with evidence you already have.
ObjectivesWhat will change?Limit yourself to three objectives. More usually means two projects.
Success criteriaHow do we know we won?Each criterion needs a number, a date, or a yes/no test.
Scope (in and out)What are we building, and what are we not?The out-of-scope list is more valuable than the in-scope list.
DeliverablesWhat will we hand over?Name tangible outputs, not activities.
Budget and resourcesWhat can we spend?Give a range and name who approves overruns.
Stakeholders and rolesWho decides, who does, who is informed?Link to a RACI rather than writing paragraphs.
Risks, assumptions, constraintsWhat could go wrong, and what are we taking for granted?List the top five risks only, each with an owner.
ApprovalWho signed off?Collect names and dates. A charter without signatures is a draft.

Free project charter template (copy and paste)

Copy this project charter template into your doc tool and replace each bracket.

PROJECT CHARTER

Project name:        [Short, memorable name]
Project ID:          [Optional internal code]
Version / date:      [v1.0, YYYY-MM-DD]
Sponsor:             [Name, title - holds budget authority]
Project manager:     [Name, title]

1. BACKGROUND AND PROBLEM
[2-4 sentences. What is happening today, who is affected,
and why it needs fixing now.]
Business case: [Link, or "not required" and why]

2. OBJECTIVES
- [Objective 1 - starts with a verb]
- [Objective 2]
- [Objective 3]

3. SUCCESS CRITERIA
- [Measurable result + target + date]
- [Measurable result + target + date]

4. SCOPE
In scope:
- [Item]
Out of scope:
- [Item that someone will probably ask for]

5. DELIVERABLES
- [Tangible output and its owner]

6. MILESTONES
| Milestone             | Target date |
| [Kickoff]             | [Date]      |
| [Key checkpoint]      | [Date]      |
| [Go-live / handover]  | [Date]      |

7. BUDGET AND RESOURCES
Budget range:         [Amount or range]
Overrun approval by:  [Name]
Team / time commitment: [Roles and % allocation]

8. STAKEHOLDERS AND ROLES
[Name / group - role - R, A, C, or I]

9. RISKS, ASSUMPTIONS, CONSTRAINTS
Risks:        [Risk - impact - owner - mitigation]
Assumptions:  [What we believe is true but have not proven]
Constraints:  [Fixed limits: dates, budget, policy, technology]

10. APPROVAL
Sponsor:         ____________  Date: ________
Project manager: ____________  Date: ________
Key stakeholder: ____________  Date: ________

If your team works in sprints, this format still works, but you may want a lighter version. See our agile project charter guide for an iteration-friendly variant. For a charter that defines how a team works together rather than a single project, use the team charter template.

Project charter example: rolling out a self-hosted knowledge base

The example below is fictional. Northwind Logistics is an invented 600-person company. Use it to see how a filled-in charter reads, and how specific each line should be.

PROJECT CHARTER

Project name:     Single Source - internal knowledge base
Project ID:       IT-KB-2026-04
Version / date:   v1.0, 2026-03-02
Sponsor:          VP of Operations (budget owner)
Project manager:  IT Program Manager

1. BACKGROUND AND PROBLEM
Process documents, onboarding guides, and runbooks are spread
across shared drives, chat threads, and personal notes. New hires
in the warehouse and support teams report that they cannot find
current procedures, and IT receives repeated "where is the doc
for X" requests. Security has asked that internal documentation
stay on company-controlled infrastructure.

2. OBJECTIVES
- Give all staff one searchable place for internal documentation.
- Host it on company infrastructure with company sign-in.
- Migrate the documents teams actually use, and retire the rest.

3. SUCCESS CRITERIA
- Top 150 most-used documents migrated by 2026-06-30.
- 80% of active employees sign in at least once by 2026-07-31.
- Each department has a named page owner by go-live.
- "Where is the doc" tickets reduced versus the Q1 baseline,
  measured by IT on 2026-09-30.

4. SCOPE
In scope:
- Self-hosted deployment on the existing internal server cluster
- Sign-in through the company identity provider (OIDC)
- Migration of the top 150 documents and onboarding guides
- Page templates for SOPs, runbooks, and meeting notes
- Two training sessions per department
Out of scope:
- Customer-facing help center
- Migrating archived documents older than three years
- Replacing the ticketing system
- Custom integrations beyond sign-in and file storage

5. DELIVERABLES
- Production workspace with backups configured (IT Ops)
- Migrated document set with owners assigned (Dept. leads)
- Templates, training recordings, quick-start guide (PM)

6. MILESTONES
| Milestone                      | Target date |
| Charter approved               | 2026-03-06  |
| Tool selected, pilot running   | 2026-04-03  |
| Pilot review (2 departments)   | 2026-05-01  |
| Company-wide go-live           | 2026-06-30  |
| Post-launch review             | 2026-09-30  |

7. BUDGET AND RESOURCES
Budget range:          Internal estimate, approved by sponsor
Overrun approval by:   VP of Operations
Team:                  PM (50%), 1 DevOps engineer (30%),
                       1 IT support analyst (40%),
                       1 content lead per department (10%)

8. STAKEHOLDERS AND ROLES
VP of Operations         - Accountable
IT Program Manager       - Responsible
DevOps engineer          - Responsible (deployment, backups)
Security lead            - Consulted (hosting, sign-in)
Department leads         - Responsible (content, owners)
All employees            - Informed

9. RISKS, ASSUMPTIONS, CONSTRAINTS
Risks:
- Low adoption after launch - Dept. leads - assign page owners,
  link docs from onboarding checklist
- Migration takes longer than planned - PM - migrate top 150
  only, freeze new docs in old locations from 2026-05-15
- Server capacity - DevOps - load test during pilot
Assumptions:
- Identity provider supports OIDC.
- Department leads can give 10% of their time.
Constraints:
- Data must stay on company-controlled infrastructure.
- Go-live must happen before the Q3 hiring wave.

10. APPROVAL
Sponsor:          VP of Operations     Date: 2026-03-06
Project manager:  IT Program Manager   Date: 2026-03-06
Key stakeholder:  Security lead        Date: 2026-03-06

Projects like this one usually produce follow-on documentation work. If you are in that position, our guides to writing process documentation and creating a user manual cover what comes after the charter.

One-page charter vs full charter

Not every project needs ten sections. Match the charter to the size and risk of the work: start from the same project charter template and delete what you do not need.

FactorOne-page charterFull charter
Best forInternal projects under a few months, one teamCross-department, multi-quarter, or budget-heavy projects
SectionsProblem, objectives, success criteria, scope, sponsor, milestonesAll ten sections in the template above
ApprovalSponsor sign-off, often in a meetingSponsor plus key stakeholders, recorded
Budget"Within team budget" or a single figureRange, overrun authority, resource allocation

A useful rule: if the project needs approval from more than one budget holder, or if failure would be visible outside your team, write the full version.

How to write a project charter in 7 steps

  1. Interview the sponsor first. Ask three questions: Why now? What does success look like in a year? What would make you cancel this? Write down the answers in their words.
  2. Draft the problem and objectives alone. Do this before you open a meeting. A blank page in a group setting produces vague goals.
  3. Turn objectives into success criteria. For each objective, ask "how would we measure that?" If nobody can answer, rewrite the objective.
  4. Write the out-of-scope list with the team. Ask, "What will people assume we are doing that we are not?" This is the most productive 15 minutes of the process.
  5. Map stakeholders and roles. Use a RACI chart or the RACI matrix template so decision rights are clear.
  6. List the top risks with owners. Five is plenty. Give each a mitigation you would actually do.
  7. Review and sign at kickoff. Walk through the charter in the first meeting, then collect approvals. Our kickoff meeting agenda guide shows where the charter review fits.

Charter acceptance test: score before you ask for sign-off

Before you send the charter to the sponsor, run it through this ten-point check. Score one point per "yes." Below 8, revise before the meeting.

#TestPass if
1SponsorOne named person with budget authority, not a committee
2ProblemA new reader understands why now in under a minute
3ObjectivesThree or fewer, each starting with a verb
4Success criteriaEvery criterion has a number or yes/no test and a date
5Out of scopeLists at least one item a stakeholder has already asked for
6DeliverablesOutputs, not activities, each with an owner
7BudgetA range plus the name of who approves overruns
8RisksFive or fewer, each with an owner and a mitigation
9LengthFits in three pages without attachments
10ApprovalSignature lines name real people, with a version number

Pre-kickoff red flags

Stop and resolve these before kickoff, not after:

  • The sponsor has not read the draft, or a delegate will sign "on their behalf."
  • Two stakeholders describe the goal differently when asked separately.
  • A constraint (hosting rules, a hard date, a frozen budget) surfaces only in the kickoff meeting.
  • Security, legal, or finance has not seen a charter that touches their area.

How to version a charter after a scope change

A charter changes rarely, so each change should be easy to trace.

  1. Decide if it is a charter change. Changes to objectives, success criteria, scope boundaries, budget range, or sponsor go in the charter. Date shifts within milestones go in the plan.
  2. Bump the version. Use v1.1 for clarifications and v2.0 for changes to scope, budget, or success criteria.
  3. Add a change log at the end. Record version, date, what changed, why, and who approved it, one line each.
  4. Keep the old version readable. Do not overwrite approved text without a record. Save a copy or use page history so anyone can see what was originally agreed.
  5. Re-sign for major versions. A v2.0 charter needs fresh sponsor approval, and the team should hear about it in the next status update.

Common project charter mistakes

  • Writing the plan inside the charter. Detailed schedules belong in the plan and in your project tracker.
  • Never revisiting it. Bring the charter to milestone reviews and to the lessons learned session at the end.

How to create a project charter in AFFiNE

AFFiNE combines docs, an edgeless whiteboard, and databases in one workspace, which suits charter work because a charter is part document, part diagram, and part tracker.

  • Doc for the charter itself. Paste the project charter template above into a page, then save it as a template so every new project starts from the same structure.
  • Edgeless canvas for scoping. Switch the same page to edgeless mode to sketch in-scope and out-of-scope items or a stakeholder map during the kickoff, next to the written charter.
  • Database view for risks and milestones. Turn the risk list or milestone table into a database so you can add owner, status, and due date columns and filter them later.
  • AI assistant for first drafts. Ask the built-in AI to turn sponsor interview notes into a draft problem statement, then edit it yourself. Teams can bring their own API key.
  • Self-hosting for internal projects. AFFiNE is open source, and teams can self-host it with Docker Compose, use OIDC single sign-on and S3-compatible storage, and keep working offline thanks to its local-first design.

If you are comparing tools for the rest of the project, see our roundup of project management software.

FAQ

What is a project charter?

A project charter is a short document that formally authorizes a project. It names the sponsor and project manager, states the problem and objectives, defines scope and success criteria, and lists budget, key risks, and approvals. The PMI PMBOK Guide describes it as the document that gives the project manager authority to use organizational resources on the project.

What should a project charter template include?

A complete template includes the project name, sponsor, project manager, background, objectives, success criteria, in-scope and out-of-scope items, deliverables, milestones, budget and resources, stakeholders and roles, risks, assumptions, constraints, and an approval block. Smaller projects can use a one-page version with the problem, objectives, success criteria, scope, sponsor, and milestones.

How long should a project charter be?

Most charters should be one to three pages. A one-page charter is enough for a short internal project run by a single team. Cross-department or multi-quarter projects usually need the full version. If your charter grows beyond a few pages, detailed schedules and plans have probably crept in and should move to the project plan.

What is the difference between a project charter and a project plan?

The charter authorizes the project and sets its boundaries: why it exists, what is in scope, and how success is measured. The project plan explains how the work will be delivered, including the schedule, work breakdown, resources, and communication approach. The charter is written first and changes rarely. The plan is built afterward and updated often.

Who writes and approves the project charter?

The project manager usually drafts the charter, often with input from the sponsor and core team. The sponsor approves it, because the sponsor holds budget authority and is accountable for the project's business outcome. On larger projects, key stakeholders such as security, finance, or department heads also sign before work begins.

When should you create a project charter?

Create the charter during project initiation, after the idea has support but before detailed planning or kickoff. Draft it once you have interviewed the sponsor, then review and sign it in the kickoff meeting. Starting work before the charter is approved usually leads to scope disputes and unclear decision rights later.

Can a project charter change after approval?

Yes, but only through a deliberate change process. If scope, budget, or success criteria change significantly, update the charter, record the version and reason, and get the sponsor to approve it again. Small schedule adjustments belong in the project plan. Treating the charter as stable is what gives it authority.

Is an agile project charter different?

An agile charter usually keeps the vision, objectives, success measures, and team roles but leaves detailed scope open, because the backlog evolves each iteration. It is often shorter and revisited at release planning. The core purpose is the same: authorize the work, name the sponsor, and agree on what success means.

Conclusion

A good charter is short, specific, and signed. Interview the sponsor, write measurable success criteria, name what is out of scope, and give every risk an owner. Then use the charter as your reference point every time priorities shift. Copy the project charter template above, adapt the worked example to your own project, and keep it in one shared place your whole team can find. Start your next project charter in AFFiNE for free.