
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
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:
People often merge these two documents, and the result is a 30-page charter nobody reads. Keep them separate.
| Project charter | Project plan | |
|---|---|---|
| Purpose | Authorize the project and set boundaries | Explain how the work will be delivered |
| When written | Before kickoff, during initiation | After the charter is approved |
| Owner | Sponsor approves, PM drafts | Project manager and team |
| Contents | Goal, scope, success criteria, budget range, key risks, roles | Work breakdown, schedule, resource plan, communication plan, risk register |
| How often it changes | Rarely, only through formal change control | Regularly, as the team learns |
You may be handed any of five related documents. This matrix shows which one you need.
| Document | Main question | Who signs | Use it when |
|---|---|---|---|
| Business case | Is this worth the money? | Investment or budget owner | Funding must be justified before anyone commits |
| Project charter | Is the project approved, and within what limits? | Sponsor | Almost every project, PMI-style or not |
| Project brief (PRINCE2) | Is it worth initiating? | Project board | Your organization runs PRINCE2 |
| PID (PRINCE2) | How will the project be controlled? | Project board | PRINCE2 projects after initiation |
| Statement of work (SOW) | What will a supplier deliver, for how much? | Client and vendor | Outside 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.
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.
| Section | Question it answers | Practitioner tip |
|---|---|---|
| Background and problem | Why now? | Describe the current pain in one paragraph, with evidence you already have. |
| Objectives | What will change? | Limit yourself to three objectives. More usually means two projects. |
| Success criteria | How 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. |
| Deliverables | What will we hand over? | Name tangible outputs, not activities. |
| Budget and resources | What can we spend? | Give a range and name who approves overruns. |
| Stakeholders and roles | Who decides, who does, who is informed? | Link to a RACI rather than writing paragraphs. |
| Risks, assumptions, constraints | What could go wrong, and what are we taking for granted? | List the top five risks only, each with an owner. |
| Approval | Who signed off? | Collect names and dates. A charter without signatures is a draft. |
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.
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.
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.
| Factor | One-page charter | Full charter |
|---|---|---|
| Best for | Internal projects under a few months, one team | Cross-department, multi-quarter, or budget-heavy projects |
| Sections | Problem, objectives, success criteria, scope, sponsor, milestones | All ten sections in the template above |
| Approval | Sponsor sign-off, often in a meeting | Sponsor plus key stakeholders, recorded |
| Budget | "Within team budget" or a single figure | Range, 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.
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.
| # | Test | Pass if |
|---|---|---|
| 1 | Sponsor | One named person with budget authority, not a committee |
| 2 | Problem | A new reader understands why now in under a minute |
| 3 | Objectives | Three or fewer, each starting with a verb |
| 4 | Success criteria | Every criterion has a number or yes/no test and a date |
| 5 | Out of scope | Lists at least one item a stakeholder has already asked for |
| 6 | Deliverables | Outputs, not activities, each with an owner |
| 7 | Budget | A range plus the name of who approves overruns |
| 8 | Risks | Five or fewer, each with an owner and a mitigation |
| 9 | Length | Fits in three pages without attachments |
| 10 | Approval | Signature lines name real people, with a version number |
Stop and resolve these before kickoff, not after:
A charter changes rarely, so each change should be easy to trace.
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.
If you are comparing tools for the rest of the project, see our roundup of project management software.
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.
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.
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.
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.
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.
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.
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.
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.
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.