Guides /

What to Include in a Steering Committee Update

What a steering committee update must contain: health rating, milestones, budget variance, top risks, decisions needed, and prior actions, with templates.

By The Unblockd teamPublished

A steering committee update should cover the overall health rating, milestone progress, budget variance, the top risks and issues, the decisions the committee must make, and the status of actions from the last update. Open the update with a short summary of exceptions so members see first what needs them. Status.net's guide lists its executive-summary items and advises leading with exceptions.

Sentences that name a guide come from that guide's text. The other steps are practical advice from this guide, and the reviewed guides give no numeric thresholds for them.

How should the summary of exceptions open the update?

The summary of exceptions should open the update and name every milestone, cost, or risk that is off plan, along with each decision the committee must make and its deadline. A member who reads only the top should still know what needs them. Keep it short, and move everything else into the detail below.

Status.net's guide advises leading with exceptions in the same way. Write each item in this pattern:

[Milestone, risk, or cost] is [status]: [short reason]. The committee needs to decide [decision] by [deadline], because [what waits].

Include only items that changed since the last update or that need the committee's help. Put the summary above the health rating, so it is the first thing a member reads.

How do you set the health rating?

Set the health rating by agreeing what green, yellow, and red mean with the sponsor or committee chair before the next update. Write those definitions at the top of every update, so members read the rating the same way each cycle. The reviewed guides give no numeric thresholds, so the rules come from your project.

Status.net describes a RAG health indicator in its executive summary. CornerStone Dynamics' guide uses a stoplight in which yellow means the team is handling a risk and red asks the committee for help. Those are rules about who acts, so treat them as a starting point.

  1. Ask the sponsor or committee chair to agree the definitions for green, yellow, and red before the next update.
  2. Write the definitions at the top of every update using this pattern:
Green: [what green means for this project]
Yellow: [what yellow means, including risks the team is handling itself]
Red: [what red means, including any decision or help the team needs from the committee]
  1. Rate the overall project and each workstream in the same words. If a rating changed since the last update, name the rule that changed it.
  2. Let a red item set the overall rating, so the summary never shows green above a red item in the detail.

Once the sponsor has agreed the definitions, members can check each rating against them without asking what it means.

What belongs in the milestone and budget section?

The milestone and budget section lists each milestone that moved, with its planned date, current forecast, and status, then shows budget planned, actual, and forecast at finish with the variance and its cause. Lead with any milestone that moved and any cost that now differs from plan, in the same units and period as the last update.

Slidemodel's guide lists project progress and a financial update as separate sections of a steering deck, so keep that split in the written update. Tie progress to milestones a member can check. A percentage complete on its own tells a member little.

Milestone: [milestone name]
Planned: [date]. Current forecast: [date]. Status: [green, yellow, or red].
Reason if not green: [short reason]

Budget to date: planned [amount], actual [amount], forecast at finish [amount].
Variance: [amount], because [cause].

Use the status words from your rating rule, and take the planned and forecast dates from the project plan.

How do you show risks the committee can act on?

The risks section of a steering update should show only the risks and issues the committee can help with or must know about to decide. Give each one an owner, an impact statement, the response under way with its date, and the help or decision needed. Risks the team can close alone belong in the project's own log.

Risk or issue Owner Impact Response under way Needed from committee
[risk or issue] [name] [impact] [action and date] [decision, help, or nothing]

Slidemodel's guide lists risks and issues as a section of a steering deck, and names problems without solutions as a common pitfall. Its appendix can hold the full log. Rows that still lack a response go back to their owner before the update is sent.

How do you write a decision for the committee?

A decision for the committee should be written as a question the committee can answer, with a deadline, the options, your recommendation, and the next step for each answer. Tactical Project Manager's guide recommends giving the background and the reason for any extra spending first, then the pros and cons of each option.

Decision needed: [question the committee can answer]
Deadline: [date], because [what waits if there is no answer]
Option A: [option], with [main benefit and main cost]
Option B: [option], with [main benefit and main cost]
Recommendation: [option], because [reason]
If approved: [next step, owner, date]
If not approved: [next step, owner, date]

Repeat the decision and its deadline in the summary of exceptions, so a reader who sees only the top still sees what is waiting.

How do you carry actions from the last update forward?

An update's actions list should carry every action and decision from the previous update, with its owner, due date, and status. Keep each open or overdue item until someone closes it, and mark a closed item with what was done. CornerStone Dynamics' guide suggests following up with an email of decisions after the meeting.

Tactical Project Manager's guide covers minutes and the follow-up work after each meeting. Send the decisions to members in a short email, and copy the same items into the actions list so the two match.

Actions from the [date] update
- [action], owner [name], due [date], status [done, open, or overdue]. [What changed.]

Decisions recorded at the [date] meeting
- [decision], agreed [date], follow-up owner [name].

Start the next update from this list, not from memory.

How often should the update go out?

The written update should go before each committee meeting, on the cadence the chair sets and on the same day each cycle. Tactical Project Manager's guide advises sending slides at least a week ahead of a decision meeting, and Slidemodel's FAQ suggests sending a deck two to three days ahead.

The two sources describe different formats. A written update is decision material, so ask the chair whether it should go out earlier than any deck.

  1. Ask the chair which day the update should go out, for example [day] before each committee meeting.
  2. Send the written update first, and any deck on the day the chair agrees.
  3. Use the same send day each cycle, so members know when to look for it.

Agree a page limit for the body with [chair name], such as [number] pages, and move the full risk log and budget lines to an appendix.

Who should receive the update?

The update should go to committee members and to anyone the chair names, and not be forwarded further without the chair's agreement. Keep individual performance, personnel matters, and contract terms out of the shared body. The reviewed guides do not cover distribution, so confirm the list with the chair.

If one item should not reach every member, raise it with the chair in a separate note and leave it out of the shared body. The rest of the update stays the same for everyone.

How do you tailor the update for each member?

Tailor the order and depth of detail for each committee member, but keep the facts and ratings the same for everyone. Name each member's role beside the first thing they must act on. Slidemodel's guide names ignoring audience priorities as a common pitfall.

[Chair name], chair: needs the decisions list first.
[Finance member name], finance: needs the budget variance and its cause first.

Write these lines before drafting the summary of exceptions, so the top of the update suits the first person who reads it.

What does one milestone line and one risk row look like?

A milestone line and a risk row show how one item carries its status, owner, and response into the update. Every name, date, and amount below is a placeholder that describes no real project, so replace each bracket with your own facts before you copy a line.

Milestone line:

Milestone: [milestone name]. Planned [date]. Current forecast [date]. Status: yellow.
Reason: [risk name] is open, [owner name] is handling it, and the committee does not need to decide anything yet.

Risk row:

Risk or issue Owner Impact Response under way Needed from committee
[risk name] [owner name] [impact] [response and date] Nothing yet

To read the status, work through the rule you agreed:

  1. Rate the milestone yellow only while the team handles the risk and the committee needs to decide nothing yet. CornerStone Dynamics' guide uses yellow for that case.
  2. If the response later needs a committee decision, move the item into the decisions list with its deadline.
  3. Rate it red under your rule, and let it set the overall rating.

Copy a line only after its last bracket is replaced.

Which mistakes make a steering update fail?

These faults make a steering update hard to act on: an overall green above a red item, decisions named only at the bottom, prior actions dropped, and problems without responses. Check the draft against each sign below before it goes out.

  • Overall green above a red item. Sign: the summary says green while a milestone or risk row is red. Fix: apply the rule in the health rating section.
  • Decisions named only at the bottom. Sign: the summary of exceptions names no decision and no deadline. Fix: put each decision and its deadline in the summary, then give the full block in the decisions section.
  • Prior actions dropped. Sign: the update lists only new items. Fix: carry every open and overdue item forward.
  • Problems without responses. Sign: a risk row has an owner and impact but an empty response cell. Fix: add the response and its date, or move the item to the project log.

Slidemodel's guide lists overloading slides, ignoring audience priorities, and problems without solutions among common pitfalls. Read the draft once against these signs, then send it to the chair.

What should the complete update look like?

A complete update follows the same section order each cycle: summary of exceptions, health rating, milestones, budget, top risks, decisions needed, then actions from the last update. Members then find each part in the same place. Every name, date, and amount in the block below is a placeholder.

This is a fill-in template, and no name, date, or amount in it is real.

Subject: [project name] steering committee update, [date]

Summary of exceptions
[Milestone or risk name] is [status]: [short reason]. The committee needs to decide [decision name] by [deadline], because [what waits].

Health rating: [green, yellow, or red]
Green: [definition]
Yellow: [definition]
Red: [definition]
Overall: [rating], because [rule applied, including any red item].

Milestones
Milestone: [milestone name]. Planned [date]. Current forecast [date]. Status: [status].
Reason if not green: [short reason]

Budget
Budget to date: planned [amount], actual [amount], forecast at finish [amount].
Variance: [amount], because [cause].

Top risks and issues
[Risk name], owner [name], impact [impact], response under way [action and date], needed from committee [decision, help, or nothing].

Decisions needed
Decision needed: [question]
Deadline: [date], because [what waits].
Option A: [option]. Option B: [option].
Recommendation: [option], because [reason].
If approved: [next step, owner, date]. If not approved: [next step, owner, date].

Actions from the [date] update
- [action], owner [name], due [date], status [done, open, or overdue]. [What changed.]

Copy the block, keep its order, and replace every bracket with your project's facts.

What should you do before the next update?

Ask the sponsor or committee chair to agree your rating definitions in writing before the next update. A short note with your draft definitions and a reply date is enough to start, and the reply then becomes the record for your rating rule.

Subject: Rating definitions for the [project name] steering committee update

[Sponsor name], before the next update I would like agreement on what each rating means. My draft:

Green: [draft definition]
Yellow: [draft definition]
Red: [draft definition]

Please confirm, or tell me what to change, by [date].

Send it to [sponsor name] once every bracket is filled in, and keep the reply with your rating rule so members can see what changed and when.

Questions people ask

Should the update be a slide deck or a written document?

[Slidemodel's guide](https://slidemodel.com/steering-committee-presentations/) sets out sections for a steering committee deck, and the same parts work as a written update sent before the meeting, so meeting time can go to decisions. If the chair also wants a deck, send it on the day the chair agrees and use the same section order in both. Confirm the format with the chair before you prepare either one.

What if the sponsor already uses a different rating scale?

Use the scale the sponsor already knows, and write its definitions at the top of the update the same way you would any other rating. If the rule changes, say so in the update so members can compare it with the last one.

What if the committee has not decided by the deadline?

Restate the deadline and what waits in the summary of exceptions of the next update. Ask the chair to put the decision on the next agenda with a named date, and keep it in the actions list with an owner and due date until someone closes it.

What if a member asks for more detail than the update holds?

Offer the detail in an appendix, or in a short follow-up the chair agrees to, rather than adding it to the shared body. Members should see the same ratings and facts, so the answer stays consistent for everyone.

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.