The steering committee (in Italian comitato direttivo or comitato guida) is the group of people (usually senior executives) that exercises strategic oversight of a project, programme or initiative. It sets priorities, decides on resources and scope when an issue exceeds the authority of the person leading it, and receives from them, at regular intervals, progress, issues and required actions.
Most guides list what the committee does: steer, monitor, support. Here, though, we start from the problem that makes it necessary. The project manager is accountable for the outcome, but budget, people and priorities belong to other departments, and when two functions compete for the same resource, neither can overrule the other. The steering committee is where that conflict is settled by a decision rather than a favour, which is why it belongs to the organisational structure even before it belongs to project management.
The steering committee in three key points
Governs the project, does not manage it
The committee decides priorities, resources, scope and blockers. Execution stays with the project manager.
Written mandate, few members, decisions recorded
A committee that works has a written mandate, a small number of members with real authority, and meetings that produce decisions on the record.
Issues escalate by threshold, not by feeling
What reaches the committee is determined in advance by set thresholds, not by the perception of whoever is living the problem.
Steering committee: meaning and translation
The meaning of steering committee lies in the English verb to steer: rendered literally in Italian, it becomes comitato guida or comitato sterzante. Figuratively, the sense is comitato direttivo, a management committee (Alma Laboris). The distinction between steering and managing is crucial. Managing means getting the work done; steering means setting the direction and removing whatever stands in its way (Alma Laboris). A committee that merely receives reports has the name of a steering committee and the function of a hearing.
What the steering committee does
It decides on scope (adding, removing or stopping activities), on budget and resources beyond the project managerโs thresholds, on priorities between conflicting projects and on risks that exceed the agreed threshold. It does not decide how the work is done, does not redo the plan and does not replace the project manager in dealings with the team.
Not every project needs one. The Ohio guide makes it mandatory for projects classified as major and strongly recommends it when the cost reaches one million dollars, the duration exceeds six months or several organisational units are involved (Ohio Office of Budget and Management). In an Italian company the thresholds will differ, but the criterion stands: more functions involved and more time required call for a place in which to decide.
Steering committee members: who sits on it
Steering committee members are people with authority over the project’s resources and a stake in its outcomes: the sponsor, who normally chairs, the heads of the areas involved, a finance representative when the budget is significant, subject-matter experts or stakeholder representatives and, at times, external and independent voices (Ohio Office of Budget and Management). Sources agree neither on the number nor on the project manager:
How many members, and where the project manager sits
Three sources, three recommendations that converge on a small committee.
Ohio Office of Budget and Management
3 to 6
Up to 10, but with highly structured meetings.
Project manager
Not a member: reports and answers questions.
Dilitrust
5 to 9
Project manager
One of the five essential roles, tasked with presenting updates.
Institute of Directors
Around six
Project manager
Not specified.
The number matters less than the criterion: every member must be able to decide for the area they represent; otherwise they are an observer. On the project manager, the first option holds up best: they propose and report without a vote, so the person executing is not also the person authorising themselves. A RACI matrix makes explicit who proposes, who decides and who is informed for each type of decision.
Steering committee and other bodies: the differences
The steering committee is often confused with other bodies, which differ in the level of decision and in duration:
The steering committee and other bodies
| Body | What it decides | Duration |
|---|---|---|
| Steering committee | Priorities, resources and scope of a project or programme | Same as the project |
| Operational committeeworking committee | How to carry out the work, day by day | Same as the project |
| Management committee | The day-to-day running of the business | Permanent |
| Board of Directors | The companyโs strategy, structure and accountabilities | Permanent |
| Advisory board | Non-binding advice on specific topics | Variable |
The Board of Directors is accountable for the company, not for the individual project: it delegates the decision to the committee, which reports back if the matter exceeds its delegation. The advisory board advises and does not bind. When a major project ends up before the management committee, it becomes one item among many on the agenda of an already overloaded body.
The Bliss view
A committee is judged by its decisions
For us, the steering committee is first and foremost an allocation of decision rights. The project manager is accountable for the outcome but rarely has the authority to change other departments’ budgets, scope or priorities: the committee exists to bridge this gap and is judged by how well it does so.
A ten-minute test: take the minutes of the last three meetings and count the decisions recorded. If updates outnumber decisions, the committee is a periodic hearing, and every decision that is needed waits for the next meeting.
The remedy is a one-page document: the mandate. A study of four organisations published in the Project Management Journal describes a steering committee through five elements: configuration, authority, responsibilities, decision-making processes and organisation (Lechler and Cohen, 2009). Translated into questions:
- Who sits on it
- How far its authority extends
- What it is accountable for
- How it decides
- How it is organised
Without written answers, every meeting starts again by debating what the committee is allowed to do. The other half of the problem is the sponsor: if the role is honorary, the committee has no one to lead it and decisions pile up.
The Bliss Agency perspective
How to organise the steering committee meeting
A steering committee meeting exists to take decisions, and should be prepared accordingly. For projects of six months or more, the Ohio guide indicates a fortnightly or monthly cadence, with dates fixed in advance, the agenda circulated several days beforehand and minutes issued within a week; Dilitrust recommends that materials arrive at least forty-eight hours ahead. These are good-practice guidelines, not rules: the right cadence depends on the pace of the project and on how many decisions build up between one meeting and the next.
What separates a useful meeting from a status update is the quality of the decisions on the table: each one needs the alternatives, the project manager’s recommendation and the consequences of each option. If there is nothing to decide, the meeting can be cancelled at no cost; if decisions arrive unprepared, the committee defers them. This is why the decision log matters: it records who decided what, and on what information, and makes it possible to reconstruct choices months later, even when the people have changed. The indicators the committee decides on are the business KPIs applied to the project, plus risk indicators such as KRIs.
Business escalation: when an issue goes up to the committee
Business escalation is the step by which an issue the project manager cannot resolve goes up to someone who can. The opposite risk to a committee that intervenes too much is one that arrives too late, once the delay is entrenched: to avoid this, thresholds are agreed in advance, so escalation does not depend on the temperament of whoever is running the project. An example, to be adapted:
What goes up to the committee, and when
Thresholds are set in the mandate, before the problem arises.
| Variance | The project manager decides | Goes up to the committee when |
|---|---|---|
| Timing | Delays recoverable within the phase | The delay moves a deadline agreed with third parties |
| Costs | Variances within the assigned tolerance | The margin is exceeded or new budget is needed |
| Scope | Changes that do not alter outcome or cost | Any addition or removal affecting objective or cost |
| Risks | Risks below the alert threshold | A risk exceeds the threshold or has materialised |
| Cross-functional conflicts | Agreements within their own resources | The conflict involves resources or priorities of other departments |
The right-hand column is the part worth writing into the mandate: without it, every variance becomes a matter for negotiation the moment it arises.
The most useful rule sits outside the table: the committee should not discover a serious problem in the meeting. The Ohio guide asks sponsor and project manager not to use the meeting to announce delays or budget overruns; the project manager informs the sponsor as soon as a threshold approaches. An indicator-based alert system makes escalation less subjective, as happens with risk management in every area of the business.
Project governance and portfolio governance
Project governance is the set of rules by which a project is decided, authorised and controlled, and the steering committee is its central body. It rests on a sponsor accountable for the expected benefits, a committee with a written mandate and a project manager with a clear scope of authority.
Portfolio governance, or project portfolio governance, addresses a different problem: when there are many projects, the constraint becomes shared resources. The committee no longer steers a single project but chooses which to launch, which to stop and which to prioritise, based on their contribution to the companyโs objectives. Without an explicit choice, resources go to the project that pushes hardest, not to the one that matters most.

