What is a Project Charter?
A project charter is a short document that formally authorizes a project — defining its purpose, objectives, scope boundaries, team, and key decisions before work begins.
A project charter is a short document that formally authorizes a project and documents its key parameters: what it will accomplish, why it matters, who's in charge, what the boundaries are, and what resources are approved.
In formal project management (PMBOK methodology), the project charter is the first artifact produced — it's the document that officially makes the project real. It's signed by a sponsor who has authority to commit the resources needed.
For agencies and small teams, a full formal charter may be overkill. But the questions the charter answers — what are we building, why, who decides, and what's out of scope — need to be answered for every project, in some form.
What a Project Charter Contains
A complete project charter covers eight elements:
- Project purpose — why this project exists and what problem it solves
- Objectives — specific, measurable outcomes the project will achieve
- Scope boundaries — what's included and explicitly what's not included
- Deliverables — the specific outputs the project will produce
- Timeline — start date, key milestones, expected completion
- Budget — total approved budget and any spending constraints
- Team — who's on the project, roles, and the project manager
- Stakeholders and authority — who can approve changes, who needs to be informed
Charter vs SOW vs Scope Statement
These documents overlap but serve different purposes:
| Document | Purpose | Audience | Detail level |
|---|---|---|---|
| Project Charter | Authorize the project | Internal stakeholders | High-level |
| Statement of Work (SOW) | Define deliverables and terms | Client-facing | Detailed |
| Scope Statement | Define what's in and out of scope | Internal + client | Detailed |
| Project Plan | Schedule and resource plan | Team | Very detailed |
Project Charters for Agency Work
Agencies rarely use formal project charters. The client-facing equivalent is the proposal and SOW — they define deliverables, timeline, and cost. But internally, a one-page brief that answers "what are we building, why, who decides, and what's out of scope?" serves the same purpose.
The most common reason agencies skip the internal charter: everyone's in a rush to start the work. The irony: the 30 minutes spent aligning on these questions upfront saves hours of confusion and rework later.
A minimal internal charter for an agency project: project goal (2 sentences), client contact and decision authority, out-of-scope list, timeline and milestones, and who on the team owns what.
One-Page Project Charter Template
A one-page charter is the practical version for agencies and small teams. The goal: one document that answers 'what is this project and what does success look like?' for every stakeholder.
| Section | What to write | Example content |
|---|---|---|
| Project name | Short, specific name | Harborview Legal — Website Redesign 2026 |
| Project sponsor | Who has ultimate authority and budget ownership | Sarah Chen, Managing Partner |
| Project manager | Who runs the day-to-day | Olena K., Senior PM |
| Objective | One sentence on why this project exists | Redesign website to improve lead generation; target 30% increase in contact form submissions |
| Deliverables | Numbered list of specific outputs | 1. 8-page website 2. Brand-aligned design system 3. Analytics setup |
| Timeline | Start, key milestones, end date | Start: Aug 1. Design approval: Aug 21. Launch: Sep 15 |
| Budget | Total approved budget | $18,500 fixed price |
| Scope boundaries | Key inclusions and exclusions | Includes: 8 pages, contact form, GA4. Excludes: copywriting, CMS training |
| Success criteria | How you'll know it's done and done well | Site launched on schedule, client sign-off, all pages pass PageSpeed score of 80+ |
| Key stakeholders | Who needs to be informed or consulted | Sarah Chen (approver), Marketing team (reviewers) |
Getting Stakeholder Buy-In on the Charter
A charter that isn't reviewed and approved by key stakeholders is a document, not an agreement.
Buy-in happens in two stages. First, circulation: send the draft charter to all stakeholders listed in it before the kickoff meeting. Give them 48 hours to review and raise questions. This prevents the kickoff meeting from being the first time anyone sees the charter.
Second, explicit sign-off: at the kickoff meeting, walk through the charter, address any questions or changes, and close with explicit confirmation from the sponsor. A verbal yes in the meeting plus an email follow-up confirming approval is the minimum.
The sponsor's sign-off is most critical. The sponsor's authority is what makes the charter binding. When the sponsor has signed off, scope changes require going back to them — which is exactly the friction you want when clients try to add work without a change order.
- Send charter 48 hours before kickoff — don't debut it in the meeting
- Address all questions during kickoff and revise the charter if needed before sign-off
- Get explicit sponsor confirmation, not just 'looks good' from the team
- Follow up the verbal approval with an email confirming the agreed charter
- Ensure the decision-maker is in the kickoff — approval from the wrong person isn't approval
When to Update the Project Charter
A project charter should reflect the current agreement between the agency and client. Update the charter when: the project objective changes materially; the budget increases due to an approved change order; the timeline changes by more than 10% of the original duration; major deliverables are added or removed; or the project sponsor changes.
Do not update the charter for: task-level changes within existing deliverables; minor schedule adjustments within the same milestone week; or internal team changes that don't affect the client-facing agreement.
When you do update, use version control. Label it 'v2.0' with the date and a one-line note on what changed. Send the updated version to all original sign-off parties and get re-confirmation of approval.
- Update for: objective changes, budget increases, major deliverable additions/removals
- Don't update for: task-level changes, minor scheduling shifts, internal team changes
- Version control: label v2.0, note what changed, date it
- Re-circulate and get fresh approval from all original sign-off parties
Melororium
Kick off and structure projects in Melororium
Project management, time tracking, CRM, and invoicing — one flat monthly fee. Starter $29/mo · Agency $59/mo · Studio $119/mo.
Frequently Asked Questions
Is a project charter the same as a proposal?
Not exactly. A proposal is client-facing and often includes pricing, terms, and case studies. A project charter is internal and focuses on authorizing and defining the project after the proposal is accepted. The SOW (often part of the proposal) is the closer equivalent to a charter.
Who writes the project charter?
Typically the project manager, in collaboration with the project sponsor. The sponsor signs it to formally authorize the project and the resources needed. For small teams, the charter may be drafted by whoever is leading the project.
How long should a project charter be?
1–3 pages for most projects. It's a summary document, not a detailed plan. If it's longer than 3 pages, you're including detail that belongs in the scope statement or project plan.
Put it into practice
Manage it all in Melororium
Project management, time tracking, CRM, and invoicing — one workspace, one flat fee. From $29/mo.