Steering Committee: Definition, Membership and Purpose
A steering committee is the standing group that holds decision rights over a project or programme: funding, scope changes above a threshold, escalated risks and go/no-go. It is normally chaired by the sponsor and includes senior business and delivery representation. It meets on a fixed cadence, works from a status pack, and produces recorded decisions.
Who sits on it
A steering committee is a standing body, not a meeting invitation list. Membership is kept small enough that a decision can be taken in the room, and senior enough that the decision holds once everyone leaves it.
| Role | Usually held by | Decision rights |
|---|---|---|
| Chair | Sponsor | Funding, scope change above threshold, go/no-go, closure |
| Senior business owner | Head of the receiving function | Business acceptance, release of business resource, readiness |
| Senior supplier | Delivery or vendor lead | Delivery approach, escalation of supply-side constraints |
| Presenter | Project or programme manager | None. Prepares the pack, records decisions and actions |
| Standing attendees | PMO, finance, architecture, risk | Advisory. Present when the agenda requires them |
Some organisations call the same body a project board, and many delivery teams shorten the name to SteerCo. The label matters less than whether the group can commit money and people without going somewhere else first.
What it works from
A steering committee runs on a pack circulated before the meeting, not on a live walkthrough. The pack normally carries status against plan, a RAG summary, the decisions being asked for, escalated risks and issues, financials against budget, and the dependencies that sit outside the team. The steering committee report guide sets out how those sections are ordered so the ask is visible before the detail. The SteerCo deck is built on the same ordering, and the governance pack generates the status page from the RAID log and action log underneath it.
How it is used
The cadence is typically monthly for a project and monthly or fortnightly for a programme, with a slot held open for exception meetings. Each cycle follows the same shape: the pack goes out several working days ahead, the meeting opens on decisions rather than on progress, and the record produced afterwards lists what was decided, who decided it, what was deferred and what action was assigned to whom.
The committee is also where escalation lands. A risk that the project manager cannot mitigate inside their own authority, a dependency a partner team will not commit to, a forecast overspend beyond tolerance — all of these move upward to this group. How that escalation path is drawn, and what tolerances trigger it, is a matter of programme governance design rather than something the committee decides for itself in session.
Where it goes wrong
- Delegates instead of members. A deputy attends who cannot commit funding, so the decision moves to the next cycle. Four weeks are lost to a diary problem.
- No explicit ask. The pack reports at length and requests nothing. The committee comments, nobody decides, and the same slide returns next month.
- The pack is read in the room. Distribution on the morning of the meeting turns a decision forum into a presentation.
- Membership growth. Every function that asks to be added is added. At fourteen attendees the group discusses; it no longer decides.
- Decisions not written down. Without a decision record with a date and an owner, the same question is reopened later by whoever was absent.
- Risks presented without a request. A red risk with no proposed mitigation and no ask gives the committee nothing to act on.
Related terms
SteerCo — the common contraction of the same body. Project board — the equivalent term in PRINCE2-derived methods. RAG status — the colour coding used on the pack the committee reads. Exception report — the artefact raised when a tolerance is breached between scheduled meetings. Change request — the mechanism by which a scope change reaches the committee for approval.
Questions
How often should a steering committee meet?
Most projects run monthly, with programmes at monthly or fortnightly cadence. The pattern matters more than the interval: a fixed slot with a pack circulated in advance, plus the ability to convene an exception meeting when a tolerance is breached.
Who chairs a steering committee?
The sponsor normally chairs, because the sponsor is accountable for the investment. The project or programme manager prepares the pack and records the outcome but does not chair and does not vote.
What is the difference between a steering committee and a project board?
In practice very little. Project board is the PRINCE2 term and comes with defined roles; steering committee is the more general term. Both are the body that holds decision rights above the project manager.
How large should a steering committee be?
Small enough to decide. Beyond roughly six to eight members with decision rights, sessions tend to turn into briefings, and the real decisions move to side conversations.