New Manager DailyTeam meeting agenda template (with filled-in examples)
A good team meeting agenda has five parts: one line on why you're meeting, a short round of updates, two or three topics to discuss with a time and an owner each, a few minutes to agree who does what next, and a parking lot for anything that comes up. Send it a day ahead, and put the topic that needs the group's thinking first, not last.
Below you'll find a blank template to copy, the same template filled in for a real-looking weekly meeting, versions for a 15-minute check-in, a monthly team meeting and a meeting about one problem, how to collect items from the team, how to decide what to cut, the invite to send, and what to do when the agenda falls apart halfway through.
The blank template (copy this)
Paste this into a shared document, an email or the calendar invite. Keep everything on one screen: if your agenda needs scrolling, the meeting is too long.
[Team name] meeting · [day, date] · [start]–[end] · [room or link]
Why we're meeting: [one sentence: what we'll decide or finish]
Before the meeting: [anything to read, with a link; "nothing" is fine]
1. Updates ([5–10] min): each person, one minute: done, next, stuck
2. [Topic] ([10–15] min, led by [name]): [the question we need answered]
3. [Topic] ([10] min, led by [name]): [the question we need answered]
4. Who does what next (5 min): [read back each action, owner and date]
Parking lot: [topics raised that we'll handle elsewhere]
Notes and actions: [filled in during the meeting by [name]]
Two things make this different from the agendas most people send. Each topic is written as a question ("Do we move the launch to March?"), not a label ("Launch"). A label invites a tour of the subject; a question tells everyone what they're there to answer. And each topic has one person leading it, so it isn't automatically you.
A filled-in example: a 30-minute weekly meeting
Here is the same template for a six-person customer support team. The names and topics are made up, but the shape is the one that works.
Support team meeting · Tuesday 10:00–10:30 · Room 4 / video link
Why we're meeting: agree how we cover the holiday week, and decide whether to change the refund reply.
Before the meeting: look at the holiday rota draft (link). Two minutes.
1. Updates (6 min): one minute each. Done, next, stuck.
2. Holiday week cover (10 min, Maya): two people are off on the 23rd. Who swaps, and do we need weekend help?
3. Refund reply (9 min, Sam): customers keep replying "so is it refunded or not?" Do we rewrite the template, and who tries the new one?
4. Who does what next (5 min)
Parking lot: (empty to start)
Notes and actions: Jordan
Notice what's left out: no "AOB" (any other business) slot that swallows the last ten minutes, no "manager update" that's really a ten-minute monologue, and no topic that only concerns two people. Those two can talk after.
What each part is for
| Part | Time | What it does | What goes wrong without it |
|---|---|---|---|
| Why we're meeting | 0 min (it's written) | Tells people what "done" looks like for this meeting | The meeting ends when the clock runs out, not when the work is done |
| Before the meeting | 0 min in the room | Moves reading out of the meeting | The first 10 minutes are someone reading a slide aloud |
| Updates | 1 min a person | Shows what everyone is doing; surfaces blockers | People learn about each other's work by accident, or not at all |
| Topics | 10–15 min each | The reason to meet: things that need several people thinking at once | The meeting is only updates, which an email could do |
| Who does what next | 5 min | Turns talk into actions with a name and a date | Everyone leaves agreeing and nothing happens |
| Parking lot | 0 min | A place for good points that aren't for today | Tangents take over, or good ideas get lost |
How long should the whole thing be? For a team of up to about eight, 30 minutes is enough for a weekly meeting. Granola's template guide suggests 20–45 minutes for 2–8 people and 45–60 for 9–15, which matches what most managers find. If you have more than three topics, you don't need a longer meeting; you need fewer topics.
Templates for other team meetings
A 15-minute weekly check-in
For teams that already talk all day and only need to line up.
1. One win from last week (3 min, anyone)
2. This week's priorities (5 min): the manager names the top three; anyone can challenge the order
3. Who needs help (5 min): each blocker gets an owner, solved after the meeting
4. Actions read back (2 min)
If your team meets every day, this is a stand-up, and it has its own shape: see our stand-up meeting format.
A monthly team meeting (60 minutes)
Once a month, step back from the week. This is where you look at how the team is doing, not only what it's doing.
1. The month in numbers (10 min, manager): three or four numbers the team cares about, last month vs this month, and what they mean
2. What's coming from above (10 min, manager): decisions or changes from your own boss that affect the team; questions welcome
3. One problem worth solving (20 min, a team member): the biggest recurring annoyance; agree one thing to try
4. Recognition (5 min, anyone): specific thanks for specific work
5. How are these meetings going? (5 min): keep, drop, change
6. Actions read back (10 min)
Item 4 matters more than it looks. Thanks said in front of the team lands differently from thanks in a private chat; our guide on how to give positive feedback to an employee covers how to make it specific instead of "great job, everyone."
A meeting about one problem
When something has gone wrong, or a decision is stuck, don't squeeze it into the weekly meeting. Give it its own 30–45 minutes.
Why we're meeting: decide [the question] by the end of this meeting.
1. The facts (5 min, whoever knows them best): what happened, what we know, what we don't
2. Options (15 min, everyone): at least three ways forward, written where everyone can see them
3. Choose (10 min): who decides is said up front: "I'll make the call, but I want to hear everyone first" or "we'll go with the majority"
4. Who does what next (5 min)
Saying who decides before the discussion, not after, saves you from the worst ending a meeting can have: the team thought they were voting, and you overrule them.
Your first team meeting as a new manager
That one is different: it's for trust, not tasks. Our guide on how to conduct your first team meeting has a 45-minute agenda written for it, with what to say if you were promoted from the team.
How to write the agenda, step by step
- Write the "why" line first. If you can't finish the sentence "By the end, we'll have…", you may not need the meeting this week. Cancelling a meeting with nothing to decide is a gift to the team, not a failure.
- Collect topics from the team. Keep the shared agenda document open all week and tell people: "Add anything you want the group's help with by Monday 5pm." Topics people add themselves get better attention than topics you assign.
- Turn every topic into a question. "Hiring" becomes "Do we hire one senior or two juniors?" If a topic can't be written as a question, it's probably an update and belongs in the updates round or an email.
- Put the hardest topic first. People think best in the first 15 minutes. Most agendas put the big item last, after updates have overrun, so it gets five rushed minutes.
- Give each topic a time and an owner. The owner opens it in one minute ("Here's the question, here's what I think, what am I missing?") and makes sure it ends with an action.
- Add up the times. If they're over the meeting length, cut (next section). Don't shorten every item a little; that just means every item ends unfinished.
- Send it 24 hours ahead, with anything people need to read attached. Two days ahead if there's a real decision.
What to cut when there's too much
Most agendas are too full. Here is a quick test for every item, in order:
| Ask | If yes |
|---|---|
| Is it only information, with nothing to decide? | Send it in writing. Ask for questions by reply. |
| Does it concern only two or three people? | Those people meet separately. |
| Is it waiting on facts nobody has yet? | Move it to next week; assign someone to get the facts. |
| Did it come up last week and nothing changed? | Find out why it's stuck before you bring it back. Usually nobody owns it. |
| Is it a one-person problem (performance, behaviour)? | Never in the team meeting. That's a private conversation. |
The invite and the reminder
A short message with the agenda pasted in, not attached, so people read it on their phone:
Subject: Tuesday team meeting: holiday cover and the refund reply
Hi all, agenda below for Tuesday 10:00. Two things to decide: who covers the 23rd, and whether we rewrite the refund reply. Please look at the rota draft before (two minutes, link). If you've got something to add, put it in the doc by Monday 5pm. Thanks.
Putting the two topics in the subject line does most of the work. People who only read subject lines still arrive knowing what the meeting is for.
Running it: keeping to the agenda in the room
- Open by reading the "why" line aloud. "We're here to decide two things. If we're done in 20 minutes, you get 10 back."
- Say the time out loud at each change. "That's ten minutes on cover. Maya, where did we land?" A visible clock helps; so does asking someone else to keep time.
- Use the parking lot. When a point is good but off topic: "That's a real one. I'm putting it in the parking lot so it doesn't get lost." Then actually handle it later, or the parking lot becomes a polite way of saying no.
- Close every topic with an action. "So: Sam rewrites the reply, tries it on Thursday's tickets, tells us next week." If there's no action, say so: "No change; we'll leave it."
- Read the actions back at the end. Each one with a name and a date. This is the five minutes people skip and regret.
For the people problems inside a meeting, the one who talks too much, the silence after every question, the endless tangent, our guide on how to run an effective team meeting has the words to use for each.
When the agenda falls apart
Updates overrun and eat the topics
Move updates to writing. Ask everyone to post three lines in the team chat before the meeting (done, next, stuck), and use the meeting only for topics and for the stuck items. Most teams that try this don't go back.
A topic turns out much bigger than planned
Stop and choose out loud: "This is bigger than ten minutes. We can keep going and drop the refund item, or we book 30 minutes on this tomorrow. Which is better?" Asking the room keeps you from quietly running over.
Something urgent arrives that isn't on the agenda
If it really can't wait, say so at the start and swap it in for the lowest item. Don't add it on top.
Nobody adds topics
Ask a specific question instead of "anything for the agenda?": "What's one thing that wasted your time this week?" Answers to that question are usually topics.
The same item comes back every week
It has no owner, or the owner doesn't have the power to act. Ask in the meeting: "Who owns this, and what do they need from me to finish it?"
Notes and actions afterwards
The agenda doubles as the notes page. During the meeting, the note-taker writes under each topic what was decided and the actions. Within an hour, send the whole page to the team (and anyone who missed it). Keep each week's page in the same document, newest at the top, so next week's agenda starts by checking last week's actions: "Sam, how did the new refund reply go?"
Rotate the note-taker. It's dull work, and if it always falls to the same person, people notice.
Common mistakes
- Topics as labels ("Budget") instead of questions.
- Your own update first and longest.
- No time next to items, so the first one takes everything.
- Sending the agenda five minutes before, or not at all.
- Bringing up one person's mistake in front of the group. If someone's work needs fixing, that's a private feedback conversation.
- Never asking the team whether the meeting is useful.
Not sure whether you'd run your meetings tight or let them drift? The free leadership style quiz takes about 2 minutes and tells you which habits come naturally to you and which take effort.
Questions about team meeting agendas
What should be on a team meeting agenda?
The purpose in one line, anything to read beforehand, a short updates round, two or three topics with a time and owner each, a few minutes for actions, and a parking lot. That's all most teams need.
How far ahead should I send the agenda?
24 hours for a regular meeting; two days if people need to read something or a real decision is on it.
How many topics should a team meeting have?
Two or three for a 30-minute meeting. More than that and each gets a few minutes, which is rarely enough to decide anything.
Should the manager always run the meeting?
You run the clock and the close; let others lead topics. Some teams rotate the chair each week, which also shows you who's ready for more responsibility.
What is "AOB" and should I keep it?
"Any other business": a slot at the end for unplanned items. Most teams do better without it. Use a parking lot instead, and ask people to add items to the document beforehand.
Is there a Word or Google Docs version?
Copy the blank template above into any document; it's plain text on purpose, so it works in an email, a calendar invite or a shared doc.
Next: take the free leadership style quiz to see which parts of running a team come easily to you, or browse all our guides for new managers.
Sources
- Granola, "Team meeting agenda template": https://www.granola.ai/blog/team-meeting-agenda-template
- MeisterTask, "Meeting agenda examples: 10 templates for every team meeting": https://meistertask.com/blog/meeting-agenda-examples-10-templates-for-every-team-meeting
- Smartsheet, "Free team meeting templates: agenda, minutes, and notes": https://www.smartsheet.com/content/team-meeting-templates