A steering committee is a small group of senior decision makers who are accountable for the outcome of a project or program and who hold the authority to fund it, change its scope, or shut it down. It does not manage the work. It meets on a fixed cadence, most often monthly, to make the calls the project manager has no authority to make alone: releasing money, settling conflicts between departments, accepting risk, and confirming the project still earns its place. In most companies you will hear it called the SteerCo.
The distinction that matters, and the one most organizations lose within about three meetings, is between a decision-making body and an audience. A steering committee that receives a status update and nods is not governing anything. It is watching. The test is simple: if the last four meetings produced no decision that changed the project, you do not have a steering committee.
Key takeaways
- A steering committee owns four decisions: approve the baseline, approve changes above an agreed threshold, resolve escalations the project manager cannot resolve, and decide whether the project continues.
- SteerCo is simply the common workplace abbreviation of "steering committee." It carries no separate meaning.
- Five to eight members is the working range. Below five you lack the authority to settle cross-functional disputes. Above eight the meeting becomes a briefing.
- Monthly is the default cadence for a project running longer than a quarter, with additional meetings pinned to stage gates rather than to the calendar.
- The project manager attends every meeting but is not a member and does not vote. The sponsor chairs it.
- PRINCE2 calls the same body the project board, with three defined roles: Executive, Senior User, and Senior Supplier. The Executive is the role most organizations call the sponsor.
- Steering committees decay into status meetings when the agenda leads with progress instead of leading with the decisions required.
What is a steering committee?
A steering committee is a governance body of senior stakeholders that provides direction and holds decision authority over a project, a program, or a major initiative. Its members are drawn from the parts of the business the project affects, they are senior enough to commit their own function's money and people, and they are collectively accountable for whether the investment pays off.
Three things separate it from every other meeting on the project calendar. First, membership is based on authority rather than interest. If a person on the committee has to leave the room to get approval for something, they are the wrong person. Second, the committee is accountable for the business case, not for the delivery plan. The project manager owns the plan. The committee owns the question of whether the plan is still worth executing. Third, it has the power to stop the work. A body that cannot cancel a project cannot govern one.
That last power is the one that gets used least and matters most. A steering committee whose only available answer is "continue" provides no control at all, because a control that always returns the same value is not measuring anything. If your organization has never killed a project at a steering committee, that is a finding about your governance, not a compliment about your project selection.
What does SteerCo mean?
SteerCo is an abbreviation of "steering committee." It is spoken shorthand, common in consulting, financial services, and large delivery organizations, and it means exactly the same thing as the full phrase. You will also see "steering group," "steering board," and "project board" used for the same body. None of these signal a different structure by themselves, though PRINCE2 gives "project board" a specific and formal definition that the others do not carry.
A "SteerCo meeting" is therefore just the meeting of the steering committee. There is no separate ceremony hiding behind the abbreviation, and treating it as a distinct thing is a common source of confusion for people joining a company where the term is standard.
Steering committee roles and responsibilities
A steering committee is built from roles, not from job titles. The same person can hold two roles on a small project. On a large one, each role is a separate seat, and the seat exists because the decision it represents has to be made by someone with authority over that domain.
| Role | Who typically fills it | What they are on the committee to decide |
|---|---|---|
| Chair / Sponsor | The executive whose budget funds the project | Whether the project continues, and whether the business case still holds. Breaks ties. Owns the outcome. |
| Senior user | Leader of the function that will use the output | Whether the scope still delivers the benefit, and whether the business is ready to absorb the change. |
| Senior supplier | Delivery, engineering, or vendor leader | Whether the solution is technically sound and whether the delivery capacity actually exists. |
| Finance representative | Finance business partner or controller | Whether funding is released, and whether the forecast reconciles to the ledger. |
| PMO lead | Head of the PMO or portfolio manager | Whether the project's demands on shared people and money are consistent with the rest of the portfolio. |
| Project manager (attends, not a member) | The PM | Nothing. Presents the position, tables the decisions, records the outcome, and does not vote. |
| Secretary | PMO analyst | Nothing. Circulates the pack in advance, records decisions and owners, tracks actions to closure. |
The seat that is missed most often is finance. A steering committee that approves a scope change without a finance representative in the room has approved a cost it cannot see, and the reconciliation happens three months later when someone notices the forecast moved. The seat that is added most often without cause is a functional director with no exposure to the project, invited for political cover. That seat costs the meeting its speed.
The project manager's position deserves care. They attend, they present, they answer, and they leave with the decisions. They are not a member because the committee's job includes judging whether the plan the PM authored is still credible, and you do not put the author on the panel. This is the same reason a PMO analyst prepares the pack rather than the delivery team preparing it: the numbers should arrive from someone with no stake in how they read.
What a steering committee actually decides
Write the decision rights down before the first meeting, in the charter, with numbers. A committee that has to argue about whether something is in its remit spends the meeting on procedure. The thresholds below are illustrative, not a standard. Set your own against the size of your projects.
| Decision | Project manager | Steering committee | Portfolio board |
|---|---|---|---|
| Change within tolerance (say, under 5% of budget, no date move) | Decides | Informed | Not involved |
| Change above tolerance, funded from contingency | Recommends | Decides | Informed |
| Change requiring new money or a new end date | Recommends | Recommends | Decides |
| Accepting a risk with material residual exposure | Escalates | Decides | Informed if it crosses projects |
| Passing a stage gate | Requests | Decides | Informed |
| Stopping the project | Recommends | Decides or recommends | Confirms, and reallocates the money |
| Reprioritizing this project against others | Not involved | Not involved | Decides |
Notice the last row. Ranking one project against another is not a steering committee decision, because a steering committee only sees one project and will always conclude that its project matters. That comparison belongs to the portfolio review meeting, where the same money is being contested by everything else in flight. A steering committee that starts arguing about priority relative to other work has drifted out of its lane, and the usual symptom is a sponsor lobbying for people who are committed elsewhere. Keeping those two forums separate is one of the load-bearing ideas in project portfolio governance.
How often should a steering committee meet?
Monthly is the right default for a project running longer than a quarter. Add meetings at stage gates, whenever they fall, because a gate is a decision and the committee exists to make decisions. Move to every two weeks when the project is in a recovery period, is inside its highest-risk phase, or is spending faster than it is delivering. Drop to quarterly only when the project is genuinely in a low-change window, and expect to regret it.
Cadence should follow the rate at which decisions arrive, not the calendar. The practical test: if the average meeting has fewer than two real decisions to make, you are meeting too often and the agenda will fill with status to justify the hour. If decisions are being made over email between meetings because they cannot wait, you are meeting too rarely. Both failures are visible in the minutes, which is one reason the minutes should record decisions rather than discussion.
What should be on a steering committee agenda?
Lead with the decisions. A pack that opens with a progress summary trains the committee to spend its energy on the first thing it sees, and progress is the least useful thing they can look at, because they cannot change it. Sixty minutes, structured like this, and the pack circulated at least two working days ahead so nobody is reading in the room:
| Item | Time | Purpose |
|---|---|---|
| Decisions required | 25 min | Each with a recommendation, options considered, and cost of delay if deferred. |
| Escalations | 10 min | Only items the PM cannot resolve. Named owner and date leave the room with each. |
| Risks and issues above the escalation threshold | 10 min | Movement since last meeting, not the whole register. The full register lives in the project risk register. |
| Exceptions to plan, budget, and benefit | 10 min | Variance only. Where forecast has moved and why. |
| Actions from last meeting | 5 min | Closed, open, overdue. Nothing else. |
There is no status item. Status goes in the pack and is read before the meeting. The moment you give status a slot on the agenda, it takes the whole hour, because presenting progress is comfortable for everyone in the room and making decisions is not. If your committee needs a visual of where the project stands, put it on a standing project portfolio dashboard that they can look at any day of the month.
Steering committee vs project board vs portfolio review board
| Steering committee | PRINCE2 project board | Portfolio review board | |
|---|---|---|---|
| Scope | One project or program | One project | All projects competing for the same money and people |
| Composition | Defined locally. Sponsor plus affected senior leaders | Fixed: Executive, Senior User, Senior Supplier | Executives who own the strategy and the budget |
| Core question | Should this project continue as planned? | Is the business case still viable, and can the next stage be authorized? | Is this still the right set of projects to be funding? |
| Cadence | Monthly plus gates | At the end of each management stage, plus exceptions | Monthly or quarterly, on the funding cycle |
| Can it start a project? | Rarely. Usually receives an approved project | Authorizes initiation and each stage | Yes. This is where projects enter through the intake process |
PRINCE2 is worth understanding even if you never use it, because it is unusually precise about a thing most companies leave vague. It requires every project to have a project board, and it fixes the board's membership at three roles. The Executive holds ultimate accountability and represents the business interest. The Senior User represents the people who will use what the project produces, and is held accountable for specifying and then actually realizing the benefits. The Senior Supplier represents the people who build it and is accountable for the technical integrity of the solution. In organizations that do not use PRINCE2, the Executive role is nearly always the person called the project sponsor.
The value of that model is not the vocabulary. It is that it forces the question "who on this committee speaks for the users, and will they still be here when the benefits are supposed to arrive?" A steering committee with no senior user is a committee that will approve a technically excellent system nobody adopts.
Who should be on a steering committee?
Five to eight people, each holding delegated authority over a domain the project touches, plus the project manager and a secretary who are present but not members. Add a member only when you can name a decision that cannot be made without them. Remove a member when you cannot.
Two practical rules keep the size honest. First, no delegates: if a member consistently sends a deputy, the deputy either has the authority (in which case make them the member) or does not (in which case the seat is empty and the decision will be re-litigated later). Second, no observers. People who attend to stay informed should receive the pack and the minutes, not a seat, because a room with silent observers changes how the members speak.
Why steering committees turn into status meetings
The decay follows a pattern, and it is predictable enough that you can design against it.
It begins when the project manager, wanting to demonstrate control, opens with a comprehensive progress report. The committee, having nothing to decide, engages with the only thing available and asks questions about the schedule. The PM, now rewarded for detail, brings more detail next month. Within a quarter the pack is forty slides, the meeting is a performance, and real decisions are being taken in side conversations with the sponsor because the formal forum is too slow. Everyone continues attending because the meeting is in the calendar.
Three countermeasures work. Put decisions first on the agenda and keep status out of the room entirely. Require every decision item to arrive with a written recommendation from the project manager, so the committee is confirming or overturning a position rather than inventing one from scratch. And publish the minutes as a decision log: date, decision, owner, rationale, and a one-line note of what was rejected. A committee that reads its own decision log every month notices when the log is empty.
The fourth countermeasure is harder and more effective: retire the committee when the project ends. Standing committees that outlive their project become forums looking for content, and the content they find is status.
Writing a steering committee charter
The charter, also called terms of reference, is one page. It exists so that a dispute about the committee's remit can be settled by reading rather than by seniority. Cover seven things:
- Purpose. One sentence naming the project and the outcome the committee is accountable for.
- Members. By role and by name, with the chair identified. Delegates named explicitly or prohibited explicitly.
- Decision rights. The thresholds. What the PM decides, what the committee decides, what escalates above it.
- Quorum and decision method. How many members, and whether the chair decides after discussion or the committee votes. Most work better with the chair deciding, because consensus bodies avoid stopping projects.
- Cadence. Standing frequency plus the gate-triggered meetings.
- Inputs. What the pack contains and when it is circulated.
- Duration. The date the committee dissolves, which is normally the closure of the project and the handover of the benefit tracking to whoever owns benefits realization management.
If your organization runs many projects, the charter should be a template the PMO issues rather than a document each project invents. That is the sort of thing a functioning project management office exists to standardize, and it is covered in more depth alongside the other governance artifacts in the PMO charter.
Frequently asked questions
What is the purpose of a steering committee?
The purpose of a steering committee is to make the decisions a project manager has no authority to make: releasing funding, approving changes beyond agreed tolerances, resolving escalations that cross departments, accepting material risk, and deciding whether the project continues. It provides direction and holds the sponsor's authority in a forum where the affected parts of the business are represented.
Who chairs the steering committee?
The project sponsor chairs it. The sponsor is the executive whose budget funds the work and who is accountable for the business case, so they are the person who must own the decision when the committee cannot agree. A neutral chair sounds fair in theory and produces indecision in practice, because nobody in the room is accountable for choosing.
What is the difference between a steering committee and a project sponsor?
The sponsor is one person, accountable for the project's business case and outcome. The steering committee is the group the sponsor chairs, which brings the other affected functions into the decision. A project can have a sponsor without a steering committee. It cannot have a steering committee without a sponsor, because the committee has no accountable owner otherwise.
Does every project need a steering committee?
No. A project needs a steering committee when its decisions cross organizational boundaries, when it consumes people or money that other functions control, or when its failure would be material to the business. A project inside one department, funded by that department, with no shared resources, needs a sponsor and nothing more. Convening a committee for it adds delay and no control.
What is a steering group?
A steering group is the same body as a steering committee. The terms are interchangeable in ordinary use, with "steering group" more common in UK and European organizations and "steering committee" more common in the US. Neither term implies a different structure, membership, or set of powers.
How many people should be on a steering committee?
Five to eight members. Fewer than five and you usually lack authority over one of the functions the project depends on, so decisions get made and then reopened. More than eight and the meeting shifts from decision making to briefing, because there is no longer time for each member to speak on each item within an hour.
Is the project manager a member of the steering committee?
The project manager attends every meeting, presents the position, and records the decisions, but is not a voting member. The committee's function includes judging whether the project manager's plan and forecast remain credible, and placing the author of that plan on the panel that judges it removes the independence the forum is there to provide.
What is the difference between a steering committee and a working group?
A steering committee decides and directs. A working group produces. The committee is senior, meets monthly, and holds decision authority. A working group is operational, meets as often as the work requires, and holds no authority beyond producing the analysis or deliverable it was formed to produce. Working groups frequently report into a steering committee.
Where the steering committee fits
One project, one steering committee, meeting monthly to decide whether the plan still holds. Above it, one portfolio board, deciding whether this project deserves the money at all against everything else in flight. Around both, a set of written decision rights that keeps them from doing each other's job. That structure is the substance of a project governance framework, and the reason it is worth writing down is that in its absence the two forums merge, the merged forum defaults to status, and the projects that should have been stopped continue until the money runs out.
If you are standing one up for the first time, start with the decision rights table and the charter. Get the four decisions on paper, get finance in the room, and make the first meeting's agenda a set of choices rather than a report. The rest of the practice follows from that, and the failure modes you will meet are the ones described in PMO best practices.