A good update meeting agenda keeps the room on what moved and what needs deciding. This template does that, and Husn fills the update for you so the meeting starts informed.
Project update agenda, filled before the meeting3 to know
The API milestone slipped after a third party delay, and the downstream date has not moved to match.
Risk
A scope change was agreed in Slack last week but never reflected on the board.
Changed
Two tickets are blocked on the same review that has sat unactioned for four days.
Watch
Update ready - 5 items changed - 2 need a decision
The problem
Project update meeting template
Most project update meetings drift into a round of verbal status, where each person reports what they remember and the group spends the hour reconstructing the week. The agenda exists, but without the update written down ahead of time, the meeting fills with catch up instead of decisions.
A blank agenda still needs someone to gather the actual update, which usually happens out loud in the meeting.
Going person by person rewards whoever talks longest, not whichever change matters most.
Decisions get raised late, after the status tour has already eaten the hour.
Why this gets hard at scale
Why update meetings drift off the agenda
01
The more contributors in the room, the longer the status round runs, and the agenda gets abandoned in real time.
02
The genuinely important update is often the quiet one that no contributor thinks to raise in their turn.
03
Without a written update beforehand, every attendee is hearing the news for the first time, so the meeting moves at the pace of catching up.
How Husn helps
Step 01Husn reads Jira, Slack, and docs and fills the update section of the agenda, so the room knows what changed before the meeting starts.
Step 02It places the decisions and risks at the top of the agenda, so the meeting opens where it should.
Step 03Everyone receives the same filled agenda ahead of time, so the update round is read, not recited.
Husn reads and reasons, and never changes your tools.
What is inside
The sections, in the order leaders read them.
01What changed since last meeting, the update at the top so decisions get the time.
02Decisions needed, the calls this meeting exists to make.
03Risks and blockers, what is exposed and what is stuck right now.
04Dependencies, the cross team handoffs that moved or are at risk.
05Actions and owners, who is doing what by when, carried from last time.
06Asks for the room, what you need decided or unblocked before you leave.
Connect your stack and Husn will fill your update agenda for the next meeting in about fifteen minutes, so the room knows what changed before it starts.