Your VP doesn't want a 14-tab Smartsheet rollup. They want one page, three lines, RAG with trend, and what blocks delivery. This Excel template is the format I've used for 20 years across enterprise programs.
Weekly exec status, monthly steering, single-program detail, portfolio rollup. Pick the one that fits the audience, fill the same data, ship the right view.
Not just "we're amber." This shows the trend: were we green last week, drifting amber, or stuck red for three reporting cycles? That's the question execs walk into the meeting wanting answered.
One-page guide on what to put in (and what to leave out) of an exec status. Covers risk framing, milestone language, and the "no surprises" principle.
One purchase, yours to keep. Use it on every program, customize for your team. Works in Excel and Google Sheets.
Most templates ship as a 12-section monster: detailed milestone tables, sprint velocity, burn-down charts, risk matrices with five score columns, dependency graphs, change requests, three flavors of meeting notes. By the time the exec opens it, they've stopped reading.
An executive status report is a different artifact. It exists to answer four questions in under 90 seconds: are we on track, what changed, what blocks delivery, and what do you need from me. Everything else belongs in the working doc the team uses, not in front of the VP.
The six things this template explicitly leaves out:
What's in: the RAG row, what changed since last week, the one or two risks that need a decision, and the ask. That's it. The template enforces the discipline.
The most common failure mode I see in junior PM status reports: every workstream is green every week, and then in week 18 something goes red and it's a surprise. That's not green. That's a PM who hasn't built the muscle to color-call.
Three rules this template builds in:
The template tracks RAG with a trend column: were we green last week, drifting amber, or stuck red for three reporting cycles? That's the signal an exec actually wants. A flat green for 12 weeks and then a sudden red is a credibility-burning event.
"The report is supposed to be a side effect of the work, not the work itself."
This template flips the ratio. Drop your inputs into pre-built fields: RAG, trend, owner, ETA, risk callout. All formatted, all consistent, all in the layout your VP already reads. Ten minutes to fill it in, the rest of the morning back.
A template is the artifact. Executive status reporting is the habit that makes the artifact worth reading. The discipline is small and unglamorous: the same four answers, in the same place, on the same day every week, whether the news is good or bad. Executives come to trust a report they can read on autopilot, because the format never moves and the hard weeks look structurally identical to the easy ones.
Done well, executive status reporting is a forecasting tool, not a recap. The trend column is the whole game: not "we are green," but "we have held green for three weeks and confidence is steady," or "we slipped to amber, and here is the one decision that pulls it back." That is what a VP scans for. This template builds the cadence in, so the reporting becomes a side effect of running the program instead of a Thursday-night writing assignment.
Here is the entire top of a real weekly report. Four lines, readable in under 30 seconds:
Status: Amber, trending green. Red two weeks ago; the recovery plan is holding.
What changed: UAT entry slipped 5 days on the staging outage. The recovery plan absorbs it, and the Sep 12 launch date holds.
What I need: A decision on the vendor SOW by Friday. Every week without it moves the migration start week-for-week.
At risk: SSO cutover is still gated on the platform org's identity service, due Aug 22. Escalation path agreed; watching weekly.
Why each line earns its place. The status line carries a trend, not just a color, so the reader knows whether this amber is recovering or decaying. The changed line connects the event to the date that matters. The ask has a deadline and a cost of delay attached, which is what turns "please advise" into a decision. And the risk line names the gate, the date, and the plan, so nobody is surprised in three weeks.
That structure is the whole template. The Excel file pre-builds it in four formats (weekly exec, monthly steering, single-program detail, portfolio rollup), and the free one-page version of the discipline is the Status Report Cheat Sheet.
Excel (.xlsx), and it opens cleanly in Google Sheets. The one-page format is built to paste into an email or a slide without rework: four report formats, RAG with trend, and the milestone and risk callouts already structured.
Three sections: what changed since last week, what you need (the ask), and what is at risk. If the reader finishes and does not know what to do, the report failed. The template enforces the structure; the free cheat sheet is the one-page version of the discipline.
Fifteen minutes, if the inputs are alive. The template pulls from a live RAID log and milestone list, so the weekly writing is assembly, not archaeology. If it takes two hours, the problem is upstream of the report.
Red, amber, green, plus the direction of travel: a green that has been quietly degrading for three weeks is more dangerous than a stable amber. The template tracks both so the trend is visible before the color changes.
“I used the tools for my first weekly report and it helped me validate the right level of communication and information for Senior Leadership and has saved me generous time.”
The Status Report Cheat Sheet is free: one page, the exact format I use to brief leadership in under five minutes. If you want a working file instead, the free RAID log and the free OKR tracker are both one-sheet Excel templates, also free.