Weekly team meeting agenda template (45 minutes)

A weekly meeting fails when it becomes a catch-all of status reports with no clarity on what matters or who decides. Priorities are set before blockers are raised, so that when something is stuck the room already knows whether it is stuck on the thing that matters.

Topic Minutes Running total
Wins and check-in Two minutes each, or skip if the team came from daily standups. The tone sets here. 5 5
Metrics Five minutes on the numbers that matter: revenue, volume, quality, velocity. Then move on. 10 15
Priorities this week What the team executes on starting now. Be specific about owners; if no one owns it, it doesn't happen. 15 30
Blockers and decisions Problems needing the group and decisions that move the week forward. Record who decides by when. 10 40
Actions and close Confirm who does what by when. Read the list back. Then stop. 5 45

Open this agenda in BriefMe:

Opens a working agenda you can start straight away. Nothing to sign up for — anonymous agendas are kept for 7 days.

Build it with your assistant

Already connected to BriefMe? Paste this. Connect BriefMe to Claude

Using BriefMe, create a 45-minute weekly team meeting for eight people: a 5-minute opening with wins, 10 minutes on metrics, 15 minutes on priorities, 10 on blockers and decisions, and 5 to close with actions.

Questions

How long should a weekly team meeting be?
Forty-five minutes is the usual span for a team of eight to twelve and aligns with a weekly calendar slot. Many smaller teams do well in thirty minutes; larger ones might push to an hour if they have multiple priorities to align.
What if we have nothing to talk about?
Then you probably do not need a weekly—consider meeting every other week or moving to asynchronous updates. But if you are shipping something, you have a priority this week, even if it is 'carry over what is working'.
Should we include customer feedback in this meeting?
If it shapes this week's priorities, yes. Otherwise, save it for a separate monthly review. The weekly works best when it stays focused on what the team controls and delivers, not a report from downstream.

Related templates