Skip to article
Bridge

How to run a steering committee meeting

A steering committee is the small senior group that directs a project, approves resources and settles issues the project manager can't. Each meeting should end with recorded decisions, clear escalation outcomes and an updated action log.

What a steering committee meeting is for

A steering committee, also called a project board or steering group, gives a project direction and authority. It approves resources, sets the limits the project manager works within, and decides what falls outside those limits.

It doesn't run the work day to day. Northern Ireland's Department of Finance says the project manager runs the project with authority from the project board. The board steps in on direction, funding and escalated issues.

The committee is not a vote. In the same guidance, the Senior Responsible Owner stays the key decision maker, and the board gives that person stakeholder and technical input.

Who sits on the committee

Keep membership to the minimum needed to make decisions, as the Department of Finance advises. Every member should be able to commit something on behalf of the group they represent.

  • The University of Waterloo's IT governance guidance adds functional managers whose areas the project changes.
  • It also names experts, such as a subject matter expert, who support decisions but may not be decision makers.
RoleWhat they do in the meeting
Sponsor or Senior Responsible OwnerAccountable for the project; makes the final call on decisions brought to the committee
ChairRuns the agenda and confirms each decision out loud; often the sponsor
Project managerPresents the status pack, frames decisions and takes away actions; attends to report
MembersSenior representatives of users and suppliers who can release funding, people or other resources
AdvisorsSpecialists who inform decisions without being decision makers
Secretary or notetakerRecords decisions, actions and escalations, and keeps the action log

Agree terms of reference and tolerances first

Write a short terms of reference before the first meeting. It should state the committee's purpose, members, decision rights, cadence and how papers and minutes will flow.

Set tolerances too. The Department of Finance expects board members to set tolerance levels within which the project manager must operate. Anything forecast to go past them comes to the committee. The thresholds below are examples; set your own.

  • Schedule: for example, more than two weeks late on a milestone.
  • Budget: for example, a forecast overspend above 5% of the approved budget.
  • Scope: any change to what was approved in the business case.
  • Risk: any new risk rated high on impact and likelihood.

Cadence and pre-reads

Niagara College's project office recommends standard monthly steering committee meetings. Meet more often when a major decision or go-live is close, and less often during stable delivery.

Send a short status pack several working days before each meeting. Mark which papers need a decision, so members know what to read closely.

  • Overall health: green, amber or red, with one line on why.
  • Actions from the last meeting, with owner and status.
  • Decisions needed at this meeting, each with options and a recommendation.
  • Critical issues and risks, new and carried over.
  • Change requests and their effect on scope, cost and schedule.

A 90-minute steering committee agenda

This agenda is illustrative, for a monthly meeting with a status pack sent in advance. Spend most of the time on decisions, not on reading the pack aloud.

TimeItemOutcome
0–5 minWelcome, apologies and approval of last minutesMinutes approved or corrected
5–15 minAction log reviewEach action closed, updated or re-dated
15–25 minProject health by exceptionQuestions only on amber and red items
25–65 minDecisions and escalationsEach decision recorded with owner and rationale
65–80 minTop risks and change requestsResponses agreed and changes approved or refused
80–90 minRecap of decisions and actionsEveryone hears the same list before leaving

Handle decisions and escalations

Bring each escalation as a short decision paper: the problem, two or three options, their impact and a recommendation. The committee then chooses, rather than designing a solution in the room.

The chair should state each decision aloud before moving on. The University of Waterloo guidance gives governance groups the power to review scope changes and, in extreme cases, stop an underperforming project.

  • Approve: the recommendation goes ahead as written.
  • Approve with conditions: write the conditions into the decision record.
  • Refuse: the project stays within its current tolerances.
  • Defer: name the missing information, who brings it and when.

Example decision record

This record is illustrative. Acme's CRM migration project forecast a three-week slip because a data vendor delivered late.

FieldEntry
Decision IDSC-2026-07
Escalated byProject manager: forecast slip exceeds the two-week schedule tolerance
OptionsMove go-live by three weeks; add contract staff to hold the date; cut reporting from release one
DecisionMove go-live by three weeks; no change to budget
Decided bySponsor, after input from finance and sales members
RationaleContract staff would exceed budget tolerance, and sales needs reporting at launch
Follow-upProject manager re-baselines the plan and shares it before the next meeting

Minutes, action log and follow-up

Always take minutes. Niagara College's guidance says minutes reinforce what was decided and which actions were agreed, and by whom.

Keep minutes short: attendees, decisions, escalation outcomes and actions. Track actions in a separate log that the next meeting reviews first.

Action IDActionOwnerDueStatus
A-31Re-baseline the plan for the new go-live dateProject managerNext meetingIn progress
A-32Confirm the vendor's revised delivery date in writingProcurement memberIn two weeksOpen

Running steering meetings with Bridge

Before each meeting, the Brief shows the calendar description or agenda and previous action items from earlier Bridge meetings. Starter includes limited automatic preparation; full agenda and history need Professional or above.

After the meeting, notes include a summary, decisions and assigned action items on every plan. Ask the meeting's Assistant to list each decision and its owner for your minutes. Custom recap templates need Professional or above.

  • Spaces keep every steering meeting for a project in one place, with files and a Space Assistant. They need Professional or above.
  • You can share a space with stakeholders outside your workspace. They join as guests and need a Bridge account.
  • Guests can view meetings and files but can't use the Space Assistant.

Sources & further reading