How to turn a transcript into meeting minutes

A transcript is a record. Minutes are a decision instrument — the document a colleague reads in ninety seconds and acts on. The gap between the two is editing, and most people skip it because trimming an hour of speech by hand takes longer than the meeting did. This guide covers the structure that survives contact with real meetings, what to keep and what to cut, and how to automate the first draft with on-device AI (in QuickSpeak, which we make) without sending the transcript anywhere.

What minutes are made of

Five sections, in this order — the order matters, because busy readers start at the top:

1. Decisions made. One line each, past tense, unambiguous: "Approved the Q3 budget at $48k." If a sentence could be argued with later, it isn't finished — quote who said it.
2. Action items with owners and dates. "Priya sends the revised SOW by Friday" — not "the SOW will be revised." An action item without a name is a wish.
3. Open questions. What the meeting couldn't settle and who carries it forward. This section is what makes next week's agenda write itself.
4. Key numbers and commitments, quoted. Prices, deadlines, quantities — copied exactly from the transcript, not paraphrased from memory.
5. A one-paragraph summary for anyone who won't read further. Written last, placed first or last by house style.

Everything else in the transcript — the discussion, the dead ends, the joke about the printer — is source material, not minutes.

The manual pass, in ten minutes

With a speaker-labeled transcript in front of you, the trimming is mechanical:

1. Skim for decision language — "so we'll go with", "agreed", "let's do it". Each hit is a candidate for section 1.
2. Search for verbs of obligation — "I'll", "can you", "by Friday". Each hit is an action item waiting for an owner. The transcript's timestamps tell you the moment to re-check if a commitment is vague.
3. Mark what you can't resolve — every "we should look into that" becomes an open question with a name attached.
4. Copy numbers verbatim from the transcript, never from memory. This is why the transcript beats your notes: your notes say "around 40k"; the transcript says "forty-eight, maybe forty-nine with support".
5. Cut by the 5% rule: one page of minutes per hour of meeting. Longer than that and nobody reads them, which makes them archive, not minutes.

The automated first draft, on your machine

QuickSpeak Pro automates the draft with an on-device brief. After a recording stops, a small language model — running through llama.cpp in WebAssembly, inside your browser — reads the transcript and produces the four sections that matter: summary, key decisions, open questions, and action items. Because the model runs locally, the draft of your confidential meeting is generated on the machine the meeting happened on; nothing is uploaded for summarization, which is where most cloud notetakers make their trade. The engineering write-up covers how that's possible and what small local models honestly can't do.

The workflow, end to end:

1. Record the meeting as usual — tab, desktop, or mic. The free tier covers this part without limits.
2. Open the meeting and generate the brief (Pro — every install starts with 14 days of full Pro, no card). Seconds later you have a structured draft with the decisions and actions the model found.
3. Correct names and fix misattributions. The brief is a first pass from a machine that heard the words but doesn't know your org chart. Rename "Speaker 3" before you circulate anything.
4. Add the judgment the model can't: context, politics, the decision that was made silently by nobody objecting. This is the part of minute-taking that's actually work, and it's yours.
5. Export to Markdown (Pro) and paste into wherever minutes live — Notion, a wiki, an email. Then delete the recording if your retention practice says so; it's a file on your disk, so deletion is deletion.

Which meetings deserve minutes

Not all of them. Decision meetings, client calls, and anything with commitments: yes. Status updates that exist as a document anyway: the brief is enough. Brainstorms: keep the transcript, skip the minutes — decisions come later. And for the meetings where the audio itself is sensitive, the same pipeline runs without anything leaving the room, which changes which conversations you're willing to record at all.