What is the difference between a project board and a steering committee?
In most organisations they are the same body under different names: a group with authority over scope, budget and dates that the project reports into. The real difference is origin. A project board is a defined structure with named roles from a method such as PRINCE2. A steering committee is a locally designed forum with membership set by the organisation.
The short version
If someone describes a project board and a steering committee doing different things in the same organisation, ask what each one decides. Nine times out of ten the answer is the same list, and the two names reflect the method the organisation grew up with rather than a structural difference.
| Project board | Steering committee | |
|---|---|---|
| Origin | A formal method, typically PRINCE2 | Local convention; no single defining standard |
| Membership | Defined roles: executive, senior user, senior supplier | Whoever the organisation decides, usually sponsor plus senior stakeholders |
| Scale | Usually a single project | Project or programme; sometimes several projects at once |
| Decision basis | Stage boundaries and tolerance breaches | Whatever the terms of reference set out |
| Reporting into it | Highlight reports, exception reports, end-stage reports | A monthly pack, format set locally |
| Vocabulary | Method vocabulary: stages, tolerances, exceptions | Organisational vocabulary |
What the method roles add
The project board's three roles exist to make sure three interests are represented and cannot be quietly ignored. The executive owns the business case and has the final say. The senior user represents the people who will use the output and are expected to realise the benefits. The senior supplier represents whoever is building it, internal or external.
The value of the structure is that it forces a question most steering committees answer badly: is the user side represented by someone with authority to commit their organisation. A committee of eight senior managers with no named user representative will approve a design and then discover at UAT that nobody agreed to the process change it requires.
The corresponding weakness is rigidity. Three roles do not describe a programme where five business units, two vendors and a shared services function all have a legitimate stake. Steering committees expand to cover that, and then have the opposite problem.
Where the differences actually bite
Size. A project board is small — three to five people — and that is deliberate: a decision-making group larger than about seven stops making decisions and starts taking soundings. Steering committees drift towards a dozen because attendance becomes a status question. Membership on the basis of who might be offended by exclusion is the most reliable way to make a committee slow.
Trigger for involvement. Method-based boards convene at stage boundaries and when tolerances are breached — the escalation is defined by the numbers rather than by judgement. Most steering committees meet monthly regardless, which makes them a standing forum rather than an exception-handling one. That is workable, but it means the committee has to be given something to decide each month or it will fill the time with scrutiny of detail.
Delegation. A method-based structure writes down what the project manager can decide alone. Many locally designed committees never do, and the boundary gets discovered by getting it wrong once. Writing the delegation limits into the terms of reference costs an hour and prevents a recurring argument; the wider structure this sits in is covered in programme governance.
When both exist
On larger programmes they sometimes coexist, and then the distinction is real: project boards sit under a programme steering committee, each owning a project, with the committee owning the programme business case and anything cross-cutting. The design question is which decisions sit at which level, and it needs answering explicitly. Where it is left implicit, decisions travel upwards by default, the committee becomes a queue, and the project boards become status meetings.
The split of accountability between the two levels is the same split described in project manager vs programme manager.
Practical consequences for the reporting
The reporting differs less than the naming suggests. Both want the same things: current status against plan, decisions required with options and a recommendation, risks needing authority above the project, financials, and what is coming next. A board operating under a formal method will additionally expect exception reporting when a tolerance is breached, and end-stage reports at each boundary.
What does not change is the shape of a decision item. Whatever the forum is called, it needs the question, the options with costs, a recommendation and the consequence of not deciding — covered in the steering committee report guide. The SteerCo Deck (PowerPoint) works for either body, since the sections are driven by the decisions rather than by method vocabulary, and the decision log records the output the same way regardless of which name is on the terms of reference.
Other names for the same thing
Programme board, delivery board, governance board, oversight committee, portfolio board, design authority. The first five are usually the same body. A design authority is genuinely different — it holds technical decision rights rather than commercial ones, and it does not own the business case. The way to tell any of them apart is not the name but two questions: what can this group approve without asking anyone else, and who has the final say when it disagrees.
Questions
Can a project have both a board and a steering committee?
On a large programme, yes: project boards under a programme steering committee. On a single project, having both usually means one is a status meeting in disguise.
How many people should be on either?
Small enough to decide. Beyond roughly seven the group starts taking soundings rather than decisions, and the real decision moves to a conversation before the meeting.
Who chairs a steering committee?
The sponsor or programme executive. The project manager presents and answers questions but does not chair the body that is meant to challenge them.
Does the reporting differ between the two?
Not much. A board working to a formal method also expects exception reports on tolerance breaches and end-stage reports at boundaries; the monthly content is largely the same.