Templates / Charter vs Project Plan
Project Charter vs Project Plan: The Constitution and the Operating Manual
A project charter and a project plan are the two foundational documents of any project, but they serve fundamentally different purposes and are created at different times by different people. Confusing them, or skipping the charter and jumping straight to planning, is one of the most common and costly mistakes in project management.
Updated 30 March 2026
The Core Distinction: What/Why vs How/When
The project charter answers two questions: what are we doing and why are we doing it? The project plan answers two different questions: how will we do it and when will each part happen? These are not overlapping questions. They require different information, different levels of detail, and different people to answer them. A 2024 PMI survey of 4,069 project professionals found that 39% of projects without formal charters exceeded their original budget by more than 25%. The charter is not bureaucratic overhead. It is the document that prevents scope creep, budget overruns, and stakeholder misalignment before they start.
Project Charter
The project's constitution. Defines boundaries and authority.
- ● Answers: What and Why
- ● Created: Hours (2 to 8 hours)
- ● Length: 1 to 5 pages
- ● Author: PM + Sponsor
- ● Timing: Before team assembly
- ● Changes: Rarely (formal control)
Project Plan
The project's operating manual. Defines execution details.
- ● Answers: How and When
- ● Created: Weeks (2 to 6 weeks)
- ● Length: 20 to 200+ pages
- ● Author: PM + Full team
- ● Timing: After charter approval
- ● Changes: Regularly (weekly updates)
Side-by-Side Comparison: 12 Key Differences
The table below compares every dimension where the charter and plan differ. Use this as a reference when deciding what content belongs in which document. The most common mistake is putting plan-level detail (resource assignments, Gantt charts, detailed risk mitigation) into the charter, which makes it too long and delays approval.
| Dimension | Project Charter | Project Plan |
|---|---|---|
| Purpose | Authorise the project, define boundaries | Guide execution, track progress |
| Core questions | What are we doing? Why? | How will we do it? When? |
| Length | 1 to 5 pages | 20 to 200+ pages |
| Time to create | 2 to 8 hours (plus 3 to 5 days review) | 2 to 6 weeks |
| Created by | PM and Sponsor (2 people) | PM and full project team (5 to 20+ people) |
| When created | Initiation phase (before team exists) | Planning phase (after charter approved) |
| Scope detail | In/out boundary table (10 to 20 items) | Work Breakdown Structure (100+ tasks) |
| Schedule | 4 to 8 high-level milestones | Detailed Gantt chart with dependencies |
| Budget | Total range with contingency % | Line-item breakdown by phase and resource |
| Risks | Top 3 to 5 with P x I scoring | Full register with triggers, responses, owners |
| Change frequency | Rarely (0 to 2 times total) | Regularly (weekly or biweekly updates) |
| Approval | Sponsor signature required | Baseline approved by PM and steering committee |
Why the Charter Must Come Before the Plan (Not Alongside)
Some project managers try to create the charter and plan simultaneously to "save time." This approach fails for three specific reasons, each backed by data:
1. You cannot plan what has not been scoped
The charter defines scope boundaries. The plan breaks that scope into tasks. If the scope changes during charter review (which it does 78% of the time, based on a 2024 survey of 600 PMs), any planning work done in parallel is wasted. The average charter undergoes 2.3 revision cycles. Each revision can shift scope by 15% to 30%. Planning against a moving target costs 40 to 60 hours of rework on a typical 6-month project.
2. The team does not exist yet
The charter is created before the full project team is assembled. The plan requires input from the team: developers estimate development tasks, designers estimate design tasks, testers estimate testing tasks. Creating a plan without the team that will execute it produces estimates that are off by 50% to 200% (based on Standish Group data comparing PM-only estimates vs team-based estimates). The charter authorises the project and justifies assembling the team. The team then creates the plan.
3. Stakeholder alignment requires focused documents
Stakeholders who need to approve the charter (VP-level and above) do not read 50-page project plans. They read 1 to 5 page charters. If you present a combined charter-plan document, executives skip to the summary and miss critical scope decisions. A 2023 study of 1,200 project managers found that charters presented separately had a 89% approval rate within two review cycles, while charter-plan combinations had a 61% rate, because reviewers would flag plan-level concerns that delayed charter approval.
The Charter-to-Plan Handoff: What Transfers and What Does Not
When the charter is approved, specific content flows into the project plan. But the relationship is expansion, not copy-paste. Each charter element becomes a more detailed plan element:
| Charter Element | Becomes in Plan | Expansion Factor |
|---|---|---|
| Problem statement (2 to 3 sentences) | Project background section (1 to 2 pages) | 5x to 10x more detail |
| Success criteria (3 to 5 items) | Quality management plan with measurement protocols | Each criterion gets its own measurement section |
| Scope in/out table (10 to 20 items) | Work Breakdown Structure (100 to 500+ tasks) | Each in-scope item becomes 10 to 50 tasks |
| Milestones (4 to 8 dates) | Gantt chart with task dependencies | Each milestone becomes 20 to 50 predecessor tasks |
| Budget range ($100K to $150K) | Cost breakdown structure by phase, resource, and month | Range becomes line-item precision |
| Top 3 to 5 risks with P x I scores | Full risk register (15 to 30 risks) with response plans | Each risk gets triggers, owners, and budgeted responses |
| Decision authority (3 roles) | Full RACI matrix (all team members, all deliverables) | 3 roles become 10 to 30 named individuals |
The charter is roughly 2% to 5% of the total project documentation by volume. But it contains 100% of the strategic decisions. If the charter is wrong, the plan cannot be right.
When You Need Both vs Charter Only
Not every project needs a full project plan. Some only need a charter. The deciding factors are budget, duration, team size, and organisational requirements:
| Factor | Charter Only | Charter + Plan |
|---|---|---|
| Budget | Under $50K | Over $50K |
| Duration | Under 8 weeks | Over 8 weeks |
| Team size | 1 to 5 people | 5+ people |
| Departments | Single department | Cross-departmental |
| Methodology | Agile/Scrum (backlog replaces plan) | Waterfall, hybrid, or SAFe |
| Compliance | No regulatory requirements | SOX, HIPAA, PCI, or PMO governance |
The grey zone is projects in the $30K to $80K range with 4 to 8 team members and 8 to 12 week timelines. For these projects, a lean charter (1 page) plus a lightweight plan (5 to 10 pages covering WBS, schedule, and risk register) is usually sufficient. The full 12-section charter and 50+ page plan are reserved for enterprise projects over $100K with cross-department impact.
5 Common Mistakes When Creating Charters and Plans
1.Putting task-level detail in the charter
"Design wireframes for homepage, about page, and contact page" is plan-level detail. The charter should say "Homepage and 12 landing page redesigns (in scope)" and leave the page-by-page breakdown to the plan. Charters with task-level detail average 8 to 12 pages and have 34% lower approval rates in the first review cycle.
2.Skipping the charter for "small" projects
Even a $10K project benefits from a half-page charter documenting the problem, 3 success criteria, and scope boundaries. Projects without any charter have a 25% higher rate of scope disputes (PMI, 2024). The lean charter takes 1 to 2 hours. The average scope dispute costs 8 to 16 hours to resolve. The maths is straightforward.
3.Creating the plan before the charter is approved
This wastes an average of 40 to 60 hours on a typical 6-month project. The charter defines what the plan will cover. If the charter scope changes during review (which happens 78% of the time), any planning done in parallel becomes rework. Wait for the signed charter.
4.Using the charter as a project status document
The charter is a baseline document that should rarely change. Project status goes in status reports and the project plan. If you update the charter every week, you are using it as a plan. PMI data shows that projects modifying their charter more than twice have a 60% higher failure rate, because frequent charter changes signal unclear objectives.
5.Writing success criteria that are actually deliverables
"Deliver the new website" is a deliverable, not a success criterion. "Increase conversion rate from 1.2% to 3.5% within 90 days of launch" is a success criterion. The charter defines what success looks like for the business. The plan tracks what gets delivered to achieve that success. Mixing them up causes teams to focus on outputs (did we build it?) instead of outcomes (did it work?).
From Charter to Execution
Once your charter is approved and your plan is underway, you will need execution templates. An action plan template converts plan tasks into assigned, tracked actions. A meeting agenda template keeps your steering committee meetings focused and productive. Together, these three documents form the project management documentation stack: charter (initiation), plan (planning), and action items (execution).