Weekly Team Meeting Notes Template
The weekly meeting has one job: close loops
A daily standup surfaces blockers. A weekly team meeting does something slower and more valuable: it reviews what the team committed to last week, looks at the numbers that say whether the work is landing, and makes the handful of decisions that unblock the next seven days. Weekly notes fail when they become a diary of updates nobody acts on — lots of "worked on X," no record of what was decided, and last week's action items never mentioned again.
This template is built to close loops. It opens with last week's action items (reviewed before any new business), puts a small metrics snapshot at the top so discussion starts from the same facts, and ends with carry-overs — the items that stay visibly open instead of quietly expiring. Copy it into one running doc per team, newest entry on top.
The weekly team meeting notes template (copy and paste)
Blank template
# Weekly Team Meeting — [Team name] — Week of [date] **Facilitator:** **Note taker:** ## Metrics snapshot | Metric | This week | Last week | Note | |--------|-----------|-----------|------| | | | | | ## Last week's action items — review | Action | Owner | Status | |--------|-------|--------| | | | Done / Carried over / Dropped | ## Updates by owner - **[Name / area]:** ## Decisions made - Decision: … | Decided by: … ## Action items | # | Action | Owner | Due date | Status | |---|--------|-------|----------|--------| | 1 | | | | Open | ## Risks & blockers - Risk: … | Impact: … | Mitigation / owner: … ## Carried over to next week - ## Shout-outs -
Example: the template filled in
A growth team at a SaaS company, Monday morning. The example is deliberately ordinary — one metric moving the wrong way, one item carried over for the second week (which is information, not failure), and two real decisions.
Filled example
# Weekly Team Meeting — Growth Team — Week of Oct 20 **Facilitator:** Lena (rotating) **Note taker:** Omar ## Metrics snapshot | Metric | This week | Last week | Note | |--------|-----------|-----------|------| | Trial signups | 1,284 | 1,190 | +8%, driven by the comparison page going live | | Trial → paid conversion | 4.1% | 4.6% | Down — new traffic converts worse; investigate mix before changing onboarding | | Support tickets (trial users) | 96 | 81 | "How do I import recordings?" is now the #2 question | ## Last week's action items — review | Action | Owner | Status | |--------|-------|--------| | Publish onboarding checklist v2 | Omar | Done | | Interview 3 churned trial users | Lena | Carried over — 2 of 3 done, third rescheduled twice | | Add import help article | Sofia | Done — likely cause of ticket topic shift | ## Updates by owner - **Omar (lifecycle):** Checklist v2 live Thursday; early read: activation up slightly on the new cohort, too early to conclude. - **Sofia (content):** Import guide published; next: a "first recording" walkthrough video script. - **Lena (research):** Churn interviews point at one theme — teams trial during a busy week, never form the habit. Full notes in research doc. ## Decisions made - Decision: No onboarding changes until conversion dip is explained by traffic mix | Decided by: Lena, agreed by all - Decision: "First recording in 5 minutes" becomes the Q4 activation theme | Decided by: Lena ## Action items | # | Action | Owner | Due date | Status | |---|--------|-------|----------|--------| | 1 | Break down conversion by traffic source | Omar | Wed Oct 22 | Open | | 2 | Finish third churn interview + theme summary | Lena | Fri Oct 24 | Open | | 3 | Draft "first recording" video script | Sofia | Fri Oct 24 | Open | | 4 | Add import FAQ link into the empty-state screen | Omar | Mon Oct 27 | Open | ## Risks & blockers - Risk: Conversion dip is real, not mix | Impact: Q4 target at risk | Mitigation / owner: Omar's breakdown Wed decides; if real, we pull the onboarding experiment forward ## Carried over to next week - Churn interview #3 (second carry-over — if it slips again, Lena reassigns or closes it with 2 interviews) ## Shout-outs - Sofia's import guide cut "how do I import" tickets within days of publishing — the ticket rise is the *other* questions surfacing.
Two habits in this example are worth stealing. The carried-over item names what happens if it slips again — an escalation rule decided in advance, so a third slip triggers action instead of a third apology. And the metrics note for tickets resists the lazy reading ("tickets up = bad") because the update section explains the cause.
Facilitation rules that make the template work
- Review last week before discussing this week. Ten minutes, non-negotiable. A team that never looks back trains itself that commitments are optional.
- Keep the metrics snapshot small. Three to five numbers the team actually influences. A 20-row dashboard gets read by no one; three rows with a "note" column get argued about, which is the point.
- Updates are by owner, in writing first. Have each owner drop their update into the doc before the meeting. The meeting then spends its time on decisions and problems, not on serial monologues.
- Rotate the facilitator. It shares ownership of the meeting's quality and stops the team lead from being the permanent referee of their own meeting.
- End with carry-overs read aloud. Anything open crosses into next week's doc explicitly. The carry-over list is the team's institutional memory of what it keeps not doing — review it monthly for patterns.
How an AI note taker helps with weekly meetings
The weekly meeting is where AI notes earn their keep for teams: an hour of discussion, several decisions, and a dozen commitments is exactly the volume where human notes start dropping things. With CoHear, the meeting is recorded on an iPhone in the room — no bot joins if some attendees are remote — and you get the transcript and an organized summary back in about 65 seconds for a one-hour meeting. Decisions and action items with owners are extracted into the same shape as the template above, so the follow-up is pasting the reviewed draft into the running doc rather than reconstructing the meeting from memory.
The step not to skip: two minutes of human review on the decisions and the carry-overs. An AI draft that mislabels a discussion as a decision is worse than no note, because next week's review will hold someone to something they never agreed to. Use the verbatim quotes with timestamps when a decision is disputed — the recording is the tiebreaker.
If your team runs its whole cadence in this doc, pair it with the standup notes template for the daily layer, and see the general meeting notes template for one-off meetings. For how the notes feed the wider team's decisions and weekly reporting, see CoHear for teams.
FAQ
What should weekly team meeting notes include?
Five things: a small metrics snapshot, a review of last week's action items with honest statuses, updates by owner, the decisions made, and new action items with owners and due dates — plus a carry-over list so open items stay visible. If your notes lack the review of last week's items, they're a diary, not a management tool.
How long should a weekly team meeting be?
Forty-five to sixty minutes for most teams of five to ten. If updates are written into the doc beforehand, the live hour can be spent almost entirely on decisions, risks, and the one or two topics that need real discussion. Meetings that regularly overrun are usually update monologues in disguise.
What's the difference between a weekly team meeting and a standup?
A standup is daily, minutes long, and exists to surface blockers. A weekly meeting is longer and exists to review commitments, look at trends in a few key metrics, and make decisions. Teams that merge the two badly get a daily meeting that's too long and a weekly one that decides nothing.
Should weekly meeting notes be shared outside the team?
Share the decisions and action items widely; think twice about the rest. Stakeholders benefit from knowing what was decided and what's blocked. Raw discussion notes and shout-outs are team-internal by nature. A good default: the doc is visible to the company, but the team writes knowing that — which also improves the notes.
