22 August 2026
One-on-one notes rarely get followed up because writing them competes directly with listening to what your report just told you about their career, their frustration, or their next move. The fix isn't a better template — it's a short private log the manager keeps for themselves, kept apart from anything a shared transcript would touch, that resurfaces the right line at the start of the next call instead of a blank page.
Watch someone's face change when their manager starts typing mid-sentence. In a status meeting that's just admin. In a one-on-one, where the content is often the person's own read on their career, their frustration with a peer, or a plan to leave the team, typing reads as filing rather than hearing.
That's the real reason one-on-one notes fail more than any other meeting type. It isn't that managers forget to write things down. It's that writing things down while someone is being honest about themselves is the wrong move to make in the room, so the note either doesn't happen or happens after the call, from memory, badly.
A one-on-one usually runs every two weeks, sometimes three if calendars fight back. That gap is long enough that specific commitments decay into vague impressions unless something concrete survives between calls. What a manager needs isn't a transcript — it's four or five load-bearing lines.
Without them, the manager either opens the next call cold, or worse, fakes continuity: "didn't you say something about wanting more ownership?" when what was actually said was a date, a name, and a condition.
A lot of what gets said in a one-on-one is precisely the material that shouldn't survive in any record other people can search: a named colleague someone is struggling with, a health or family circumstance affecting hours, a comp conversation, a plan to move teams before the current manager has been told directly.
Most meeting tools that transcribe by default were built for calls where everyone in the room already agreed to say things on the record. A one-on-one isn't that call. If the transcript lands in the same searchable pool as every other meeting, the report has one fewer place they can be honest, and they'll notice.
AVAY transcribes every meeting it's in and its search reaches across a person's past calls, which is exactly what makes a one-on-one different from every other meeting on the calendar. The setting that matters here isn't whether to record — it's who a specific meeting's notes are visible to, restricted to the manager and the report rather than the whole team's search.
The other honest limitation: a recording made in a browser saves to the device that made it, not automatically to some shared cloud everyone can reach. That cuts against convenience but it also means a one-on-one's raw audio isn't sitting in a company-wide archive by accident.
The private note a manager actually needs is three or four lines, not a running dossier. Pulling up AVAY's coach with ⌘K mid-call lets a manager draft that condensed version while the conversation is still happening, without it becoming part of anything the report or anyone else will later search.
Tell the report the log exists. A private note that's acknowledged reads as diligence. A private note discovered later reads as surveillance, and the difference between those two things is entirely whether you said it out loud.
| Carries forward? | Visible to the report? | Survives a skipped week? | |
|---|---|---|---|
| Memory only | No | N/A | No — decays within days |
| Shared team doc | Yes, but anyone can edit it | Yes, fully | Yes, but chills what gets said |
| Manager's private notebook | Yes, if kept up | No | Depends entirely on the manager |
| Scoped transcript plus private note | Yes, automatically | Only what's marked shared | Yes |
Transcribe them if it helps you keep continuity, but only if the transcript's visibility is locked to you and the report — not searchable across the wider team by default. If that scoping isn't available or the relationship is fragile, it's reasonable to turn recording off for this meeting specifically.
Hand over the short private note — the commitments and dates — not the transcript. The old transcript should stay archived with the outgoing manager's records rather than being passed on verbatim to someone the report hasn't built trust with yet.
A private note kept outside the shared meeting record isn't visible to them by default in most tools, including AVAY. Tell them you keep one anyway — an acknowledged log reads as care, a hidden one reads as something to worry about.
That content doesn't belong in an AI transcript or a casual private note at all. It belongs in whatever formal HR process your company already runs, which has its own retention rules and its own access list, deliberately separate from the weekly cadence.
The difference is where it lives. A note that's part of the meeting cadence — surfaced automatically before the next call rather than filed away somewhere the manager has to remember to reopen — gets used because it's in front of you at the moment it matters.
The one-on-one that gets followed up isn't the one with the fullest transcript — it's the one where the manager kept three private lines and let the rest go.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.