§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).