Project Charter Template
Formalise project boundaries, authorise the project manager, and align stakeholders with this comprehensive charter structure and worked example.
§1 Template Structure (Blank)
A standard project charter establishes the boundaries of the initiative, formally authorises the Project Manager to apply organisational resources, and ensures immediate alignment between the sponsor and the delivery team.
When authoring a new charter, organise your document using the structure below. Ensure every field is completed before seeking formal sign-off from the project sponsor.
1. Core Metadata
- Project Title: The formal name of the initiative.
- Date Prepared: Authoring date.
- Project Sponsor: The executive funding the work.
- Project Manager: The individual authorised to lead.
- Project Customer: Internal or external end-users.
2. Project Overview
- Project Purpose: The business problem being solved.
- High-Level Description: What is being delivered.
- Project Boundaries: Explicit In Scope and Out of Scope items.
- Key Deliverables: Tangible outputs.
- High-Level Requirements: Critical capabilities required for success.
- Overall Project Risk: Initial risk assessment (Low/Med/High).
3. Objectives & Milestones
- Objectives & Success Criteria: Measurable targets across Scope, Time, Cost, and Quality.
- Summary Milestones: Key schedule dates (e.g., Charter Approved, Design Approved, Go-Live, Closeout).
- Financial Resources: Pre-approved budget and funding source.
4. Governance & Authority
- Stakeholders: Key individuals and their project roles.
- Project Exit Criteria: Conditions required to formally close the project.
- Project Manager Authority Level: Explicit tolerances for Staffing, Budget Management, Technical Decisions, and Conflict Resolution.
- Approvals: Signatures from the PM and the Sponsor.
§2 Worked Example: Website Project
The following is a fully populated charter for a mid-sized marketing and IT project: delivering a new corporate website for a consulting firm.
Context: Mary’s Consulting is updating their marketing presence to target Fortune 500 buyers. Andrew (Project Manager) has drafted this charter to secure a $150,000 USD budget from Mary (CEO & Sponsor).
| Core Project Details | |
|---|---|
| Project Title | Mary's Consulting - New Company Website |
| Project Sponsor | Mary (CEO) |
| Project Manager | Andrew |
| Project Customer | Mary's Consulting (internal) and Fortune 500 prospective clients (external) |
| Project Purpose | Replace the existing Mary's Consulting marketing presence with a new, modern company website that reflects the firm's global scale (500+ consultants), positions the brand to Fortune 500 buyers, and generates qualified leads for the project-management consulting practice. |
| High-Level Description | Design, develop, and launch a public-facing website (marysconsulting.com) with an updated brand identity, a service catalogue covering project management consulting, a consultant directory, case studies featuring Fortune 500 engagements, a thought-leadership blog, and a 'Contact / Request for Proposal' lead-capture flow. The site will be responsive, WCAG 2.1 AA accessible, and integrated with the company CRM. |
| Project Boundaries | IN SCOPE: Public marketing site, CMS, contact/RFP form, blog, case study pages, hosting set-up, basic SEO, analytics. OUT OF SCOPE: Internal consultant portal, client project workspaces, billing or time-tracking systems, paid advertising campaigns. |
| Key Deliverables | 1. Approved brand/visual design system 2. Information architecture and wireframes 3. Content (copy, imagery, case studies) 4. Fully developed CMS-driven website 5. Integrated lead-capture / CRM connection 6. Hosting, DNS, and SSL configuration 7. Production launch and post-launch support transition |
| High-Level Requirements | • Responsive across desktop, tablet, and mobile • WCAG 2.1 AA accessibility compliance • Page load < 3 seconds on standard broadband • Editable by non-technical staff via a CMS • Integration with existing CRM for lead routing • Brand-aligned design suitable for Fortune 500 audiences |
| Overall Project Risk | MEDIUM - Primary risk areas include content readiness from consultants, alignment on brand direction with the CEO/sponsor, and CRM integration complexity. Schedule risk is moderate; budget risk is low. |
| Project Objectives | Success Criteria |
|---|---|
| Scope | Deliver a new public website covering marketing, services, case studies, blog, and lead capture. All key deliverables accepted by the sponsor; site passes UAT with no Severity-1 defects. |
| Time | Complete launch within approximately 6 months of charter approval. Production launch on or before the agreed Go-Live milestone date in the schedule baseline. |
| Cost | Deliver within the approved budget of $150,000 USD. Final cost variance within ±10% of approved budget; no unapproved cost overruns. |
| Quality (Other) | Meet brand, performance, and accessibility standards. Site achieves WCAG 2.1 AA, <3s load, and CEO sign-off on brand fit. |
| Summary Milestones | Target Date |
|---|---|
| Project charter approved | May 2026 |
| Requirements & design approved | Jul 2026 |
| Development complete (alpha) | Sep 2026 |
| UAT complete & content loaded | Oct 2026 |
| Production launch (Go-Live) | Nov 2026 |
| Project closeout | Dec 2026 |
Resources & Exit Criteria: For this example, the pre-approved financial resources are strictly capped at $150,000 USD. The project formally exits when the website is live in production, the sponsor formally accepts the deliverables, and hosting is handed over to the support owner.
| Project Manager Authority Level | Tolerances & Escalation |
|---|---|
| Staffing Decisions | PM may select and direct the assigned core team (Bob, Bill, Christine) and engage approved external vendors within budget. |
| Budget Management | PM may approve expenditures up to $5,000 per item and reallocate up to 10% within budget categories. Anything beyond requires sponsor approval. |
| Technical Decisions | PM, in consultation with Bob (Tech Lead), has authority on technology stack, CMS selection, and architectural decisions consistent with IT standards. |
| Conflict Resolution | Issues are first addressed by the PM. Unresolved issues are escalated to the Project Sponsor (Mary) for final decision. |
§3 Quick Reference
Purpose
The charter is a formal contract between the business and the project team. It protects the Project Manager by setting explicit boundaries and tolerances early in the lifecycle.
Common Pitfalls
Avoid drafting technical specifications within the charter. Keep requirements high-level. Always ensure the Out of Scope section is just as detailed as the In Scope section.
Next Steps
Once the sponsor signs the charter, the PM initiates detailed planning, leading to the creation of the formal Project Management Plan and the Work Breakdown Structure (WBS).
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Project Charter Template & Example. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Project Charter Template & Example as a decision instrument rather than an administrative form. The subject terms—charter, template, example, objectives, milestones—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Name the decision. Write the decision, approval, handover or control activity the completed template must support.
- Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
- Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
- Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
- Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Filling every box even when a field is not applicable instead of recording why.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Writing vague statements without an owner, measure, date or evidence source.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Copying a previous project without revalidating assumptions and stakeholders.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Using the document as a private worksheet when it is meant to support a shared decision.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Creating an approved baseline but failing to define who maintains it and when.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Is the purpose and intended decision clear to a reader outside the team?
- Are owners, dates, measures and sources complete and internally consistent?
- Which fields are assumptions and how will they be validated?
- What event, threshold or review date causes this document to change?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Project Charter Template & Example?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about charter would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.