Template Overview
A project charter formally authorizes a project to begin. It defines the project purpose, gives the project manager authority to use resources, and gets sign-off from the project sponsor. Every project — large or small — benefits from a charter.
Project Identification
Basic project information for formal authorization
- Project Name: _________________________________
- Project ID / Code: _________________________________
- Prepared by: _____________ Date: _____________
- Version: _____________
- Department / Business Unit: _________________________________
Project Purpose & Justification
Why this project exists and what business need it addresses
- Business Need / Problem Statement: _________________________________
- Strategic Alignment: _________________________________
- Expected Business Value: _________________________________
- Consequences of NOT doing this project: _________________________________
Project Objectives
Specific, measurable outcomes the project must deliver
- Primary Objective: _________________________________
- Objective 2: _________________________________
- Objective 3: _________________________________
- Success Criteria (measurable): _________________________________
Scope Summary
High-level scope boundaries
- In Scope: _________________________________
- Out of Scope: _________________________________
- Key Deliverables: _________________________________
- Major Milestones: _________________________________
- Target Completion Date: _________________________________
Stakeholders & Team
Identify all key parties and their roles
- Project Sponsor (authority to approve): _________________________________
- Project Manager: _________________________________
- Core Team Members: _________________________________
- Key Stakeholders: _________________________________
- External Parties / Vendors: _________________________________
Budget & Resources
High-level resource and budget authorization
- Estimated Budget: $_____________
- Budget Approved by: _________________________________
- Staff Resources Required: _________________________________
- Technology / Equipment: _________________________________
- External Services / Vendors: _________________________________
Constraints, Assumptions & Risks
Document known constraints and assumptions at project start
- Key Constraints: _________________________________
- Key Assumptions: _________________________________
- Top 3 Risks: _________________________________
Authorization & Sign-off
Formal approval authorizing the project to proceed
- Project Sponsor Name: _________________________________
- Signature: _________________________ Date: _____________
- Project Manager Name: _________________________________
- Signature: _________________________ Date: _____________
- Additional Approver: _________________________ Date: _____________
Project Charter Tips
Keep It to One Page
A project charter should be brief. If it is over two pages, you are writing a project plan. The charter's job is authorization, not detail.
Get Sponsor Signature Before Work Starts
The charter has no value without a sponsor signature. It is the document that gives the PM authority to allocate resources.
Define Out of Scope
Half of scope creep can be prevented by writing "Out of Scope" explicitly in the charter. Stakeholders will say "but I thought..."—the charter is the answer.
Use Numbers, Not Words
Success criteria should be measurable: "reduce processing time by 30%" not "improve efficiency". Vague objectives create vague outcomes.