Why programs without charters drift on scope
Three months into every program, someone asks "is X in scope?" and the team has three different answers. By month six, the program has accreted four adjacent initiatives nobody formally approved but everyone is somehow committed to. By the end, you're well over budget and the success metric has shifted twice.
A charter doesn't prevent this by being wordy. It prevents it by being explicit about what's NOT in scope. That's the conversation people avoid in kickoff because it feels combative. It's also the most useful 30 minutes you'll spend on the program.
"A charter without an out-of-scope section is a wishlist."
This template structures the kickoff to force the hard conversations early. The cheat sheet covers how to facilitate it without the sponsor checking out at slide 4.
Program charter vs project charter
Most templates online are project charters dressed up. They cover one workstream, one delivery date, one team. That's a project charter. It's a useful artifact for a single delivery effort, but it's not what you want for a program.
A program charter is broader and longer-lived. It governs multiple related projects under one strategic outcome, often spans multiple quarters or years, has an executive sponsor (not a delivery manager), and explicitly defines the boundary between this program and the adjacent ones it will be confused with. The charter is the artifact you point to in a steering committee when someone proposes adding a sixth workstream that doesn't belong.
Three things a program charter has that a project charter usually doesn't:
- Out-of-scope statement. Explicit list of what this program will NOT do. Often longer than the in-scope list.
- Governance model. Who decides what at which forum. Steering committee composition, decision rights, escalation path.
- Success metrics that aren't delivery metrics. "Ship by Q3" is a project goal. "Reduce customer time-to-onboard by 40%" is a program goal. The charter binds the program to the outcome, not the deliverable.
This template is built for the program-level conversation. If you only need a project charter, the format will feel heavy.
The 7 sections that prevent scope creep
The template walks through these in order. Each one forces a specific conversation at kickoff that's much harder to have in month four.
- Strategic outcome. One sentence on the business result this program delivers. If you can't write it, you don't have a program.
- In-scope. The workstreams and deliverables this program will produce.
- Out-of-scope. The adjacent initiatives that look like this program but aren't. This is where most charters fail.
- Stakeholders & RACI. Sponsor, decision-makers, contributors, informed. Names, not roles.
- Success metrics. Outcome metrics, not delivery metrics. Targets, not directions.
- Constraints & assumptions. The conditions under which this scope is achievable. When an assumption breaks, the charter triggers a re-baseline conversation.
- Governance. Steering committee, cadence, decision rights, escalation path. The forum that will use this charter to make decisions.
Pair the charter with a RAID log for ongoing risk and dependency tracking, and a weekly status report for the rhythm that keeps the program on the charter's intended path.
Building a program charter in Excel
People ask why a charter lives in a spreadsheet instead of a document. The answer is that a charter has to be signed, locked, and pointed at later. A Word file gets copied, renamed, and edited by four people until nobody knows which version the sponsor actually agreed to. A program charter Excel template can be protected cell by cell, printed to exactly one page, and stamped with a date that does not move. Here is how to set that up.
Layout, and the merged-cell trap. Column A holds the section label, column B holds the content. Do not merge B across C and D to make it look wider. Merged cells break AutoFit row height, so long content silently clips when you print, which is how a charter goes to a sponsor with half the out-of-scope list invisible. Instead, widen column B, turn on Home › Wrap Text, and when you need a heading centered across several columns use Format Cells › Alignment › Horizontal › Center Across Selection. It looks identical to a merge and behaves like normal cells.
Print to one page, on purpose. Select the charter block, then Page Layout › Print Area › Set Print Area. Page Layout › Margins › Narrow. Then Scale to Fit, Width: 1 page, Height: 1 page. Check it in Print Preview before you send it. If it will not fit, that is information: a charter that cannot fit on one page is a charter nobody will read, and the fix is to cut the prose, not to raise the page count.
The completeness check. One formula tells you whether the charter is finished, which is more useful than reading it top to bottom for the fourth time:
=IF(COUNTBLANK($B$4:$B$18)>0,"Incomplete: "&COUNTBLANK($B$4:$B$18)&" sections empty","Complete")
Put a companion next to the out-of-scope block: =IF(COUNTA($B$20:$B$29)<3,"Thin out-of-scope list",""). Fewer than three explicit exclusions means the kickoff conversation did not happen. I have never seen a program with only two things worth refusing.
Date the signature so it stays dated. Do not put =TODAY() in the sign-off cell. TODAY is volatile, so it recalculates every time the file opens and your July signature will read as October in October. Press Ctrl and semicolon instead. That inserts a static date that never moves again. On a Mac it is the same keystroke. This is a two-second habit that keeps a signed artifact honest.
Locking the signed version. Every cell in Excel starts out marked Locked, which does nothing until the sheet is protected. So work in the right order. Select the content cells in column B, Format Cells › Protection, and uncheck Locked. Then Review › Protect Sheet, set a password, and leave "Select unlocked cells" ticked. Now the section labels, the formulas, and the sign-off block are immovable while the content cells stay editable for the next revision. Add Review › Protect Workbook › Structure so nobody renames or reorders tabs. For the version that goes to the sponsor, File › Info › Protect Workbook › Always Open Read-Only is the last latch.
Excel and Google Sheets. The file is an .xlsx and opens in both. COUNTBLANK, COUNTA, the wrap text, the print scaling, and the data validation dropdowns carry over. Sheet protection does not translate the way people expect: Google Sheets has no password model, it has permissions, so an Excel protected sheet arrives as a protected range tied to editor accounts. If the signed copy of the charter has to be tamper-evident, keep that copy in Excel and use Sheets for the working draft.
A worked program charter example
Six rows from a real-shaped charter, filled the way I would want to find one if I inherited the program in month four.
| Section |
What it says |
| Strategic outcome | Cut checkout abandonment from 38% to 28% by the end of Q3, without adding a login requirement. |
| In scope | Guest checkout, payment vendor migration, currency display for the five largest markets. |
| Out of scope | Loyalty program changes. The mobile app rewrite. Anything touching returns. Adjacent requests route to roadmap intake, owned by S. Beaumont, VP Product. |
| Success metrics | Abandonment 38% to 28%. Median time to first payment 9 days to 4 days. Fraud rate stays under 0.4%. |
| Constraints and assumptions | Vendor contract signs by Aug 15 (M. Okafor, procurement). Two engineers leave for the replatform in Q3, accepted. If either breaks, the charter is re-baselined at the next steering. |
| Governance and sign-off | Steering every second Thursday, chaired by S. Beaumont. PM approves changes under one week of schedule; sponsor approves one to four weeks; steering approves anything larger. Signed S. Beaumont, 2026-07-08. |
Read those six rows and you can run the program. You know what it is for, what it refuses, what number it is judged on, what has to stay true, who decides, and who signed. Four of the six take a sentence.
The third row is the one doing the work. Every charter has an outcome and a scope. Almost none of them name the three neighbouring things people will try to hand you in month four, and name the person those requests go to instead.
Questions PMs ask
What's the difference between a program charter and a project charter?
A project charter governs one workstream and one delivery effort. A program charter governs multiple related projects under one strategic outcome, with an executive sponsor and explicit governance. Use this template if you're chartering a multi-quarter, multi-team initiative.
What format is the program charter template?
Excel (.xlsx) with eight structured sections, plus a one-page PDF cheat sheet and a sponsor sign-off page. Also opens in Google Sheets.
Why does the template emphasize out-of-scope so heavily?
Because that's the section that prevents scope creep. Most charter templates list what's in scope. The good ones explicitly list what's out. The conversation people avoid at kickoff is the one most worth having.
Can I use this for a single project?
You can, but the format will feel heavy. The template is built for program-level governance, multiple workstreams, executive sponsor, multi-quarter horizon. For a single project, a lighter project charter is usually enough.
