What to cover in a 1:1 (employee-led agenda)
The defining rule of a good one-on-one: it is the report’s meeting. Status has other homes (standups, the weekly report); the 1:1 exists for the things that never make it into either: how the person is actually doing, what is bothering or exciting them, and where they are heading. The structure that protects that:
| Section | Time | The point |
|---|---|---|
| Check-in | 5 min | How are you, actually? Not the work yet |
| Their agenda | 15 min, first | Whatever they bring; empty twice running is itself the topic |
| Since last time | 5 min | Open items with status, and what changed; continuity is respect |
| Your topics | 10 min | One specific piece of feedback + context they should have |
| Growth | 5 min, every other 1:1 minimum | The next skill or responsibility being built toward |
| Wrap | 2 min | Actions owned and dated; they feed next time’s opener |
One on one meeting questions to ask
Keep a short rotation rather than a long list. These earn their airtime:
- “What’s on your mind this week?” The open door; let the silence work.
- “What’s been more frustrating than it should be?” Finds process problems while they are still small.
- “What did you enjoy most this month, and how do we get you more of it?” The growth conversation, disguised as a easy one.
- “What do you need from me that you’re not getting?” Uncomfortable, and the single highest-yield question on the list.
- “Is there anything you’ve been hesitating to tell me?” Use sparingly; answer calmly whatever comes back.
Weekly, fortnightly or monthly: picking a 1:1 cadence
Weekly 30 minutes for new starters, new managers, or anyone mid-change; fortnightly 45 is the steady state for most small teams; monthly only works alongside genuinely open day-to-day access, and even then growth topics need protecting or they disappear. Whatever the cadence, the two rules that outrank it: the meeting is never cancelled casually (moved, fine; vaporised, corrosive), and the agenda carries over, because a 1:1 with amnesia teaches the report that nothing said in it matters.
Free one on one meeting template (plain text, Google Docs, Notion)
Three ways to a 1:1 with a memory. The plain text pastes cleanly into Google Docs or Notion; one running doc per report works best.
The plain-text template
Employee-led structure with the since-last-time and growth slots built in.
1:1 · [Manager] × [Report] · [Date] · [30-45 min] CHECK-IN (5 min) How are you, actually? (Not the work yet.) THEIR AGENDA FIRST (15 min) - [Whatever they bring: wins, worries, ideas, frustrations] (The report sets this section, ideally the day before. If it’s empty two 1:1s running, that is itself the topic.) SINCE LAST TIME (5 min) - Open items from last 1:1: [item] → [where it stands] - What changed since we spoke: [shipped, landed, moved] YOUR TOPICS (10 min) - [Feedback: one specific thing, with an example] - [Context they should have: what’s coming, what changed above them] GROWTH (5 min, at least every other 1:1) - What did you do this month you’d want to do more of? - What’s the next skill or responsibility we’re building toward? WRAP (2 min) - Actions: [item] → [owner] → [by when] - Anything for the private list, note it now.
The AI prompt
Prefer to use your own AI? Copy this into Claude or ChatGPT with last 1:1’s notes, and it preps the next agenda.
--- title: 1:1 Agenda Generator description: A prompt that preps a one-on-one agenda from last time’s notes and what’s happened since, employee-led by design. author: readywhen source: https://readywhen.ai/one-on-one-meeting-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-18 keywords: [one on one meeting template, 1:1 agenda, one on one questions, manager meetings] --- # 1:1 Agenda Generator _By readywhen. Full guide + free template: https://readywhen.ai/one-on-one-meeting-template_ You are prepping a manager’s next 1:1 with a direct report. A 1:1 is the report’s meeting; your job is to make sure the manager arrives having done their homework. ## Principles - The report’s agenda comes first and gets the most time. The 1:1 is not a status report; status has other homes. - Continuity is the respect signal: open items from last time appear with their current state, never re-asked from scratch. - "What changed since we spoke" gets surfaced: things shipped, wins landed, anything the manager should acknowledge or ask about. - Feedback is one specific thing with an example, not a themes review. - Growth gets a slot at least every other 1:1, or it becomes never. - End with actions, owned and dated, so next time’s "since last time" writes itself. ## What I need from you Last 1:1’s notes or actions (paste them) · anything notable since (wins, changes, concerns) · the one piece of feedback you want to give · cadence and length. I’ll build the agenda with their section first and your homework done. --- _Made by readywhen. readywhen preps each 1:1 from the last one and what’s changed since, so the manager walks in already caught up. https://readywhen.ai/one-on-one-meeting-template_
Let readywhen do itRecommended
Continuity and preparation are memory problems. readywhen keeps the thread per report: open items with status, what changed since, the win worth naming, and the growth topic when it’s due, so you walk in caught up.
readywhen preps each 1:1 from the last one in ~45 seconds, so the meeting starts at “since last time” instead of “remind me where we got to?”
Let readywhen prep each 1:1 from the last one
Every 1:1 guide says the same two things: continuity and preparation. Both are memory problems, and memory is exactly what a busy manager runs short of by Thursday.
readywhen keeps the thread: it brings forward last time’s open items with their current state (including the ones the manager owes the report), surfaces what changed in between (the win worth naming, the thing that shipped), requests the report’s agenda a day ahead so their section really does come first, and queues the growth topic when it is due. The manager walks in caught up; the report notices.
Works with your existing tools
One on one meeting FAQs
What should a one on one meeting cover?
In order: a genuine check-in, the report’s agenda (the biggest slot), open items from last time with their status, the manager’s topics (one specific piece of feedback plus context), a growth conversation at least every other meeting, and a two-minute wrap with owned actions.
How often should one on ones happen?
Weekly for new starters or anyone mid-change; fortnightly 45 minutes as the steady state for most small teams; monthly only alongside genuinely open day-to-day access. Whatever the cadence, move the meeting if you must, but never let it quietly vanish.
Should a 1:1 be a status update?
No. Status has other homes: standups, the weekly report, the project board. The 1:1 exists for what those never capture: how the person is doing, what is bothering or exciting them, and where they are growing. If status keeps eating the meeting, shrink it to one written line beforehand.
Who owns the 1:1 agenda, the manager or the employee?
The employee leads; the manager prepares. The report’s items run first and get the most time, while the manager arrives having done the homework: last time’s items with status, the feedback, the growth thread. If their agenda arrives empty two meetings running, that is the conversation.
Is there a one on one meeting 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; one running doc per report works best. All formats are free.
Can’t I just use ChatGPT or Claude to prep my 1:1s?
Yes. Paste last time’s notes and the prompt above, and it builds the agenda. readywhen is the version that already holds the thread: last meeting’s items, what shipped since, the win worth naming, so every 1:1 starts caught up instead of reconstructed.
More templates for meetings that matter
Team meeting agenda
Next week’s agenda, pre-filled with carried-over actions and open decisions.
Action items
Owned, dated actions and a same-day recap, extracted from your transcript.
Decision log
Every decision with its rationale, captured from your meetings.
Stop walking into 1:1s cold.
Prep your 1:1 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 employee-led structure and cadence guidance reflect common management 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.