A steering committee agenda should make the next decision easier. If every item is labelled “update”, members must work out for themselves whether you need advice, approval or simply their attention. Give each item a purpose before adding slides.
Definition
SteerCo agenda: A SteerCo agenda is an ordered plan for a steering committee meeting that identifies the decisions, discussions and updates needed to govern a project.
In practice: Label each item information, discussion or decision, and give decision items an owner and a latest useful decision date.
Not the same as: The pre-read, which supplies supporting evidence before the meeting.
Start with the committee’s authority
Check the steering committee’s remit before asking it to approve anything. A committee may recommend a funding change without having authority to release the money. Name the decision authority in the agenda and confirm the escalation route if that person or forum cannot attend.
Ask the chair which decisions cannot wait until the next cycle. Those items deserve protected time. Routine progress can sit in the pre-read, with questions raised in advance so the meeting can focus on the exceptions.
A practical agenda sequence
Use the following sequence as a starting point, adjusting it to the project’s governance arrangements. There is no universal meeting length or mandatory order.
| Item | Purpose | Expected outcome |
|---|---|---|
| Previous decisions and actions | Confirm changes and unresolved commitments | Escalate overdue work or accept evidenced closure |
| Delivery exceptions | Explain material changes since the pre-read | Agree whether action or a decision is needed |
| Decision requests | Compare options within the committee’s remit | Record the authorised choice and conditions |
| Risks and dependencies | Consider exposures that need wider authority | Name the response owner and escalation route |
| Read-back and next review | Check the record before people leave | Confirm decisions, actions and dates |
Give each decision an evidence trail
Write a decision item as a choice: “Approve the reduced launch scope or authorise the revised date.” Add the deadline and consequence of deferral. Link the recommendation to source records, with a clear evidence date. Use agreed RAG criteria to support the colour rather than asking members to accept an unexplained assessment.
For each exception, reference the RAID record that holds the issue, risk or decision context. Define the RAID expansion used on the project. Keep implementation actions distinct from approval, even when both are recorded in linked logs.
An example decision item
Illustrative example: a supplier cannot support the planned rehearsal. The agenda asks the authorised sponsor to choose between a later launch and a smaller initial scope by 29 October 2026. The pre-read compares readiness, operational effort and cost for each option, with evidence from the supplier and delivery leads.
The project manager recommends the smaller scope only if the operations lead confirms it is supportable. That condition belongs in the decision record. If it is not met, the recommendation must be reconsidered; the meeting should not turn a conditional proposal into unconditional approval.
Send a pre-read people can use
Keep the summary short enough to expose the choice, while making supporting evidence available to authorised readers. State what changed since the previous pack. Reuse agreed reporting inputs rather than rewriting dates and owners across several documents.
As of Oct 2026, AI assistance should still be treated as draft preparation within an approved workflow. The AI in project management guide explains suitable boundaries; the AI status-report checklist supports the final fact-check. Check every claim about approval against the original record.
Close the meeting with a read-back
Read back each decision, its authority, conditions and rationale. Confirm who owns the resulting work, when it is due and what will count as completion. Where members disagree with the record, resolve the wording or mark the matter as unresolved; silence alone should not become approval.
Keep urgent decisions moving between meetings through the agreed escalation route. A missing agenda slot is not a reason to let a decision deadline pass. Bring subsequent approvals back into the record so the next pack shows a continuous history.
Before circulating the final record, check that the agenda item and the recorded outcome still describe the same choice. Discussion may have changed the proposal or added conditions. Update the decision wording accordingly, retain the source of approval and ask the implementation owner to confirm the next step. This makes the following meeting’s review about progress against an agreed commitment rather than competing recollections of what was said.
Common questions
Does every agenda item need a decision? No. Some items provide context or need discussion. Labelling their purpose helps the chair protect time for the choices that do need authority.
Should the project manager chair the meeting? Follow the agreed governance arrangement. The project manager can prepare and facilitate the pack while an authorised sponsor or other chair leads the committee.
What if the evidence is incomplete? Make the gap and its consequences explicit. The committee can defer, request further evidence or make a conditional choice within its authority. Do not describe an unverified assumption as an established fact.