How to Prepare for a Steering Committee Meeting When You Need a Decision

The pack went in on time. You walked the committee through twelve slides, they nodded at the green ones and asked two questions about the red one. Then the chair thanked you and moved to the next item.

Nothing was decided. Which means next month you will be back with the same problem, four weeks older.

Most steering committee preparation fails before the meeting starts, because what gets prepared is an update. Updates invite reassurance. If you need the committee to actually decide something, you have to prepare a decision request — and that is a different artefact built from different parts.

Why steering meetings default to status

Steering committees are decision bodies that spend most of their time receiving reports. That is not because the members are lazy. It is because of what lands in front of them.

A typical steering pack is built to demonstrate control: progress against plan, RAG status, risks being managed. A committee given evidence of control concludes that no intervention is needed. That is the rational response to what it was shown.

So the delivery manager who needed a call on the date, the scope or the dependency leaves with a nod instead. The gap between the plan and the reality stays exactly where it was — being carried quietly by the team.

The fix is not a better update. It is bringing a decision request.

What to bring when you need a decision

A decision request has five parts. If the committee is going to decide something in your slot, all five need to exist before you walk in.

1. The record — the position in dated facts with sources, not adjectives.
2. The decision — the call you need, written as a choice between named options.
3. The owner — whose call it is, and a fallback decider if a group cannot conclude.
4. The options — two or three, each with its trade-off in one line.
5. The line — the single sentence you will say if you only get to say one.

Everything else in your pack exists to support these five things. Anything that does not support them is decoration.

If you want help assembling this before the meeting, Before the Meeting turns five questions into your read of the situation, the ask, the one line and the records to gather. It is free, runs in your browser and never stores or sends your answers.

Gather the record, not a summary

The committee has heard summaries before. What changes minds is the record: what was committed, when, by whom and what has moved since.

Go back through your own sent mail, meeting minutes and decision log and pull out dated facts. The shape to aim for is a short table: date, source, what was recorded. If your organisation has approved workplace AI with access to your mail and documents, a well-scoped search brief can pull the same table together in minutes — but the method works by hand, and the discipline is the same either way.

Two rules make the record land. First, quote the record rather than characterising it — “the rehearsal moved twice, recorded as timeline tight” beats “we have some schedule concerns”. Second, list what you could not find under a heading called evidence gaps. A date with no plan behind it is not a gap in your preparation. It is usually the strongest fact you have.

Name the decision and whose call it is

Write the decision as a choice, in one sentence, containing the word “or”.

“Choose one: change the plan to meet the date or change the date to meet the plan.”

If you cannot write that sentence, you are not ready for the meeting — you are still diagnosing. And if you do not know whose call it is, that becomes your first ask, because it is small, easy to grant and puts the question on the record.

One committee-specific move is worth the discomfort: if the decision belongs to the group and the group has a habit of not concluding, propose a fallback decider and a date in the paper itself. Committees rarely object to being offered a way to succeed.

Bring options, not a problem

A problem handed to a committee comes back as an action to investigate. Options handed to a committee come back as a choice.

Two or three options are enough. For each one, a single line: what moves, what holds and what it costs. Then one more line the pack usually leaves out — what deciding late costs, because the options that exist this month quietly close over the next one.

Prepare the one line

Somewhere in the meeting you will get thirty seconds of genuine attention. Prepare the sentence for it in advance.

A workable shape is: how this was raised before, what has changed and the call you need. For example: “I’ve raised this in writing and it’s still open: the date and the plan have come apart and I need a call on which one moves — can we agree who makes that call and by when?”

Say it early. The rest of your slot then becomes evidence for a question the room already understands.

A short example

An update version of a slot: “Mostly on track. A few risks we’re watching. The date’s tight but we’re holding it for now.” The committee nods. The minutes record “noted”.

A decision-request version of the same position: the record shows the go-live date restated in a leadership deck with no re-baselined plan behind it, a rehearsal moved twice and a concern minuted as “monitor”. The ask is a choice: re-plan to the date or move the date to the plan. The owner is named. The minutes record a decision and a date.

Same project. Same facts. Different preparation.

Steering item, escalation, risk review or replan?

Preparation goes wrong when the meeting type is misread, because each one needs a different artefact.

A steering decision is a choice between options inside the current mandate — the method above.

An escalation is a request for someone senior to act or unblock. It needs the explicit ask with a date, and it deserves its own wording — the Escalation Pack helps you decide whether to raise and what to bring if you do.

A risk review is about a risk being carried without a decision. The honest outcomes are formal acceptance with a named owner or funded mitigation. Framing a risk review as an escalation reads as alarm and burns credibility.

A replan is a recovery decision — what has changed, the options and your confidence in each. Bringing it as bad news rather than a decision usually gets it deferred.

And if the meeting is really a trade-off conversation between competing demands, the preparation is less about the pack and more about the words — the Priority Conversation Check is built for exactly that.

Walk in with the five things

None of this requires seniority, charisma or a better committee. It requires the record, the decision, the owner, the options and the line — prepared before the meeting instead of reconstructed during it.

Before the Meeting turns five questions into your read of the situation, the ask, the one line and a brief listing exactly which records to gather. Free, browser-side, nothing stored, nothing sent — and the same selections produce the same preparation every time.