A one-on-one meeting agenda that starts with the team member's topics.

Copy this one-on-one agenda

The agenda below fits a 30-minute meeting. Share it in a document you both can edit, ask the team member to add their topics a day before, and keep the timings loose: the point is that their topics are never squeezed out by status updates.

One-on-one: [Team member] and [Manager]
Every [week / 2 weeks] · 30 minutes · same link each time

Before the meeting (team member adds, manager reads)
- My most important topic this week:
- A win, or something I learned:
- Where I am stuck or need a decision:

1. Check-in (0–5 min)
   - How are you doing, honestly?
   - Anything outside the work that affects this week?

2. Team member's topics (5–18 min)
   - Topic 1:
   - Topic 2:
   - What would help most here: advice, a decision or a sounding board?

3. Manager's topics (18–24 min)
   - Context the team member should know:
   - Feedback: one specific example, its effect, what to keep or change

4. Growth (once a month, replaces part of step 3)
   - Which skill do you want to build this quarter?
   - Which piece of work would stretch you?
   - What support do you need from me?

5. Actions (24–30 min)
   - [Owner] will [action] by [date]
   - Anything to carry over to next time?

For a 45-minute meeting, give the team member's topics the extra time. For a meeting every two weeks, run the growth block every second meeting rather than once a month.

How do you run a one-on-one that stays useful?

Protect the time, let the team member lead and finish with actions that someone owns. Most 1:1s fail slowly: they turn into status reports, get cancelled when the week is busy, or end without anything changing.

1. Keep status out. Project updates belong in the stand-up or the tracker. If an update matters, discuss the decision or the blocker behind it, not the progress itself.
2. Listen before advising. Ask what kind of help the person wants. Sometimes they need a decision, sometimes only a second opinion.
3. Give feedback with an example. Describe what happened, the effect it had and what to keep or change. Feedback without an example is hard to act on.
4. Write actions with an owner and a date. “Look into the release process” is not an action until one person owns it and you both know when you will check.
5. Start the next 1:1 with the last actions. A quick “done, in progress or dropped” keeps promises visible on both sides.

Remote 1:1s need a little more care: turn on cameras when both of you are comfortable, close chat notifications and say so when you need a minute to think. The video meeting privacy guide covers what to agree before any capture.

Keep a running notes document for every 1:1

One document per person, newest meeting at the top, works better than a new file each time. It shows the history of decisions and actions in one place, and either of you can add a topic the moment it comes up.

[Date] — [Team member] / [Manager]

Topics discussed
-

Decisions
-

Actions
- [Owner] — [action] — due [date] — [open / done]

Carry over to next time
-

Private to the team member (optional)
- 

Agree who can read the document. A 1:1 record is personal: share it only with the two people in the meeting unless both agree otherwise. For meetings with more people, use the meeting minutes template instead.

Where Meeto helps with recurring one-on-ones

Meeto turns the 1:1 into a recurring series with one link, sends the invitation and the reminders, and keeps the room closed to anyone else. Recording and AI summaries exist, but they are optional and need a paid host.

If you do use an AI meeting summary, it gives a short summary, key points, decisions and action items with a transcript; copy the actions into your running notes and check them first. To set up the series step by step, follow how to schedule a video meeting. For the team-wide view, see how remote teams use recurring meetings.

Frequently asked questions

Explore more with Meeto