What should be on a steering committee agenda?
A steering committee agenda covers: actions and decisions from last time, programme status by exception, decisions required this meeting, risks and issues needing committee attention, financials, and forward look. Decisions come early while attention is highest. Status is taken as read from the pre-read rather than presented slide by slide.
The shape of the agenda
Most steering committees fail in the same way: forty minutes of status presentation, ten minutes of questions, and the decisions taken in the last four minutes with half the room already thinking about the next meeting. Reversing that order is the single change that improves most committees.
| Item | Purpose | Typical time |
|---|---|---|
| Actions and decisions from last meeting | Confirm what was agreed happened. Anything outstanding gets a date. | 5 min |
| Status by exception | Overall RAG, what changed since last time, what the committee did not expect. Not a walkthrough. | 10 min |
| Decisions required | Each with options, a recommendation and the consequence of not deciding today. | 25-30 min |
| Risks and issues for the committee | Only those needing committee authority, money or escalation outside the programme. | 10 min |
| Financials | Spend to date, forecast at completion, variance and its cause. | 5 min |
| Forward look | Next major milestones and what is coming to the committee next time. | 5 min |
| Any other business | Named in advance where possible. | 5 min |
That is roughly seventy minutes, which is what a monthly committee usually has. The proportions matter more than the exact numbers: the largest block belongs to the decisions.
Decisions first
A decision item needs four things on the page before the meeting starts. What is being decided, stated as a question the committee can answer. The options, with the cost and consequence of each. A recommendation from the programme, because a committee asked to choose without one will usually defer. And the effect of not deciding today — which date moves, which cost is incurred, which work stops.
The fourth is the one that gets left out, and it is the one that converts a discussion into a decision. Without it, deferral looks free. The way each decision is written up afterwards feeds the decision log, which is the record anybody later asks for; the decision log and dependency matrix covers both artefacts in the format they usually get presented in.
Status by exception
The committee has the pack. Presenting the pack aloud spends the most expensive twenty minutes in the organisation's month reading to people who can read. Status at the meeting covers the overall position in a sentence, what changed since last time, and anything the committee would not have predicted from the last pack. Questions on the detail are then taken against the pre-read.
This only works if the pre-read genuinely goes out in advance — usually three to five working days — and if the chair is willing to say that a question is answered on page six. A committee that never reads the pre-read will not start because the agenda says so; it starts when the meeting stops repeating the pre-read. The content of that pack is covered in the steering committee report guide.
What does not belong on the agenda
- Technical design discussion. Architecture decisions belong in a design authority, with the funding or risk consequence brought to the committee if there is one.
- Working-level problem solving. If four people in the room need thirty minutes to resolve something, that is a separate meeting, and the committee should agree to hold it rather than hold it now.
- Every risk in the log. The committee sees items needing its authority. The rest stay in the RAID log.
- Round-the-table updates from each workstream. This is what expands a governance meeting into two hours of reporting nobody acts on.
- Decisions the programme is empowered to take. Bringing them anyway is either a request for cover or a sign the delegation limits are not written down.
Standing items and variable items
Actions, status, risks, financials and forward look are standing — they appear every time, in the same order. Decisions are variable, and their number sets the length of the meeting. Some committees add a rotating deep dive: one workstream or one theme gets fifteen minutes each month, which keeps the committee informed at depth without turning every meeting into a full review.
Phase gates are the other variable item. A go/no-go decision, a stage gate or a business case reapproval usually takes a meeting of its own, or at least a substantially rearranged agenda, because the evidence set is larger and the decision is not reversible in the same way.
Minutes, actions and decisions
Three separate records come out of the meeting, and collapsing them into one narrative document is why decisions get relitigated. Actions go to the action log with an owner and a date. Decisions go to the decision log with the date, the decision, who took it and what it was based on. Minutes record attendance, the items covered and anything material said. The decision log is the one that gets read a year later, usually by someone asking why an approach was chosen.
The SteerCo Deck (PowerPoint) is structured in this order, with the decisions section ahead of the detail, and the Program Governance Deck Bundle adds the risk, decision and dependency packs that sit behind it. How the committee fits with the other boards on a programme is covered in programme governance.
Questions
How long should a steering committee meeting be?
Sixty to ninety minutes monthly is the common range. Meetings that regularly run to two hours are usually carrying working-level discussion that belongs elsewhere.
When should the pre-read go out?
Three to five working days before, so it can be read and questions raised in advance. A pack circulated the night before will be read in the meeting, which defeats the agenda.
What if there are no decisions to take this month?
Then the meeting can be short, or in some governance models skipped. A committee that meets monthly with nothing to decide tends to invent scrutiny to fill the time.
Who chairs it?
Normally the sponsor or programme executive. The project manager presents and answers, but chairing your own governance meeting removes the challenge the committee exists to provide.