A steering committee is not a status meeting. It is where the people who can say yes or no meet to say yes or no. The packs that work are the ones that make that easy. Everything else is padding.
The structure, page by page
- Decisions required. One page. Each decision has a question, the options, your recommendation, and what happens if no decision is made today. If there are no decisions, say so, and make the meeting shorter.
- Headline status. One page. Overall RAG, the three things that matter this month, and what changed since last time. The colour must match the detail pages.
- Milestones. The next five that matter, with planned date, forecast date, and the reason for any gap. Not the whole plan. The plan is an appendix.
- Budget. Approved, spent to date, forecast at completion, and the variance. Four numbers. If a number moved since last period, say why.
- Top risks and issues. The ones that could change a decision on page one. Each with its path to green: problem, plan, date, named owner.
- Decisions from last time, and what happened. Every decision the board made last period, with the action taken and the owner. This is the page most packs leave out. It is the one that builds trust.
- Appendices. The full plan, the full RAID log, the detail someone might ask for. Nobody reads them in the meeting. They are there so the summary is defensible.
A checklist before the pack goes out
- Every decision on page one names an owner and a date.
- The overall RAG on page two matches the worst RAG on the milestone and risk pages.
- Every milestone date is the one in the plan, not the one in last month’s pack.
- The budget figures add up, and they match the budget tracker.
- Every risk on page five is in the RAID log with the same colour.
- Every decision from last time has an outcome written down.
- Nothing in the pack contradicts the Status Report that went out last week.
A real example
A programme we took over had a SteerCo pack of 64 slides. The sponsor told us she read the first two and the last one. The middle was a tour of every workstream, with each lead’s own colour scheme. Nobody could find the decisions. Three of them had been waiting for two months.
We cut it to nine pages in the order above. The first meeting with the new pack made four decisions in forty minutes. The leads still kept their detail. It just moved to the appendix, where it belonged.
Where PMOpack fits
PMOpack builds the SteerCo pack from the data you already keep, in a decision-first order, with the same vocabulary as the other seven artefacts in the pack. Fixed checks run across the set at generation time: the SteerCo pack against the Milestone Report, the RAG roll-up against its rows, the decisions page against the placeholder-owner check. A critical finding blocks publish until a person fixes the data or accepts it with a written reason. A check skips, and says so, if the partner document is not there. It does not decide what the board should decide. It makes sure the pack does not argue with itself before the board sees it.
Questions people ask
- What is the first page of a SteerCo pack?
- The decisions required. Each with a question, the options, a recommendation and what happens if no decision is made today.
- How long should a SteerCo pack be?
- Short enough that the board reads all of it. Around six to nine pages of summary, with detail in appendices that are there to be checked, not read aloud.
- Should the SteerCo pack include the full plan?
- As an appendix. The summary shows the next five milestones that matter, with planned and forecast dates and the reason for any gap.
- What page do most packs leave out?
- Decisions from last time, and what happened. Showing the board that its decisions led to action is what builds trust in the pack.