Guides /

Steering Committee Meeting Prep: Project Manager Checklist

Steering committee prep checklist for project leads: the order to pre-wire the sponsor, brief members, build the agenda and decisions pack, and track actions.

By The Unblockd teamPublished

Prepare a steering committee meeting in this order: name the decisions the committee must make, pre-wire the sponsor one to one, brief members on any item they have not seen, build the agenda and decisions pack from the same decision list, then record decisions and actions after the meeting. Each step depends on the one before it, so skipping ahead leaves the sponsor and members to meet a surprise in the room.

In what order should the steering committee prep steps run?

Run the prep in this order: name the decisions, pre-wire the sponsor, brief members on new items, set the agenda, write and circulate the decisions pack, then record decisions and actions. Each step relies on the one before it, so the decision list comes first and the record comes last.

Start with the decision list. Write each decision as a question the committee can answer. "Approve the revised delivery date or keep the current one" works. "Discuss the vendor delays" does not, because nobody can answer it in the room. Keep the list short enough that each decision gets its own agenda slot.

Count back from the meeting date using the lead time your charter or sponsor sets. Published guides disagree on timing. Plane's guide suggests sending progress updates at least 48 hours ahead, and Wrike's guide suggests reminders in the days before the meeting. Neither sets a rule for your committee, so take the timing from the charter or the sponsor.

Step When Owner Check before moving on
Name each decision as a question [n1] working days before the meeting, first Project manager, with the sponsor Each decision has its options listed
Pre-wire the sponsor, one to one After the decision list, by [n2] working days before Project manager The sponsor's conditions are written down
Brief members on items they have not seen [n3] working days before, after the sponsor call Project manager Each member has replied or raised a concern
Set the agenda around the decisions [n4] working days before, once briefings are in Project manager; sponsor approves Every slot has an expected output
Write the decisions pack [n5] working days before Project manager One page per decision
Sponsor reviews the pack first [n6] working days before Sponsor The sponsor has seen the pack before members do
Circulate the agenda, pack, and last minutes [n7] working days before, after sponsor review Project manager Sent only after sponsor review
Rehearse the hard questions [n8] working days before Project manager and sponsor Answers agreed for the likely challenges
Send one reminder with the open questions [n9] working days before Project manager Each open question names who answers it
Confirm each decision aloud Meeting day Sponsor Each decision is read back to the room
Circulate decisions and actions [n10] working days after the meeting Project manager Every action has an owner and a due date

Replace each [n] with the count your sponsor confirms. Keep the counts in table order, so each earlier step has the larger count and the sponsor's review lands before members see the pack.

How do you pre-wire the sponsor before the meeting?

Pre-wire the sponsor by walking through each decision one to one before the pack reaches the wider committee. The sponsor should hear any surprise from you first, in a short call, not in the room. Ask what they need to see before they can decide, and add that answer to the pack.

Book the call once the decisions are named and before the pack is final. Open with the decision, not the project history. Use this wording with the brackets filled in:

Before the committee meets, I want to check one decision with you. The committee needs to decide [decision] by [date]. The options are [option A], which means [impact], and [option B], which means [impact]. My recommendation is [option], because [reason]. Is there anything you need to see before this goes on the agenda?

Write down the answer and any condition the sponsor sets. Agree with the sponsor who will raise the item in the meeting, so the item does not reach the room as a surprise to anyone.

Which members should you brief before the committee meets?

Brief each member who will decide on an item they have not seen, or whose team the decision affects, before the meeting. Keep each briefing to one item: the decision, the options, and the reply you need. Send it early enough for a written reply.

Start with the sponsor, the client where there is one, and the team that does most of the work on the item. Send each question early enough for the member to answer in writing before the meeting. This timing is working practice rather than a rule from a published source, so agree the reply deadline with the sponsor.

[Name], before the committee meets on [date], I want to flag [item]. The committee will be asked to [decision]. Is there a concern about [topic] you want addressed in the pack? Please reply by [date].

What belongs on the steering committee agenda?

Put the decisions first on the agenda, and give each one a time slot and an expected output. The decision list from the first step is the agenda's spine. Drop any item that has no expected output, or ask whether it belongs in the meeting at all.

Open by confirming the previous actions, then spend most of the time comparing options. Adapt this template and fill in the times yourself:

  • [Start] to [end]: confirm the decision and follow up on previous actions. Expected output: [decision to make today].
  • [Start] to [end]: review changes to [scope, cost, dates, or risk]. Expected output: a shared view of what changed.
  • [Start] to [end]: compare the options and agree the trade-off. Expected output: a decision, an owner, and any conditions.
  • [Start] to [end]: escalations and dependencies. Expected output: named owners and due dates.
  • [Start] to [end]: read back the decisions and actions. Expected output: the decision log and the next review date.

What should a decisions pack contain?

A decisions pack holds one page for each decision on the agenda, in agenda order, plus only the status detail those decisions need. Build the agenda and the pack from the same decision list so every slot has a page.

Copy the decision list from the first step, and make each decision one page numbered to match its agenda slot. Cut the status report down. A status report lists what the team did. The pack keeps only what changes a decision: a milestone that moved, a risk that changes an option, or a cost that changes the recommendation.

On each page, write the question, the options with their impact, and your recommendation. Susanne Madsen's 2013 post recommends showing the top 5 to 10 risks and issues with their owners and actions. Include them only where they bear on a decision.

The page below is illustrative. Every name, figure, and option is a placeholder:

Decision [n] of [total]: [decision question] Options: [option A], impact [impact]. [option B], impact [impact]. Recommendation: [option], because [reason]. Evidence the sponsor can check: [item and where it is].

If a page needs a long read before anyone can answer it, the question is probably too broad. Return to the decision list and frame it again.

How do you frame a decision request for a contested item?

A contested decision is one where members disagree about the option, not only the facts. Frame it as a one-page request with the options, the cost of waiting, your recommendation, and a named fallback owner. The fallback owner decides if the committee cannot agree by the date you set.

Agree the request with the sponsor during the pre-wire call, so the sponsor knows the fallback before the meeting. The example below is illustrative and uses placeholders only:

Illustrative example: decision request for a re-baseline Question: Approve the re-baselined [milestone] date of [new date], or keep [current date] and accept [named risk]. Option A, re-baseline to [new date]: [scope or cost impact]. Option B, keep [current date]: [impact on the next milestone]. Cost of waiting: if no decision is made by [date], [what slips and by when]. Recommendation: Option [A or B], because [reason]. If the committee cannot agree: [name, role] decides by [date], after [name] gathers [information].

Put the cost of waiting near the top of the page, so the committee sees what a delay costs before it compares the options.

Should a contested decision wait for a later meeting or go to the sponsor?

Hold a contested decision for a later meeting when the missing information can be gathered before that meeting and the delay will not break a deadline. Take it to the sponsor when the delay would break one, or when the committee does not have the authority to decide.

The trade-off is time against standing. A later meeting keeps the decision with the committee, but it adds a delay the team has to carry. A sponsor decision is faster, but members who expected to decide may feel bypassed, so tell them before you ask.

Before the meeting, ask the sponsor which route they prefer for contested items, and write the answer in the charter or the decisions log. When you take an item to the sponsor, send the same one-page request to the sponsor and the members involved, with a short note on what the sponsor is deciding and by when.

When and how should the pack go out?

Send the pack and the agenda together, after the sponsor has seen the pack and early enough for members to send questions before the meeting. Then send one short reminder that names the open questions and who will answer each one.

Wrike's guide lists circulating the agenda and prior minutes before the meeting, with reminders in the days ahead. Use a clear request in the covering note:

Please send questions on [item] to [name] by [date].

  1. Confirm with the sponsor the date they will see the pack.
  2. Send the pack with the request above.
  3. Send one short reminder before the meeting.
  4. If something changes, send a short note that names the item it affects and what changed.

How do you handle disagreement and bad news in the room?

If members disagree in the room, the person named before the meeting makes the call, or the committee sets a date and a named owner gathers the missing information. For bad news, lead with the status, then the options and your recommendation.

Confirm the quorum and voting rules in the charter. If the charter is silent, agree the rule with the sponsor before the meeting, so the committee does not have to work out how a decision is counted in the middle of the discussion.

Before closing, check whether every needed decision was made. Say this at the close:

Before we close: have we decided [decision]? If not, it goes to [name] by [date], and the information needed is [item].

Susanne Madsen's 2013 post recommends stating plainly where the project is off track. Leave the cause for later in the discussion, after the options are on the table.

What happens after the meeting?

Record each decision and action as soon as the meeting ends, with an owner and a due date for every action. Susanne Madsen's 2013 post recommends distributing minutes within 24 hours, so agree a distribution time with the sponsor before the first meeting.

Use this record so the next pack starts from what was agreed:

Decisions: [decision], agreed by [who], with conditions [conditions]. Actions: [action]. Owner: [name]. Due: [date]. Status: [open or done]. Open questions: [item]. Owner: [name]. Next review: [date].

Send the record to the members, and keep it open for the next pack. Before the next committee meeting, check each owner and due date with that person, so the next decision list starts from what was agreed.

Questions people ask

Should every committee member receive the full decisions pack?

Send the full pack to the members who make the decisions, and only after the sponsor has reviewed it. Members who need the outcome but not a decision can receive the agenda before the meeting and an outcome note after it.

What if a member raises an item that is not on the agenda?

Note it in the minutes with an owner and a date, and offer a separate conversation if it needs a decision. Do not let an unplanned item replace a decision already on the agenda.

How do I prepare for a remote or hybrid steering committee?

Collect questions from remote members in writing before the call, so they do not have to interrupt it. Agree with the sponsor beforehand how remote members confirm a decision, and write that rule in the charter if it is not already there.

The Unblockd team

Unblockd helps teams deliver projects faster by getting stuck work in front of the sponsor who can clear it: an AI agent drafts the ask from the project's evidence, the team checks and sends it, and the sponsor answers without signing up.

Get the sponsor ask checklist

One screen to check before you send an ask: the decision, the options, the date, and what waits on it. Then one email a week with new guides.