Steering Committee Report Template: One Page That Gets a Decision

What belongs in a steering committee report — status, decisions needed, risks, financials — and how to structure one page that actually produces decisions.

A steering committee exists to make decisions the project manager cannot make alone. Most steerco packs fail at this, because they are written as a record of activity rather than a request for a decision.

The test for a good report is simple: could an attendee who skim-read it on the way to the meeting arrive knowing what they are being asked to decide?

The structure

1. Headline status. RAG rating for the project overall, plus the same for scope, schedule, budget and risk separately. One line explaining any amber or red, in plain language. If the status changed since last time, say so and say why.

2. Decisions required. Put this second, before the detail. Each item: what the decision is, the options, your recommendation, what happens if it is deferred, and the date by which it is needed. If there are no decisions required, the meeting is a briefing, and worth asking whether it needs to happen.

3. Progress since last meeting. Milestones completed, milestones missed with revised dates. Short. This section exists to establish credibility, not to fill pages.

4. Next period. What is planned before the next meeting, and what could stop it.

5. Top risks and issues. Five entries maximum, drawn from the RAID log rather than rewritten. Each with owner, impact and what is being done. If everything is on the list, the committee cannot tell what deserves their attention.

6. Financials. Budget, spent to date, forecast at completion, variance. A variance without an explanation is a question you will be asked anyway.

7. Dependencies needing escalation. The things another part of the organisation owes you and has not delivered. This is often the single most valuable section, because it is the one thing a steering committee can genuinely unblock.

Writing it so it works

Lead with the ask. Executives read the first third of any document. Put decisions there.

Give a recommendation. Presenting three options without a preference transfers your job to the committee, and they will notice.

Explain amber and red in consequence terms. Not "integration testing is delayed" but "integration testing is two weeks late, which moves the go-live from 12 September to 26 September unless we add a second test environment."

Keep the RAG rating honest. Watermelon reporting — green outside, red inside — is discovered eventually, and it costs more credibility than an early amber ever would.

Same format every time. Committees read faster when the layout does not move. Consistency also makes trends visible across meetings, which is where the real signal lives.

One page of substance, appendices for the rest. Detail belongs behind the summary, available if asked.

The cadence

Circulate 48 hours ahead. Reports handed out in the room are read in the room, which means the first ten minutes are silent and the decisions are made without preparation.

Follow up with the decisions recorded in writing within a day, including who committed to what. Decisions that are not written down are re-litigated at the next meeting.