I remember my first Steering Committee meeting. I had a room full of senior people in front of me and was worried I would say something that made me look unprepared. Once the discussion started, I realised the group was there to consider the project’s direction and decisions—not to make the project manager defend every line of a slide.

That is the useful idea behind a Steering Committee (often called a SteerCo): bring the people with the right authority and perspective together to make decisions, resolve matters beyond the delivery team and keep the work connected to its intended outcome.

The name, membership and authority vary by organisation. Some places use “project board” or “steering group”; others have different governance arrangements. Check the project’s terms of reference and your organisation’s rules before assuming what this particular group can approve.

What should the committee do?

A useful committee provides direction and oversight at the level assigned to it. Depending on its authority, it may:

• confirm or recommend changes to outcomes, scope, funding, timing or priorities;
• decide issues that are outside the project manager’s delegated authority;
• review material risks, dependencies, forecasts and the evidence behind them;
• agree an escalation or intervention when delivery is blocked;
• confirm whether the project remains worth continuing when assumptions or expected benefits change.

It should leave day-to-day delivery with the people responsible for delivering it. A steering meeting that spends its time assigning every task may be missing a clear boundary between governance and project management.

Who should attend?

Choose members for the decisions and oversight the group needs to provide—not seniority for its own sake. The sponsor normally has a central role, but the exact chairing and decision arrangements should be stated in the terms of reference.

Depending on the project, membership may need someone who can speak for the business or service, people affected by the change, delivery leadership and relevant partner or supplier perspectives. Ask who is authorised to approve the decisions on the agenda. Invite specialists to an item when their input is needed; they do not always need to attend every meeting.

There is no universal ideal number of members. Keep the group small enough to reach decisions and broad enough to cover its responsibilities. If a decision requires an absent role, defer it or use an authorised delegate in line with the group’s rules. Do not imply that attendance alone grants decision authority.

Independent challenge can be useful for some projects or assurance reviews. It is not a requirement for every Steering Committee. Follow the relevant governance arrangements and manage conflicts of interest openly.

Agree the authority before the first meeting

Write down the committee’s purpose, what it can decide, how it makes decisions, what it must escalate, and who records and communicates the result. Include any quorum, conflicts process and delegated limits required by your organisation.

If the sponsor is asking the committee to approve a change but nobody can say whether the group has that authority, do not treat a show of hands as an approval. Find the right decision route and record who owns the next step.

The Association for Project Management explains that governance boards may be called a steering committee, steering group or project board, and that their authority should be defined. UK Government standards provide another formal example for government projects. Both are useful references; your organisation’s own rules and project terms still determine this group’s authority. See APM’s explanation of project governance and the Government Functional Standard for Project Delivery.

Set the meeting up for decisions

Send an agenda that says what the group is being asked to do. Mark items as for decision, for discussion or for information. Keep routine updates short and spend the time on the choices, exceptions and risks that need this group’s attention.

For a decision paper, include:

• the decision required and its deadline;
• the current position and evidence behind it;
• realistic options, including the consequence of making no decision;
• impacts on the outcome, scope, schedule, cost, quality, people and risk;
• the recommendation and its assumptions;
• the decision-maker or authority route.

Agree how early papers should be sent and what happens if they arrive late. The right lead time depends on the organisation and the decision. If members have not had enough time to consider a material choice, move it or agree a safe interim action; do not present a rushed decision as considered approval.

A practical 60-minute agenda

Here is one agenda you can adapt. Change the timing and headings to fit your terms of reference and the decisions due.

1. 5 minutes: confirm the purpose, previous actions and any urgent changes.
2. 10 minutes: review the overall position and the most material movement since the last meeting.
3. 25 minutes: discuss the decisions listed in the agenda, starting with the most time-critical.
4. 10 minutes: consider significant risks, dependencies, benefits or assurance concerns needing committee attention.
5. 10 minutes: read back decisions, conditions, actions, owners and dates; confirm what will be communicated.

Do not force an item into the agenda if it needs information that is not available. Record what is missing, who will obtain it and when the group will decide.

Keep the discussion at the right level

Present the project position in a way members can question. Highlight changes, uncertainty and decisions needed. Do not bury an unresolved issue under a green status simply because no one has made a decision yet.

If members disagree, clarify the point of disagreement and what evidence or authority would resolve it. A committee is not automatically a democracy; use the decision process set out for that project. Capture dissent or conditions when they matter to the decision and its follow-up.

SteerCo should challenge the quality of the plan and the evidence, but it does not need to design every solution in the meeting. When discussion drops into task-level detail, ask which decision or risk requires the group’s attention and take delivery planning back to the project team where appropriate.

Record decisions and actions clearly

Minutes are a useful record, not a word-for-word transcript. Capture:

• the decision, including any conditions or limits;
• who made or authorised it and when;
• the key rationale or evidence where needed to understand it;
• actions, one named owner for each, and an agreed due date;
• issues deferred, what information is needed and who will bring it back;
• material risks or conflicts that remain open.

Keep the level of detail appropriate to the decision and the organisation’s retention and confidentiality rules. Use approved systems for papers and minutes; limit sensitive detail to the people who need it.

Send minutes for correction using the timeframe and approval process the committee has agreed. Silence should not automatically be treated as acceptance unless the group’s formal rules explicitly say so. If an action or decision was recorded incorrectly, correct it through the established record process and make the change visible.

What to do between meetings

Do not wait for the next SteerCo if a material risk or decision is urgent. Use the agreed escalation route and keep a record of the decision and its authority. For routine work, track actions with their owners, check progress and bring back items that are late, blocked or have a changed impact.

Before the next meeting, ask whether the committee needs to meet at the same frequency. Monthly meetings are not automatically right or wrong. Set the cadence around decision needs, delivery risk and any mandatory governance. A lighter written update may work between meetings if the sponsor and members agree how urgent matters will be raised.

Example: a test environment is late

This is an illustrative scenario. The supplier now forecasts a test environment after the date the team planned to begin testing. The team cannot confirm the effect on the release until it reviews the sequence. A demonstration date is approaching.

The project manager should first ask the test lead to assess what can still be tested and the supplier lead to confirm the forecast. The committee paper can then ask the authorised sponsor or board to choose between a revised demonstration, reducing the demonstration scope or another feasible option. It should show the effects, assumptions and deadline for the decision.

The minutes record the option chosen, any conditions, who will update the forecast and who will communicate it. The team continues work that is not dependent on the missing environment. Nobody silently turns the supplier’s forecast into a confirmed date.

10 tips for a more useful Steering Committee

1. Write a clear remit. State the purpose, decision rights and escalation route.
2. Invite the people who can contribute or decide. Confirm authority and use delegates only when allowed.
3. Keep membership proportionate. Bring in specialists for relevant items rather than filling every meeting with observers.
4. Send a decision-focused agenda. Mark why each item is there and what response is needed.
5. Give members time to prepare. Agree paper deadlines and defer poorly prepared material when appropriate.
6. Report changes and uncertainty honestly. Make the important exceptions easy to see.
7. Ask for options and consequences. Include the impact of waiting when a decision is time-sensitive.
8. Keep governance separate from daily task management. Let the delivery team manage delivery within its delegated authority.
9. Record decisions and actions precisely. Include conditions, owners and dates agreed with those owners.
10. Review whether the forum is helping. Adjust the agenda, cadence or membership when the decision needs change.

Before your next SteerCo

Check the terms of reference, list the decisions that are genuinely due, confirm who has authority to make them and send concise papers with realistic options. After the meeting, capture what was decided, what remains open and who will follow up.

A Steering Committee can help a project move through decisions and issues that the delivery team cannot resolve alone. Its value comes from clear authority, useful evidence and follow-through—not the number of slides or the seniority of the room.

If a project’s meetings are not connected to its plan or decisions, my guide to bringing order to a messy project includes a practical reset agenda. For a short report that makes a decision visible, see the project reporting guide.