Transcript to Action Items
A transcript is a record. Make it a to-do list.
A transcript is a complete record of a conversation and a terrible record of what happened next. It preserves every “um,” every tangent, and every half-commitment, but it does not tell you who agreed to do what.
Turning a transcript into action items is a filtering problem. You are not summarizing the conversation; you are looking for a small set of linguistic patterns and discarding everything else.
What to look for
The signal is in modal verbs and first-person commitments:
- “I'll send the deck by Friday.”
- “We agreed to move the launch.”
- “Sam can check the contract tomorrow.”
- “Can you follow up with the vendor?”
- “Let's revisit this next week.”
The noise is everything else: opinions, background, anecdotes, and restatements of the problem.
The four-column extraction
For each candidate sentence, extract:
| Field | Question | Example |
|---|---|---|
| Task | What will be done? | Send the revised deck |
| Owner | Who committed? | Priya |
| Due | By when? | Friday |
| Source | Where was it said? | 00:12:04 |
The source field matters more than it seems. When someone disputes an action item, the timestamp ends the argument.
Step 1: Clean the transcript
Transcripts carry noise that gets in the way of extraction:
- Timestamps —
[00:12:04]or00:12:04. Strip them from the task text but keep them in the source field. - Speaker labels —
Priya:is useful; keep it for attribution. - Filler — “um,” “you know,” “like.” Remove it before reading for tasks.
- False starts — “I'll— actually, Sam will send it.” The final commitment wins.
If the transcript has no speaker labels, attribution becomes guesswork. Use the surrounding context and mark uncertain owners as unassigned rather than guessing.
Step 2: Read for commitments, not topics
A transcript is organized by time, not by importance. Do not read it top to bottom looking for “the important part.” Scan for these cues:
- First person + future: “I'll…”, “I'm going to…”, “I can…”
- Name + modal: “Priya will…”, “Sam should…”, “Alex can…”
- Requests: “Can you…?”, “Could you…?”, “Would you mind…?”
- Collective obligations: “We need to…”, “Someone should…”
- Decisions: “We agreed…”, “Let's go with…”, “Approved.”
Each cue produces a candidate. Most candidates are real; some are rhetorical. “I'll take a look” may mean nothing. “I'll send it by Friday” means something.
Step 3: Resolve the owner
Ownership is the hardest part of transcript extraction.
- “I'll…” with a speaker label → the speaker is the owner.
- “Priya will…” → Priya is the owner, even if someone else is speaking.
- “Can you…?” → the person addressed is the owner; look at the next speaker or the name in the sentence.
- “We need to…” → no owner. Mark it unassigned and raise it in the follow-up.
Do not assign a task to a team. “Marketing will…” is not an owner. Pick a person or leave it blank.
Step 4: Normalize the dates
“Friday” is fine if everyone knows which Friday. “Next week” is not a date. Convert relative language when you can:
| Said | Write |
|---|---|
| “by end of day” | Today, 5:00 p.m. |
| “next week” | Week of Nov 16 |
| “after the launch” | After Nov 18 |
| “soon” | Ask for a date |
If the transcript does not resolve the date, leave it blank and put the question in the follow-up. A fake date is worse than no date.
Step 5: Separate decisions
A decision is not a task, but it belongs in the same recap. Look for:
- “We decided…”
- “We agreed…”
- “Let's go with…”
- “Approved.”
- “The final call is…”
List decisions separately, with the date of the decision. This prevents the same debate from reopening next week.
A worked example
Transcript:
[00:12:04] Priya: I'll send the revised deck by Friday. [00:13:10] Alex: We agreed to push the launch to Nov 18. [00:14:22] Sam: I can check the vendor contract tomorrow. [00:15:40] Priya: Someone should update the pricing page.
Output:
| Task | Owner | Due |
|---|---|---|
| Send the revised deck | Priya | Friday |
| Check the vendor contract | Sam | Tomorrow |
| Update the pricing page | Unassigned | — |
Decision: Launch moved to Nov 18.
The last row is the most valuable one. “Someone should” became a visible gap, and the follow-up meeting can start by filling it.
The follow-up message
Keep it under 200 words:
Decisions
- Launch moved to Nov 18.
Actions
- Priya: send revised deck — Friday
- Sam: check vendor contract — tomorrow
- Unassigned: update pricing page — need an owner
Reply if I misheard anything.
That last line gives people permission to correct the record without re-opening the whole meeting.
Do it with text, not audio
You do not need to upload the recording. Paste the transcript into Transcript to Action Items; it strips timestamps, finds speaker labels, and separates decisions from tasks. Read the result before sending — extraction is pattern matching, and patterns miss context.