One-on-One Meeting Notes Template

6 min read

Why 1-on-1 notes are different from meeting notes

A 1-on-1 is not a status meeting. Status can go in a dashboard; the 1-on-1 exists for the things a dashboard can't hold — what's blocking someone, how they're actually doing, feedback in both directions, and the slow-moving topic of their growth. The notes have a different job, too: they are a longitudinal record. A single 1-on-1 rarely matters. What matters is whether last month's blocker is still this month's blocker, whether the commitment from three weeks ago quietly vanished, and whether the feedback you gave in March connects to the review you write in November.

That means the template below is built around two things most meeting templates skip: commitments carried over (reviewed first, before anything new) and two-way feedback (a named section for feedback to the manager, not just from them). Copy it into one running doc per direct report — not a new doc per meeting — and add a dated entry each week or two.

The 1-on-1 meeting notes template (copy and paste)

Blank template

# 1-on-1 Notes — [Manager] & [Direct report]

## [Date]

### Commitments from last time
| Commitment | Owner | Status |
|------------|-------|--------|
|            |       | Done / In progress / Dropped |

### Wins since last time
-

### Blockers & challenges
- Blocker: … | What would unblock it: … | Who can help: …

### Feedback for [direct report]
-

### Feedback for [manager]
-

### Growth & career
-

### New commitments
| Commitment | Owner | By when |
|------------|-------|---------|
|            |       |         |

### Parking lot (topics for a future 1-on-1)
-

Example: the template filled in

Here is one entry from a running 1-on-1 doc between a manager (Dana) and a senior engineer (Alex), mid-way through a promotion case.

Filled example

## Tue, Oct 21

### Commitments from last time
| Commitment | Owner | Status |
|------------|-------|--------|
| Draft design doc for the notifications rework | Alex | Done — circulated Oct 17 |
| Intro to payments team lead re: pairing session | Dana | Done |
| Prepare two talk-track options for the team demo | Alex | Dropped — demo moved to November, revisit then |

### Wins since last time
- Notifications design doc got sign-off from staff eng with only minor comments.
- Mentored Priya through her first on-call week; she flagged Alex's
  runbook notes as the thing that helped most.

### Blockers & challenges
- Blocker: API review from the platform team has been waiting 9 days;
  notifications timeline assumes it lands this sprint. | What would
  unblock it: a named reviewer instead of the team queue. | Who can
  help: Dana to raise in Thursday's platform sync.

### Feedback for Alex
- Design doc was strong on trade-offs. One gap: the "alternatives
  considered" section was thin, and staff-level reviewers will push on
  it. Add a short rejected-options paragraph before the next big doc.

### Feedback for Dana
- Alex: sprint planning keeps landing on top of the 1-on-1 slot; two of
  the last four were cut to 15 minutes. Asked to protect the full 30.

### Growth & career
- Promotion packet: evidence is strong on technical depth, thin on
  cross-team influence. The platform API review is actually an
  opportunity — if Alex drives it to resolution, that's a concrete
  influence example. Target: packet review in January.

### New commitments
| Commitment | Owner | By when |
|------------|-------|---------|
| Escalate API review, get a named reviewer | Dana | Thu Oct 23 |
| Add rejected-options section to doc template | Alex | Oct 28 |
| Move 1-on-1 to Tuesday 11:00 (avoids planning clash) | Dana | Next week |

### Parking lot
- Interest in tech-talk circuit next year — revisit in December.
- Compensation review cycle timing.

Notice two things about the example. First, the review of old commitments happens before new business — the dropped demo item is recorded as dropped, not silently forgotten, which is what makes the doc trustworthy. Second, the feedback section for the manager is not empty. If that section is empty every week, the problem is the meeting, not the template.

How to run the running doc

One doc per person, appended over time. A folder of forty disconnected 1-on-1 docs will never be re-read. One scrolling doc makes patterns visible: recurring blockers, growth over quarters, commitments kept.
The direct report co-owns it. Both sides add agenda items and wins during the week. If only the manager writes, it's surveillance; if both write, it's a shared memory.
Open with last time's commitments, every time. It takes three minutes and is the single highest-value habit in 1-on-1s. Anything "dropped" gets said out loud.
Keep feedback small and frequent. One specific observation per meeting beats a quarterly download. "Your design doc's alternatives section was thin" is usable; "communicate better" is not.
Protect the growth section from the urgent. Blockers will happily eat every meeting. If Growth & career is empty three entries in a row, schedule one 1-on-1 per month that is only growth.
Know what's off the record. Personal context shared in a 1-on-1 (health, family, job-search anxieties) does not belong in a shared doc by default. Note the minimum needed, or nothing.

How an AI note taker helps with 1-on-1s

1-on-1s are the meeting people least want a bot in — and they usually happen in person, walking, or over coffee, where there is no call to join. With CoHear, you record on your iPhone with no bot involved and get a transcript and an organized summary back in about 65 seconds for a one-hour conversation (most 1-on-1s are half that). The verbatim quotes with timestamps are the useful part for this format: feedback lands differently when you can revisit the exact words — "the alternatives section was thin" — rather than a paraphrase written from memory two days later.

Keep the human judgment about what goes into the running doc. A sensible workflow: let the AI draft the record, then copy only the commitments, feedback, and blockers into your 1-on-1 doc — and leave the personal context out. Notes stay private by default, which matters more in this meeting than any other.

For general meetings, see the meeting notes template. If your 1-on-1s are part of a wider team cadence, the weekly team meeting notes template covers the group side.

FAQ

How often should 1-on-1 notes be taken?

Every meeting, briefly. Weekly or biweekly 1-on-1s are the common cadence; the note entry itself should take five minutes or less once the meeting ends — wins, blockers, feedback, commitments. If entries regularly take longer, you're writing a report, not notes, and you'll stop doing it within a month.

Should 1-on-1 notes be shared with the direct report?

Yes — the running doc works best as a shared document both people edit. Shared notes prevent the most corrosive 1-on-1 failure mode: the manager and the report remembering the same conversation differently, especially about commitments and feedback. The exception is a manager's private preparation for sensitive conversations (performance plans, layoffs), which belongs in a separate, clearly private place.

What is the difference between 1-on-1 notes and a performance review?

1-on-1 notes are the raw material; the review is the summary judgment written from them. Keeping dated notes all year is what makes a fair review possible — it replaces "what do I remember from the last six weeks" with evidence across the whole period. If your reviews feel recency-biased, the fix is usually better 1-on-1 notes, not a better review form.

What should I do if the feedback-for-manager section is always empty?

Treat it as a signal, not a relief. Ask directly, with a specific prompt: "What's one thing I did this month that made your work harder?" or "What should I stop doing in sprint planning?" Then act on the first answer visibly and thank them for it — the section fills up only after giving feedback once has visibly been safe.

More templates

All note-taking templates