Skip to content
QuietNoteJoin the beta

Team meeting minutes template for weekly meetings

Last updated

This team meeting minutes template is for the weekly meeting of a single team with one manager: the meeting where last week is reviewed and this week is planned. It runs from wins to metrics to blockers, then decisions, then the priorities for the week, with a parking lot for everything that came up and did not belong. The minutes are short on purpose. The team was in the room; the record is for the person who was not, and for the team itself in three months when it asks why a decision was made.

Download the Word file, copy the plain text, or read the example from a marketing team at a software company first.

Word file (.docx), free and without signing up. Opens in Google Docs and Pages too.

What’s in the template

The minutes open with these details:

  • Team
  • Week of
  • Date and time
  • Location (or video platform)
  • Facilitator
  • Notes by
  • Present
  • Absent

Then the body follows the meeting in this order:

  1. 1. Wins from last week — Two or three concrete things that shipped, closed or landed. Name who did them.
  2. 2. Metrics and status — The three to five numbers the team is measured on, with last week's figure and the target. Note the trend, not the whole dashboard.Metric: · Last week: · Target: · Note:
  3. 3. Review of last week's priorities — Each priority from the previous minutes: done, carried over or dropped. Carried-over items need a reason.
  4. 4. Blockers — Anything stopping work, who is blocked, and who is taking it away. If it cannot be solved by the team, record who will escalate it.Blocker: · Blocking: · Owner:
  5. 5. Decisions — One line each: what was decided and, if useful, why. Decisions made outside the meeting during the week can be logged here too.
  6. 6. Priorities for this week — Three to five, in order, each with an owner. If everything is a priority, nothing is.
  7. 7. Announcements and upcoming — Leave, deadlines, launches, people joining or leaving, meetings with other teams.
  8. 8. Parking lot — Topics raised that need their own conversation. Record the topic and who will set up the conversation.

At the end: action items and decisions log, as tables you can keep across meetings.

The template

Download it as a Word file, or copy the text version into your own document.

Weekly Team Meeting Minutes

Team: 
Week of: 
Date and time: 
Location (or video platform): 
Facilitator: 
Notes by: 
Present: 
Absent: 

1. Wins from last week
   [Two or three concrete things that shipped, closed or landed. Name who did them.]

2. Metrics and status
   [The three to five numbers the team is measured on, with last week's figure and the target. Note the trend, not the whole dashboard.]
   Metric:
   Last week:
   Target:
   Note:

3. Review of last week's priorities
   [Each priority from the previous minutes: done, carried over or dropped. Carried-over items need a reason.]

4. Blockers
   [Anything stopping work, who is blocked, and who is taking it away. If it cannot be solved by the team, record who will escalate it.]
   Blocker:
   Blocking:
   Owner:

5. Decisions
   [One line each: what was decided and, if useful, why. Decisions made outside the meeting during the week can be logged here too.]

6. Priorities for this week
   [Three to five, in order, each with an owner. If everything is a priority, nothing is.]

7. Announcements and upcoming
   [Leave, deadlines, launches, people joining or leaving, meetings with other teams.]

8. Parking lot
   [Topics raised that need their own conversation. Record the topic and who will set up the conversation.]

Action items
No. | Action | Owner | Due | Status

Decisions log
Date | Decision | Context

What a weekly team meeting is for

A team meeting has two jobs: everyone leaves knowing the same facts, and the week's priorities are agreed in public so they stick. Everything else, including status updates that could have been a message and problem-solving between two people, is better done elsewhere. The template reflects that: the metrics and review sections are about shared facts, the priorities section is about commitments, and the parking lot is where everything else goes.

If the meeting regularly runs over, it is usually because the blockers section has become a problem-solving session. Record the blocker and an owner, and let the owner solve it after the meeting with the people who need to be involved.

What team meeting minutes must record

  • The metrics as stated in the meeting, so a later disagreement about the numbers can be settled by the minutes.
  • Every decision, in one sentence, with the date. A decisions log running across weeks is the most valuable artefact the meeting produces.
  • Priorities with a named owner. Next week's review of them is only possible if they were written down this week.
  • Blockers and who owns clearing them. A blocker that stays on the list for three weeks is a signal the manager needs to act.
  • Who was absent, so they can be pointed to the minutes rather than briefed one by one.

What to leave out

  • Individual status updates in full. One line per person at most, and only if it affects someone else.
  • The discussion that led to a decision. If the reasoning matters, one clause of context is enough.
  • Anything about a team member's performance or workload capacity. That belongs in a one-to-one.
  • Items that were parked. They go in the parking lot with an owner, not in the body of the minutes.

Running a decisions log

Keep the decisions table from every meeting in one running document, newest at the top, with the date and a line of context. New team members read it to understand why things are the way they are, and it ends the recurring conversation that starts with "didn't we already decide this?". If a decision is reversed, log the reversal rather than editing the original entry.

Example: filled-in team meeting minutes

What the template looks like once it’s been used. The organisation and people are made up.

Weekly team meeting minutes, Lumen Analytics marketing team

Week of: Monday 12 October 2026
Date and time: Monday 12 October 2026, 9:30 am to 10:05 am

Location: Video call

Facilitator: Nadia Karimi, Head of Marketing

Notes by: Owen Fletcher

Present: Nadia Karimi, Owen Fletcher, Isla Brennan, Ravi Shah, Theo Lindqvist

Absent: Chloe Martin (annual leave until 19 October)

1. Wins from last week

The pricing page redesign went live on Thursday (Theo Lindqvist, Ravi Shah). Trial sign-ups from the page were up 18% over the first four days against the previous four.

The data-governance webinar had 412 registrations and 196 live attendees (Isla Brennan), the highest live number this year.

2. Metrics and status

Marketing-qualified leads: 143 last week, target 150. Slightly under, with the webinar leads still being scored.

Trial sign-ups: 287, target 260. Over, helped by the pricing page.

Organic sessions: 21,400, target 22,000. Flat for three weeks.

Blog posts published: 2 of 2 planned.

3. Review of last week's priorities

Ship pricing page: done.

Run data-governance webinar: done.

Finish Q4 campaign brief: carried over. Ravi Shah is waiting on the product roadmap confirmation from the product team, expected Wednesday.

Brief the agency on the retargeting creative: done.

4. Blockers

The Q4 campaign brief cannot be finalised until product confirms which two features launch in November. Blocking Ravi Shah and, after him, Theo Lindqvist. Nadia Karimi to raise with the VP of Product today.

The marketing automation vendor has not fixed the lead-scoring sync that broke on 6 October. Blocking Isla Brennan's reporting. Isla Brennan owns the support ticket; escalation to the vendor's account manager if not fixed by Wednesday.

5. Decisions

The November newsletter moves from the first Tuesday to the second Tuesday so it can carry the feature launch.

The team stops producing the monthly PDF report for sales and instead shares the live dashboard, from November. Ravi Shah to tell the sales leads.

The organic-traffic plateau gets a dedicated session next week with Owen Fletcher and Isla Brennan, rather than being discussed in the weekly meeting.

6. Priorities for this week

1. Finalise the Q4 campaign brief once product confirms the launch features (Ravi Shah).

2. Score and hand over the webinar leads to sales by Wednesday (Isla Brennan).

3. Publish the two planned posts and the webinar recording page (Owen Fletcher).

4. Start the launch landing-page design once the brief is confirmed (Theo Lindqvist).

7. Announcements and upcoming

Chloe Martin returns Monday 19 October.

The quarterly marketing and sales review is Thursday 29 October; Nadia Karimi will circulate the deck for comments on Monday 26 October.

8. Parking lot

Whether to keep the review site listings subscription when it renews in December. Isla Brennan to bring a one-page summary of leads from it to the meeting on 2 November.

Organic-traffic plateau: separate session, Owen Fletcher to schedule.

Decisions log

Decisions log
No.DecisionOutcome
1November newsletter moves to the second TuesdayTo carry the feature launch
2Monthly PDF sales report replaced by the live dashboard from NovemberReport took a day a month and was rarely opened
3Organic-traffic plateau gets its own sessionToo big for the weekly meeting

Action items

Action items
No.ActionOwnerDue
1Raise the launch-feature confirmation with the VP of ProductNadia Karimi12 October 2026
2Score the webinar leads and hand over to salesIsla Brennan14 October 2026
3Tell sales leads the monthly PDF report is replaced by the dashboard from NovemberRavi Shah16 October 2026
4Schedule the organic-traffic sessionOwen Fletcher14 October 2026

Tips for team meeting minutes

  • Ask for metrics before the meeting and paste them into the template, so the meeting discusses the numbers rather than reading them out.
  • Review last week's priorities before setting this week's. The template puts them in that order for a reason.
  • Limit priorities to five. The minutes from a team with twelve weekly priorities are not read because they cannot be acted on.
  • Give every parked item an owner and a date it will be looked at, or it will be raised again next week.
  • Keep the decisions table in one running document across weeks; it is the thing a new team member will actually read.

Related templates

Or let the notes write themselves

A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.

Questions

What should team meeting minutes include?

Who attended, the key metrics as stated, the status of last week's priorities, blockers with an owner, every decision in one line, the priorities for the coming week with owners, and an action list. Keep discussion out; record what was agreed and who is doing what.

How long should a weekly team meeting be?

Thirty minutes is enough for a team of five to eight if metrics are shared beforehand and blockers are recorded rather than solved in the room. Larger teams or teams with many cross-dependencies may need 45 minutes. If it is regularly over an hour, something that belongs in a smaller meeting is happening in the big one.

What is the difference between team meeting minutes and a standup?

A standup is daily, a few minutes, and usually not minuted at all beyond a blockers list. A weekly team meeting reviews the week's numbers, makes decisions and sets priorities, and is worth a written record because those decisions and priorities will be checked against next week.

Who takes notes in a team meeting?

Rotate it, so the manager can run the meeting and everyone learns what a useful record looks like. The notes are short enough that the job is not a burden: metrics, decisions, priorities, blockers and actions. Whoever takes them sends the minutes the same day.

Can a team meeting be recorded with an AI note taker?

It can, and for a weekly meeting it mostly saves the note-taker from typing while people talk. The draft still needs someone to pull out the decisions and priorities into the template, since a transcript summary is not the same as an agreed list of commitments. Tell the team the meeting is recorded.

Notes without the bot.

QuietNote captures meetings from your own computer, so nothing joins the call. It’s in private beta — join to help shape the first version.

Private beta. No credit card.