Project Charter in the Google PM Certificate: What It Is and How to Write One
The project charter is the foundation of traditional project management (Courses 1-3 of the Google PM Certificate). It's the document that officially authorizes a project and clarifies its boundaries. A strong charter prevents endless scope creep, clarifies stakeholder expectations, and gives the PM authority to execute. This article explains what goes into a charter and how to write one that's actually useful.
What is a Project Charter?
A project charter is a document that formally authorizes a project. It says: "This project exists, here's why, here's what we're building, here are the boundaries, and these are success criteria." It's typically 1-2 pages—concise but complete.
The charter is created during project initiation (Course 2 of the Google certificate) and signed by the sponsor (executive who approved the project). It's your permission slip to execute.
Key difference: Charter vs. Plan
- Charter: What are we doing and why? (High-level, stable)
- Plan: How are we doing it? (Detailed, can evolve)
The charter is stable; you don't replan it each week. The plan evolves as you learn.
What Goes Into a Project Charter
1. Project Title and Description**
"Website Redesign for Nonprofit XYZ" - Simple, clear.
2. Business Case / Problem Statement**
"Current website is 10 years old. User satisfaction surveys show 40% of users struggle to navigate. Donor abandonment at checkout is 30% higher than industry benchmark. Rebuilding the website is expected to improve user satisfaction by 25% and reduce checkout abandonment by 15%, increasing annual donations by $100k."
This answers: Why are we doing this? What's the business driver?
3. Project Objective / Goals**
"Deliver a modern, user-friendly website that improves donor experience and increases donations."
Specific goals:
- Improve user satisfaction score from 60 to 80 (survey post-launch)
- Reduce checkout abandonment from 30% to 15%
- Improve page load time to under 2 seconds
- Launch new website by December 31, 2026
4. Success Criteria (How will we know it succeeded?)**
- Website launches on-time (Dec 31) and on-budget ($50k)
- User satisfaction survey shows 75+ score
- Checkout abandonment is 20% or lower in first 30 days
- Zero critical bugs in first 30 days
5. High-Level Scope**
What's included / not included:
Included:
- Homepage redesign
- Product/service listing pages
- Donation checkout flow
- Mobile responsive design
- SEO optimization
Not included (in this phase):
- Blog (separate project)
- Mobile app (future phase)
- Advanced analytics (Phase 2)
6. Key Deliverables**
- Design mockups (final approved by stakeholders)
- Developed website (code, tested)
- User documentation
- Training for staff (2-hour session)
- Post-launch support plan (30-day period)
7. Constraints & Assumptions**
Constraints (can't change):
- Budget: $50,000 (no contingency)
- Timeline: December 31 deadline (donor campaign season)
- Must run on existing hosting infrastructure (AWS)
Assumptions:
- Design vendor will deliver mockups by July 1
- Stakeholders will review and approve designs within 2 weeks
- Current donor database can integrate with new site (no data migration issues)
- Team will have 30% availability for testing
8. Stakeholders & Responsibilities (RACI Matrix or Simple List)**
| Stakeholder | Role | Interest / Influence |
|---|---|---|
| Executive Director | Sponsor, approves major decisions | High interest, high influence |
| Marketing Team | Provides content, promotes new site | High interest, medium influence |
| Donors | Use the site, provide feedback | High interest, low direct influence (but critical feedback) |
| Development Team | Builds the site | Medium interest (contractors), high influence (execution) |
9. Budget**
High-level allocation:
- Design: $10,000
- Development: $25,000
- QA/Testing: $8,000
- Project Management: $5,000
- Contingency: $2,000
- Total: $50,000
10. Timeline / Milestones**
- Project start: April 1, 2026
- Design approved: June 15, 2026
- Development complete: October 31, 2026
- Testing/UAT: November 1-30, 2026
- Launch: December 1, 2026
- Post-launch support: December 1-31, 2026
11. Sign-off**
Who approved this charter?
- Sponsor: [Executive Director signature] Date
- Project Manager: [PM name] Date
- Key Stakeholder: [If applicable] Date
Signatures matter. They mean the sponsor is committed and the project is officially authorized.
How to Write a Strong Charter
Be specific, not vague.**
Vague: "The project is to improve the website."
Specific: "Redesign the website to improve user satisfaction from 60 to 80 and reduce checkout abandonment from 30% to 15%, with a budget of $50k and a December 31 delivery date."
Define constraints clearly.**
Don't pretend constraints don't exist. "Our timeline is tight. Our budget has no contingency. We must use existing infrastructure." Acknowledging constraints shows realism and prevents surprises.
Set realistic success criteria.**
Criteria should be measurable. "Users will be happy" is not measurable. "User satisfaction survey will show 80+ score" is. "Checkout abandonment will be 20% or lower" is. Measurable criteria prevent ambiguity about whether you succeeded.
Clarify what's NOT in scope.**
"Not included: Blog platform, mobile app, advanced analytics." Scope boundaries prevent "But we thought we were doing the blog too!" arguments.
Identify assumptions and risks.**
"We assume the design vendor hits July 1. If they miss, the timeline slips 4 weeks." Making assumptions explicit prevents surprises and helps with risk planning.
When a Charter Prevents Problems
Scenario: Scope Creep**
Mid-project, stakeholder asks: "Can we also build the blog?"
PM (with charter): "The charter explicitly says the blog is not in scope. If we add it, we'll miss the December deadline and exceed the budget. We can add it to Phase 2 after the January fundraiser."
Without a charter, this becomes a negotiation nightmare.
Scenario: Budget Overrun**
Development is taking longer. Team asks for 2 more contractors ($15k cost overrun).
PM (with charter): "The charter has no contingency and no room in the budget. Before we add cost, let's check: can we cut scope? Or push the timeline? Or find within-budget efficiency?"
The charter forces hard conversations about trade-offs instead of just spending more.
How to Use Your Capstone Charter in Job Interviews**
Your capstone includes a charter you built for a hypothetical project. Reference it in interviews:
"In my Google PM Certificate capstone, I built a charter for a nonprofit website redesign. I defined clear business goals, specific success criteria, and scope boundaries. I identified key stakeholders and created a RACI matrix. I listed assumptions explicitly—like 'design vendor delivers by July 1.' This showed me how a charter prevents scope creep and aligns stakeholders upfront."
This demonstrates you understand the charter's purpose, not just its contents.
Related reading: Explore how the charter connects to other planning documents and learn about defining scope and success criteria.
Next Steps
If you want a structured study companion, our Google PM Certificate Study Guide covers the full 6-course breakdown, a week-by-week study plan, and 50 practice questions with answer explanations—everything you need in one place.
For AI-powered tutoring, SimpuTech's Google PM Certificate study coach walks you through practice questions, explains concepts you're stuck on, and builds a custom study plan around your schedule. Try it free for 1 day.
Program details verified against grow.google/certificates/project-management as of March 2026. Pricing and course structure are subject to change—confirm current details before enrolling.