As a working convention, we call a steering committee here the body where the people with authority over a project take, at regular dates, the decisions that exceed the project manager’s delegation: scope, budget, committed deadlines, passing a milestone. Running a steering committee, in this sense, means conducting a cycle longer than the meeting itself.
Elsewhere, the same name refers to meetings with a different purpose, and each organisation sets its own. In the cycle described here, the purpose of the body and its members are written down once. Each meeting is then prepared through a pack sent in advance, follows the order of the decisions requested, closes with a record validated on the spot and continues with follow-up. The content of the review (actual progress, risks, passing a milestone) is the subject of our article on the project review. The steps that follow concern how the body is run, and we propose them as a method.
The purpose of the body is written down before the first meeting
A committee without a written purpose can take on anything: top-down information, coordination between teams, technical questions. The first step produces a page, which the sponsor signs. It states which decisions belong to the committee, which remain with the project manager, how often the body meets and who chairs it.
The boundary with the project manager is set by thresholds: a budget or schedule overrun beyond an agreed margin, a change of scope that affects an objective. These margins have a name in the PRINCE2 method, tolerances: a forecast overrun is escalated to the committee.
The same page separates the steering committee from neighbouring meetings. The progress meeting, sometimes called the project committee, coordinates the teams’ work and does not need the decision-makers. On a programme, a programme committee arbitrates between projects, according to the governance described in our page on programme management. Combining these purposes in a single meeting lengthens the agenda and can keep away those whose presence counts.
Around the table, people who can decide
The committee is made up of the people who can decide on what the purpose page entrusts to the body. We propose that it include the sponsor, a representative of those who will use the result and a representative of those who build it, in-house or at a supplier: in the vocabulary of IT projects, the project owner and the project contractor. Experts attend by invitation, for the item that concerns them.
Chairing and facilitating are two roles. The sponsor chairs: they decide, or note the members’ agreement. Facilitation falls to the project manager or, where the project has one, to its PMO: preparing the pack, keeping to the agenda, wording the decisions, writing the record.
Absence is settled in advance. A member who cannot attend appoints a deputy holding a written delegation. A deputy without delegation can only listen: the decisions that depended on the member are then withdrawn from the agenda and follow a written circuit, outside the meeting.
A pack read before entering the meeting
The pack goes out a fixed time before the meeting, set in the purpose page: early enough to be read, late enough to be up to date. Its first page sets out the decisions requested. Each takes up a few lines: the question, the options, what each option costs in time, budget and scope, the project manager’s recommendation, and the date after which not deciding amounts to choosing.
The rest of the pack serves as evidence: milestone status, forecasts at completion, risks whose decision deadline is approaching, according to the sorting described in our article on project risk management.
Between sending the pack and the meeting, the facilitator talks to each member on whom a decision depends. They do not seek to obtain agreement. They check that the question is understood, collect objections and identify the missing information. A decision that its author discovers in the meeting may be postponed for that reason alone.
If the pack is not ready on the sending date, the sponsor chooses between a meeting with a reduced agenda and a postponed meeting.
Running a steering committee, decision after decision
The meeting follows a fixed order. It opens with the previous record: each decision that has fallen due is declared applied, late or abandoned, without reopening the substantive debate. Next come the decisions requested, from the heaviest to the lightest, while all the decision-makers are present. Information, progress status included, comes last and is limited to questions on the pack.
For each decision, the facilitator proceeds in the same way. They recall the question and the options, give the floor to the project manager for their recommendation, then to the members. Before moving to the next item, they restate aloud what has just been decided, name the owner and the deadline, and wait for the chair’s agreement. This restatement is the moment when a disagreement that has remained implicit can come out.
An item closes with one of these outcomes: decided; postponed, with the missing information and the person who will provide it; or referred to another body, which the facilitator names. As long as none has been pronounced, the item remains open.
The facilitator also keeps time. A technical discussion that settles in is referred to a workshop, with a date and a rapporteur. A subject brought up in the meeting, outside the pack, is placed on the next meeting’s agenda, unless the chair recognises it as urgent.
The decision record is written during the meeting
The record contains what the meeting produced, without recounting the discussions. It is organised in sections: decisions, postponements, actions. Each decision is written in one sentence that can be understood without having attended the meeting, with its owner, its deadline and, where relevant, the option set aside.
Written as the meeting goes along, then projected or read back before closing, it is validated by the chair in front of the members. This on-the-spot validation avoids a review circuit, which can delay circulation and reopen debates. We propose sending the record the same day or the next, to the members and to the people responsible for an action, including those who were not present.
A wording is checked by putting yourself in the position of the person designated: the line that concerns them must tell them, on its own, what they will have done and by what date. “Look into the schedule question” does not meet this condition. “The project manager presents two cutover scenarios, with their cost, at the next committee” does.
The decisions from all the records feed a single register, kept by the facilitator: number, date, wording, owner, deadline, status.
Between two committees, following up decisions
Follow-up starts the day after the meeting. The facilitator chases the owners before the deadline, without waiting for the next committee. When a decision runs into an obstacle, they flag it to the sponsor, so that it is maintained, modified or lifted by the person who took it.
Some decisions cannot wait for the next meeting. The purpose page provides a short circuit for them: a one-page note sent to the members, a written answer from the chair within an announced time, then entry in the register.
The register provides measures of the body: the share of decisions that have fallen due and been applied, and the time between a request being entered and the decision. Their conventions are set out in our article on PMO KPIs. When several projects run their committees according to this cycle, a common pack and record format makes their decisions comparable: this is one of the purposes of setting up a PMO.
When the records of several consecutive meetings contain only information, the facilitator says so to the sponsor and proposes reviewing the frequency or the purpose of the body.