From meeting transcript to decision record: keep the exact words

A meeting transcript is the most complete record a team will ever have of a conversation, and one of the least useful. Every decision is in there somewhere, between the small talk and the tangents, and a month later nobody can find any of them.

Turning a transcript into a decision record is mostly about one rule. Get that right and the rest is bookkeeping.

The rule: no decision without the words it came from

Every decision you record should carry the sentence from the transcript that made it, quoted exactly, not a summary of it.

Summaries drift. Whoever writes them up remembers the meeting through what they wanted from it. “We should probably look at a one-year renewal” becomes “Agreed: one-year renewal”, and a maybe has turned into a commitment nobody made. An exact quote cannot drift that way, and anyone who doubts the record can check it against the transcript in seconds.

The same goes for summaries written by AI tools. A summary that reads well can still state a decision more firmly than anyone in the room did. The quote is what lets you tell the difference.

A decision, or still a question?

Most of the damage in a decision record comes from things filed as decisions that were never decided. The test is simple: has a choice actually been made?

• Decided: “We’ll renew for a year.” “Let’s go with the annual plan.” “Agreed, no three-year term.”
• Not decided yet: “I’m leaning towards renewing.” “We should probably…” “Let’s sleep on it.” “Can we find out whether…?”

Anything in the second group is an open question, and it belongs on the record as one, with the same quote and someone to answer it. A question written down is useful. A question filed as a decision is how two teams end up acting on different answers.

What to take out of a transcript

For each meeting, you want four kinds of thing, and each one gets its quote:

• Decisions: choices actually made.
• Open questions: things being weighed, and who is finding out.
• Risks: what someone said could go wrong.
• Assumptions: what the decision depends on being true. These are the ones that quietly stop being true later.

Add the meeting’s name and date to each, and a link back to the transcript. That is the whole record. Action items matter too, but they belong in your task tracker; this record is about why.

A worked example

Here is a short, invented excerpt from a vendor review:

And here is the record it should produce:

• Decision: Renew with the current vendor for one year; revisit the move in January. “…we settled on a one-year renewal with the current vendor, and we revisit the move in January”
• Open question: Can procurement negotiate the 18% increase? (Dana is asking.) “Can procurement push back on the 18%?”
• Risk: The export might not carry the history across. “…the export worries me.”
• Owner noted: Priya is testing the closed-lost export. “Priya owns testing the closed-lost export.”

Notice what is not on it: Sam’s “leaning towards moving”. It was never decided, so it is not a decision. If the team had already recorded a plan to move, though, this meeting has just contradicted it, which is exactly the situation in our example board and the subject of the first guide.

Doing it by hand, in ten minutes

• Do it the same day. The transcript is still fresh enough that you know which sentences mattered.
• Search the transcript, don’t reread it. Look for “decided”, “agreed”, “let’s go with”, “we’ll” and question marks. Then read around each hit.
• Copy the sentence, then write the one-line version. In that order, so the quote leads and the summary has to agree with it.
• Ask the person who made the call to check it before it goes in the shared record. It takes them a minute, and it settles the wording while everyone still remembers.
• Before saving a decision, look for an earlier one on the same subject. If they cannot both stand, say which one does.

Where doing it by hand breaks down

Ten minutes a meeting is fine for one weekly meeting. Across several teams and many meetings, it is the job that slips first in a busy week, and the comparison with earlier decisions, the step that catches contradictions, is the one that slips first of all.

What EchoLogic does about it

In EchoLogic you upload the transcript (a .txt, .md, .vtt, .pdf or .docx file) or write the meeting up as a note. Echo picks out the decisions, open questions, risks and assumptions, and keeps each one with its quote. A quote is kept only if those words are actually in the transcript, and something only leaned towards is filed as a question, not a decision.

Each new decision is then checked against what has already been decided on every board you can see, and a pair that cannot both hold is flagged. There are no integrations yet, so recordings are not picked up from your meeting tool: you upload the transcript.

See it on a real board

The example board is the one every EchoLogic trial starts on: the decisions, risks and questions Echo picked out of a chat, a meeting and a note, each with the words it came from, and two decisions that disagree. No signup.

More guides

• Why your team keeps re-arguing decisions it already made