The steering committee (COPIL in French, from comité de pilotage) is the governance body of a project: the place where decision-makers approve the direction, arbitrate trade-offs and remove the blockers the team cannot remove on its own. Well organised, it is the difference between a project that drifts in silence and one that corrects its course in time. This guide gives the definition of a steering committee, its composition, what sets it apart from the project committee, a model agenda, the indicators to present, a minutes template and the mistakes to avoid.
Steering committee: definition and purpose
A steering committee is a decision-making body that meets at regular intervals for the whole duration of a project or programme. It does not do the work: it steers. It brings together the sponsor, the business owner, the delivery lead and the heads of the business units concerned, around the project manager who prepares and runs the session. Its purpose fits in one sentence: to decide what the project team has no authority to decide alone.
- What it decides: the roadmap and its milestones, the budget and its reallocations, scope / cost / deadline trade-offs, end-of-phase go/no-go, major changes.
- What it does not do: track tasks one by one, solve technical problems, replace the project manager in day-to-day steering.
- What it produces: a dated decision log, with an owner and a deadline for every action.
Who sits on the steering committee, and what for
An effective steering committee has five to eight members. Every seat corresponds to a real decision-making power: observers dilute the debate and lengthen the session. The table below describes the classic composition of a project steering committee and each member’s responsibility during the meeting.
| Role | Who | Responsibility in the steering committee |
|---|---|---|
| Sponsor | Director or executive board member | Chairs the session, owns the objectives, arbitrates as a last resort, releases budget and resources |
| Business owner | Business lead for the need | Confirms the deliverables meet the need, prioritises change requests |
| Delivery lead | Head of delivery (IT department, supplier) | Commits on feasibility, deadlines and effort, escalates technical risks |
| Project manager | Operational lead | Prepares the pack, presents progress and indicators, frames the decisions to take, writes the minutes |
| Business unit heads | Departments impacted (finance, HR, operations…) | Confirm their teams’ availability, validate the impacts on their scope |
| PMO (optional) | Project management office | Guarantees the method, consolidates the indicators, follows decisions from one session to the next |
Steering committee, project committee, executive committee: what is the difference?
The three bodies are often confused. Yet they do not deal with the same topics, at the same pace, or with the same people. The project committee moves the work forward; the steering committee decides; the executive committee arbitrates between projects.
| Body | Frequency | Participants | Decisions |
|---|---|---|---|
| Project committee | Weekly | Project manager, team, business referents | Work organisation, resolution of blocking points, preparation of topics to escalate |
| Steering committee | Monthly or at each milestone | Sponsor, business owner, delivery lead, project manager, business unit heads | Scope / cost / deadline trade-offs, go/no-go, major changes, budget reallocations |
| Executive committee | Monthly or quarterly | General management, department heads | Priorities between projects, project launch and stop, overall portfolio envelope |
Why steering management is key to project success
A project rarely fails for lack of skills. It fails because a decision was taken too late, or never. Steering management through a committee is the mechanism that forces that decision on a date set in advance, in front of the people who have the power to take it. Its concrete effects:
- It puts a deadline on arbitration: a disagreement between the business and IT cannot drag on for more than a month.
- It makes drift visible early: a budget overrun presented every month gets handled; discovered at the end of the project, it is simply suffered.
- It commits the sponsor: an executive who approved a milestone in session then defends its consequences.
- It protects the project manager: hard decisions (postponement, scope reduction) are carried by the body, not by one person.
- It leaves a trace: the decision log is the project’s memory and prevents debates already settled from being reopened.
Model steering committee agenda
A session lasts one hour to ninety minutes. The steering committee agenda always follows the same sequence, from the most summarised to the most binding, and ends with decisions and actions. Send it with the meeting pack at least 48 hours in advance.
- Project weather (5 min): overall green, amber or red status, and trend since the previous session.
- Progress and milestones (10 min): milestones passed, milestones ahead, gap between the baseline schedule and the current schedule.
- Budget and resources (10 min): spent, committed, remaining work, estimate at completion, team workload.
- Risks and blocking points (10 min): the three to five major risks, how they evolved, the blockers the committee must remove.
- Decisions to take (20 min): each point framed as a question, with the options, their impact and a recommendation.
- Actions and next steps (5 min): review of the previous session’s actions, new actions with owner and deadline, date of the next committee.
The 5 indicators to present
A steering committee does not read a 300-line schedule. It needs five indicators, always the same from one session to the next, to see the trend at a glance:
- Physical progress: percentage of deliverables completed against the baseline, not the percentage of time elapsed.
- Schedule variance: number of days of slippage on major milestones and on the end date, with the main cause.
- Budget consumption: spent and committed against the approved budget, and estimated cost at completion.
- Major risks: number of critical open risks, and how they evolved since the previous session.
- Pending decisions and actions: decisions not taken and overdue actions, which measure the responsiveness of the governance itself.
Steering committee minutes: the template
Steering committee minutes are not a transcript. They are a one- to two-page decision log, circulated within 48 hours, that serves as the starting point of the next session. The template that lasts has six sections:
- Header: project, date, attendees present and excused, author.
- Weather and summary: overall status in three lines, key facts since the last session.
- Indicators: the five indicators above, with their value and trend.
- Decisions: one numbered line per decision, with the date, the decision-maker and the impact on the plan (scope, budget, deadline).
- Actions: owner, deadline, status, distinguishing new actions from carried-over ones.
- Next session: date, topics already identified, decisions to prepare.
Preparing a steering committee in 5 steps
The quality of a steering committee is decided before the session. Five steps, to run through in the preceding week:
- Update the data: task progress, milestones, budget spent, risk register. One outdated indicator discredits the whole presentation.
- Identify the decisions to take: list what is blocking, and for each point prepare the options with their impacts and a reasoned recommendation.
- Meet the sponsor beforehand: no bad news should be discovered in session. The sponsor arrives knowing the sensitive points.
- Build the meeting pack: agenda, dashboard, decision sheets. Ten slides maximum, circulated 48 hours in advance.
- Frame the facilitation: time each point, assign who presents what, decide who takes notes and who records decisions live.
Common steering committee mistakes
Steering committees that add nothing almost always make one of these mistakes:
- The committee turns into a detailed review: tasks are walked through one by one, and the session ends without reaching the decisions. Detail belongs to the project committee.
- No decision is recorded: people discuss, “take note”, but nothing is written down with a name and a date. The topic comes back at the next session.
- The sponsor is absent or represented: without them, the committee cannot arbitrate. Better to postpone the session than to decide without authority.
- The indicators change at every session: without continuity, no trend can be read.
- Bad news is dressed up: a project stays green until it turns red. The committee exists precisely to deal with amber.
- The session overruns: without timing, the first points consume all the time, and decisions fall through the cracks.
- Decisions are not applied: nobody rereads the previous log, and actions pile up without an owner.
The steering committee in FoxPlan
FoxPlan’s Committees module gives the steering committee a home in the tool: recurring sessions scheduled in advance, an agenda prepared per session, and the decisions and actions taken attached directly to the project, visible from one committee to the next. The project weather report feeds the first agenda item, and the portfolio dashboards give the sponsor a consolidated view of progress, budget, resources and risks, without rebuilding a snapshot by hand.
See how to do it in the FoxPlan documentation ↗
Frequently asked questions
What is a steering committee?
A steering committee is the governance body of a project. It brings together the sponsor, the business owner, the delivery lead and the business unit heads around the project manager, to approve the direction, arbitrate scope, cost and deadline trade-offs, and take the decisions the team cannot take alone.
Who sits on a project steering committee?
The sponsor, who chairs; the project manager, who prepares and runs the session; the business owner and delivery lead representatives; the heads of the impacted business units; and sometimes the PMO. Five to eight people, each with real decision-making power.
What is the difference between a steering committee and a project committee?
The project committee is operational: weekly, it brings the team together to organise the work and remove blocking points. The steering committee is decisional: monthly or at each milestone, it brings the decision-makers together to arbitrate and approve the project’s major orientations.
How often should a steering committee meet?
Most often once a month, or at each major project milestone. More frequent, it turns into a status meeting; less frequent, it rubber-stamps decisions already taken by default. On a short project or one in crisis, a fortnightly rhythm is possible.
What should steering committee minutes contain?
The header (project, date, attendees), the weather and summary, the key indicators, the numbered list of decisions with decision-maker and impact, the actions with owner and deadline, and the date of the next session. One to two pages, circulated within 48 hours.
How do you prepare a steering committee agenda?
Always start from the same outline: project weather, progress and milestones, budget and resources, risks and blockers, decisions to take, actions. Time each item, frame each decision as a question with options and a recommendation, and circulate the pack 48 hours in advance.
