Three calls with three sources, and a story that comes together on the Mac itself.

Wednesday is a three-interview day: a morning call with a company spokesperson who prepared talking points, a midday conversation with an industry analyst who has seen this problem before, and a late-afternoon call with an affected customer who has been living with the problem since last month. The story is due Thursday morning, and the draft is not written until all three are in the transcript files. Nothing about today's interviews depends on uploading them anywhere to understand what was said.

8:45am — before the first call rings in

The Mac is already recording. Press the record button, open the call in the meeting app, and two audio sources the Mac can hear — the microphone in the room and the Zoom or Teams audio playing through the speakers — both go onto two separate tracks. The person on the other end never sees a new name in the participant list and never gets asked for permission. By 8:45, the track is already rolling.

9:00am — the spokesperson interview, where the story's official version takes shape

The company has prepared a statement and sent it by email that morning. The call itself goes deeper: the spokesperson explains the reasoning, says which parts of the statement are most important to understand, and addresses the two gaps the journalist's research had already identified. By the time the call ends, the interview has been transcribed into a searchable text file on the Mac, and the summary — the key commitments the company made — is already available for reference.

10:15am — reading what the company actually said before talking to the analyst

Most journalists' workflows pull quotes from memory: a manager remembers the executive's phrasing as something close to what they said, and an hour's worth of other interviews narrows what is remembered further. This workflow is different. Before the 11:00 call with the analyst, the journalist searches the just-completed interview for the exact sentence the spokesperson used about timeline and recurrence, and finds it timestamped: not a paraphrase, but the words actually said.

11:00am — the analyst interview, where the context the story needs comes into focus

The analyst has covered this space for years and has seen this exact failure mode twice before — once in 2023 and once in 2024. The interview transcript captures both case studies the analyst names, the timeline of each, and the specific differences between them and today's outage. By 11:50, those details are searchable on the Mac in a second transcript file, and the summary shows which warnings the analyst had flagged before this failure.

12:00pm — lunch, and a five-minute fact check

Before stepping away, the journalist searches both transcripts for the phrase "post-mortem" to confirm the company's commitment and the analyst's expectation align. They do. No calls to the office, no messages checking memory — a search across two files, on the Mac, takes five minutes and pulls both exact sentences side by side.

12:30pm — on background: what the customer actually experienced

The third interview is with a customer who has been dealing with the outage since 6:30am that morning. They are frustrated, specific about what broke, and adamant that this is not their first time with this company. The interview runs long — 47 minutes instead of 30 — because the customer adds details the journalist had not anticipated. By 1:20pm, that third transcript sits on the Mac, searchable, and the summary shows what the customer asked for when the company's support line finally picked up.

2:00pm — building the story from three searchable transcripts instead of notes

All three interviews are now on the Mac. The journalist's working draft opens in a text editor beside the transcript folders, and the story takes shape differently than it would if built from memory and handwritten notes. Each paragraph now has sources the journalist can search for to find the exact quote: not a paraphrase, but the words the source actually spoke, timestamped.

The opening lists what happened (the outage, when it started, the company's response time). The second section brings in the analyst's historical context — the two 2023 and 2024 cases the analyst cited, with the timeline each followed. The third section is the customer's experience: the third outage in nine months, and the support workflow that did not help. The final section is the company's post-mortem commitment and what that means for the next month.

Each section is backed by a searchable transcript. If an editor asks for a different quote or a second source to verify a detail, the journalist does not reread three hours of call recordings — they search the transcript files on the Mac for the phrase. This has a compound effect on speed: not just finding the quote itself, but confirming it appeared nowhere else in the interviews, or appeared in a different context. A phrase the analyst used about timeline might be different from how the customer used the same word. Knowing which source said which version, with the exact timestamp, is how a story that accurately reflects what three different people actually said becomes possible.

2:45pm — exporting only what the story uses

Not all three interviews go into the draft that the journalist sends to the editor. The customer's frustration is important to the story, but the customer asked that their name not be used, so the journalist exports the timestamp and the quote but strips the customer's name from the exported text. The company's post-mortem commitment goes in as a direct quote. The analyst's comparison to the 2024 incident goes in by date and outlet, since the analyst is a named source.

The Mac keeps the full recordings and transcripts — everything the journalist gathered — while the export that goes to the editor shows only what the story actually says. Nothing is reconstructed from memory between the interview and the first draft.

4:00pm — fact-checking with the company before the story ships

The company had asked, during the morning interview, to see the draft before publication. The journalist exports their own notes from the call — the summary the Mac produced — and sends that excerpt to the company's spokesperson to confirm the quotes are exact and the timeline is right. The export shows only that interview, not the others; the journalist controls what each source sees.

5:00pm — the story is drafted, quoted, and fact-checked on the same day

By end of day, the story is a first draft to the editor, quoted from the three searchable transcripts on the Mac, and fact-checked with one of the sources using an export of just their own interview. No voice memos are half-transcribed on an afternoon napkin. No quotes are reconstructed from memory at 8pm after the day has blurred them into something close. No sources are called back to verify they said what the journalist remembered them saying.

Thursday morning — when an editor questions a quote

The editor reads the draft and flags a sentence: "Does the analyst really say the company's timeline is too slow, or did we infer it?" The journalist does not go back to the office voice memos or call the analyst again. They search the Wednesday 11:00 interview transcript on the Mac for the exact phrase, find the timestamp, and paste the full sentence into the message to the editor: the analyst's words, verbatim, and the time in the call when they said it. The edit takes three minutes; without the searchable transcript, it would take a phone call and a promise to call back.

Why interviews stay interviews and do not become something else

A journalist's goal on an interview is to listen, to follow up when something does not make sense, and to capture exactly what the source said — not to take such detailed notes that half the brain is looking at the steno pad instead of the source's tone. A recorder that produces a searchable transcript on the Mac means the journalist's hand stays free: there are no notes to take because the transcript is being built in real time. The moment the interview ends, the transcript is done and searchable. Transcription running while the conversation is happening — the journalist can already search the first half while the second half is still being typed.

This is why interviews produce better stories. The journalist's attention stays on the source's tone, hesitation, and emphasis — the things that change meaning. When a source pauses before answering a question, that pause says something; a transcript captures the words, not the pause, but the journalist who listened to that pause knows which quotes matter most. When a source clarifies something unprompted, that clarity matters; the journalist who heard it can search for all the moments that person brought up that topic, and see whether the clarification was an afterthought or the core of their concern. A transcript built in real time, searchable on the Mac, keeps the journalist's attention where interviews need it most: on the source, not on the process of recording.

What today would have looked like with a voice memo and a loose workflow

Without a transcript, the story would be built from handwritten notes, a voice memo that takes 30 minutes to play back to find a quote, and a memory of what seemed important as the day went on. The fact-check with the company would mean replaying the morning interview to find the exact post-mortem commitment — if it was written down clearly at the moment, and if the voice memo's position is easy to remember. A quote the editor asks about gets found by memory and approximate timing, not by search, and the journalist either re-calls the source or risks a paraphrase.

What today's workflow deliberately does not do

Nothing here publishes the interview online or makes it searchable to readers — the interview is a journalist's work product, not a public record. No call is backed up to the cloud; every interview lives on the Mac that recorded it, and the journalist is the gatekeeper of who sees the recordings, who sees the transcripts, and what gets exported for fact-checking. There is no "share with my team" feature and no automatic upload to a shared workspace a colleague can browse. This workflow works for a single journalist on a macOS-based setup; a newsroom sharing interviews across a dozen reporters, or interviews that need to be archived for years, has a different set of needs this tool was not designed for.

The three interviews Wednesday is not unusual. The habit this workflow depends on — opening the record button before the call connects, then searching the transcript before the next call — takes a week to feel automatic. By the second week, most journalists find that they can close their note pads entirely. The transcripts are the notes. The searchability is the recall. What took hours with voice memos and memory becomes a three-minute search on the Mac where the interviews already live.

What it costs, what it runs on

Coii AudioNotes is $19, paid once, covering three of a journalist'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 — the same Mac used for all three of today's interviews. The full case for a journalist's notetaker covers the argument in more depth, and interview transcription on a Mac walks through the specific tools involved. For the specific constraint of interviews that stay off the cloud, best private meeting recorders covers the wider field, and how to keep client recordings confidential walks through the mechanics of export. To find what was said weeks later, searching old meetings and writing minutes from a transcript both walk through the other moments this page showed in motion. A user researcher's day and a consultant's workflow both face different back-to-back-interview days but use the same recording setup.