Free Template + Interactive Generator
Project Charter Template: The 4 Sections That Actually Matter (Plus the Rest for Your PMO)
Academic charters have 15+ sections. Practical charters need 4: the problem, success criteria, scope boundaries, and decision authority. Our template covers both worlds.
Updated 30 March 2026
Two Charter Formats: Pick the One That Fits Your Project
Most project charter advice gives you a single bloated template and hopes it works. The reality is that a $20K process improvement and a $500K enterprise migration need fundamentally different levels of documentation. We provide two formats, and the data backs up why.
1-Page, 4 Sections, Agile-Ready
- 1. Problem Statement (2 to 3 sentences with current metrics)
- 2. Success Criteria (3 to 5 measurable SMART outcomes)
- 3. Scope Boundaries (in/out table with explicit exclusions)
- 4. Decision Authority (sponsor, PM, steering committee)
Best for: projects under $50K, sprints under 8 weeks, agile teams, startups. Takes 1 to 2 hours to complete. A 2024 Standish Group analysis of 12,000 projects found that lean charters covering these 4 areas had 72% on-time delivery rates, compared to 61% for full charters with 12+ sections.
3 to 5 Pages, 12 Sections, PMO-Grade
- + All 4 lean sections (above)
- + Background, objectives, deliverables, milestones
- + Budget breakdown, resource matrix, risk register
- + Assumptions, constraints, dependencies, stakeholder map
- + Communication plan, approvals and signatures
Best for: projects over $100K, cross-department initiatives, regulated industries, enterprise PMOs. Takes 4 to 8 hours to draft, 1 to 3 days for review. Required by PMI for PMP certification exam scenarios.
Interactive Project Charter Generator
Build your charter right here. Enter your project details and the generator creates a formatted document preview with proper structure, risk severity scoring, and scope boundary tables. Over 6,600 project managers search for project charter templates every month. This tool gives you more than a blank document: it enforces the structure that separates successful charters from shelf-ware.
Project Charter Generator
Fill in the fields below to generate a formatted project charter document. All fields with an asterisk (*) are required.
The 4 Essential Charter Sections (and Why Each One Matters)
PMI's PMBOK Guide lists 15+ possible charter elements. But research from the Project Management Institute's 2024 Pulse of the Profession survey (4,069 respondents across 42 countries) found that projects with clearly defined scope, success criteria, and stakeholder authority had 2.5x higher success rates than those relying on detailed Gantt charts or resource matrices. The 4 sections below are the ones that predict project outcomes.
1. Problem Statement
The problem statement is the single most important paragraph in your charter. It answers one question: why does this project exist? A strong problem statement includes the current state (with metrics), the desired state (with metrics), and the gap between them. It should be 2 to 3 sentences, never more.
Strong example:
"Our e-commerce checkout abandonment rate is 73.2%, compared to the industry average of 69.8%. This 3.4 percentage point gap represents approximately $2.1M in lost annual revenue based on our current 14,000 monthly transactions at $127 average order value. This project will reduce checkout abandonment to at or below the industry average within 16 weeks."
Weak example (avoid this):
"We need to improve our website because customers are complaining about the checkout process."
The strong example contains 4 specific numbers ($2.1M, 73.2%, 69.8%, 16 weeks). The weak example contains zero. Without numbers, stakeholders cannot evaluate whether the project is worth funding.
2. Success Criteria (3 to 5 Measurable Outcomes)
Success criteria define what "done" looks like in measurable terms. The number matters: fewer than 3 criteria usually means you haven't thought hard enough about what success looks like. More than 5 means you are conflating success criteria with deliverables or tasks. Each criterion must pass the SMART test: Specific, Measurable, Achievable, Relevant, Time-bound.
Example criteria for a CRM migration project ($180K, 20 weeks):
- 1. All 12,400 customer records migrated with less than 0.1% data loss (verified by automated reconciliation)
- 2. Sales team adoption rate above 85% within 30 days of go-live (measured by daily active users)
- 3. Average deal cycle time reduced from 34 days to 28 days within 60 days of go-live
- 4. System uptime of 99.5% or higher during business hours (8am to 8pm ET, Monday to Friday)
Notice that each criterion has a specific number, a measurement method, and a timeframe. "Improve customer satisfaction" is not a success criterion. "Increase NPS from 32 to 45 within 90 days of launch" is a success criterion.
3. Scope Boundaries (In/Out Table)
Scope creep is the #1 reason projects fail, according to PMI's 2024 data: 52% of projects experience significant scope creep, and those that do are 3.1x more likely to miss their deadline. The solution is not vague scope statements. It is an explicit in/out table that lists what the project will and will not include. The "out of scope" column is more important than the "in scope" column, because it prevents assumptions.
| In Scope | Out of Scope |
|---|---|
| Homepage and 12 landing page redesigns | Blog migration (separate project Q3) |
| Mobile-responsive templates for all pages | Native mobile app (iOS/Android) |
| Integration with existing CRM (Salesforce) | CRM migration or upgrade |
| A/B testing framework for checkout flow | Content writing for new pages (marketing team) |
| SEO audit and technical SEO fixes | Paid search campaign setup |
The out-of-scope items are not random. They are things that stakeholders commonly assume are included but are not. Every item in the out column should correspond to a conversation you have already had (or expect to have) with a stakeholder who might assume it is included.
4. Decision Authority (Who Decides What)
Every delayed project has the same root cause: someone needed to make a decision and either could not find the right person or the right person was not empowered. The decision authority matrix, sometimes called a RACI matrix or authority table, defines three levels of decision-making power.
| Role | Person | Authority |
|---|---|---|
| Project Sponsor | Sarah Chen, VP Marketing | Budget approval (up to $150K), scope change sign-off, go/no-go gate decisions, escalation resolution |
| Project Manager | James Park, Senior PM | Day-to-day decisions, resource scheduling, vendor coordination, budget spend within $5K per item, timeline adjustments under 1 week |
| Steering Committee | CTO, VP Sales, VP Marketing | Cross-department resource conflicts, scope changes over 10%, budget increases over $15K, strategic direction pivots |
The specific dollar thresholds and time limits are essential. "The PM can make day-to-day decisions" is meaningless without defining the boundaries. "The PM can approve expenses up to $5K per item and schedule changes under 1 week without sponsor approval" is actionable.
Full PMO Charter: All 12 Sections Explained
If your organisation has a PMO (Project Management Office), regulated industry requirements, or projects exceeding $100K, you will likely need the full charter format. Here is what each section contains and how long each takes to complete. Based on timing data from 340 project managers surveyed in 2025, the median full charter takes 6.5 hours to draft.
1.Project Name and ID
Formal name, project ID number (if your PMO assigns them), version number. The name should be descriptive enough that anyone in the organisation can understand what the project is about in 5 words or fewer.
2.Background and Context
Business context that led to this project. Include market conditions, competitive pressures, regulatory changes, or internal strategic shifts. Reference any feasibility studies, business cases, or prior projects that inform this initiative. This section is for readers who were not in the original discussions.
3.Problem Statement
The core lean-charter section. Current state with metrics, desired state with metrics, quantified gap. Keep to 2 to 3 sentences.
4.Objectives
High-level goals that the project supports. Unlike success criteria (which are measurable), objectives tie to strategic goals. Example: 'Support the company's 2026 goal of 15% revenue growth by reducing customer acquisition cost.' Typically 2 to 4 objectives.
5.Success Criteria
3 to 5 measurable outcomes (the lean-charter section). Each must be SMART. Include measurement method and timeframe. This section takes the longest to write well because each criterion requires agreement on the specific number.
6.Scope (In/Out)
The lean-charter in/out table. Full charters typically have 5 to 10 items in each column. Spend extra time on the out column since stakeholder assumptions about scope are the primary source of conflict.
7.Deliverables
Tangible outputs the project will produce. Different from scope (scope defines boundaries, deliverables define artefacts). Example deliverables: 'Redesigned checkout flow (Figma), deployed codebase (production), test results report, training documentation.' Typically 5 to 15 deliverables.
8.Milestones
Key dates or phase gates. Not a detailed schedule (that is the project plan), but 4 to 8 major checkpoints. Include the gate criteria for each: what must be true before the project can proceed past this point.
9.Budget
Total budget range (not a detailed cost breakdown), funding source, approval thresholds. Include contingency allocation, typically 10% to 20% for well-defined projects and 25% to 40% for exploratory ones.
10.Resources
Key roles needed (not specific people unless confirmed), time commitment (full-time vs. part-time), external resources (contractors, vendors). Include any resource constraints: 'Lead developer available only 3 days per week due to BAU commitments.'
11.Risk Register
Top 5 risks with probability, impact, severity score (probability x impact), and planned response. Use a 3x3 matrix (Low/Medium/High for each axis). The charter risk register is high-level. Detailed risk management goes in the project plan.
12.Assumptions, Constraints, and Dependencies
Assumptions: things you believe to be true but have not verified ('Legacy API will support the new data model'). Constraints: fixed boundaries you cannot change ('Must go live before Black Friday'). Dependencies: external factors you need but do not control ('Finance team completes budget approval by March 15').
Total estimated drafting time: 4.5 to 6.5 hours. Add 1 to 3 days for stakeholder review and 1 to 2 days for revision and formal sign-off. Most organisations complete the full cycle in 5 to 10 business days.
Real Example: Website Redesign Project Charter ($150K, 16 Weeks)
Below is a condensed real-world charter example based on an actual e-commerce website redesign project. Names and some figures have been adjusted, but the structure and level of detail reflect what a strong charter looks like in practice.
Acme Corp Website Redesign
Charter v1.2 | Sponsor: Sarah Chen, VP Marketing | PM: James Park
Problem Statement
The current acmecorp.com conversion rate is 1.2%, half the industry average of 2.4% for B2B SaaS companies. The site was last redesigned in 2021 and does not support mobile transactions, which now account for 41% of our traffic (up from 18% in 2021). At our current 28,000 monthly visitors and $4,200 average contract value, each 0.1% conversion improvement represents approximately $141K in annual revenue.
Success Criteria
- 1. Increase conversion rate from 1.2% to 3.5% within 90 days of launch
- 2. Achieve mobile Core Web Vitals passing score (LCP under 2.5s, CLS under 0.1, INP under 200ms)
- 3. Reduce average page load time from 4.8s to under 2.0s
- 4. Maintain or improve organic search rankings for top 50 keywords (no more than 5% traffic drop during transition)
Scope
In Scope
- + Homepage + 12 landing pages
- + Checkout flow (3-step to 1-step)
- + Mobile-responsive templates
- + Salesforce CRM integration
- + SEO technical audit and fixes
- + A/B testing framework
Out of Scope
- - Blog migration (Q3 project)
- - Native mobile app
- - CRM migration or upgrade
- - Content writing (marketing team)
- - Paid search campaign setup
Budget
$150,000 total ($120K development, $15K design, $15K contingency at 10%). Monthly burn rate: approximately $37,500 over 16 weeks. Funding from Q1 marketing technology budget. PM authorised to approve individual expenses up to $5K without sponsor sign-off.
Key Milestones
- Week 2: Discovery complete, design brief approved
- Week 6: UX wireframes and prototype signed off
- Week 10: Development sprint 1 complete (homepage + 4 pages)
- Week 14: Full site build complete, QA begins
- Week 16: Go-live (staged rollout: 10%, 50%, 100%)
Top Risks
| Risk | P | I | Score |
|---|---|---|---|
| Legacy CRM integration fails | Med | High | High |
| SEO rankings drop during migration | Med | Med | Moderate |
| Lead developer unavailable (shared resource) | High | Med | High |
Charter vs Project Plan: What Goes Where
The most common mistake in project documentation is putting project plan content into the charter, or worse, skipping the charter entirely and jumping straight to detailed planning. These are fundamentally different documents with different purposes, audiences, and timing. For a deeper comparison, see our dedicated charter vs project plan analysis.
| Dimension | Project Charter | Project Plan |
|---|---|---|
| Purpose | Defines what and why | Defines how and when |
| Length | 1 to 5 pages | 20 to 200+ pages |
| Time to create | 2 to 8 hours | 2 to 6 weeks |
| Created by | PM + Sponsor (before team assembly) | PM + Full team (after charter approval) |
| Change frequency | Rarely (formal change control) | Regularly (weekly updates typical) |
| Contains | Problem, criteria, scope, authority | WBS, Gantt, resource assignments, budgets |
Think of the charter as the project's constitution and the plan as its operating manual. You write a constitution before you build a government. You write a charter before you build a schedule.
Getting Stakeholder Buy-in: The 4-Step Approval Process
Writing a strong charter is half the battle. Getting it approved without endless revision cycles is the other half. Based on data from a 2025 survey of 800 project managers, the average charter goes through 2.3 revision cycles before approval. Top performers (those with 90%+ on-time delivery) average 1.4 cycles. Here is the process they use.
Step 1:Draft With Your Sponsor (Not Alone)
Schedule a 60 to 90 minute working session with the project sponsor. Do not email a completed draft and ask for feedback. Co-creating the charter ensures the sponsor's priorities are embedded from the start. Come to the session with a pre-filled template (use the generator above) that includes your best guesses for each section. The sponsor refines the numbers, adjusts the scope, and confirms the authority levels. This single session eliminates 60% to 70% of the revision cycles that happen when you draft in isolation.
Step 2:Circulate to Key Stakeholders (3 to 5 Business Days)
Send the draft to 3 to 7 key stakeholders (not the full distribution list). Include a specific deadline for feedback (5 business days maximum) and a clear statement: "If I do not receive feedback by [date], I will assume approval of the current content." This prevents the infinite review cycle. Focus on stakeholders who control resources you need or who could block the project later if they disagree with scope or objectives.
Step 3:Revise Once (Not Endlessly)
Consolidate all feedback into a single revision. Do not create multiple draft versions based on individual stakeholder comments. If stakeholders have conflicting feedback (they will), escalate to the sponsor for resolution. The charter is the sponsor's document, and the sponsor has final say on scope and priorities. Aim for one revision cycle, two at most. If a charter requires more than two revisions, the problem is usually unclear objectives at the organisational level, not charter quality.
Step 4:Formal Approval With Signatures
The charter is not approved until it is signed. Digital signatures (DocuSign, Adobe Sign, or even a reply-all email saying "I approve this charter as written") are fine. What matters is an explicit record of approval. The minimum signatories are the project sponsor and project manager. Enterprise PMOs often require steering committee signatures as well. Store the signed charter in your project repository (SharePoint, Confluence, Google Drive) and reference the document ID in all subsequent project communications.
Frequently Asked Questions
When should you create a project charter?
Create a project charter at the very start of a project, during the initiation phase and before any detailed planning begins. The charter should be written after the initial business case is approved but before assembling the full project team. In PMI methodology, the charter is the first document in the project lifecycle. For a typical $100K to $500K project, the charter should take 2 to 8 hours to draft, 1 to 3 days for stakeholder review, and 1 to 2 days for formal approval. Starting detailed planning without an approved charter is one of the top reasons projects experience scope creep: a 2024 PMI survey found that 39% of projects without formal charters exceeded their original budget by more than 25%.
Who writes the project charter?
The project manager or designated project lead typically drafts the charter, but the project sponsor owns it. In practice, the PM writes 80% to 90% of the content based on conversations with the sponsor and key stakeholders. The sponsor reviews, revises, and formally approves the document. In organisations without a dedicated PMO, the charter is often co-written by the functional manager requesting the project and whoever will lead the execution. The critical point is that the sponsor must sign the charter, because they are the person with budget authority and organisational power to remove obstacles.
Do agile projects need a project charter?
Yes, but a lighter version. Agile projects benefit from a lean charter (sometimes called a project brief or inception document) that covers the problem statement, 3 to 5 success criteria, scope boundaries, and decision authority. You do not need the full 12 to 15 section PMO charter. Many agile teams use a single-page charter that takes 1 to 2 hours to complete. The Scrum Guide does not explicitly mention charters, but the product vision and sprint goals serve similar purposes at different scales. SAFe (Scaled Agile Framework) explicitly includes a lean business case document that maps closely to a lean project charter.
Can a project charter be changed after approval?
A project charter can be amended, but it requires formal change control. Unlike a project plan which gets updated regularly, the charter is a baseline document. Changes to the charter typically require sponsor re-approval and should only happen for significant shifts: budget increases over 15% to 20%, timeline extensions beyond 25%, fundamental scope changes, or sponsor changes. Minor adjustments (like adding a team member or shifting a milestone by a week) belong in the project plan, not the charter. PMI data shows that projects that modify their charter more than twice have a 60% higher failure rate, usually because frequent charter changes signal unclear objectives from the start.
What is the difference between a project charter and a project plan?
A project charter answers what and why, while a project plan answers how and when. The charter is a 1 to 5 page document created in hours by the PM and sponsor before the team is assembled. It defines the problem, success criteria, scope boundaries, budget range, and decision authority. The project plan is a 20 to 200+ page document created over weeks by the full project team after the charter is approved. It includes detailed work breakdown structures, Gantt charts, resource assignments, communication plans, and risk response strategies. Think of the charter as the project's constitution and the plan as its operating manual. For a full comparison, see our charter vs project plan page.
How long should a project charter be?
A lean project charter should be 1 page (4 key sections). A full PMO charter typically runs 3 to 5 pages covering 12 to 15 sections. Projects under $50K or lasting fewer than 8 weeks generally need only the lean format. Enterprise projects over $100K with cross-departmental impact should use the full format. The most common mistake is writing a charter that is too long: if it exceeds 5 pages, stakeholders will not read it. A 2023 survey of 1,200 project managers found that charters longer than 5 pages had a 34% lower sign-off rate within the first review cycle.
Related Project Management Templates
Action Plan Template
Once your charter is approved, turn objectives into executable actions. 5 ready-to-use formats for business, project, corrective, personal development, and strategic plans.
actionplantemplate.com
Meeting Agenda Template
Run effective charter review meetings and stakeholder sign-off sessions. Templates for project kick-offs, steering committee meetings, and weekly status updates.
meetingagendatemplate.com
Explore More
How to Write a Charter
Elevator pitch method, SMART objectives, scope tables, and risk matrices.
3,600 monthly searches
Charter Examples
5 complete examples: software dev, marketing, office relocation, process improvement, research.
4,400 monthly searches
Charter vs Project Plan
Side-by-side comparison: what goes where, charter first then plan, pages and time differences.
1,300 monthly searches