Steering Committee Presentation Maker That Turns Your Status Report Into a SteerCo Deck

What should be included in a steering committee presentation?

A steering committee presentation should include six things: the decisions you need from the committee, overall status against scope, schedule and budget, milestones hit and missed since the last meeting, the top risks and issues with owners, the budget position, and the plan for the next period. Put the decisions first. Sponsors give a project thirty minutes a month, and the reason the meeting exists is the handful of calls only they can make.

What does not belong is the working detail: the full RAID log, the task list, the sprint board. Keep those in an appendix or in the speaker notes, where you can reach them when a sponsor asks. A status report written for the project team usually contains all six items already, in a different order and with far more detail than a sponsor wants. That reordering and trimming is the work DocSlide does.

What is a SteerCo deck?

A SteerCo deck is the slide pack a project or program manager presents to the steering committee, the group of senior sponsors who approve scope, budget and schedule changes. It is shorter and more decision-led than a team status report: usually 8 to 12 slides, one message per slide, with red, amber and green status and a clear ask. Consultancies often call the same thing a SteerCo pack.

Steering committee presentation example, slide by slide

This is the outline most PMOs settle on for a monthly project steering committee meeting. Ten slides fill a thirty to forty-five minute slot with room for discussion.

1. Decisions needed today. Two or three, each with the options and the recommendation.
2. Executive summary. Overall status in one line, and what changed since last time.
3. Status by workstream. Scope, schedule, budget and resources, each rated red, amber or green with one line of reason.
4. Milestones. What was due, what landed, what moved and by how long.
5. Budget. Approved, spent, forecast at completion, and the variance.
6. Top risks. Five at most, with owner, mitigation and the date it gets worse.
7. Open issues. What is blocked and who can unblock it.
8. Change requests. The scope or date changes that need approval, with their cost.
9. Next period. The milestones due before the next meeting.
10. Actions from last meeting. Closed, open, overdue.

If your status report has headings close to these, the generated deck follows them closely. If it is one long narrative, expect to move a slide or two after the draft arrives.

How to turn a project status report into a steering committee deck

Write the status report once, as a document, then generate the deck from it. Save it as a PDF or Word file up to 20 MB, upload it, and read the draft against the source: every slide sits beside the section it was built from, so checking a date or a forecast takes seconds. Then open the .pptx in PowerPoint, apply the company theme from the Design tab, move the decision slide to the front if your report buried it, and color the status cells. Red, amber and green ratings arrive as the words your report used, in editable text, not as traffic-light graphics.

Most of the time the report starts in a work management tool, and the export from that tool is the input. The route from each one is written up separately: monday.com to PowerPoint, Jira to PowerPoint, Smartsheet to PowerPoint and Confluence to PowerPoint. A report that already lives in Word goes straight through Word to PowerPoint. Budget tables reach the slide as figures in text, which is explained on how your numbers reach the slide; there are no chart objects, so add a burn-down or a Gantt view in PowerPoint where one earns its place.

Steering committee presentation template or a deck built from your report

A template gives you ten empty boxes and a color scheme. You still read the status report, decide what a sponsor needs, and type it in, every month. That is fine for a single project. It stops being fine for a PMO that runs eight programs, each with a monthly SteerCo, because the hours go into moving words between two files that say the same thing.

A deck built from the report starts with the boxes filled, in your words, and you spend the time on what a sponsor will challenge. The two approaches work together: keep your approved template as a .potx and apply it to each generated deck, so the layout the committee is used to stays the same. The same flow covers the meetings on either side of the SteerCo, from the project kickoff presentation built from the statement of work to the executive briefing and the quarterly board deck.

How often should a steering committee meet?

Most project steering committees meet monthly, and large programs in a critical phase meet every two weeks. Quarterly is common for portfolio-level committees that oversee many projects. The cadence matters for the deck: a monthly SteerCo means twelve decks a year per project, which is why PMOs standardize the structure and stop building each one by hand.