Ten reports, ten half-hours a week, and an uneven memory of each one.

A manager running one-on-ones across a full team doesn't have the problem of forgetting any single conversation — it's remembering all of them evenly. The report who raises something every week stays vivid; the one who mentions a concern once, quietly, in week three, is the one a manager draws a blank on by week nine, right when it turns out to have mattered. Typed notes taken live don't fix that unevenly either, because typing during the conversation that's supposed to be about the person changes what a report is willing to say in it.

What the app is actually built to do here

Coii AudioNotes records the Mac's own microphone and system audio as two separate tracks and transcribes them while the conversation is still happening. A language model bundled inside the app then turns that transcript into a short write-up — decisions, action items, open questions — so a commitment made in one one-on-one is still findable months later, rather than depending on which manager happened to remember it.

A team large enough that the details blur

A manager with eight or ten direct reports is, in effect, running the same conversation format ten separate times a week, each with its own context that has to stay in the right file. Because each recording and its write-up live as their own entry, searching by a report's name surfaces that person's history specifically — what came up in March, what's been raised twice now, what was promised and hasn't happened yet — without scrolling through a shared notes document where everyone's conversations sit mixed together.

Onboarding, where the details matter more than usual

A new hire's early one-on-ones carry more weight than a longtime report's routine check-in: a manager is forming a first read on how someone works, and a new hire is forming a first read on whether concerns raised early actually get followed up on. A transcript of those early conversations means a specific worry mentioned in week two — a tool they're struggling with, a teammate dynamic that feels off — doesn't quietly disappear by week six because it wasn't written down anywhere durable.

A remote or hybrid team, where tone doesn't travel through text

A distributed team's one-on-ones happen over a call more often than in person, and a manager relying on a typed summary written from memory loses more on a video call than in a room — the pause before someone answers a hard question, the tone that a bullet point strips out entirely. A transcript keeps the actual exchange, not a manager's interpretation of it typed up twenty minutes later between other meetings.

What it deliberately doesn't do

There's no integration with an HR platform, a performance-review tool or a calendar — nothing here files a note against a review cycle automatically, and nothing schedules the next one-on-one. There's no shared workspace a skip-level can browse without being sent a specific file directly. It runs on macOS only, so a manager working from a Windows laptop needs a different tool for this. Those are real gaps against a platform built specifically for performance management, not features this happens to be missing by accident.

The conversation a manager actually needs to get right

A performance conversation — flagging that something isn't working, or that a promotion case needs more evidence before it's ready — goes better when a manager can quote precisely what was already discussed rather than paraphrasing from memory a report may recall differently. "We talked about this in April, and here's exactly what I said then" is a stronger and fairer sentence than "I'm pretty sure I mentioned this before," and it's the difference a transcript makes available on demand.

A manager who used to be a peer

Being promoted to manage a team someone was recently part of themselves makes the first round of one-on-ones a specific kind of awkward — a former peer now has to speak more carefully, and the new manager has to resist the urge to fill silences with reassurance rather than let a real concern surface. A transcript doesn't fix that awkwardness, but it does mean a new manager isn't also trying to remember exactly what was said while still working out how to run the conversation itself; the record is there afterward, to be read calmly rather than scrambled for in the moment.

A conversation that has to hold up later

A performance improvement conversation is one of the few one-on-ones where exact wording can matter well beyond the meeting itself — what was actually agreed as the expectation, and by when. A manager relying on a typed summary written from memory risks a report reasonably disputing it later; a transcript settles what was actually said, which protects a fair process as much as it protects the manager who ran it.

A team going through a stretch of real uncertainty

A reorg, a round of layoffs elsewhere in the company, or a leadership change tends to make ordinary one-on-ones carry more emotional weight for a while — reports ask questions a manager may not have full answers to yet, and what a manager did or didn't commit to in that period matters more than usual once things settle. Having an accurate record of those specific conversations, rather than a blurred memory of a difficult few weeks, is worth more exactly when it's hardest to trust anyone's memory, including the manager's own.

The conversation before someone leaves

An exit conversation, or the one-on-one where a report first mentions they're considering leaving, is easy to want a precise record of afterward — what was actually offered to try to keep them, what feedback they gave about the role, what a manager promised to follow up on even if the person stays. That record matters for the manager's own learning as much as for anything formal, and it's exactly the kind of conversation where a fading memory a few weeks later is the least reliable version of events.

A manager who inherited a team overnight

Taking over a team through a reorg or a sudden departure means starting without the context a predecessor built up over months or years — what each report already raised, what was already promised, where a performance conversation had already begun before the handoff happened. Without any record of that history, a new manager either re-asks questions a report has already answered once, which reads as not having been briefed, or works blind for the first few months. A transcript archive doesn't hand over a predecessor's judgment, but where one exists, it hands over the actual conversations rather than a secondhand summary filtered through whoever wrote the handoff notes.

Checking a pattern across a whole team, not one report

A single one-on-one's transcript answers a question about one conversation. Searching across every one-on-one a manager has ever recorded answers a different kind of question — whether a specific concern, a specific tool complaint, or a specific scheduling conflict has come up with more than one report, which is often the first sign of a team-wide problem rather than an individual one. That search happens by hand, the same way searching any folder of documents does; there's no dashboard summarising it automatically, but the material to search through already exists rather than living only in a manager's general impression of "a few people have mentioned something like that."

A manager preparing for their own one-on-one, one level up

A manager's own one-on-one with their director benefits from the same kind of preparation a report's does — being able to say precisely what came up across the team that week rather than a general impression of how things are going. Pulling up the specific commitments made in a report's one-on-one earlier that week, before walking into a conversation with a skip-level manager, turns "the team seems fine" into an actual account of what was discussed and what's still open.

Who this genuinely isn't built for

A larger organisation already running one-on-ones through a dedicated people-management platform — with templates, review-cycle integration and a director's dashboard across a whole department — has a workflow this doesn't replace. This is built for the manager whose one-on-ones are theirs to record and theirs to remember from, not for a system that depends on a skip-level browsing raw notes across a team without asking.

Starting before it's the conversation that matters most

The habit is worth building on an ordinary week rather than the one where a report is about to raise something difficult — a manager who tries it first on a routine check-in knows what the write-up looks like and where it lives before trusting it for a harder conversation. That costs nothing and means the tool is already familiar the week it actually counts.

What a report can be told about where it goes

"It stays on my laptop — nowhere else" is a complete, honest answer to the question a report occasionally asks about a recording indicator, and it's a better opener to the habit than pointing at a vendor's privacy policy nobody reads before their next one-on-one happens anyway.

Setting it up

The first launch asks for two macOS permissions — microphone access and permission to record system audio — the same prompt any Mac app requesting audio triggers. No account, no workspace, nothing to configure before the next one-on-one. The larger adjustment is habit rather than setup: remembering to press record instead of trusting a bot that used to join a calendar invite automatically.

What it costs, what it runs on

Coii AudioNotes is $19, paid once, for three of a manager's own Macs, with a 30-day trial needing no card and no account. It runs on macOS 13 Ventura or later, Apple Silicon or Intel. Against Otter's $8.33–$16.99-a-month Pro tier, checked today, that's $19 total rather than a recurring line item for as long as the job runs one-on-ones; against Granola's $14-a-month Business tier the price gap narrows, though the audio still goes to a cloud service to produce the notes either way. Full comparisons here and here. The wider case for a Mac-native meeting notes app, what an AI notetaker without the bot actually changes, and a round-up of meeting notes apps without a bot all cover ground this page doesn't repeat. The closer, engineering-specific version of this case is here, and the adjacent case for customer success calls covers a different recurring conversation the same team often also has to track.