What happens to a session recording between one appointment and the next?

The pattern is the same across most meeting software: the recording travels to a server the practitioner never picked and a client never met, gets turned into text somewhere out there, and comes back later as a transcript. That detour is usually why the recording never gets made in a therapy practice at all, and notes end up written from memory instead — after the next three sessions have already started blurring into this one.

What a general-purpose notetaker asks a practice to accept

Otter and Fireflies both join a call as a named participant to build their transcript, and both produce that transcript on a server the vendor operates — reasonable enough for a sales call, and a harder thing to accept for a session where the content is, by design, more personal than almost any other kind of meeting. Granola avoids the participant on the call but is still a cloud subscription end to end, transcribed and summarised on infrastructure the practice doesn't control. Neither question — who's on the call, and where the audio goes — has a version of "yes" that sits comfortably with a session recording.

Recording that stays where the session happened

Coii AudioNotes records the microphone and, on a telehealth call, the system audio too, as separate tracks, and transcribes and summarises entirely on that same Mac. Nothing about the session — not the audio, not the transcript, not the summary — is uploaded anywhere to produce any of those three things.

A summary written on the same machine as the session

A language model bundled inside the app turns the transcript into a short recap — a decision reached, something to follow up on, a question to revisit — right after the session ends, while the specifics are still accurate. It is a general summary, not a clinical note written to any particular documentation standard, and it is generated on the Mac rather than sent off to be written somewhere else.

Two things this page is careful not to claim

It does not claim any compliance certification — not HIPAA, not any other. What is actually true, and the thing worth relying on instead, is the behaviour: the recording, transcript and summary are produced on the Mac and nothing is uploaded to produce any of them. Confirming that is sufficient for a specific practice's obligations is a question for the practitioner's own compliance advisor, not this page. It also does not tell anyone whether or how to disclose that a session is being recorded — that answer depends on jurisdiction, licensing board and the practice's own consent procedures, and belongs with a practitioner's own counsel rather than with a piece of software.

What it deliberately doesn't do

There is no clinical documentation template — no SOAP note, no treatment plan, no diagnosis code. The summary is general, not clinical, and turning it into a note that fits a specific practice's documentation standard is still the practitioner's own step. There is no EHR integration, no billing system connection and no scheduling tool link. And it runs on macOS only, with no Windows, iOS or Android version, so a group practice with clinicians on different platforms won't get the same tool across the whole team from this one alone.

What actually changes about the session itself

Nothing about how the session runs changes — same room or same call, same conversation. What changes is what happens to the recording afterward: instead of a transcript written on a vendor's server, or notes reconstructed from memory between one appointment and the next, there's a transcript and a short recap sitting on the same Mac the session happened on, searchable later without ever having left it.

Who this genuinely isn't built for

A larger group practice already running structured clinical documentation through an EHR, with notes that need to fit a specific format for insurance billing, has a real requirement this tool doesn't attempt to meet — it writes a general summary, not a billing-ready clinical note. This is written for the version of practice where the recording's only job is helping the practitioner remember the session accurately, not replacing the documentation a practice's compliance and billing requirements already dictate.

Setting it up is smaller than the decision to switch

The first launch asks for two macOS permissions — microphone access and, for a telehealth session, permission to record system audio — the same prompt any Mac app requesting audio capture triggers, and that's the whole of it. No account to register, no workspace to configure, nothing to connect before the first session can be recorded. The bigger part of introducing recording into a practice is usually not the software at all — it's the practice's own decision about how and when to raise it with a client, which is a conversation this page can't have on the practitioner's behalf.

Recording is a choice made session by session

Nothing here records automatically or without the practitioner starting it. That's a deliberate difference from a bot that logs into a scheduled call on its own: recording a session is a decision made in the moment, for that specific client and that specific conversation, rather than a default that applies to every appointment on a calendar whether or not it was ever discussed. A practice that wants some sessions recorded and others not gets that by simply not starting it, not by configuring an exception somewhere.

Why the recording matters beyond the note itself

A therapist's memory of a session, even a good one, is a reconstruction — which detail came up first, whether a client's own words or the practitioner's paraphrase is what actually got written down. A transcript removes that layer of reconstruction from at least the record itself, even though what a practitioner chooses to write into a client's file afterward is still their own clinical judgment, applied to what the transcript shows rather than to what they happened to remember an hour after the session ended.

What a full caseload makes visible over time

A single session's recap is useful the same afternoon; a searchable archive of them becomes useful in a different way months into a course of treatment, when a pattern across sessions matters more than the detail of any one of them — whether a particular topic keeps resurfacing, whether a coping strategy discussed weeks ago was ever actually tried. Reconstructing that pattern from memory alone, across a full caseload, is close to impossible by the twentieth session; a transcript sitting on the practitioner's own Mac, searchable by keyword, makes it a question that can actually be answered.

What actually changes in a practitioner's week

The time saved isn't the session itself — that runs exactly as it always has. It's the twenty minutes after each one that used to go to writing notes from memory while the details were still fresh, now spent instead on the next thing on the calendar, with a transcript and a short recap already sitting on the Mac to write the actual clinical note from later, whenever there's time to do it properly rather than doing it rushed immediately after the client leaves.

The trust question underneath the recording

A client who agrees to a session being recorded is trusting that the recording goes somewhere specific and limited, even if they never ask exactly where. A cloud notetaker's privacy policy can describe that in detail, but it's a document neither the client nor, often, the practitioner has actually read closely before the session starts. Recording, transcribing and summarising on the Mac the session already happened on sidesteps the question rather than needing a reassuring answer to it — there's no vendor's server in the chain to describe at all.

Who this genuinely isn't built for, said a second way

A solo or small practice where the practitioner is the one writing every note and the client relationship is the whole of the record is exactly who this is built for. A larger group practice with shared clinical oversight, supervision requirements that need transcripts reviewed across a team, or documentation that has to flow into a specific EHR format has a real reason to stay with tools built around that infrastructure — not because a single session is handled worse here, but because the value of that infrastructure comes from sharing this tool deliberately doesn't do.

The first weeks after introducing it

The first few sessions after starting to record tend to feel slightly different for one specific reason — remembering to press record before the session begins, rather than relying on habit. That adjustment fades within a couple of weeks, and what replaces it is a transcript and a short recap waiting on the Mac after each session, without a bot, a participant, or anything new for a client to notice on the call itself.

What a client remembers about the session

A client rarely remembers the exact wording used, but they do remember whether the practitioner seemed present or distracted by writing during the session. Recording instead of taking notes live keeps that attention where it belongs, which matters as much for the session itself as it does for the accuracy of the eventual note.

Who this is written for, plainly

Not a large group practice standardising clinical documentation across a team of clinicians — that's an EHR and supervision-workflow decision, not a single app's job. This is written for the solo practitioner or small practice whose session notes currently get either written from memory between one appointment and the next, or typed live at the cost of attention a client can feel, and who wants a transcript worth trusting without a recording that has to leave the Mac to produce it.

What it costs, what it runs on

Coii AudioNotes is $19, paid once, for three of a practitioner's own Macs, with a 30-day trial needing no card and no account, and every feature unlocked from the first launch rather than gated behind a tier a small practice would have to justify upgrading into. It runs on macOS 13 Ventura or later, Apple Silicon or Intel. Against Otter's or Fireflies' monthly subscriptions, or Granola's $14-a-month Business tier, the $19 is paid once rather than every month for as long as the practice keeps recording. Full comparisons here and here. A wider round-up of meeting notes apps for regulated work covers therapists alongside doctors and lawyers who share the same requirement and is worth reading before a practice settles on a single tool for session recordings, and meeting apps that don't train on your data covers a closely related question a compliance review usually asks next. The broader case for a Mac-native meeting notes app, what an AI notetaker without the bot changes, what a round-up of private meeting recorders turns up, and what happens when a session runs somewhere without a reliable connection, in offline transcription for Mac, all cover ground this page doesn't repeat, and each is worth a look before a practice settles on a single tool for session recordings.