DEV Community

Mira
Mira

Posted on

How to Get Action Items With Owners and Due Dates Out of Your Meeting Transcripts

#saas #tutorial #webdev #productivity

Every meeting ends with commitments scattered through conversation:
"I'll send it by Friday." "Priya will draft the page by the 10th." "We decided to launch in January."

A week later, nobody can find them. Here's how to pull them out reliably, by hand and with a tool.

Why summaries don't solve this

A summary tells you what a meeting was about. It doesn't give you a list you can work from: every commitment, from every meeting, with a name and a date attached, in one place. Fathom's own task sync, as one example, pushes tasks only to Asana, only assigned to you, without the due date — so even inside one tool, the list you need doesn't exist yet.

The manual method (works, costs time)

  1. Pick a fixed set of search phrases and use them on every transcript: "I'll", "I will", "will " (then scan), "by Friday / Monday / tomorrow", "by the", "due", "decided", "agreed", "action item", "TODO".
  2. For every hit, write down four things in a spreadsheet: the commitment in the person's own words, the owner, the due phrase exactly as said, and the meeting date. You need the meeting date because "by Friday" only becomes a real date if you know which Friday — the Friday after that meeting.
  3. Resolve every relative date by hand: "by next Monday" from a Nov 6 meeting is Nov 16 (if "next" means the Monday of next week) — and write down which rule you used, because you'll second-guess it later if you don't.
  4. Do this for every meeting, every week, forever. That's the real cost: not doing it once, it's keeping it up.

The tool method

Disclosure: I built MeetScribe.

MeetScribe's extractor is rule-based (no AI, offline, runs on your computer). It scans sentence by sentence for those same patterns — "I'll…", "Name will…", "Name to…", "Name needs to…", "assigned to Name", "Action item:" labels — and for decisions ("we decided", "agreed to", "going with", "we approved"). Owners are checked against the meeting's actual speakers so a random capitalized word doesn't become a person. Due phrases are resolved to calendar dates against the meeting date.

One command:

python -m meetscribe actions
Enter fullscreen mode Exit fullscreen mode

Real output from its included samples (4 meetings, verified 2026-11-07): 14 action items, 6 decisions. Examples:

  • "Jordan Ellis will follow up with the corrected invoice by end of week." (owner: Jordan Ellis, due 2026-11-06)
  • "Alex Morgan to send the signed form by Nov 12" (owner: Alex Morgan, due 2026-11-12)
  • Decision: "We agreed to extend the trial by two weeks while your team finishes the security review."

Honest limit: it'll miss a commitment phrased in an unusual way. Every extracted item quotes the full sentence, so you can check it in context, and it never invents one that isn't in the text.

Trial covers 5 imports free; $29 one time after: https://solopreneur87.gumroad.com/l/mrysy

The rule either way

If a commitment matters, it needs a name, a date, and a place it lives outside the transcript. Pick a method you'll actually keep doing weekly. A perfect system you abandon in week three loses to a simple one you keep.

Top comments (0)