Project charter: a template that sets scope before work starts
Define scope, roles, and goals before the first task is created.
The kickoff meeting goes well. Everyone nods, the timeline looks reasonable, responsibilities feel clear — the team leaves the room ready to start. No one has run into a disagreement yet. The gap shows up later — what seems in scope to one person is an addition to another.
A project charter template helps fix that before the project starts pulling in different directions. It gives the team one short document that captures the goal, the scope, the owners, and the timing. Those decisions are still cheap to agree on at this stage.
What a project charter is really for
A project charter is a short document that defines the project before execution begins. It records the goal, the scope, the timing, and the people involved. The team starts from one shared version of the work instead of several private interpretations.
The document does not need to be formal or long. What matters is that it exists before the first task is created. At that point, the scope is still flexible and agreement is still easy to reach. Once execution is underway, every change to the goal or the boundaries costs more. The cost shows up in time, rework, and scope arguments mid-delivery.
It also helps to separate the charter from similar documents people often confuse it with:
- Project plan — explains how the project will be delivered once execution is underway. The charter comes first and defines what the project is and why it exists.
- Team charter template — covers how the team works together: norms, communication, ways of collaborating. A project charter is about one specific initiative, its purpose and limits.
For most small teams, one clear page is enough. The goal is to stop ambiguity before it starts leaking into delivery.
What to include in a project charter
A useful charter should be quick to scan and specific enough to settle the questions that usually create friction later. Most teams do not need a long document for that. Here is what project charter templates include:
Section | What to include |
|---|---|
Project name | A specific, recognizable project name |
Project goal | What should change and why — written in one or two sentences |
Scope | What is in scope and what is out of scope |
Key stakeholders | Who is involved — names or roles. Sponsor, PM, core team roles |
Roles | Who owns what across the work |
Timeline | Start date, end date, major milestones |
Success metrics | Concrete criteria that define success |
Budget | Budget or resource limit, when relevant |
Key risks | One to three risks that could affect the outcome |
Approval | Who approves the charter — the Project Sponsor's name or sign-off |
The scope row is often the hardest to fill. For projects that need a more detailed breakdown of deliverables and exclusions, a scope of work template helps define it before the charter is signed off.
The roles section does not need to become a second planning document. Make it a short role summary. The detailed ownership can sit in a linked RACI matrix when the project is complex enough to justify it.
Project charter sample
Below is a filled charter for a real project scenario rather than a generic outline. It uses a specific goal and concrete dates. The document reads like something a team could review before kickoff, not a formal placeholder.
Section | Value |
|---|---|
Project name | Redesign new user onboarding flow |
Project goal | Reduce time-to-first-value from 7 days to 3 days by the end of Q3 2026 |
Scope | In: onboarding email sequence, in-app checklist, welcome screen. Out: pricing page, mobile app, support docs |
Key stakeholders | Sponsor: VP Product PM: Alex Team: 2 engineers, 1 designer, 1 content writer |
Roles | PM owns delivery / Design owns UX / Engineering owns implementation / Marketing owns email copy |
Timeline | Start: May 1 Beta: June 15 Full release: July 31 |
Success metrics | Time-to-first-value of 3 days or less. Activation rate of at least 45% in the first 2 weeks after launch |
Budget | $12,000 in design and engineering time |
Key risks | 1. A/B test data may take more than 3 weeks. 2. Engineering capacity depends on the Q2 sprint plan |
Approval | VP Product sign-off required before kickoff |
A project charter template example like this works because it stays specific. The goal is measurable, and the scope has real boundaries. The success metrics also give the team something concrete to check later.
How to write a project charter that stays useful
Write the charter before kickoff. Once work is already moving, the document becomes a record of what already happened, not a guide for what comes next.
A few rules make the charter stronger:
- Keep it short enough that one person can read it in a few minutes.
- Agree on the goal and the scope with the sponsor before the team starts.
- Use metrics that can be checked later. A target without a number is not a target.
- Write the out-of-scope line as carefully as the in-scope line. That is usually where scope creep enters — not through obvious additions but through work that was never explicitly excluded. One clear sentence about what the project does not cover is often more useful than three sentences about its content.
A short project charter works better than a long one. Short documents with clear boundaries are usually enough to get the team aligned before work begins.
How to create it in Vaiz
In Vaiz, you can build a project charter template as a live document. Keep it inside the same project where the work will happen.
The setup looks like this:
- Create a document inside the project.
- Add sections for goal, scope, stakeholders, roles, timeline, and success metrics.
- Copy the key dates from the charter into project milestones.
- Turn next actions from the charter into tasks in the same project.
- Keep the document visible during kickoff so the team starts from the same agreement.
That setup works because the charter stays close to the work itself. The document keeps the agreement visible, while milestones and tasks carry that agreement into execution. The result is easier to maintain than a charter that lives in one place while delivery happens somewhere else.
The point of the document is speed later
People often assume a charter slows the project down. In practice, 30 minutes spent writing one early can save days of confusion once the work is under pressure. The charter's job is to make later disagreements easier to resolve.
Before the next kickoff, fill in one page and treat it as the project's first alignment check.