Meeting Agenda Template — Structure, Examples & Best Practices
A meeting without an agenda is a conversation waiting to go wrong. A shared agenda set clear expectations for everyone in the room — what's being decided, who's responsible for what, and what comes next. Preview the template below or use the interactive version in FigJam.
What is a meeting agenda?
A meeting agenda is a structured list of topics, time allocations, and owners that defines what a meeting is for, what it needs to accomplish, and how the time will be used. It's shared with participants before the meeting — not handed out at the start — so everyone arrives prepared rather than reactive.
A good meeting agenda does three things. It makes the meeting's purpose explicit: what decision is being made, what information is being shared, or what problem is being solved. It tells participants what to prepare: who needs to have read what, who's presenting, who needs to make a call before the meeting. And it creates accountability after: the action items, owners, and deadlines that come out of the meeting have a home in the same document that started it.
The meetings people complain about most — the ones that feel like a waste of time — are almost always the ones that started without a clear agenda. The ones people want more of are the ones where the agenda made it obvious why their presence mattered and what was expected of them.
See the Template in Action
Explore the template below to see how it's structured. To use the fully editable version, open it in FigJam, where you can copy, customise, and collaborate with your team.
How to write a meeting agenda that people actually use
Start with the purpose, not the topics
Before you list agenda items, write one sentence that answers: why does this meeting need to happen? "Quarterly review" is not a purpose — it's a label. "Agree on Q3 priorities and assign owners before the team meeting on Friday" is a purpose. When the purpose is clear, the agenda items follow naturally — and the ones that don't serve the purpose get cut.
Send it at least 24 hours before
An agenda sent an hour before the meeting is noise. An agenda sent the day before is a tool. 24 hours gives participants enough time to prepare properly — to read the pre-read, make the decision they need to make before they walk in, and add their own items if something's missing. Some meeting cultures use 48 hours as the standard for anything that requires significant preparation.
Assign time to each item
Time allocations do two things: they signal the relative importance of each agenda item, and they give the facilitator something to enforce. Without time boxes, meetings drift. With them, the facilitator has the standing to say "we have five minutes left on this item — do we need to extend or park it?" That's a legitimate facilitation move when the time is in the agenda; it feels arbitrary when it isn't.
Name an owner for each item
Every agenda item should have a person attached to it — the person who's leading that part of the discussion, presenting the information, or calling for the decision. "Marketing update" is an item. "Marketing update — Fatima presents, team Q&A" is an agenda item. The owner knows they're responsible; everyone else knows who to direct their questions to.
Include a wins and recognition moment
The most consistently skipped part of team meeting agendas is also the one with the highest return on the two minutes it takes. A brief "what went well since we last met?" or a specific shoutout to a team member who did something worth naming publicly costs almost nothing and consistently changes the energy in the room for the better. Teams that build recognition into the agenda structure — not as an add-on but as a standing item — are the ones where appreciation happens regularly rather than occasionally. If your team uses Karma, the kudos sent in Slack after the meeting can make the private recognition moment public — carrying it beyond the call and into the team's shared channel.
End with action items
The last five minutes of any meeting should produce a list of: what's been decided, what action each person is taking, and by when. This section of the agenda doesn't need to be filled in before the meeting — it's filled in during it. But it needs to exist as a space in the document, or it won't happen.
40 meeting agenda items and questions organised by type
Use these to build agendas for any meeting format — team standups, all-hands, retrospectives, project kickoffs, and 1:1s.
For team standups and weekly syncs
For all-hands and company-wide meetings
For project kickoffs
For retrospectives
For strategy and decision meetings
For 1:1s
For closing any meeting
Why recognition belongs on every team meeting agenda
Most team meetings have a standing agenda: updates, blockers, priorities, AOB. Almost none have a standing recognition moment — and it's the item most likely to have a lasting effect on team culture.
This isn't about adding ceremony for its own sake. A two-minute "what went well since we last met?" or a specific public shoutout to a team member changes the energy of a meeting immediately and consistently. It signals to every person in the room that contribution is noticed, that good work doesn't go unacknowledged, and that the team's culture values appreciation alongside performance.
The challenge is that recognition gets crowded out when it isn't structural. The agenda items with hard deadlines — decisions to make, blockers to resolve, updates to give — always feel more urgent than a moment of appreciation. The solution is to put recognition on the agenda first, so it happens before the meeting runs out of time. Teams using Karma extend this moment beyond the meeting itself. The public kudos sent in Slack after the call — for the thing that was named in the meeting — makes the private recognition visible to the whole team, including people who weren't in the room. That's the difference between a warm moment and a cultural habit.
Frequently asked questions
What is a meeting agenda?
A meeting agenda is a structured list of topics, time allocations, and owners that defines what a meeting is for and how the time will be used. It's shared with participants before the meeting — ideally 24 hours in advance — so everyone arrives prepared. A good agenda makes the meeting's purpose explicit, tells participants what to prepare, and creates a home for action items and decisions.
What should a meeting agenda include?
A meeting agenda should include: the meeting's purpose in one sentence, the list of agenda items with time allocations and an owner for each, any pre-read materials or preparation required, space for wins and recognition, and a closing section for action items, decisions, and next steps. The most important element is the purpose statement — without it, the agenda is a list without a direction.
How do you write a good meeting agenda?
Start with the purpose — one sentence that explains why this meeting needs to happen and what it needs to produce. Then list the agenda items that serve that purpose, with time allocations and an owner for each. Send it at least 24 hours before. Include a wins or recognition moment. End with space for action items. The agenda should be short enough that participants actually read it before they join.
How far in advance should you send a meeting agenda?
At least 24 hours before the meeting — enough time for participants to prepare properly, read any pre-read materials, and make any decisions they need to make before they join. For meetings that require significant preparation or that involve senior stakeholders, 48 hours is better. An agenda sent an hour before the meeting is too late to be useful.
Why do meetings fail without an agenda?
Meetings without agendas fail because participants don't know what's expected of them, the conversation drifts without a structure to return to, decisions are made without clarity on who has the authority to make them, and there's no mechanism for capturing action items. The result is a meeting that produces a feeling of having discussed things without the clarity of having decided anything.
How does a meeting agenda connect to employee engagement?
A well-structured meeting agenda contributes to employee engagement by making people's time and preparation feel valued, by creating clarity about roles and decisions, and — when it includes a recognition moment — by making appreciation a standing part of how the team communicates. Teams that consistently run well-structured meetings with a recognition component report higher engagement scores than those that don't, because members feel their time and contributions are taken seriously.
Other templates
One-on-one Meeting Template
Run productive one-on-one meetings with a structured agenda for feedback, goal tracking, and employee development.
Ready to get started?
If you're ready to get started with Karma, sign up now and explore the benefits of the recognition for your team. You can also reach out for a free demo.