A good one-on-one meeting notes template turns a weekly 1:1 from a chat that evaporates the moment the call ends into a record both the manager and the report can actually use. Most managers run a dozen or more of these a week, and without a consistent format, each one becomes a blur of the last few by Friday. Worse, the report rarely sees what was written, if anything was written at all, so promises made in one 1:1 quietly disappear by the next. This guide gives you a template to copy today, a filled-in example, the questions worth asking, and the mistakes that make 1:1 notes useless six weeks later.
What one-on-one notes need to capture
A 1:1 note is not a performance review and it is not a to-do list for the report alone. It exists so that both people walking into the next 1:1 can answer three questions without trying to recall last week's conversation from memory:
- What did we agree to do, and who owns it. This includes commitments from the manager, not just from the report. A manager who promised to check on a transfer or a raise and forgot is worse for trust than a report who missed a deadline.
- What is actually going on, beneath the status update. Workload, a difficult teammate, a worry about the next appraisal cycle. These rarely come up again if nobody wrote them down the first time.
- What has changed since the last 1:1. A report who seemed fine two weeks ago and is now checked out is a pattern you only notice if you can compare notes across weeks, not just remember the last one.
Everything else, like a detailed recap of a project status that is already covered in a team stand-up, can be left out. A 1:1 note that duplicates the team meeting notes is a sign the 1:1 itself did not go deep enough.
A one-on-one meeting notes template you can copy
Use this structure every time, and keep it short enough to fill in during the call itself, not after.
1:1, [manager] and [report], [date]
How they are doing: [in their own words, one line]
Work and workload
- What is going well: [specific, not generic]
- What is stuck or at risk: [and why, not just what]
- Workload check: [stretched, fine, has room for more]
Growth and feedback
- Feedback given: [to the report, specific and recent]
- Feedback received: [about the manager or the team, worth acting on]
- Growth or skill they raised: [a course, a project, a stretch assignment]
Commitments
- [Action], owner: [name], due: [date]
Carried over from last time
- [What was open last 1:1, and whether it moved]
A filled-in example
Here is the same template after a real 1:1, so you can see how short each section stays in practice.
1:1, Neha Kulkarni (manager) and Rohan Iyer (report), 14 October 2026
How they are doing: Good week overall, a bit stretched since Divya went on leave
Work and workload
- Going well: Billing module shipped a day early, client feedback was positive
- Stuck: Waiting on the design team for the refund flow mockups, two weeks now
- Workload: Stretched, covering two of Divya's tickets on top of his own
Growth and feedback
- Feedback given: Praised how he handled the client escalation on Tuesday without pulling in Neha
- Feedback received: Wants more notice before scope changes land mid-sprint
- Growth: Interested in leading the next small project himself
Commitments
- Neha to chase the design team for refund flow mockups, due: 17 October
- Neha to think about a lead role for Rohan on the Q1 reporting project, due: next 1:1
- Rohan to hand back one of Divya's tickets once she is back, due: 20 October
Carried over from last time
- Raise conversation from two weeks ago: Neha confirmed it is with finance, still waiting
Notice what carried over: the raise conversation. That one line is the entire point of keeping notes. Without it, Rohan either has to ask again and feel like a nag, or stop asking and quietly lose trust in the process.
Questions worth asking in a one-on-one
A 1:1 that only covers task status is a status meeting with extra steps. These questions tend to open up the conversation that actually needs a manager's attention:
| Area | Ask | Listen for |
|---|---|---|
| Workload | What took up most of your time this week that wasn't on the plan? | Hidden work nobody scoped or assigned |
| Team health | Is there anything about how the team works together that is slowing you down? | A process issue, not a person issue, unless named directly |
| Growth | Is there something you wanted to work on that you haven't had a chance to? | A specific project or skill, not a vague "more responsibility" |
| Manager feedback | Is there something I could be doing differently for you? | Said hesitantly the first few times, worth asking every time regardless |
| Outside work | How are things outside work, if you want to share? | Context for a drop in energy, never pressed if declined |
Not every question needs to be asked every week. Rotating through them keeps the 1:1 from becoming a script both people can predict and tune out.
Common mistakes that make one-on-one notes useless later
- Only the manager keeps notes, and the report never sees them. A 1:1 note that lives only in the manager's private file misses half its purpose, which is giving the report something to hold the manager to as well.
- Writing down tasks, not the person. If every note reads like a sprint update, the 1:1 has quietly turned back into a status meeting.
- No carry-over section. Without one, commitments like a raise conversation or a promised mockup review simply vanish after a week or two.
- Treating every 1:1 the same. A new hire's first few 1:1s need more structure and more listening. A long-tenured report's 1:1 can move faster and skip the basics.
- Letting a difficult topic go unrecorded because it felt awkward to write down. A line as simple as "raised concern about recognition, will revisit" is enough, and it matters more than the easy topics.
Keeping one-on-one notes without slowing the conversation down
The real reason most managers stop keeping 1:1 notes after a few weeks is not that they disagree with the idea, it is that typing while someone is talking about a hard week makes the conversation feel transactional. An AI meeting notetaker like Zrec can take that pressure off. Zrec records the call from your own computer, with no bot joining the meeting, so a 1:1 over Google Meet or Teams still feels like a normal conversation. It transcribes with each speaker named and writes up a summary with decisions and action items with owners, which maps onto the commitments section of this template, so you can stay present in the conversation instead of splitting attention with a notes app. For managers who switch between Hindi and English with their team, Zrec also handles Hinglish, so the write-up comes out in clear English either way.
A quick checklist before you close a 1:1
- Did you ask at least one question that was not about task status?
- Does the report know what you committed to, not just what they did?
- Did you check what carried over from the last 1:1, out loud?
- Is there one piece of feedback in either direction, not zero?
- Will you both remember this conversation in four weeks without the note?
For the format a recurring team sync needs, see our daily standup notes template, and for turning commitments from any meeting into action items that actually get done, read our guide on action items from meetings. You can read more about how Zrec writes meeting notes automatically on the Zrec home page.
If you can read a 1:1 note from a month ago and recognise exactly where that conversation went next, the template worked. If every note reads the same no matter who it was with, it did not.