Steering committees exist to make decisions. This template puts the decisions, escalations, and dates up front, and Husn can fill it from the work so prep stops eating your week.
Most steering updates are a status deck wearing a governance hat: lots of green RAG dots, a wall of progress, and the one decision the committee actually convened to make hidden on slide eleven.
The committee spends its time being briefed on progress instead of resolving the items only it can resolve.
RAG colors get set by whoever owns the slide, so amber becomes green under pressure and nobody trusts the dots.
Escalations that needed the committee last month show up as a surprise this month, after the window to act has closed.
Why this gets hard at scale
Why this gets hard at scale
01
A standing committee meets on a cadence, but risk does not, so the template has to surface what changed since last time, not just where things stand today.
02
Across a portfolio, each program lead formats their update differently, and the committee cannot compare apples that were prepared as oranges.
03
Filling the template honestly takes hours of chasing owners, so it gets done fast and shallow exactly when the program is under strain.
How Husn helps
Step 01Husn fills the template from Jira, Slack, and docs, so the agenda, RAG, decisions, and escalations arrive drafted rather than blank.
Step 02It grounds each RAG color in evidence and flags where the data disagrees with the rating, so green has to earn it.
Step 03It carries forward open decisions and aging escalations automatically, so nothing the committee owns quietly drops off the page.
Husn reads and reasons, and never changes your tools.
What is inside
The sections, in the order leaders read them.
01Agenda, the running order with the decision items placed before the progress review.
02RAG status, a color per workstream with the evidence behind each rating attached.
03Decisions needed, the specific choices that require the committee this session, with owners and options.
04Escalations, items that exceeded the program's authority, including how long each has been open.
05Risks, the active risks with likelihood, impact, and the change since the last session.
06Key dates, upcoming milestones and commitments, flagged where a date has moved.
Walk into the meeting with the template already filled, so prep is review and not assembly.
Cross-program governance
Give every program lead the same structure, so the committee can compare status across initiatives without translation.
Decision tracking
Keep open decisions and escalations visible from session to session, so accountability does not reset each month.
Who this is for
Built for the people who have to keep it all straight.
PMO leaders
Program and delivery managers
Chiefs of staff
VPs running multiple programs
FAQ
Questions, answered.
What is in the template?+
An agenda, RAG status by workstream, decisions needed, escalations, risks, and key dates. Each section is structured so the committee reads it the same way every time.
Can Husn fill it in for us?+
Yes. Husn reads your Jira, Slack, and docs and drafts each section, so the template arrives populated and traced to source rather than empty.
How does it handle RAG honestly?+
Husn grounds each color in evidence and flags where the status rating disagrees with the underlying data, so a green dot has support behind it.
Does it post the update anywhere?+
No. Husn drafts the update for you to use. It never writes back to Jira, Slack, or your documents.