Packs & Bundles
Executive Reporting & SteerCo Command Pack
A complete executive reporting system, not another template.
The full artifact set, the reporting guide and the worked examples. Yours to keep.
- Produce a weekly report a sponsor can act on without a follow-up call
- Run a SteerCo that closes decisions instead of noting them
- Keep RAID, decisions and milestones telling one consistent story
The problem
The weekly report, the SteerCo pack and the RAID log tell three different stories
Reporting is rarely a template problem. It is that each artifact was created separately, by a different person, for a different audience, and nothing reconciles them. The status report says amber. The RAID log carries a risk that would make it red. The SteerCo pack from last month shows a milestone that has since moved and was never restated. A sponsor reading all three concludes, correctly, that nobody has the whole picture.
- A status report that generates a follow-up call rather than a decision
- SteerCo meetings that note decisions instead of closing them
- Risks that appear in the RAID log and never in the report
- Milestones quietly re-baselined between packs, with no record that they moved
Why the usual approach does not settle it
What people reach for first, and where it stops
Downloading a template
A template is a shape. It tells you which boxes exist and nothing about what an executive audience needs in each one, which is why most completed templates are a project diary formatted into a grid.
Copying the last project's pack
It inherits that project's compromises, including the sections nobody read and the RAG definition nobody agreed. What made it work was the context around it, and that does not copy.
Reporting from whatever the tools export
The tools report on the work. A sponsor is not asking about the work; they are asking whether the commitment still holds, what it now costs, and what they have to decide this week.
What changes
What Executive Reporting & SteerCo Command Pack changes about the decision
One story across six artifacts
The status report, SteerCo pack, RAID register, decision log, action tracker and milestone tracker are designed to reconcile. A risk raised in one is visible in the others rather than living in a file of its own.
Reports written for a decision, not for a record
Each artifact states what is being asked of the reader. A report that asks for nothing is a status update; a report that names the decision is what a sponsor can act on.
A worked example of every artifact, completed properly
The hard part is not the empty template, it is knowing what good looks like in it. Each artifact ships with one completed to the standard a senior audience expects.
A RAG definition somebody can defend
The reporting guide sets out what amber actually means and what has to be true to call something green, so the colour survives being challenged in the room.
How it works
The sequence
Most reporting problems are not template problems. They are that the weekly report, the SteerCo pack and the RAID log tell three different stories because nobody connected them. This pack supplies the full set as one system, with worked examples showing what a defensible report looks like.
- 1
Adopt the artifact set
Six connected artifacts and the guide that explains what each audience needs from them. Used as they are, or adapted to the organisation's own house style.
- 2
Establish the reporting standard once
The guide settles the questions that otherwise get re-argued every month: what the RAG thresholds are, what belongs in a risk rather than an issue, what a decision log entry has to contain to be closed.
- 3
Run the weekly and the monthly cycle
The weekly report feeds the SteerCo pack, which draws on the same RAID, decisions and milestones, so the monthly pack is assembled rather than rewritten.
- 4
Keep the record that makes the next report arguable
Decisions, actions and milestone movements accumulate. Six weeks later the question of when a date moved and who accepted it has an answer.
What you get
What is in your hands afterwards
- Executive Status PowerPoint
- SteerCo PowerPoint
- RAID Register
- Decision Log
- Action Tracker
- Milestone Tracker
- Executive Reporting Guide
- Worked examples
- AI workflow guide
Why it holds up
What makes the result defensible
Each of these is something you can check before you buy, and hold KnownShift to afterwards. None of them asks you to take a result on trust.
Built from delivery practice, not from a slide library
The structures are the ones that survive a sponsor who asks a second question. They come from running programs at the level where the answer matters.
Connected by design
The artifacts share a vocabulary and cross-reference deliberately. Inconsistency between them becomes visible rather than being absorbed by three separate documents.
Yours outright, in formats you already use
PowerPoint and Excel, unlocked and editable, on your own machine. Nothing depends on KnownShift remaining in the picture.
Capabilities
- Executive status reporting
- SteerCo pack structure
- RAID visibility
- Decision and action tracking
- Milestone communication
What it does not do
- A reusable professional system, not a connected live workflow. Governed project data across a full delivery lifecycle is what Project OS does.
Questions
Questions about Executive Reporting & SteerCo Pack
- Is this just a set of templates?
- The templates are the artifacts. What the pack adds is how they connect, worked examples of each one completed properly, and the reporting guide that explains what an executive audience needs from each.
Reporting the project, or running it from one source?
The pack gives you the artifacts and the standard they should be produced to. Project OS produces them from governed project data, so the weekly report, the RAID register and the SteerCo pack cannot tell three different stories about the same project.
Evaluating this for a team? Discuss team or enterprise use with the KnownShift team.