A team meeting agenda should spend most of the time on what needs the whole team: problems someone is stuck on, decisions to make together, and who takes what this week. Collect updates in writing before the meeting and only discuss the ones that raise a question. Start by checking last week's action items, and end by reading back each new one with its owner and date.
Best forTeams of 3 to 12 people who work together every week
Meeting length30 to 45 minutes, weekly or every two weeks
Newest week at the top. Before each meeting, copy this block, fill in the date and move open items into carried forward.
Week of[date]AttendeesAbsentFacilitatorNotes by
Standing items
Number or check, this week vs. target
Calendar: next two weeks
Carried forward
ID
Item
Owner
Weeks open
Status this week
Done / Moving / Stuck on [what] / Dropped
New topics
Topic
Added by
What they need
Outcome
Decision / input / FYI
Decisions
Decision, as a full sentence
Action items
ID
Action
Owner
Due
Done looks like
Parking lot
Topic
Raised by
Target week or waiting on
Word MarkdownPastes into Google Docs, Word or Notion with headings and tables intact. Copied. Paste it into your document.
Harbor Outdoor customer support team, weekly meeting, March 9
Filled-in example
Harbor Outdoor customer support team, weekly meeting, March 9
DateMonday, March 9, 2026, 9:30 to 10:00PresentMaya Brooks (lead), Daniel Ortiz, Priya Shah, Tom Keller, Grace LinAbsentSam Wu (out until Wednesday)Run byMaya BrooksNotes byPriya Shah
Last week's action items
ID
Item
Owner
Status
Evidence or note
A1
Rewrite the returns FAQ
Daniel Ortiz
Done
Live since Thursday, March 5
A2
Ask the warehouse why tracking emails go out late
Maya Brooks
Moved to March 11
Meeting with the warehouse lead on Wednesday
A3
Try canned replies for size exchanges
Grace Lin
Done
Median first reply is down, see numbers
A4
Change the returns window on the website from 30 to 45 days
Sam Wu
Needs confirming
Sam is out until Wednesday and the page still says 30 days. Ask Sam directly.
Updates (written before the meeting)
Name
Finished
Next
Daniel Ortiz
Returns FAQ
Holiday shipping page, draft by Thursday
Priya Shah
Cleared the backlog of 40 old chat tickets
Training the two new weekend hires
Tom Keller
Fixed the order-lookup macro
Damaged-item claims with the carrier
Grace Lin
Canned replies for size exchanges
Same for late deliveries
Numbers
Number
This week
Last week
Note
Open tickets on Monday morning
112
164
Backlog cleared
Median first reply
3 h 10 min
5 h 40 min
Canned replies helped
Tickets about late tracking emails
31
29
Still the top reason people write in
Blockers
Blocker
Who's stuck
Who unblocks it
By
Can't issue refunds over $200 without a manager, and the manager is out Fridays
Tom Keller
Maya Brooks asks finance for a second approver
March 13
Decisions
Weekend coverage: Saturday only, with an auto-reply on Sunday.
Late-delivery canned replies: Grace drafts them, Daniel reviews before they go live.
Not decided yet
Sunday coverage after April. Maya decides at the April 6 meeting, once there are four weeks of Sunday ticket counts.
This week's priorities
Daniel: holiday shipping page
Priya: weekend hires trained by Friday
Tom: carrier damage claims
Grace: late-delivery replies
Maya: warehouse tracking emails, second refund approver
Action items
ID
Item
Owner
Due
Done looks like
A5
Ask finance for a second refund approver on Fridays
Maya Brooks
March 13
A named second approver, and Tom can issue refunds on Fridays
A6
Set up the Sunday auto-reply
Priya Shah
March 14
Auto-reply live and tested with one Sunday ticket
A7
Draft late-delivery canned replies
Grace Lin
March 12
Drafts in the shared doc
A8
Review the late-delivery replies
Daniel Ortiz
March 13
Replies approved and live
A9
Count Sunday tickets each week
Priya Shah
April 6
Four weekly counts in the team sheet
Harbor Outdoor and its support team are a fictional sample.
Hollis County Food Bank programs team, running doc
Running doc, filled in
Hollis County Food Bank programs team, running doc
Newest week at the top. Earlier weeks are below this entry.
Week ofNovember 16, 2026Notes byOwen Fitch
Short entry: what happened to the three items that were stuck or moving last week. The rest of this week's notes follow the same sections as the entry below.
ID
Item
Weeks open
What happened
C1
Replace the compressor on walk-in cooler 2
5, closed
Done. The second quote never came, so Victor took the first one ($6,800) on Nov 12. New compressor running since Nov 14.
C3
Recruit 40 extra volunteers for the Nov 21 distribution
3
Extended to Nov 19. 34 of 40 signed up. If it is still short, staff cover the last warehouse shift.
C4
Data-sharing agreement with the county
7, dropped
Dropped for this year. The county's legal review won't finish before January. Joanna restarts it in February.
VersionsNotes for each meeting, or one running doc with the newest week on top and a weeks-open count for each carried item
FormatsGoogle Docs, Word, Notion, Markdown
When to use this template
Your weekly team meeting has turned into a round of status updates that everyone half-listens to.
Decisions keep getting made in side chats, and half the team hears about them a week later.
Someone was stuck on the same problem for two weeks and nobody knew until it was late.
The same issue has been "in progress" for a month and nobody has noticed. The Running doc tab keeps every week in one document and counts how long each item has been open.
Questions people ask
What should be on a team meeting agenda?
Last week's action items, questions on written updates, the two or three numbers the team owns, blockers, decisions the team needs to make together, and who's on what this week. Finish by reading back the new action items. Anything that's only news can go in the written updates instead.
How is a team meeting different from a staff meeting or a standup?
A daily standup is a 15-minute check on today's work and blockers. A staff meeting covers what affects everyone working in one place, like schedules, coverage and policy changes. A team meeting sits between them: once a week or every two weeks, the people who work on the same goals look back, decide what needs deciding and split up the week.
Who should run the team meeting?
Usually the team lead, but it works well to rotate the note taker each week, so the lead can focus on the discussion. Some teams also rotate who runs it, which spreads the habit of keeping items to time.
What if there's nothing to discuss?
If the updates are in, nobody is blocked and there's nothing to decide, end early or cancel and say so in the channel. A short meeting that ends on time makes people more willing to come to the next one.
Should we keep one running document or a new document each week?
For a weekly team meeting, one running document with the newest meeting at the top works well: open items stay visible, and anyone can scroll back to see when a decision was made. That's the Running doc tab. Start a new document each quarter so it stays fast to load, and carry open items into it or into an action items tracker.
How do you stop the same items carrying forward every week?
Count the weeks. Once an item shows four or more weeks open, the meeting asks one question: fix what is blocking it, give it to someone else, or drop it on purpose. Writing the count down is usually enough to make people act.
What if an action item is not mentioned the following week?
Mark it "needs confirming" and ask the owner. Silence does not mean it is done, and after a few weeks unconfirmed items quietly disappear.