Certifications PMP CertificationWorld’s top PM cert CSM — Certified ScrumMasterTop agile cert CAPMEntry-level PM cert PRINCE2UK & Europe standard View All Certifications ?
PM Guides Agile GuideComplete breakdown Scrum GuideRoles, ceremonies, artifacts EVM GuideAll formulas explained View All Guides ?
Career & Salary PM Salary 2026By country & level How to Become a PMStep-by-step roadmap 50 Interview QuestionsWith strong answers
PM Software Monday.com ReviewTop pick 2026 ClickUp ReviewBest value Best Free PM ToolsNo trials, truly free View All Software ?
Free Tools & Templates EVM CalculatorFree, no signup Gantt Chart MakerBuild & export free PMP Eligibility Checker30-second result Free PM Templates30 templates — Excel, Word, PDF
Get the Free PMP Guide ?
Free Template · Updated March 2026

Free Project Charter Template
Word & PDF Download

A professional, sponsor-ready project charter with all 11 sections pre-structured. Covers scope, SMART objectives, stakeholder register, high-level timeline, budget summary, top risks and a formal approval sign-off block. Download in Word format and edit in minutes.

By Syed Mujeeb Rehman, PMP
📅Updated March 2026
📄11 sections · 4 pages
🔓Free — no signup
What's Inside

This template includes every section required by PMI/PMBOK standards: project overview, purpose & background, SMART objectives & success criteria, in/out of scope, stakeholder register, milestone timeline, budget summary with reserves, risk register, resource plan, change control note and formal approval signatures.

Download Free Template

Word (.docx) — edits in Word, Google Docs & LibreOffice

.DOCX FREE
  • 11 fully structured sections
  • SMART objectives table
  • Stakeholder register grid
  • Milestone timeline table
  • Budget summary with reserves
  • Risk register (5 rows)
  • Three sign-off blocks
  • Document version history
  • Header, footer & page numbers
⬇ Download Free (.docx) Open in Google Docs →
11
Sections in the template
4+
Pages when completed
100%
PMBOK / PMI aligned
Free
No account or payment required
01 — Template Contents

All 11 Sections — What's Included

Every section is pre-structured with clear guidance text showing exactly what to write. Replace the placeholder text with your project details — the template handles all formatting, tables and layout.

1
Project Overview
Project name, code, sponsor, PM, department, priority, start/end dates and total budget — all in a clean reference table for quick scanning by executives.
2
Purpose & Background
Business need and problem statement, plus strategic alignment to company OKRs, programmes or regulatory requirements. Answers: why does this project exist?
3
Objectives & Success Criteria
5-item SMART objectives list plus a success criteria table with measurement method and target for each criterion. Directly linked to how benefits will be measured post-delivery.
4
Scope (In, Out, Assumptions, Constraints)
Four distinct sub-sections: what's in scope, what's explicitly out of scope, key assumptions and project constraints. The out-of-scope section is the single most important scope creep prevention tool in the charter.
5
Key Stakeholders
Stakeholder register table with name, role/title, responsibility description and engagement level (Lead / Consult / Inform / Approve). Pre-populated with sponsor and PM rows.
6
High-Level Timeline & Milestones
Phase-by-phase milestone table from kick-off through post-implementation review. Includes target date and owner columns. Pre-populated with 10 standard project phases as a starting framework.
7
Budget Summary
Cost breakdown by category (labour, external, software, materials, travel, other) plus contingency reserve, management reserve and total authorised budget row highlighted in violet. Consistent with PMI EVM terminology.
8
Top Risks & Dependencies
5-row risk register table with description, probability, impact and response plan. Plus a separate dependencies section for things the project needs from outside its control.
9
Project Team & Resource Plan
Team table with name, role, department/organisation and percentage allocation. Pre-populated with sponsor and PM rows. Add up to 8 additional team members.
10
Change Control
A formal paragraph establishing the change control process — all scope/budget/timeline changes require a Change Request Form and sponsor approval. Protects the PM and sets expectations from day one.
11
Approval & Authorisation
Three formal signature blocks — Project Sponsor, Project Manager and Steering Committee Chair — each with name, role, signature line and date. The signed charter is the PM's authority to act.
02 — How to Use This Template

Filling In Your Charter — Step by Step

Before You Open the Template

Gather these inputs before you start writing: the project sponsor's name and sign-off, a draft scope statement (even just 3–4 bullet points), an indicative budget or budget range, the target go-live date and 3–5 high-level objectives. You don't need perfect answers — the charter is a living document that gets refined during early planning. What matters is that you get sponsor sign-off on the best available information so the project is formally authorised.

Section 4 — Scope Is the Most Important Section

Most project managers spend 80% of their time on Section 3 (objectives) and 20% on Section 4 (scope). It should be the opposite. The out-of-scope list is the single most powerful scope creep prevention tool you have. If it isn't explicitly listed as out of scope, people will assume it's in scope. Be ruthlessly specific — name the systems, geographies, user groups and features that are not included in this project.

💡
Getting sponsor sign-off: Schedule a 30-minute meeting with the sponsor to walk through the charter before sending it for signature — don't just email it. Walk through sections 3 (objectives), 4 (scope) and 7 (budget) together. Any disagreement discovered in that meeting is infinitely cheaper to resolve than a disagreement discovered at month 6 of delivery. Once signed, the charter becomes your authority to act.

Opening in Google Docs

The template downloads as a .docx file which opens natively in Microsoft Word. To use it in Google Docs: open drive.google.com, drag and drop the file to upload, then double-click it and select "Open with Google Docs." All formatting, tables and text will carry across. For PDF export from Google Docs: File → Download → PDF Document.

03 — Background

What Is a Project Charter?

A project charter is the foundational document that formally authorises a project to begin. In PMBOK terms it is produced during the Initiating process group and serves as the project manager's formal authority to use organisational resources. Without a signed charter, a PM is managing a project they have not been given permission to manage.

The charter answers four questions that every project sponsor and steering committee needs answered before committing budget: Why are we doing this? (purpose and business case), What exactly are we doing? (scope and objectives), How much will it cost and how long will it take? (budget and timeline), and Who is responsible? (PM, sponsor, team).

A charter is not a detailed project plan — it should be concise enough that busy executives will actually read and sign it. The detailed planning (WBS, detailed schedule, full risk register, communication plan) comes after the charter is approved, in the Planning process group.

⚠️
Common charter mistakes: (1) Writing it after the project has already started — the charter should be the first document, not a retrospective paperwork exercise; (2) Making the scope section vague to avoid conflict — specificity prevents future disputes; (3) Not getting it signed — an unsigned charter has no authority; (4) Never revisiting it — if scope, budget or objectives change significantly, the charter should be updated and re-approved.
04 — FAQ

Project Charter — 5 Common Questions

A project charter is a formal document that authorises a project to begin. It names the project manager, defines scope, objectives and budget, lists key stakeholders and requires sponsor sign-off. The signed charter is the project manager's authority to spend budget and assign resources. In PMBOK it is produced during the Initiating process group.
A complete project charter should include: project name and code, project purpose and business justification, SMART objectives and success criteria, scope (in scope, out of scope, assumptions and constraints), key stakeholders and roles, high-level timeline and milestones, budget summary with contingency and management reserves, top risks and dependencies, resource plan, change control protocol and formal approval signatures. This template includes all of these across 11 sections.
Typically 2–5 pages for small to medium projects, 5–10 for large programmes. It should be comprehensive enough to clearly authorise the project and set expectations, but concise enough that sponsors will actually read and sign it. Excessive detail belongs in the project management plan, not the charter. This template produces approximately 4–6 pages when fully completed.
The project charter must be signed by the project sponsor — the senior person accountable for the project's business outcome and funding it. The project manager also signs, accepting delivery accountability. On larger projects the steering committee chair or programme director may also sign. Without sponsor sign-off the PM has no formal authority to spend budget or assign resources.
A project charter is a short authorisation document — it answers "should we do this project and who is accountable?" A project brief (or PID in PRINCE2, or project management plan in PMBOK) is the more detailed document produced after the charter is approved, answering "how exactly will we deliver it?" Some organisations use the terms interchangeably. In PMI methodology the charter is the founding document that precedes all detailed planning.