What should be on a steering committee meeting agenda?

The objective of the meeting, approval of the last minutes and open actions, the decisions required (each with a decision paper), change requests, the top risks and issues above tolerance, a short status-by-exception slot, a read-back of decisions and actions, and the next meeting date. Label each item as a decision, discussion or information.

Who attends a steering committee meeting?

The project sponsor, who usually chairs, and senior representatives of the affected business areas, often three to six members. The project manager attends to present and answer questions but is not a member, and a secretary records decisions and actions.

How often should a steering committee meet?

Ohio's project governance guidance suggests every two weeks or once a month for projects that run six months or longer. Meet more often around big decisions such as go-live, and less often when the project is stable.

What is the difference between a steering committee and a project team?

The project team does the work and makes day-to-day decisions within its authority. The steering committee gives direction and makes the decisions outside that authority, such as changes to scope, budget or dates and acceptance of major risks.

How do you write steering committee minutes?

Record attendance, the meeting objective, each decision with an ID, each change request as approved or declined, risks accepted or escalated, and actions with an owner and due date. Leave out the debate, since the decision papers hold the reasoning, and circulate the minutes within a week, ideally the same day.

Steering Committee Meeting Agenda and Minutes

Priya's third steering committee meeting ran 90 minutes. She walked six directors through 22 slides of progress and the meeting ended with zero decisions. The one thing she needed, approval to move the go-live by three weeks, was item 7. They never reached it. (Priya is a composite, not a real person.)

A steering committee meeting is not a status meeting with senior people in it. It exists to make the calls the project team can't make alone. A good steering committee meeting agenda is built around those calls, and it shows every member, before they walk in, what they're being asked to decide.

Below: the agenda as a template, the roles, the pre-read pack and filled sample minutes. Running the meeting and taking the minutes at the same time? Try ParrotNotes free, put your phone on the table with everyone's agreement, and keep your eyes on the room.

What a steering committee meeting is for

The University of Queensland's Project Governance Office puts it in one line: a steering committee is "senior stakeholders who provide direction and support to the project team and make decisions outside of the project team's authority" (from its steering committee guidance). Its list of jobs includes approving risk tolerances, approving or declining variation requests, and resolving issues the project can't settle itself.

That gives you a simple test for every agenda item: does it need the committee's authority? If not, it belongs in the pre-read.

	Status meeting	Steering committee meeting
Purpose	Share progress, coordinate work	Decide what the project team can't
Who talks most	The team	The members, after the project manager frames each question
Typical output	Updated task list	Decisions, approved or declined changes, accepted risks
Progress update	Main item	A pre-read, with five minutes for questions

Steering committee roles

Ohio's Office of Budget and Management sets out the standard roles in its guide to steering committee basics (both guides checked October 18, 2026). It suggests "three to six people" as the ideal size.

Role	Member?	What they do in the meeting
Project sponsor	Yes, always	Accountable for the project's success, often chairs, has the final say when members disagree
Chair (often the sponsor)	Yes	Keeps the agenda on decisions, calls the question, reads each decision back
Business and stakeholder representatives	Yes	Speak for the teams who will use the result; commit their people and budget
Subject matter experts	Sometimes	Advise on technical, legal or supplier questions
Project manager	No, attends	Prepares the pack, frames each decision, answers questions
Secretary or minute-taker	No, attends	Records decisions, actions and risks; circulates the minutes

The point most templates skip: the project manager attends but isn't a member. Ohio's guide describes the PM as "essentially 'contracted' by the Steering Committee", and suggests a team member or administrative staff record the decisions. If the PM presents and takes the minutes, one of the two jobs suffers.

The steering committee meeting agenda template (60 minutes)

Copy this and label every item. Ohio's guide asks for "an agenda for every meeting and a well-thought out objective," issued "at least a week before meetings."

[PROJECT NAME] STEERING COMMITTEE MEETING: [date, time, room]
Chair:              Secretary:            Project manager:
Members:
Objective of this meeting: [one sentence, e.g. "Decide the go-live date"]
Pre-read pack sent: [date]

#  Item                                   Type          Lead     Time
1  Opening, quorum, objective              Information   Chair    3 min
2  Minutes and actions from last meeting   Decision      Chair    5 min
3  Decisions required                       Decision      PM       20 min
   3a [decision paper title]
   3b [decision paper title]
4  Change requests                          Decision      PM       10 min
5  Top risks and issues (above tolerance)   Discussion    PM       10 min
6  Status by exception (questions only)     Information   PM       5 min
7  Read-back of decisions and actions       Decision      Secretary 5 min
8  Next meeting, close                      Information   Chair    2 min

Decisions come third, while everyone is fresh. Status is "by exception": members read it beforehand and only ask questions. At item 7 the secretary reads each decision aloud so nobody leaves with a different version.

Starting a project rather than steering one? The first meeting has different jobs, covered in our project kickoff meeting agenda.

The pre-read pack: decision papers, RAID and change requests

The pack does the informing. Send it with the agenda.

Pre-read pack checklist

One-page status summary: milestones, budget against plan, forecast to finish
One decision paper per item under agenda point 3
Change request log: only requests that need the committee's approval
RAID summary: the risks, assumptions, issues and dependencies above the agreed tolerance, not the full log
Open actions from the last meeting, with status

The one-page decision paper

DECISION PAPER: [title]                     For meeting: [date]
Decision needed:      [one sentence, ending in a question]
Background:           [three lines at most]
Options:              A. ...   B. ...   C. Do nothing
Impact of each:       time / cost / scope / benefits / risk
Recommendation:       [option and why, in two lines]
Cost of deferring:    [what happens if this waits a month]
Decision deadline:    [date]

The "cost of deferring" line stops "let's revisit next month" from becoming the default.

Steering committee minutes: template and filled sample

Steering committee minutes are short, because the decision papers hold the reasoning. Record the outcome, not the debate. For a general minutes format, see our meeting minutes template; here's the steering version, already filled in.

NORTHFIELD SUPPLY CRM ROLLOUT: STEERING COMMITTEE MINUTES
Date: October 14   Chair: D. Okafor (sponsor)   Secretary: L. Brandt
Members present: D. Okafor, S. Varga (Sales), M. Hale (Finance), R. Tran (IT)
Attending: P. Nair (project manager)   Apologies: none
Objective: decide the go-live date

1. Previous minutes: approved without changes.

2. Decisions
   D-14 Go-live moves from November 3 to November 24 (option B in the
        paper), so data migration can finish a second test cycle.
        Decided by: sponsor, with members' agreement.
   D-15 Sales reps get two half-day training sessions, not one.

3. Change requests
   CR-08 Add quote approval workflow: APPROVED, +$12,000, from contingency.
   CR-09 Custom dashboard for regional managers: DECLINED, moved to phase 2.

4. Risks and issues
   R-03 Key migration contractor leaves December 1: risk accepted until
        November 24; IT to name a backup by October 21.
   I-05 Duplicate customer records (about 4%): escalated to Finance for
        a clean-up owner.

5. Actions
   A-31 Inform sales managers of the new date | S. Varga | Oct 17
   A-32 Name backup migration contractor     | R. Tran  | Oct 21
   A-33 Assign duplicate-record owner        | M. Hale  | Oct 21

Next meeting: November 11, 10:00, Board Room 2

(Northfield Supply and everyone in it are composites, not real people.)

Notice what's numbered. Decisions, change requests, risks and actions each get an ID, so they can move into a running decision log and an action items tracker without retyping. Ohio's guide asks for minutes with "clear action lists showing who will take each action," circulated "within a week of the meeting." Aim for the same day.

Run it so decisions get made

Marta chairs the steering committee for an office relocation. For two months every decision paper ended with "let's take this offline," and the move date slipped twice. Now, before each next item, she asks, "What have we decided, and who owns it?" and waits for a one-sentence answer. (Marta is a composite, not a real person.)

That question is the core of five habits that keep a steerco meeting on decisions:

State the objective first. Members then know what "done" looks like.
Frame, then step back. The project manager presents each decision paper in two minutes, then stops. The members debate; the PM answers questions.
Call the question. When debate repeats, the chair asks for the decision, or for the information needed to make it next time, with an owner and a date.
Read back before you close. Disagreements surface now, not in a reply-all next week.
Close the loop at the next meeting. Item 2 checks every open action. An action that misses two meetings goes back to the sponsor.

When the project ends, the committee's last session reviews it; see our post-mortem meeting guide.

Record the meeting so the minutes write themselves

Lukas is the secretary for a manufacturer's ERP steering committee, where "approved for the pilot plant" is not "approved." He used to spend the meeting writing and the evening reconstructing. Now he puts his phone on the table, confirms everyone agrees to the recording, and listens. (Lukas is a composite, not a real person.)

Here's how ParrotNotes fits that job:

Summary on every recording. The AI summary arrives after the meeting on every plan, so the draft minutes start from what was said.
Action items pulled out. Owners and dates people said aloud show up as a list you can paste into section 5.
Ask the recording. Type "What exactly did we decide on CR-09?" and get the answer from the transcript before the minutes go out.
Long meetings and many languages. Pro records up to 3 hours per recording and transcribes 99+ languages, with translation, for committees that span countries.

The Free plan includes 100 minutes of recording a month, an AI summary on every recording and 5 AI-powered recordings with action items and chat. Pro ($19.99/month, or $14.99/month billed annually) adds 3,000 minutes a month, speaker identification and AI search across every note, so last quarter's decision on scope is one search away. It runs on iOS, Android and macOS. Download ParrotNotes free before your next steering committee meeting.

Put decisions at the top of your steering committee meeting agenda

A steering committee meeting earns its senior attendees by making decisions. Build the agenda around calls only the committee can make, send decision papers a week ahead, and number every decision, change, risk and action in the minutes.

Start with the next meeting. Copy the agenda, write one decision paper, and give the minute-taker one job: listen. Get ParrotNotes free so the record is ready when the meeting ends.

Steering Committee Meeting: Agenda, Roles and Minutes

Table of Contents