One-on-one meeting template: structure, cadence, and a running history both of you can read (2026)

A one-on-one is the report's meeting, not the manager's status update. The 30-minute template, the 45-minute monthly variant, how to prepare and run it, how often to hold it, the first one-on-one with a new report, fifteen questions by situation — and where the running history of your one-on-ones lives in Teams, Slack and a space built so both of you read it in your own language.

The Mind.com Team

One-on-one meeting template: structure, cadence, and a running history both of you can read (2026)

One-on-one meeting template: structure, cadence, and a running history both of you can read (2026)

A one-on-one is a recurring, private meeting between a manager and one person who reports to them. It is the one meeting on the calendar that belongs to the report: their blockers, their growth, their questions first; the manager's items second. It is not a status update — status lives in the channel — and it is not a performance review, although a year of good one-on-ones is what makes the review contain no surprises.

This guide gives you the template, the monthly variant, the way to prepare and run it, the cadence, the first one-on-one with a new report, fifteen questions by situation — and then the part templates skip: where the history of your one-on-ones lives, so that "didn't we discuss this in March?" has an answer both of you can open.

What a one-on-one is for

Three things, in this order:

  1. Unblocking. What is in the report's way this week that only the manager can move — a decision, a priority call, a conversation with someone else.
  2. Growth. Where the report wants to be in a year, and what this quarter does about it. This is the item that disappears first when the meeting becomes a status update, and the one people quit over when it has been missing for a year.
  3. Feedback both ways. One specific piece each. Small, frequent and two-directional beats one annual document.

What it is not for: reviewing the task list (the channel does that), announcements (the team meeting does that), and the manager's own update (two minutes, at the end, if at all).

The 30-minute template

[Report] / [Manager] — one-on-one
Cadence: weekly, [day, time] · Link: [the same meeting link every week]
Pre-read: last session's recap and its open items

1. Your items — report — 12 min
[Added to the agenda the day before; the report decides the order.]

2. Follow-ups from last time — both — 5 min
[Each open item: done, not done and why, or dropped on purpose.]

3. One piece of feedback each way — both — 8 min
[Specific: a situation, what happened, what to keep or change.]

4. Next steps, written down — both — 5 min
[Two or three items with a name and a date. The manager's items are here too.]

The 45-minute monthly variant

Once a month, swap item 3 for a longer growth conversation and give the meeting fifteen more minutes:

1. Your items — report — 10 min
2. Follow-ups from last time — both — 5 min
3. Growth: where you want to be in a year, and what this quarter does about it — report leads — 20 min
4. Feedback each way — both — 5 min
5. Next steps, written down — both — 5 min

The growth item has a fixed question behind it — "what would you like to be doing more of, and what is in the way?" — and a fixed output: one development step per quarter with a date, written in the report's words.

How to prepare and run it

The day before, the report adds their items where both of you already talk. One message in your shared one-on-one channel: "Thursday — 1. the review process, 2. the conference, 3. a question about the roadmap." The manager adds theirs below. Items written the day before get thought about; items raised in the first minute get reacted to.

In the meeting, the manager's job is to listen and to write outcomes aloud. Open with the report's first item, not with "how are you" that expects "fine". Ask the second question — "what makes you say that?" — more than you state anything. When something is agreed, say it as a sentence: "so we're recording — you draft the proposal, I get you fifteen minutes with Dana before the 20th." That sentence is the record; writing it down during the meeting is what makes the next one start from facts.

After the meeting, the next steps go where both of you will see them before the next session — not into the manager's private notes, and not into a document only the manager can edit. A one-on-one whose history lives in one head is a one-on-one that restarts from zero every time a manager changes.

Cadence: how often, how long, and the rule about cancelling

SituationCadenceLength
New report, first 90 daysWeekly30 min
Remote or in another time zoneWeekly30 min
Established, co-located, work is going wellEvery two weeks45 min
Monthly growth conversationOnce a month, replaces one regular session45 min

The rule: a one-on-one is rescheduled, never cancelled. A cancelled one-on-one tells the report exactly where they stand in the manager's week, and the message is heard louder than anything said in the meeting. Keep the same link every time: the history of the meeting then has one address.

The first one-on-one with a new report

The first session is the only one with a fixed agenda set by the manager, because the report does not yet know what to bring:

1. How you like to work — report — 10 min: hours, focus time, how you prefer to get feedback, what a good week looks like.
2. What the team needs from this role in the first 90 days — manager — 10 min: in writing, before the meeting.
3. How we will run these: cadence, where items go, where the notes live — both — 5 min.
4. Your first three questions — report — 5 min.

From the second session on, the template above applies and the report owns item 1.

Fifteen questions, by situation

When the report's list is short

  • What took more of your time this week than it should have?
  • What are you putting off, and what would make it easier to start?
  • Who on the team would you like to work with more?

When something is stuck

  • What decision are you waiting on, and from whom?
  • If you could change one thing about how we work, what would it be?
  • What do you need from me this week that you haven't asked for?

Growth

  • What would you like to be doing more of a year from now?
  • What is one skill you'd like to be known for?
  • Which piece of recent work are you proudest of, and why?

Feedback

  • What is one thing I could do differently that would help you?
  • When did I last get in your way?
  • Is there feedback you have been meaning to give someone and haven't?

Well-being

  • How sustainable is your current pace?
  • What is one thing outside work that is taking energy right now, if you want to share it?
  • Is there anything you'd like me to know that we haven't talked about?

Three per meeting is plenty. The point is the second question, not the first.

Where the running history lives in the tools you already use

A one-on-one is the meeting with the longest memory: the item from March matters in September. Where the notes live is therefore a design decision, not an afterthought. Documented behaviour only, from the vendors' own pages, checked October 2026:

ToolWhat it offers for one-on-onesWhere it stops
Microsoft TeamsCollaborative notes — a Loop component with agenda, notes and tasks assigned by tagging people — are available in Teams group chats on desktop and web; meeting notes can also be started from the meeting's Details or the Notes controlThe chat-notes page documents group chats, not one-on-one chats; external guests cannot edit notes; the notes are one document in one language
SlackA one-on-one template as a canvas, meant to live in a private channel per manager–report pair, with sections for development resources, goals and meeting-prep remindersThe canvas holds what someone types into it; what was said in the call is not in it unless a person writes it

Both are the right idea — one place per pair, kept over time — with the same two limits: the record is written by hand, and it exists in one language.

A running history both of you can read

InterMIND is a communication space where a meeting lives in a channel, so a one-on-one is a channel with two members and one permanent meeting link. The report posts the items the day before; the manager adds theirs. When the session ends, the recap is written from the meeting itself: a summary, the points marked agreed, open or disputed, the next steps with owners, each line keeping its timestamp — editable by either of you, with every edit keeping author and revision history. The channel keeps the recap of every past session, so the question from March is one click away in September, and the recap is members-only: forwarding the link grants nobody access.

For a channel's recurring meeting, the open items of the previous session are read back when the next recap is written and judged against what was said — reported finished, marked done; anything else marked not done with the reason in the words of the meeting, or "not discussed" — and at the start of the next session Mia names the open items and their owners. This part runs for selected accounts while it is being refined.

One more property, said once: the manager and the report each speak and read in their own language — the record is translated per reader, not written in whichever language the two of you compromise on. The host provides it; the report installs nothing and pays nothing.

FAQ

What is a one-on-one meeting?

A recurring private meeting between a manager and one of their reports, owned by the report: their blockers, growth and questions come first, the manager's items second. It is not a status update and not a performance review; it is the place where the small conversations happen that make the review contain no surprises. Other names: 1:1, one-to-one, check-in.

How do you conduct a one-on-one meeting?

Let the report set the first item and the order; ask more than you state; when something is agreed, say it aloud as a sentence with a name and a date; end with next steps written where both of you will see them before the next session. Keep it to the booking — 30 minutes weekly, 45 for the monthly growth conversation — and reschedule rather than cancel.

How do I prepare for a one-on-one with my manager?

Add your items to the shared agenda the day before, in the order you want them; read the last session's notes and update the open items — done, not done and why; bring one question about priorities and one piece of feedback for your manager. If the meeting has no shared agenda, propose one: the template above works from either side.

What should be on a one-on-one meeting agenda?

Four items: the report's items (the largest block), follow-ups from last time, one piece of feedback each way, and next steps written down with names and dates. Once a month, a twenty-minute growth conversation replaces the feedback item and the meeting runs 45 minutes.

How often should one-on-ones be?

Weekly for a new report in the first 90 days and for anyone remote or in another time zone; every two weeks for an established, co-located report whose work is going well; plus a monthly growth session. Rescheduled when needed, never cancelled.

How should I structure my one-on-one meetings?

Same link, same slot, same four items every time, with the report's items first. The structure is what lets the content change: when the shape is predictable, both people prepare, and the history of the meeting becomes readable because every session looks the same.

Is a one-on-one the same as a performance review?

No. A review is a periodic, formal assessment, usually tied to compensation and documented by HR. A one-on-one is informal, frequent and owned by the report. The relationship between them is that a year of honest one-on-ones is what makes a review uneventful.


Sources: Microsoft — Use collaborative notes in Microsoft Teams chats; Microsoft — Take meeting notes in Microsoft Teams; Slack — One-on-one meeting template. checked October 2026.

More in Meetings & recaps

All posts in Meetings & recaps
Meeting agenda examples for 12 kinds of meetings — and what each one leaves behind (2026)
Meetings & recaps

Meeting agenda examples for 12 kinds of meetings — and what each one leaves behind (2026)

Twelve meeting agenda examples you can copy — weekly team meeting, daily stand-up, one-on-one, project kickoff, sprint review, retrospective, all-hands, leadership meeting, board meeting with a consent agenda, client call, customer QBR and hiring debrief — each with purpose, items, owners and minutes, and the one thing most examples skip: what the meeting leaves behind, and in whose language.

The Mind.com Team

Meeting agenda template: format, examples, and how the agenda comes back as the recap (2026)
Meetings & recaps

Meeting agenda template: format, examples, and how the agenda comes back as the recap (2026)

A meeting agenda is the list of what a meeting is for: the items, in order, each with an owner, a time box and the outcome it needs. The format, a template you can copy, five filled-in examples for the meetings most teams actually run, where the agenda lives in Teams, Zoom, Google Workspace and Slack — and how each item comes back after the call as decided, open or deferred, in every participant's own language.

The Mind.com Team

Where Microsoft Teams and Google Meet store your transcript, recording and summary — and how to keep them after the call
Meetings & recaps

Where Microsoft Teams and Google Meet store your transcript, recording and summary — and how to keep them after the call

Looking for where Teams saved your transcript? Not with the recording. On Microsoft Teams and Google Meet the recording, the transcript and the AI summary are three separate objects in three places with three permission lists, and moving one does not move the others — Microsoft's own documentation says captions aren't fully supported once a Teams recording is moved. A documented map of where each artifact lands, who can still open it afterwards, and what it looks like when the meeting is a place instead of a folder of files.

The Mind.com Team

Get new posts and product updates by email

One email a month with new posts and product updates. Unsubscribe anytime.