Turning a Transcript Into Notes Worth Reading

Nobody has ever read a transcript

A transcript feels like the valuable thing. It is complete, it is verbatim, it is proof. It is also, for practical purposes, unreadable.

An hour of conversation becomes a very long document, and reading it properly takes roughly as long as attending the meeting did. So it defeats the entire purpose. Worse, transcripts read strangely even when they are accurate, because spoken English on the page looks like nobody involved can form a sentence. Everyone repeats themselves, everyone trails off, half the sentences never finish and the other half start twice. Send that to a client and you have not shared a record, you have shared an embarrassment.

The transcript is raw material. It is evidence you can go back to when a question comes up. It is not the deliverable, and treating it as one is the most common mistake in this whole subject.

There is a second, quieter problem with forwarding the whole thing. A transcript contains everything, including the aside about a supplier, the half joke about a colleague, and the two minutes at the start where somebody complained about their commute. You may be perfectly comfortable with all of that. The person you forwarded it to, and the person they forward it to, are working from a document nobody edited. Sending a summary is not just kinder to the reader. It is a decision about what leaves the room.

What people actually want

Ask yourself what a colleague opening your notes on a phone, walking between buildings, is trying to find out. In practice it is four things, in this order.

Decisions. What did we settle? Not what was discussed, what was settled. This is the part that has to survive.

Actions. Who is doing what, by when. Lesson four is entirely about this, because it is where most summaries quietly fail.

Open questions. What did we raise and fail to resolve? These are the things that will bite in a fortnight if nobody writes them down.

Parked items. Different from open questions, and worth separating. A parked item is something the group deliberately decided not to deal with now. Writing it down explicitly stops the same person raising it again next month, and stops everyone else wondering whether it was forgotten.

Everything else is context, and context goes at the bottom in a short paragraph, if at all.

Structure by outcome, never by chronology

The single biggest improvement you can make is to stop organising notes in the order things happened.

Meetings do not proceed tidily. A decision gets half made at ten past, revisited at half past when someone joins late, and finally confirmed in the last two minutes. Chronological notes record all three moments and leave the reader to work out which one counts. Notes organised by outcome record the decision once, in its final form, and never mention the two false starts.

The order things were said in is a fact about the meeting. It is almost never useful information about the work, and the only people who need it are the ones reconstructing an argument, who can go to the transcript.

Lazy prompt, specific brief

The default instruction people give is two words long, and it produces exactly what two words deserve.

The good prompt is longer, and that is the whole point. You are not asking for a summary, you are specifying a document. Write it once, keep it somewhere you can find it, and paste it forever.

The template

Below is a transcript of a meeting. Write notes for colleagues who were not there.
Use exactly these sections, in this order:
DECISIONS
Only things that were actually settled. One line each, naming who confirmed it.
If it was discussed but not concluded, it does not belong here.
ACTIONS
A table with columns: Task, Owner, Due date.
One row per action. Start each task with a verb.
If no owner was named, write UNASSIGNED. If no date was said, write NO DATE.
Never infer an owner from who happened to be speaking.
OPEN QUESTIONS
Things raised and left unresolved. Note who raised each one.
PARKED
Things the group deliberately chose not to deal with now, and when they said
they would return to them.
CONTEXT
Two sentences maximum, for anyone who needs the background. Optional.
Rules:

Use people's real names as they appear in the transcript.
Keep every line under 20 words.
Leave out small talk, scheduling chat and anything not related to the work.
Do not smooth over disagreement. If two people disagreed, say so.
If something is ambiguous, put it under OPEN QUESTIONS rather than guessing.
Do not add anything that is not in the transcript.
TRANSCRIPT:
[paste it]

Two lines in there do most of the heavy lifting. "Do not smooth over disagreement" matters because summarisers are relentlessly agreeable by nature and will turn a genuine split into a consensus that never existed. "If something is ambiguous, put it under OPEN QUESTIONS" gives the model somewhere to put uncertainty, which is the only way to stop it guessing.

Different readers, different documents

One meeting can produce more than one set of notes, and the good version is written for a particular reader.

The internal version names people and includes the disagreement. The client version covers what was agreed and what happens next, with the internal wrangling removed. The version for the record, the one that gets filed and read in a year, needs the reasoning: why this option and not the other two.

You do not need three separate prompts for this. Add one line to the template.

Rewrite the notes above for this reader: [a client / my director / someone
joining the project next month].
Lead with what matters to them. Cut anything internal that is not their business.
Keep every fact identical. Do not soften a decision to make it sound better.
Under 200 words.

Length is a feature

Set a limit and enforce it. If your notes run past one screen, nobody reads to the bottom, which means the action you buried in paragraph nine does not exist.

If the meeting genuinely produced more than a screen of decisions, that is worth knowing too. It usually means the meeting was doing the work of three meetings, and the fix is not a longer summary.