A weekly review only works if prep fits inside a week. This template opens on what changed since last review, and Husn fills it so the meeting stays a review, not a rebuild.
Weekly review, the change since last week3 to know
A workstream that was on track last week now has two milestones at risk after a resourcing change.
Risk
A dependency flagged red last week is now resolved, freeing the integration milestone.
Changed
A decision logged last week has not produced any movement on the board since.
Watch
Week over week - 3 items moved - 1 newly at risk
The problem
Weekly program review template
A weekly program review is supposed to be a quick read on what moved and what is now at risk. In practice, preparing it weekly means re-reading every workstream every seven days, which nobody sustains, so the review degrades into a live status meeting that runs long and decides little.
Weekly cadence means weekly prep, and the reading required does not shrink just because the meeting is recurring.
By week three, prep is being skipped, and the review turns into the same verbal status tour it was meant to replace.
The week to week change, what slipped, what recovered, is exactly what a quick skim misses and a review needs.
Why this gets hard at scale
Why weekly reviews are hard to sustain
01
A weekly meeting compounds, so unprepared prep becomes a standing weekly tax on the whole program team.
02
Comparing this week to last week by hand means holding two states in your head, which rarely happens accurately.
03
The more programs under review, the more each week's prep costs, so it is the first thing dropped when the week is full.
How Husn helps
Step 01Husn reads Jira, Slack, and docs and fills the review with what changed since last week, so you know the delta before the meeting starts.
Step 02It compares this week to the last review automatically, surfacing what slipped, what recovered, and what newly went at risk.
Step 03Everyone gets the same filled review ahead of time, so the weekly meeting opens aligned and closes on decisions.
Husn reads and reasons, and never changes your tools.
What is inside
The sections, in the order leaders read them.
01Change since last review, the week over week delta at the top.
02Status by workstream, where each stream stands and what moved.
03Risks and blockers, what newly went at risk and what cleared this week.
04Dependency status, the cross team handoffs that shifted in the last seven days.
05Decisions and actions, what was decided last week and whether it moved.
06Asks for the room, the calls this week's review needs to make.
Connect your stack and Husn will fill your weekly review for the next meeting in about fifteen minutes, so you know what changed since last week before it starts.