Why the one-pager is a different artifact than the status report
I have inherited dozens of programs over 20 years. The first thing every new sponsor or peer leader asks is the same: "give me the 60-second version." Nobody asks for the weekly status report. Nobody wants the 14-tab Smartsheet. They want a single page that lets them ask the next-level question.
Most PMs respond by emailing the latest status report. That's a category error. A status report is built for someone who already understands the program and wants the delta since last week. A one-pager is built for someone who doesn't know the program and needs the operating context.
"The first artifact a new exec asks for is the one most PMs don't have."
This template gives you the four variants you'll actually need, the field structure that produces a credible one-pager in 20 minutes, and the cheat sheet covering when to use which.
The 4 moments this template earns its keep
- New exec joins your reporting chain. They want the program in 60 seconds. The single-program brief variant is built for this exact moment.
- Board or steering committee handout. They get a 30-page deck for the meeting; they need a one-page take-away. The board variant is the artifact they'll reference between meetings.
- 1:1 prep with a peer leader. They asked what you're working on. You have 5 minutes. The 1:1 variant is the version that respects the time without being a sales pitch.
- Multi-program portfolio review. You run multiple programs and your director wants the rollup. The portfolio variant ranks them on the same axes (RAG, top milestone, top risk) so the comparison is fair.
What an exec one-pager always has (and what it leaves out)
Always has:
- The strategic outcome (one sentence on what this program is for)
- Current RAG with one-line trend ("amber, drifting from green last quarter")
- 3-5 milestones (not 12, not 40)
- The 1-2 risks that might warrant exec attention
- The ask (what you need from this person, in one sentence)
Always leaves out:
- The full risk register (link to it; don't paste it)
- Sprint metrics, velocity, burn-down (not exec signals)
- Detailed task lists (your team's tracker is the source of truth)
- Anything that needs more than one screen to read
Pair the one-pager with the executive status report for the weekly cadence and the program charter for the deeper context the one-pager points at.
Questions PMs ask
How is this different from a status report?
Audience and intent. A status report is for someone who already knows the program and wants the delta since last week. A one-pager is for someone who doesn't know the program and needs the 60-second handoff context. Different artifact, different cadence, different format.
Why 4 variants in one template?
Different audiences need different framings of the same underlying data. A single-program brief looks different from a board handout. The template gives you all four so you don't reinvent the format every time the audience changes.
Excel or PDF?
Excel (.xlsx) for editing, with a print-to-PDF cheat sheet so the output is one clean page. The Excel also opens in Google Sheets if you prefer.
Can I use this without the rest of the toolkit?
Yes. The one-pager stands alone, you can use it with any program, any source data, any reporting stack. It pairs especially well with the status report and program charter, but it's not a dependency.
