Weekly Team Meeting
A structured weekly that ends on time, with decisions and commitments instead of vibes.
Free, no sign-up. Editable, copy as Markdown, plain text, or calendar.
Pick a duration
Before the meeting
- Ask the team to submit topics 24 hours ahead
- Cap topics at two. Everything else goes async
- Share the agenda and any pre-reads the day before
After the meeting
- Post a three-line recap in the team channel
- Capture commitments and owners in a shared doc
- Unblock anyone who surfaced a blocker within 48 hours
More agenda templates
About the weekly team meeting agenda
A weekly team meeting is one of the most predictable ways to destroy an hour of your team's time. It is also one of the most powerful routines for keeping work aligned, if the agenda is tight and the facilitator holds the line. The structure below treats the meeting as two decisions, one set of numbers, and a place to name blockers, nothing else.
How long should a weekly team meeting be?
Thirty minutes for most teams, weekly. Sixty minutes is almost always a sign that the agenda is carrying work that should be async. If you cannot fit the week into thirty minutes of live conversation, it is worth asking whether some of that conversation belongs in a doc or a Slack thread instead.
Who should run it?
Whoever is best at holding the line on time. That is not always the most senior person. Some teams rotate the facilitator role because it builds the muscle across the team and keeps the format from getting stale. The facilitator's job is to run the clock, not to dominate the conversation.
What kills a weekly meeting?
Status updates. If the weekly turns into each person reciting what they are working on, you are using thirty minutes of live time to do something a shared doc can do in two. Move status async and reserve the weekly for decisions, alignment, and the things that only work in real time.
How do you handle topics that do not get covered?
Capture them in a parking lot doc. At the end of the meeting, the facilitator reviews what made it and what did not. Items that were parked either get scheduled as a separate working session, moved to async, or dropped. Nothing just rolls to next week's agenda by default.
Frequently asked
- How long should a weekly team meeting be?
- Thirty minutes is the right default. Longer than forty-five minutes and the agenda is almost certainly carrying work that should be async. Shorter than twenty minutes and you run out of space for any real discussion.
- Should we have a weekly team meeting at all?
- If your team sees each other informally and decisions are moving fine async, you probably don't need one. If decisions are stalling, if the team is cross-functional or distributed, or if you notice misalignment more than once a month, a weekly catches those before they compound.
- What goes in a weekly team meeting agenda?
- Two decisions or discussions, three to five key metrics, a quick round for blockers, and time for commitments. Status updates don't belong in a weekly team meeting. Move them to a shared doc or async thread and protect the meeting for decisions.
- How do we keep the meeting from running long?
- Cap the agenda at two real topics, set block durations ahead of time, and empower the facilitator to cut conversation when a block's time is up. Topics that need more time are scheduled as separate working sessions. Running long every week trains the team to treat the clock as negotiable.
When to use this template
A weekly meeting for a standing team of 4 to 10 people. If the team is smaller, go async. If it's larger, split the meeting in two.