Resource
Most “legal transcription software” roundups compare turnaround times and per-minute prices, and skip the only question that can end a career: where does the privileged audio go? Here’s the honest map of the category — what needs a human, what needs software, and what the software’s architecture must look like when the recording is privileged.
Quick answer
Certified transcripts are a human service, not a software feature. When the transcript itself must be evidence — proceedings, certified deposition transcripts — you hire a certified transcriptionist or court reporter. No software replaces that.
Everything else is a software job, and architecture is the buying criterion. Client meetings, dictated memos, interview prep, internal case discussions: software transcribes them instantly. But cloud transcription tools put a third party inside privileged conversations. On-device tools — where audio is transcribed and stored entirely on your own machine — are the only architecture where no outside disclosure occurs at all.
1. Court-grade transcripts. Human, certified, formatted to jurisdiction rules. Budget for a service; this category isn’t what software is for.
2. Working transcripts of privileged material. Client calls, strategy discussions, dictated case notes. Speed matters, but confidentiality governs: this is where the vendor-in-the-loop question from our privilege analysis applies with full force. ABA Formal Opinion 512 requires understanding a tool’s data handling before client information goes in — an analysis that gets one sentence long when the tool never transmits anything.
3. Non-privileged volume. Public hearings, recorded CLEs, marketing content. Any decent transcription tool works; pick on price and convenience.
Minutesis built for job #2. It records and transcribes on your own machine (whisper.cpp — the audio has no network path), labels speakers, and stores everything as markdown files on your disk with owner-only permissions — organized, greppable, and readable by your AI assistant straight from local files, with structured action items filled in once you connect one. It’s open source (MIT), so your security review can read the code instead of a vendor questionnaire.
Where it is notthe tool: certified transcripts (job #1 — hire a human), jurisdiction-formatted verbatim output, or medical-legal templating. And it doesn’t change your own obligations — recording consent, device encryption, matter-based access control stay with you, where they already live.
Next step
Informational, not legal advice. Certification requirements and consent law vary by jurisdiction — confirm with your ethics counsel.