Oria
HomeResourcesGuidesAndrew PershAugust 1, 202610 min read

Steering Committee Template: What a Good Pack Looks Like

The six sections a steering committee expects, exactly what belongs in each one, the mistakes that make a pack hard to trust, and a working template plus the prompts to build it fast.

30,000+ consultants, bankers, private equity professionals

Free skills and prompts for Claude and strategy work

Templates for Claude, ChatGPT and Perplexity — from diagnostics to board-ready decks.

How to structure a steering committee pack

A steering committee pack should run in six sections: cover and agenda, overall status, progress by workstream, risks and issues, decisions needed, and an appendix. Use this steering committee template as the standing order for every meeting. Rate the whole program before rating any single workstream, and state every decision in the exact words the committee is asked to approve.

This guide walks each section, what goes in it, the mistakes that erode a committee's trust in the pack, a working template you can copy slide by slide, and the prompts that build it fast. Everything you need is here. You will not have to leave to get the substance.

What a steering committee pack is and when it goes out

A steering committee pack is the set of slides circulated to sponsors and workstream leads ahead of a steering committee meeting. It gives everyone the same starting point: the overall delivery status, progress by workstream, the risk position, and the specific decisions on the agenda. A good pack lets a member arrive with a view already formed. A poor one forces the room to read cold, which slows the meeting and weakens the decisions it produces.

Most steering committees meet every two to four weeks while a program is active, tightening around major milestones. Send the pack far enough ahead, two or three working days, for members to read it and raise questions before the meeting rather than during it. The overall status rating deserves the same discipline used in a well-built board pack: stated once, up top, with a clear one-line reason, not rebuilt from scratch each cycle.

The structure of a steering committee pack

Six sections carry a steering committee pack from status to decision, in that order. Get the order right and a sponsor can read only the first two sections and still know exactly where the program stands.

Steering committee pack template structure: six sections from cover and agenda through overall status, workstream progress, risks and issues, decisions needed, to the appendix

1. Cover and agenda. Meeting title, date, and the pack's version number.

2. Overall status. One RAG rating for the whole program, not just for each workstream.

3. Progress by workstream. Milestones hit and milestones missed against the plan.

4. Risks and issues. The top risks, ranked, with an owner and a trend arrow.

5. Decisions needed. The exact wording of each decision the committee is asked to make.

6. Appendix. Detailed workstream backup and supporting analysis.

What goes in each section: the contents checklist

Use this as a build checklist. For each section, confirm the three items below are present before the pack goes out. If one is missing, that is usually the gap a sponsor will ask about first.

1

Cover and agenda

Meeting title, date, and the pack's version number
The agenda, in the order items will be discussed
Open actions carried over from the last meeting, so nothing gets dropped silently
2

Overall status

One RAG rating for the whole program, not just for each workstream
A one-line reason behind the rating
What changed since the last meeting, not the full history again
3

Progress by workstream

Milestones hit and milestones missed against the plan
A RAG rating and a trend arrow for each workstream
What each workstream needs from the committee, if anything
4

Risks and issues

The top risks, ranked, with an owner and a trend arrow
Issues that have crystallized since the last meeting, kept separate from open risks
What moved: new, closed, or escalated
5

Decisions needed

The exact wording of each decision the committee is asked to make
The recommendation and the alternative considered, if one exists
Who owns the decision and what happens if the committee does not decide today
6

Appendix

Detailed workstream backup and supporting analysis
Prior meeting minutes and the full action log
Anything a member might ask for but does not need to read first

For the decisions needed and risk sections specifically, our Claude skills for board-ready decks include a risk heatmap and a decision-page skill that map directly onto sections four and five above.

Common mistakes to avoid

Opening with a workstream-by-workstream readout instead of the overall status, so members reach the detail before the headline.
No single owner for the overall RAG rating, so every workstream lead defends their own color and nobody owns the rollup.
Burying the decisions needed slide in the appendix instead of placing it right after the status summary.
Carrying the same risk on the register for several meetings running with no change in wording, owner, or trend.
Writing decisions in vague language instead of the exact resolution the committee is being asked to approve.
Sending a 40-slide pack for a 60-minute meeting, so nothing gets read closely before the room.

Most of these come down to one habit: writing the pack in the order the work happened instead of the order the committee needs to read it. Lead with the status, then the decision, then the support.

The one-prompt route: turn your program update into steering committee slides

Formatting a RAG rollup, a workstream grid, and a decisions needed slide by hand, on a strict corporate template, is exactly the kind of mechanical work that eats an afternoon before a steering committee meeting. Oria removes it. It is an AI add-in that runs in the PowerPoint task pane and produces fully editable native PowerPoint elements in your template. You describe each slide in a line and Oria renders it.

Because the output is native, every tile, row, and label stays editable afterward. You can update a milestone, reword a decision, or recolor a status flag the morning of the meeting without rebuilding the slide.

One-line overall status prompt for Oria

Build an overall status slide for a steering committee pack. Add a single large status dial showing [Green/Amber/Red] for the whole program. Below it, one bold line stating why: "[the one reason behind the rating]." Add a smaller line: "Since last meeting: [what changed]." Emphasize the status dial in the color of the rating.

The prompts that build the steering committee pack

These are the exact copy-paste prompts we use to build the highest-stakes slides in a steering committee pack and to draft the narrative behind them. The first three are for Oria inside PowerPoint; the last two are for drafting content in Claude before you build. Replace the bracketed parts with your own program details.

Build the slides in Oria

Build the workstream status grid

Build a workstream status slide with one row per workstream. Columns: Workstream, Status, Milestones hit, Milestones missed. Rows: "[workstream 1]" status [green/amber/red], milestones hit "[list]", milestones missed "[list]". Repeat for [workstream 2], [workstream 3], [workstream 4]. Color the status column to match each rating.

Build the risks and issues slide

Build a risks and issues slide with five rows. Columns: Risk, Owner, Trend, Status. Rows: "[risk 1]" owned by "[name]", trend [up/down/flat], status [new/unchanged/closed]. Repeat for four more risks: [risk 2], [risk 3], [risk 4], [risk 5]. Color the status column: orange for new, grey for unchanged, green for closed.

Build the decisions needed slide

Build a decisions needed slide. State one decision in exact wording: "[the committee is asked to approve X]." Below it, add a short section "Recommendation" with our proposed answer, and a section "Alternative considered" with the option we rejected and why. Emphasize the decision wording in the header band.

Draft the narrative in Claude first

Turn workstream updates into a status rollup

Here are this cycle's workstream updates: [paste notes from each workstream lead]. Roll these up into a single overall RAG rating for the whole program, with one sentence explaining the rating that a sponsor could read in five seconds. List which workstream, if any, is driving the rating down.

Summarize risk changes since the last pack

Here is our risk register from last cycle and this cycle: [paste both]. Identify what changed: new risks, risks that moved status, and risks that closed. For each change, give me a one-sentence explanation a sponsor could read in five seconds, and flag anything that needs a verbal update in the meeting rather than just the slide.

Tip

Draft the rollup and the decision wording in Claude, then hand the clean lines straight to Oria. If the program itself is a digital transformation, our Claude skills for digital transformation include a program-status rollup skill built for exactly this handoff.

A working steering committee pack template you can copy

Eight slides cover a routine steering committee pack. Copy this order, then add appendix pages behind slide eight for whatever the current cycle needs to support.

1

Cover slide. Meeting title, date, and pack version, nothing else.

2

Agenda slide. The items in discussion order with time allocated to each.

3

Overall status slide. One RAG rating for the whole program, the one-line reason, and what changed since last meeting.

4

Workstream status slide. A RAG rating and trend row per workstream, milestones hit and missed, with the one-line reason for any red or amber.

5

Risks and issues slide. The top five risks ranked by severity, each with an owner and a trend arrow.

6

Decisions needed slide. Each decision stated in the exact words the committee is asked to approve.

7

Actions slide. Open actions from the last meeting, each with an owner and a due date.

8

Appendix divider slide. A single page marking where the workstream backup detail begins.

A meeting carrying a major decision, a scope change or a go or no-go gate, will need more appendix pages, but the first eight slides above stay the same regardless of what the committee is being asked to decide.

Frequently asked questions

What is a steering committee pack?

A steering committee pack is the set of slides circulated to sponsors and workstream leads ahead of a steering committee meeting. It gives every member the same starting point: the overall delivery status, progress by workstream, the risk position, and the specific decisions on the agenda. A good pack lets a member arrive with a view already formed rather than hearing the update cold in the room.

What sections should a steering committee pack include?

Six sections cover most steering committee packs: cover and agenda, overall status, progress by workstream, risks and issues, decisions needed, and an appendix. Smaller programs can compress these into fewer slides, but the order, status first, then detail, then the decision, should stay the same.

How is a steering committee pack different from a board pack?

A steering committee pack tracks the delivery of one specific program or project: workstream progress, milestones, and program-level risk, for the sponsors and leads running it week to week. A board pack reports company-wide financial and strategic performance to directors who meet less often and sit a level above any single program. Our guide to board pack structure covers the board-level version of the same discipline.

How often should a steering committee meet?

Most steering committees meet every two to four weeks while a program is active, tightening around major milestones or decision points. Whatever the cadence, the pack should reflect only what changed since the last meeting, not the full history again.

What is the fastest way to build a steering committee pack?

Draft the narrative first: the overall RAG rating and its one-line reason, the workstream status rows, and the exact wording of each decision. Then describe each slide in one line and let Oria render it. You get a fully editable native PowerPoint deck on your corporate template, with the RAG rollup, workstream grid, and decisions-needed slide already laid out. You skip the manual formatting entirely.