Steering Committee vs Project Board: What's the Difference?
A project board is a defined body — executive, senior user and senior supplier — accountable for a project and authorised to approve stages and exceptions. A steering committee is a looser term for a senior forum that oversees a project or programme, with membership and decision rights set by its terms of reference. One is a role structure; the other is a meeting.
Side by side
Both are the place a delivery lead goes when a decision is beyond their authority. The difference is that a project board's composition and decision rights are defined by the method, while a steering committee's are defined by whoever wrote the terms of reference — which is why two organisations can use the same word for very different forums.
| Aspect | Steering committee | Project board |
|---|---|---|
| Origin | Common practice, method-agnostic | Defined in PRINCE2 |
| Membership | Sponsor plus senior stakeholders, often wide | Executive, senior user, senior supplier |
| Accountability | Varies; sometimes advisory only | Accountable for the success of the project |
| Decision rights | Whatever the terms of reference state | Defined: authorises stages, approves exceptions and changes |
| Typical size | Six to fifteen attendees | Three roles, occasionally shared between more people |
| Cadence | Monthly, or at major gates | At stage boundaries and on exception |
| Standing inputs | Status pack, decisions requested, risks, financials | Highlight reports, end stage reports, exception reports |
| Escalates to | Sponsor, programme board or portfolio governance | Corporate or programme management |
| Common failure | Attendance without authority | Roles held by people without the time for them |
| Applies to | Projects and programmes | A single project; a programme board sits above |
When you need a steering committee
You need a steering committee when a project cuts across enough parts of an organisation that no single executive can make its decisions alone. The typical case is a cross-functional programme: finance, operations, IT and a business unit all have to move together, and each has budget and people at stake.
The committee's value comes entirely from who sits on it. A forum of delegates who have to check with their manager before agreeing anything is not a decision-making body; it is a briefing. Before setting one up, the question worth answering is which decisions this group will actually take, and whether the people invited can take them in the room.
The other design choice is the pack. A committee meeting monthly for an hour can absorb perhaps four decisions and a status summary. Everything else is reading material. Putting the decisions required at the front, each with options and a recommendation, is what separates a committee that decides from one that discusses. Our SteerCo deck is built around that ordering, and the steering committee report guide covers what goes on the one page that precedes it.
When you need a project board
You need a project board where PRINCE2 is in use, or where you want the specific clarity its structure gives. The three roles exist to make sure three interests are represented and named: the business interest that pays for it and owns the case, the user interest that will live with the result, and the supplier interest that provides the resources to build it.
That structure answers a question generic committees usually fudge, which is who breaks a tie. The executive holds the casting vote and owns the business case. The senior user speaks for the people whose processes change. The senior supplier speaks for delivery capability and feasibility. When those three are named individuals with the authority their role implies, escalation has somewhere to land.
The board's rhythm is also different. It does not meet weekly to review progress; it meets at stage boundaries to authorise the next stage, and on exception when tolerance is forecast to be breached. Between those points it reads highlight reports. That deliberately keeps routine reporting out of a decision forum, and it works only if the reporting is good enough to be trusted unread — one reason a maintained decision log matters more than minutes.
When you need both
Large programmes commonly run both, at different levels. Each project inside the programme has a board with its three roles, making project-level decisions within delegated tolerances. Above them, a programme steering committee handles cross-project trade-offs: shared resources, sequencing, dependencies between workstreams and anything that moves the overall business case.
This only works if the split of decision rights is written down. The usual arrangement is that a project board decides anything within its tolerances, and anything beyond them goes to the committee. Without explicit tolerances, everything either escalates — and the committee becomes a bottleneck — or nothing does, and the committee finds out late. Programme governance covers how to set those boundaries so the structure does not consume the delivery it exists to oversee.
The other reason to run both is representation. A three-role board is efficient but narrow. A wider committee gives affected departments visibility without giving all of them a vote, which is often the practical compromise in an organisation where a dozen functions feel entitled to attend.
The overlap
In everyday use the two terms are largely interchangeable, and most organisations run something in between: a chair who acts as executive in all but name, a handful of senior stakeholders, a monthly slot and a pack. Calling it a steering committee or a project board changes nothing about how it behaves.
The overlap in function is close to total. Both authorise spend within limits. Both take escalations. Both accept or reject changes that move scope, cost or schedule. Both are the last stop before something goes to corporate or portfolio level. Both live or die on whether the members read the pack.
Where the distinction earns its keep is under pressure. When a decision is contested and expensive, a PRINCE2 board has a defined answer to the question of who decides, and a defined route for exceptions. A steering committee has whatever its terms of reference say, which in many organisations is nothing at all. If you inherit a committee without terms of reference, writing them — membership, quorum, decision rights, escalation route, cadence — is usually a better use of an hour than redesigning the pack. Governance reporting can then be built to match, which is what the governance deck bundle is for.
Questions
Is a steering committee the same as a project board?
Functionally they usually behave the same way. A project board is a defined PRINCE2 structure with three named roles and specific authority; a steering committee is a general term whose composition and powers depend on its terms of reference.
Who chairs a steering committee?
Normally the sponsor or the executive who owns the budget and the business case. If the chair cannot approve spend or resolve a dispute between departments, the forum will struggle to decide anything.
How large should the group be?
Small enough that everyone present has a reason to be there. Large committees tend to spend their time briefing rather than deciding, and quorum becomes harder to reach as membership grows.
What should the meeting actually cover?
Decisions required, escalated risks and issues, financial position, and confirmation of status. Detailed progress belongs in the report circulated beforehand rather than in the room.
Does a programme need a separate board from its projects?
Usually. Project boards decide within their tolerances; a programme board or steering committee handles cross-project trade-offs and anything that changes the programme business case.