One-on-One Meeting Template — Agenda & Questions
A complete one-on-one meeting template for managers and direct reports, structured around wins, blockers, priorities, and professional development. Preview the template below or use the interactive version in FigJam.
What is a one-on-one meeting?
A one-on-one meeting (also written 1:1, 1-on-1, or one on one) is a regular, private conversation between a manager and a direct report. Its purpose is distinct from team meetings — it's not about project status or group decisions. It's about the individual: their progress, their blockers, their development, and the relationship between them and their manager.
Done well, 1:1s are the highest-leverage time a manager spends. A 30-minute weekly conversation with each direct report is where most of the real management happens — not in all-hands, not in performance reviews, not in annual surveys. The template below is designed to make that time as useful as possible.
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, customize, and collaborate with your team.
How to run a great 1:1
Share it before the meeting, not in it
Send the agenda to your direct report 24 hours before and ask them to add their own items to every section. The best 1:1s are genuinely two-directional — not a manager working through their list while the employee answers. When both people come prepared, the time is used better and the conversation is richer.
Start with wins, every single time
The recognition section at the top is a structural choice, not a warm-up. Managers who consistently open with something specific the employee did well build stronger working relationships over time. The specificity is what makes it land — "the way you handled the client escalation on Thursday" is recognition. "You've been doing great" is noise.
Protect the open space
The most important conversation in a 1:1 often happens in the last five minutes, when the formal agenda is done. Don't fill every minute. The question "is there anything you've been wanting to raise but haven't found the right moment?" surfaces more useful information than any structured agenda item. If you never ask it, you'll never know what you're missing.
Keep the notes, review the actions
Open the notes from the previous 1:1 before every meeting. Check on the actions you both committed to. Nothing erodes trust in a 1:1 faster than a manager who forgets what they said they'd do. Keep the document shared and editable by both people between meetings.
50 questions to ask in a one-on-one
Use these to supplement the template when you want to go deeper on a specific topic, or to restart a 1:1 relationship that's become stale and transactional.
About the work
About blockers and support
About the team
About growth and development
About recognition and appreciation
Big picture questions (use sparingly, not weekly)
About the 1:1 itself
The recognition section most 1:1 templates miss
Most one-on-one templates cover goals, blockers, and development. Almost none include a dedicated recognition section — and it's the most consistently skipped part of the 1:1 in practice.
This matters because the 1:1 is where managers notice things. They're in the conversation, they know what the employee has been working on, and they're in the best position to give specific, meaningful appreciation. The problem is that without a prompt, recognition gets crowded out by operational discussion. Adding it to the top of the agenda makes it structural rather than optional.
The recognition section is deliberately first in this template for that reason. Research consistently shows that managers who open their 1:1s with a specific acknowledgement — not "you've been doing great" but the actual thing they noticed — build significantly stronger working relationships over time. The specificity is the signal. It tells the employee that someone is paying attention.
The other thing most 1:1 templates miss: peer recognition. The manager sees some of what the employee does, but their colleagues see more. A good 1:1 occasionally includes "who on the team do you think deserves more recognition than they're getting?" — surfacing kudos the manager can help amplify, or prompting the employee to give recognition themselves in the team channel after the meeting.
Frequently asked questions
How often should you have one-on-one meetings?
Most managers run 1:1s weekly or biweekly. Weekly works best for newer employees, people in fast-moving roles, or anyone going through a significant transition. Biweekly is common for more experienced team members with established working relationships. Monthly is rarely enough — the gap is too long to catch blockers early or maintain genuine connection.
What should you cover in a one-on-one meeting?
A good 1:1 covers wins and recognition, current blockers, priorities for the next period, and development or career topics. The balance shifts over time — early in someone's tenure, role clarity and onboarding dominate; once trust is established, development and career conversations become more central. Always leave space for whatever the employee wants to raise.
What are good questions to ask in a one-on-one?
The best 1:1 questions are open-ended and genuinely curious. Examples: What's going well that deserves more attention? What's getting in your way right now? What would you do if you were in my position? Is there anything you've been wanting to raise but haven't found the right moment? The last question often surfaces the most important thing in the conversation.
What is a skip-level one-on-one?
A skip-level 1:1 is a meeting between a leader and an employee who reports to someone who reports to them — skipping one level of the hierarchy. The purpose is to hear directly from team members without filtering through their direct manager. Skip-level meetings are most useful for large teams, for surfacing systemic problems, and for building relationships across levels of the organisation.
How long should a one-on-one meeting be?
30 minutes is the standard for a weekly 1:1. 45 to 60 minutes works better for biweekly or monthly meetings where more ground needs covering. The meeting should end when the conversation is done, not when the calendar slot expires — starting with a tight agenda and good questions usually means 30 minutes is enough.
How do you make 1:1s more effective?
The most effective 1:1s start with wins and recognition, share the agenda in advance, protect time for the employee to raise anything they want, and end with clear action items. The recognition moment at the start sets the tone — a specific, named acknowledgement of something the employee did well makes the conversation feel like it's genuinely for them, not for the manager's status update. After the meeting, sending a public kudos in Slack for the win you named in private closes the loop between the private 1:1 and the team's shared recognition culture.
Other templates
Team Charter Template
Define your team's purpose, roles, values, and working agreements to improve collaboration and accountability.
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