Project Charter Template for Technical Initiatives
Updated: Oct 19
An engineering team spends three months building a self-service onboarding flow that lets enterprise customers set themselves up. The VP sponsoring the work thinks she has approved two weeks of automation bolted onto the existing white-glove process. Nobody was wrong in any single meeting. They had just never written "done" down in the same place, so each side heard its own version and nodded. The gap surfaces at the first demo, when the sponsor asks why the success team's process has changed.
This is a composite, but the pattern is common. A project charter exists to force that argument to the front, before kickoff instead of at the postmortem. Most charters don't, because they're filled in rather than argued over: the template has a box for objectives, someone writes "improve onboarding", and everyone signs.
This post gives you the template, and the four moves that make it surface disagreement instead of hiding it.
Write "done" separately first
Before anyone opens the template, ask the sponsor and the lead to answer three questions independently, in writing, without discussing them:
Done means: what will be true, and measurable, when this project has succeeded?
Not in this project: what will people expect that this project won't deliver?
We'd stop if: what result, by what date, would mean it isn't working?
Then put the answers side by side. In the composite above, they would have looked like this:
Sponsor (VP Product) Lead (Engineering Manager)
Done means Success team spends less time Enterprise customers onboard
on setup; same process themselves, no success team
Not included Changing the customer journey Custom integrations, migrations
We'd stop if It takes more than a month Fewer than 40% self-serve at 60 days
Three mismatches, found in twenty minutes, before any code. That's the discovery move: the charter's real job is to show where people disagree, and the disagreement only shows if they write independently. Drafting it together in a meeting produces the vaguest wording everyone can agree to.
The test: do the sponsor's and the lead's answers to "done means" describe the same thing? If you can't tell, the objective isn't specific enough yet.
One named sponsor who can say no
A charter needs a sponsor who can approve the direction, provide the resources and stop the project. Not a committee, and not a title nobody has asked.
UK government project guidance is blunt about this. Its guidance on the senior responsible owner (the accountable sponsor) says "there can only be one accountable person who can be held to account and this accountability cannot be delegated or shared." It also expects that person to consider stopping the project when it can no longer meet its objectives. A sponsor who can't stop the project can't really approve it either.
The lead is the other named person: the one who runs the work day to day. When sponsor and lead are the same person, you need the charter less. When they're different, it's how they agree.
The test: ask the named sponsor two questions. What budget or headcount do you control for this? Would you stop it if it missed the failure line? If either answer is "I'd have to check", you have the wrong sponsor, or not one yet.
Objectives with a baseline, a target and a failure line
"Improve onboarding" is a direction, not an objective. Every objective in a charter needs four parts: the measure, where it is today, where it needs to be, and by when. "Reduce median time to first value for new enterprise customers from 30 days to 10, within 60 days of launch."
Then write the failure line: the result that would mean the project hasn't worked. "If fewer than 40% of new customers complete onboarding without help at 60 days, we stop and review." Charters often leave this out, which means nobody can ever say the project failed, so nobody can stop it.
If you don't know the baseline, that's a finding. Measuring it becomes the first piece of work, before anyone commits to the target.
The test: for each objective, can you name the dashboard or query that will show the number on the review date? If not, the objective isn't measurable yet, whatever it says.
Out of scope: name what people will ask for
The out-of-scope list is the charter's best defence against drift, and the section most often left blank or filled with things nobody wanted. Fill it with the requests you can predict: the adjacent features, the big customer's special case, the migration everyone assumes is included.
A useful way to find them: ask the people who'll use the result, and the people who'll support it, "what will you expect this to do?" Everything they name that the project won't do goes on the list, with where it will go instead ("separate project", "stays with the success team", "phase 2, not committed").
The test: write down the feature most likely to be requested in week four. Is it either in scope or on the out-of-scope list? If it's on neither, the argument about it is still ahead of you.
Size the timeline from past projects, not this plan
Timelines in charters are usually built from the inside: list the tasks, estimate each, add them up. That method tends to be optimistic. Bent Flyvbjerg's work on project forecasting attributes inaccurate forecasts to optimism bias and strategic misrepresentation. His remedy, reference class forecasting, bases the forecast on how comparable past projects actually performed.
For a charter, that means one question before the dates go in: how long did the last three projects like this actually take, compared with their first plan? If similar integrations have run 40% over, a plan that assumes this one won't needs a reason.
The test: does the charter's timeline cite at least one comparable past project and its real duration? If no comparable project exists, say so in the risks. That uncertainty is the first risk.
Find risks with a premortem
"We might run into challenges" isn't a risk. To get real ones, run a premortem before the charter is approved. Gary Klein describes it in Harvard Business Review: the leader tells the team the project has failed spectacularly, and everyone independently writes down every reason they can think of, especially the ones they would normally keep quiet about. Klein cites research by Mitchell, Russo and Pennington finding that this kind of "prospective hindsight" increases the ability to correctly identify reasons for future outcomes by 30%.
The charter keeps the top three to five, each with an owner and a mitigation. The rest go to the risk register.
The test: does each risk in the charter name something specific enough that someone could check next week whether it is happening? "Integration complexity" fails. "The SSO connector may not support two of our customers' identity providers" passes.
Decisions required: an owner and a date for each
Most projects start with open decisions: pricing, ownership, technical approach. The charter lists them, each with the person who will decide and the date the project needs the answer by. An open decision with no owner becomes a delay nobody planned for.
The test: for each open decision, is there one named person and a date? If the date is after the work that depends on it starts, move one of them.
When to write one
Situation | Charter? | Why |
Cross-team, multi-month, or visible to executives | Yes | Several parties have different pictures of "done" |
Sponsor and lead are different people | Yes | The charter is how they agree |
Vendor or contractor involved | Yes, alongside the contract | The statement of work covers deliverables, not your own success measures |
Single team, fits in a sprint or two | No | A ticket and a conversation are enough |
Routine work on an existing service | No | There's nothing new to agree |
Approval, then keep it alive
The sequence is short: the lead drafts it from the separately written answers, the sponsor approves it or sends it back, and stakeholders see the approved version before work starts at scale. Record the approval: a date and a name, not "discussed in the steering meeting".
Then revisit it at each milestone. Add a one-line change log for anything that moves the scope, the target or the date, with who approved the change. A charter that's never updated becomes a record of what people used to believe.
The charter belongs to the lead, not the project office. If a template field doesn't change a decision (a communication plan, a responsibility chart that repeats the stakeholder list), delete it. And if you can't name a single accountable sponsor, stop. That blank isn't a formatting gap. It's the project telling you it isn't ready to start.
The template
# Project Charter: [Project name]
Sponsor: [one named person who can approve and stop it]
Lead: [one named person who runs it]
Date: [date written] Status: [Draft / Approved on date by name]
## Purpose
[1 or 2 sentences: the problem, not the solution]
## Objectives
[Measure: baseline now, target, by when, where it's measured]
## Failure line
[The result, by date, that means we stop and review]
## Scope
In scope: [bullets]
Out of scope: [the things people will ask for, and where they go instead]
## Stakeholders
[Name and role; detail lives in the stakeholder map]
## Timeline
[Milestones with dates; comparable past project and its real duration]
## Budget and resources
[Headcount and weeks, or spend if a vendor is involved]
## Risks
[Top 3 to 5 from the premortem, each with an owner and mitigation]
## Decisions required
[Decision, who decides, needed by]
## Change log
[Date, change, approved by]
A worked example
Here is the composite onboarding project, chartered properly. The figures are illustrative.
# Project Charter: Self-Service Enterprise Onboarding
Sponsor: VP Product Lead: Engineering Manager, Onboarding
Date: 2026-03-15 Status: Approved 2026-03-18 by VP Product
## Purpose
Enterprise onboarding takes 30 days and needs heavy manual setup by the
success team. It is the most-cited reason in churn surveys among customers
who never activate.
## Objectives
- Median time to first value: 30 days now, 10 days within 60 days of launch
(onboarding dashboard)
- Success team hours on onboarding: down 50% within 90 days (time tracking)
- Onboarding satisfaction score: hold at 50 or above (currently 53)
## Failure line
Fewer than 40% of new enterprise customers complete onboarding without
success team help at 60 days: stop and review with the sponsor.
## Scope
In scope: workspace setup, bulk user invite, SSO configuration,
top 5 standard integrations
Out of scope: custom integrations (stay with the success team),
migration from existing tools (separate project), white-glove
onboarding for the largest accounts (unchanged)
## Stakeholders
VP Product (sponsor), Engineering Manager (lead), Senior PM Onboarding,
2 engineers, success team lead (consulted), sales engineering (review)
## Timeline
Discovery and design week 3, internal MVP week 6, beta with 5 customers
week 10, general availability week 14. Last comparable project (admin
console self-service) planned 10 weeks, took 15: buffer added to beta.
## Budget and resources
2 engineers for 14 weeks, 1 designer for 4 weeks, PM in existing role
## Risks (from premortem)
- SSO connector may not support two current customers' identity
providers. Owner: tech lead. Mitigation: limit v1 to top 3 providers.
- Sales keeps promising white-glove setup to mid-size accounts.
Owner: PM. Mitigation: sales enablement before beta.
- Edge cases need manual handling, lowering the self-serve rate.
Owner: success lead. Mitigation: track and triage weekly in beta.
## Decisions required
- Which pricing tiers are eligible: Sales VP, by week 1
- Integration priority list: PM, by week 2
- Beta cohort: success lead, by week 8
## Change log
2026-05-02 Beta moved from week 10 to 11 (SSO); approved by VP Product
It fits on two pages. Anyone reading it can see what the project is, what it isn't, how success and failure will be measured, who decides, and when.

What to do this week
Pick the next project that crosses a team boundary. Before anyone drafts a charter, send the sponsor and the lead the three questions (done means, not included, we'd stop if) and ask for written answers by the end of the week. Compare them in a 30-minute meeting. Then fill the template from what you agreed, and run a premortem with the team before the sponsor signs. The 90-Minute Pre-Mortem Facilitation Kit has the session plan.
Final takeaway
A project charter earns its page when it surfaces disagreement before kickoff, not when every box is filled. Get the sponsor and the lead to write what done means, what's excluded and when they'd stop, separately, and compare the answers. Name one sponsor who controls the resources and could stop the project. Give every objective a baseline, a target, a date and a failure line. Put the requests you can predict on the out-of-scope list. Size the timeline from what similar projects actually took, and find the risks with a premortem. Then record the approval and keep a change log, so the charter stays a record of what people agree on now.
Sources
Government Project Delivery (UK), The Role of the Senior Responsible Owner, 2025: "There can only be one accountable person who can be held to account and this accountability cannot be delegated or shared"; the SRO is accountable for the project meeting its objectives and should consider whether to stop a project that can no longer meet them. https://projectdelivery.gov.uk/library-products/the-role-of-the-senior-responsible-owner-html/
Klein, G., "Performing a Project Premortem", Harvard Business Review, September 2007: the premortem method; cites Mitchell, Russo and Pennington's finding that prospective hindsight increases the ability to correctly identify reasons for future outcomes by 30%. https://hbr.org/2007/09/performing-a-project-premortem
Flyvbjerg, B., "From Nobel Prize to Project Management: Getting Risks Right", Project Management Journal 37(3), 2006, pp. 5–15: inaccurate forecasts explained by optimism bias and strategic misrepresentation; reference class forecasting based on the actual performance of comparable projects. https://doi.org/10.1177/875697280603700302
Related reading
Part of the Engineering Templates & Playbooks guide — ShiftQuality's collection of ready-to-adapt templates.


