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.
Karma bot privacy policy
Effective date: 18 August 2026
This Privacy Policy explains how Sliday LTD ("Sliday", "we", "us", or "our") collects, uses, shares, and protects personal data. It covers both the Karma application (for Microsoft Teams, Slack, Telegram, and the web) and the https://karmabot.chat website.
Who we are and how to contact us
The data controller is Sliday LTD, a private limited company registered in Cyprus under company number HE450506, with its principal place of business at Pavlou Valdaseridi 2A, 1st floor, Larnaka, Cyprus, 6018.
For any privacy-related enquiry, or to exercise your data protection rights, contact us at hi@karmabot.chat.
Privacy matters are overseen by our Legal Advisor / Operational Security Manager, Stas Kulesh. A dedicated Data Protection Officer has not been appointed, as Sliday LTD is not required to appoint one under Article 37 of the GDPR; privacy responsibilities are held by the Legal Advisor.
Personal data we handle and where it comes from
From the Karma application
When your organisation installs and uses Karma, we process the following personal data, obtained from Microsoft Teams / Microsoft Entra ID (Azure AD) and from your use of the application:
- Display name — from Microsoft Teams / Microsoft Graph
- Email address — from Microsoft Teams / Microsoft Graph
- User Principal Name (UPN) — from Microsoft Graph (
/me) - Microsoft Entra (Azure AD) object ID and tenant ID — from Microsoft authentication
- Profile photo — from Microsoft Graph (
/me/photo) - Team and channel names — from Microsoft Teams
- Karma activity (karma given and received, associated messages) — from your use of the app
Where Karma is used with Slack or Telegram, the equivalent identity and workspace data is obtained from that platform instead.
From this website
- Contact details you give us — such as your email address and name when you subscribe to updates, request a demo, or contact support
- Usage and device data — IP address, browser type and version, pages visited, date, time and duration of visit, referring page, and similar diagnostic data
- Cookies and similar technologies — see "Cookies and website analytics" below
Why we process personal data
We process personal data to:
- Identify you and link you to your organisation's Karma workspace
- Operate the core recognition ("karma") features, leaderboards, and adaptive cards
- Display your name and profile photo within the app
- Deliver notifications and service communications
- Administer subscriptions and billing
- Provide customer support and respond to your enquiries
- Monitor, secure, maintain, and improve the service, and detect and address technical issues
- Send newsletters, marketing, or promotional material where you have chosen to receive it — you can opt out at any time via the unsubscribe link in any email, or by contacting us
Lawful basis for processing
We process personal data on the following lawful bases under the GDPR:
- Performance of a contract — to provide the Karma service to your organisation
- Legitimate interests — to operate, secure, and improve the service, where not overridden by your rights
- Consent — for marketing communications and for non-essential cookies and analytics, where consent is required
- Legal obligation — where we are required by law to retain or disclose data, including for tax and accounting purposes
Where your organisation is the controller and we act as processor, processing is carried out on your organisation's documented instructions.
Who we share personal data with
We share personal data only with the sub-processors listed below, each of which is necessary to deliver the service and is engaged under an appropriate data processing agreement. This is the complete list of sub-processors with access to personal data. We do not sell personal data.
Service sub-processors
- DigitalOcean — application hosting and managed database
- Amazon Web Services (AWS) — profile photo storage (S3)
- Cloudflare — edge delivery and web application firewall
- Microsoft — authentication, the Teams platform, and Microsoft Graph
- Stripe — subscription billing and payment processing
- Sentry — error monitoring
- MailerLite — notification and marketing email delivery
We do not store or collect your payment card details. That information is provided directly to Stripe, our payment processor, whose use of your personal information is governed by its own privacy policy (https://stripe.com/privacy). Stripe adheres to the standards set by PCI-DSS as managed by the PCI Security Standards Council.
Website analytics and marketing providers
The https://karmabot.chat website additionally uses:
- Google — Google Analytics 4 and Google Tag Manager, for website traffic analytics (https://policies.google.com/privacy)
- Meta (Facebook) — Meta Pixel, for advertising measurement (https://www.facebook.com/privacy/policy/)
- Ahrefs Web Analytics — privacy-focused website traffic analytics (https://ahrefs.com/legal/privacy-policy)
- ProfitWell (Paddle) — subscription and revenue analytics (https://www.paddle.com/legal/privacy)
- MailerLite — newsletter sign-up forms (https://www.mailerlite.com/legal/privacy-policy)
- Calendly — demo and meeting scheduling (https://calendly.com/legal/privacy-notice)
We may also disclose personal data where required to do so by law or in response to a valid request by a public authority, or where necessary to protect our legal rights, prevent or investigate wrongdoing, or protect the safety of users or the public.
Cookies and website analytics
Cookies are small pieces of data stored on your device. We use cookies and similar technologies (including beacons, tags, and scripts) to operate the website, remember your preferences, keep the service secure, and understand how the site is used.
The cookies we use fall into these categories:
- Essential cookies — required to operate the website and keep it secure
- Preference cookies — to remember your settings and choices
- Analytics and marketing cookies — set by the providers listed above to measure traffic and advertising performance
You can instruct your browser to refuse all cookies or to notify you when a cookie is set. If you refuse cookies, some parts of the website may not function correctly.
We do not currently respond to browser "Do Not Track" (DNT) signals.
How long we keep personal data
We retain personal data for the duration of your organisation's active subscription and for six (6) months after subscription cancellation, after which it is deleted. This applies to customer account and identity data, profile photos, and karma transaction records.
- Database backups operate on a rolling 7-day point-in-time recovery window, so any backup containing erased data is automatically superseded within 7 days.
- Upon a verified data deletion request, we action it as promptly as reasonably possible and in any event within one month, as required by the GDPR.
- Billing and accounting records may be retained for longer where required by law.
- Operational data — error telemetry, security logs, and backups — is disposed of automatically as it ages out of the relevant service's retention window.
Full details are set out in our Data Retention and Disposal Policy.
Your data protection rights
Subject to applicable law, you have the right to:
- Be informed about how your personal data is used
- Access the personal data we hold about you
- Rectification — to have inaccurate or incomplete data corrected
- Erasure — to have your personal data deleted
- Restriction — to request that we restrict processing of your personal data
- Data portability — to receive your data in a structured, commonly used, machine-readable format
- Object to our processing of your personal data
- Rights relating to automated decision-making and profiling — Karma does not carry out automated decision-making producing legal or similarly significant effects
- Withdraw consent at any time, where we rely on your consent
To exercise any of these rights, contact us at hi@karmabot.chat. We may ask you to verify your identity before responding.
Making a Subject Access Request (SAR)
To submit a Subject Access Request, contact us at hi@karmabot.chat. We respond to all SARs within one month, as required by the GDPR, unless the request is complex or numerous, in which case we may extend the response time by a further two months and will tell you if we do. We maintain a data mapping process that lets us locate and retrieve all personal data held about a specific data subject across our systems — principally the production database and the profile photo object storage — so that a SAR can be fulfilled thoroughly.
International transfers and safeguards
Karma production data is hosted in the United States (DigitalOcean SFO region). As Sliday LTD is established in the EU (Cyprus), this involves a transfer of personal data to a third country.
Such transfers — and transfers to other sub-processors located outside the EU/EEA, including Microsoft, AWS, Cloudflare, Stripe, Sentry, and the analytics providers listed above — are protected by appropriate safeguards, principally the Standard Contractual Clauses (SCCs) incorporated into each sub-processor's Data Processing Agreement, supplemented by those providers' certification frameworks, including the EU–US Data Privacy Framework where the provider participates.
Sliday LTD takes all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy.
Your right to complain to a supervisory authority
You have the right to lodge a complaint with a data protection supervisory authority.
Our lead supervisory authority is the Office of the Commissioner for Personal Data Protection of the Republic of Cyprus:
- Commissioner for Personal Data Protection
- 1 Iasonos Street, 1082 Nicosia, Cyprus
- Email: commissioner@dataprotection.gov.cy
- Web: https://www.dataprotection.gov.cy
You may also lodge a complaint with the supervisory authority in your own country of residence.
Security of data
The security of your data is important to us. We apply technical and organisational measures appropriate to the risk, including encryption in transit, access controls, vulnerability scanning, and error monitoring. However, no method of transmission over the internet or method of electronic storage is completely secure, and we cannot guarantee absolute security.
Children's privacy
Our service is not directed at anyone under the age of 18. We do not knowingly collect personal data from children. If you are a parent or guardian and believe your child has provided us with personal data, please contact us and we will take steps to remove it.
Links to other sites
Our service may contain links to sites we do not operate. We have no control over, and assume no responsibility for, the content or privacy practices of any third-party site. We encourage you to review the privacy policy of every site you visit.
Changes to this Privacy Policy
We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the effective date at the top. Where changes are significant, we will notify you by email and/or a prominent notice on our service before the change takes effect. We encourage you to review this policy periodically.
Contact us
If you have any questions about this Privacy Policy, contact us:
- By email: hi@karmabot.chat
- By post: Sliday LTD, Pavlou Valdaseridi 2A, 1st floor, Larnaka, Cyprus, 6018