What a great team meeting agenda includes
A recurring team meeting does not need a creative agenda; it needs a reliable one. The same six sections every week, timeboxed, in an order that puts the important things where the energy is. Predictability is the feature: when the team knows the shape, they arrive prepared for it.
| Section | Time | Why it’s there |
|---|---|---|
| Wins & headlines | 5 min | Starts on evidence things work; surfaces news once, to everyone |
| Carried-over actions | 5 min | Accountability without a lecture; stuck items get help, done items get skipped |
| Status round | 10 min | One line per project, blockers only; detail leaves the room |
| Open decisions | 15 min | The real work; timeboxed per item, decider named |
| Topics raised this week | 10 min | Triage: discuss now, park, or take offline |
| Actions & close | 5 min | Every new action restated with owner and date; feeds next week’s agenda |
The quiet insight in that structure: most of the agenda is assembled, not invented. Sections 2, 3 and 4 come straight from last week’s notes, the boards, and the decisions that did not close. Only section 5 is genuinely new each week.
Weekly team meeting agenda example
The six sections at work for a five-person team’s Thursday meeting:
TEAM MEETING AGENDA · Studio team · Thu 10:00, 50 min Purpose: keep client work unblocked, close open decisions Facilitator: Noor 1. WINS & HEADLINES (5) Fairview shipped early; new enquiry from the podcast. 2. CARRIED-OVER ACTIONS (5) Update the rate card → Sam → STUCK (needs pricing call) Send Whitlock the revised scope → Noor → done 3. STATUS ROUND (10) Fairview → shipped, invoicing this week → no blockers Whitlock → awaiting scope sign-off → blocked on client Website refresh → wireframes in review → no blockers 4. OPEN DECISIONS (15) Rate card pricing (parked twice) → options A/B circulated → decider: Noor, today. 15 min, hard stop. 5. TOPICS RAISED THIS WEEK (10) Summer cover rota (raised by Sam) → discuss now New CRM idea (raised by Jae) → take offline 6. ACTIONS & CLOSE (5) Restate every new action: owner + date, out loud.
Free team meeting agenda template (plain text, Google Docs, Notion)
Three ways to walk in with an agenda. The plain text pastes cleanly into Google Docs or Notion and reuses week after week.
The plain-text template
Six timeboxed sections, built to reuse every week.
TEAM MEETING AGENDA · [Team] · [Date, time, length] Purpose: [the one thing this meeting exists to do] Attendees: [names] · Facilitator: [name] 1. WINS & HEADLINES (5 min) What went well since last time; anything the team should know. 2. CARRIED-OVER ACTIONS (5 min) [Action from last meeting] → [owner] → [done / stuck / in progress] (Read the stuck ones aloud; skip the done ones.) 3. STATUS ROUND (10 min) [Project or area] → [one-line status] → [anything blocking] (One line each. Detail goes to a separate conversation.) 4. OPEN DECISIONS (15 min, timeboxed per item) [Decision needed] → [options on the table] → [who decides] 5. TOPICS RAISED THIS WEEK (10 min) [Topic] → [raised by] → [discuss now / park / take offline] 6. ACTIONS & CLOSE (5 min) Restate every new action with owner and date before leaving.
The AI prompt
Prefer to use your own AI? Copy this into Claude or ChatGPT with last meeting’s notes, and it builds the timeboxed agenda.
--- title: Team Meeting Agenda Generator description: A prompt that builds next week’s team meeting agenda from last week’s actions, open decisions and project status. author: readywhen source: https://readywhen.ai/team-meeting-agenda-template homepage: https://readywhen.ai license: CC BY 4.0 (free to use and share with attribution to readywhen) version: 1.0 updated: 2026-07-17 keywords: [team meeting agenda, meeting agenda template, staff meeting agenda, weekly team meeting] --- # Team Meeting Agenda Generator _By readywhen. Full guide + free template: https://readywhen.ai/team-meeting-agenda-template_ You are building the agenda for a recurring team meeting. A good agenda is mostly assembled, not invented: it carries forward what last week left open. ## Principles - Start from last meeting’s notes: unfinished actions and parked topics go on first, automatically. - Timebox every section and put a number of minutes next to it. The agenda is a budget. - Decisions get the most time and a named decider each. Status gets the least: one line per project, blockers only. - Anything raised mid-week goes in a "topics" section with a triage: discuss now, park, or take offline. - End with five minutes to restate new actions with owners and dates. This section is why next week’s agenda writes itself. ## Structure Wins and headlines · carried-over actions · status round (one-liners) · open decisions (timeboxed, named decider) · topics raised this week · actions and close. ## What I need from you Last meeting’s notes or actions (paste them) · the projects to cover · decisions currently open · anything raised during the week · meeting length. Ask for what’s missing, then build the timeboxed agenda. --- _Made by readywhen. readywhen assembles next week’s agenda from your own tools: carried-over actions, open decisions and project status, before you’ve thought about the meeting. https://readywhen.ai/team-meeting-agenda-template_
Let readywhen do itRecommended
A recurring agenda is mostly carried forward, which means it can write itself. readywhen assembles next week’s from last week’s notes, your channels and your boards, and posts it the day before the meeting.
Most of the agenda already exists in last week’s notes and your boards. readywhen assembles it in ~45 seconds, the day before, instead of the meeting starting with “so… what’s on for today?”
Let readywhen draft the agenda from your connected tools
Because a recurring meeting’s agenda is mostly carried forward, it is exactly the kind of document that should write itself, and with your tools connected, it does.
readywhen reads last meeting’s notes for unfinished actions, your channels for topics raised during the week, and your boards for one-line statuses, then builds the timeboxed agenda with the stuck items surfaced and the repeatedly-parked decisions scheduled with a named decider. It lands in the team channel the day before, which is the difference between a meeting and a huddle.
Works with your existing tools
Team meeting agenda FAQs
What should a team meeting agenda include?
Six sections: wins and headlines, carried-over actions, a one-line status round, open decisions (with the biggest timebox and a named decider each), topics raised during the week, and a closing five minutes to restate new actions with owners and dates.
How long should a weekly team meeting be?
Forty-five to sixty minutes covers a small team comfortably with the six-section structure. If it consistently runs over, the status round is doing too much talking or a decision is missing its timebox; both are agenda problems, not people problems.
Should I share the agenda before the meeting?
Yes, the day before. People make better decisions with a night’s notice, options can circulate in advance, and anyone whose item was triaged to “take offline” finds out before the room does.
How do I stop the same topics rolling over every week?
Track the parking. When a decision has been parked twice, it gets scheduled with a hard timebox and a named decider at the next meeting. Rolling topics are usually decisions nobody was asked to make.
Is there a team meeting agenda template for Google Docs or Word?
Yes. Copy the plain-text template on this page into Google Docs, Word or Notion, or download it as a file. All formats are free.
Can’t I just use ChatGPT or Claude to build my meeting agenda?
Yes. Paste last week’s notes and the prompt above, and you get a solid agenda. readywhen is the version with standing access to those notes, your channels and your boards, so the agenda assembles itself the day before without anyone pasting anything.
More templates for meetings that go somewhere
Meeting notes
The everyday record: takeaways, decisions and actions from your transcript.
Meeting minutes
The formal record: decisions, motions and actions, drafted from the transcript.
Project status report
RAG health, milestones and risks, assembled from your project tools.
Stop opening with “what’s on for today?”
Get your agenda free with readywhen
About the author and editorial standards
About the author. Sançar Şahin is co-founder and CMO of readywhen. readywhen catches everything you say you’ll do and helps you move it forward: drafted, chased or flagged, ready when you are. He builds readywhen in public on LinkedIn.
Editorial standards. No paid placements. The six-section structure and timeboxing conventions reflect common team-meeting practice rather than a single authority. How this page was made: Sançar built the multi-agent research and drafting system behind it, checks its work at several phases, and approves the final page himself. To flag an error, email hello@readywhen.ai.
Last updated: 19 July 2026.