Answers · AI evidence
Who is responsible when an AI transcription or note-taking tool adds words nobody said, and how do you prove what was really said?
Last updated
TL;DR: In practice, the person or business that adopts the transcript as its record: the clinician who signs the note, the company that files the meeting minutes, the lawyer who quotes the interview. The tool's maker warns you about this up front. OpenAI's Whisper model card says the models may output text that isn't actually spoken in the audio and recommends against use in high-risk domains like decision-making contexts. Researchers behind Careless Whisper (ACM FAccT 2024) found that roughly 1% of Whisper transcriptions contained entire hallucinated phrases or sentences not in the audio, and that 38% of those included explicit harms such as violence, made-up names, relationships or health details, or false authority. Hallucinations were more common for speakers with longer pauses. An October 2024 AP investigation reported Whisper-based medical tools in use by over 30,000 clinicians, and that one vendor, Nabla, erased the original audio for data safety reasons, leaving nothing to check the transcript against. The fix is the same everywhere: keep the audio, or at least a hash of it, alongside the transcript, and record who reviewed and approved the transcript before it became the record.
What should I check, step by step?
1. Find out whether your transcription tool keeps the original audio, for how long, and whether you can export it. If it deletes audio by default, decide whether you can keep your own copy within your privacy and consent rules.
- When a transcript is made, hash the audio file and the transcript (SHA-256) and record the tool, model and version, so you can show later which audio produced which text.
- Have a named person review a transcript before it becomes a record: a signed clinical note, filed minutes, a quoted statement. Record who approved it and when.
- Review hardest where hallucinations cluster: long pauses and silence, background noise or music, speech impairments, accents and lower-resource languages. Whisper's model card says hallucinations may be worse in lower-resource languages.
- Watch for the telltale additions: sentences at the end of a recording, names, medications, numbers or relationships nobody mentioned, and video-style lines such as thanking viewers or asking people to subscribe.
- When someone disputes a transcript, go back to the audio, not the text. If the audio is gone, say so; don't treat the transcript as proof of what was said.
- Keep corrections visible: store the original machine transcript, the corrected version and who made the change, rather than overwriting the text.
- Tell people when they're being recorded and transcribed, and get consent where the law requires it. Whisper's model card also cautions against transcribing people recorded without their consent.
- Check your contract with the vendor for who bears errors, how long audio and transcripts are kept, and whether you can export both if you leave.
How often does Whisper hallucinate words that weren't in the audio?
Careless Whisper (Koenecke and colleagues, ACM FAccT 2024) tested OpenAI's Whisper on thousands of short audio clips. Most transcriptions were highly accurate, but roughly 1% contained entire hallucinated phrases or sentences that didn't exist in any form in the audio. In one example, Whisper correctly transcribed a simple sentence and then added five more containing words like terror, knife and killed.
- The authors sorted the harmful hallucinations into perpetuating violence, inaccurate associations (made-up names, locations, relationships and health statuses) and false authority (lines like a YouTuber's sign-off, or links to websites). They found 38% of hallucinations included explicit harms, and that hallucinations happened disproportionately for speakers with longer non-vocal pauses, a common symptom of aphasia.
- Whisper's own model card explains the cause: because the models are trained on large-scale noisy data, they combine predicting the next word with transcribing the audio, so predictions may include text not actually spoken. It recommends against use in high-risk domains.
Why does deleting the original audio make AI transcription errors hard to catch?
The AP reported in October 2024 that Nabla's Whisper-based medical tool was used by over 30,000 clinicians and 40 health systems, and that its chief technology officer said the tool erased the original audio for data safety reasons. Nabla said clinicians edit and approve the notes. Without the audio, though, nobody can later check a disputed sentence against what was actually said.
- Deleting audio can be a reasonable privacy choice. If you make it, the review before approval is the only check you get, so record that it happened: who reviewed, when, and a hash of the exact text they approved.
Who is responsible for errors in an AI-generated transcript or medical note?
No court has set a general rule for transcription hallucinations. But records are usually judged as the record of whoever signs or adopts them, so the clinician who signs a note, the company that files minutes and the reporter who quotes an interview own what the transcript says.
- That's why the useful evidence isn't the transcript alone. It's the link between three things: the audio, the machine transcript and the approved version, each with a hash and a time, plus who approved it. With that, a dispute can be settled by listening to the audio; without it, it comes down to whose memory is better.
How do I ask Rightshold about this (free, no key)?
Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code, then ask: “Record a signed receipt for this transcript: a hash of the original audio file, a hash of the reviewed transcript, the transcription model and when it ran, so we can show later which audio this text came from.”
{
"tool": "record_ai_run",
"arguments": {
"model": "whisper-1",
"provider": "openai",
"prompt_sha256": "<sha256 of the original audio file>",
"output_sha256": "<sha256 of the approved transcript text>",
"params": {
"machine_transcript_sha256": "<sha256 of the unedited transcript>",
"reviewer_ref": "<your reviewer reference>",
"recording_ref": "<your recording id>"
},
"ran_at": "2026-11-10T07:00:00Z"
}
}- Needs an API key. Send hashes only: Rightshold never needs the audio or the transcript, so nothing said in the recording is stored. The receipt is Ed25519-signed, gets an issued_at time from Rightshold's clock and goes on Rightshold's append-only ledger, whose blocks are also anchored to Bitcoin through OpenTimestamps.
- verify_ai_run is free and needs no key: in a dispute, anyone can send the receipt id plus the audio file's hash or the transcript text to check it matches what was recorded.
- In recorded mode the receipt marks the run as reported by you. It shows which audio and text hashes were recorded and when, not that the transcript is accurate.
- Use your own references for the reviewer and recording, not names, patient details or other identifying information.
Rightshold doesn't transcribe audio, store recordings or check whether a transcript is accurate, and it doesn't decide who is responsible for an error. A receipt proves which hashes were recorded and when. Recording, consent and medical-record rules differ by place and profession. Not legal or medical advice.
What are the sources?
- Koenecke et al., Careless Whisper: Speech-to-Text Hallucination Harms (ACM FAccT 2024)
- Cornell Chronicle: AI speech-to-text can hallucinate violent language (June 2024)
- OpenAI Whisper model card (hallucination, high-risk domains, consent)
- AP News: Researchers say AI transcription tool used in hospitals invents things no one ever said (October 2024)
- Engadget: OpenAI's Whisper invents parts of transcriptions (Nabla audio deletion)
- Verified AI Runs on Rightshold
Related
- How to show a customer or regulator that a human reviewed an AI decision
- How to prove what an AI model said at a specific time
- Investigating a complaint that your AI chatbot made something up
- Verified AI Runs
Not legal advice. JSON · Markdown · All answers
Get a free API key in one call
No card and no email needed. 100 free credits; the license and policy checks stay free without a key.
curl -s -X POST https://www.rightshold.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export RIGHTSHOLD_API_KEY=rs_... # the api_key from the reply (shown once)
curl -s https://www.rightshold.com/v1/licenses/check -H "Authorization: Bearer $RIGHTSHOLD_API_KEY" \
-H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'
