Action Items Extractor

The Action Items Extractor reads your meeting notes (or email thread, or transcript) and pulls out the actual to-dos. Each bullet has three parts: WHO is responsible, WHAT they're doing, and WHEN it's due. Unspecified parts get marked clearly ("Owner: TBD", "(no date)") so you know where the gaps are. It exists because the gap between "we had a meeting" and "we know what's next" is where most projects get lost.

Built by Bob Article by Lace QA by Ben Shipped May 15, 2026

Tool widget not found for slug: action-items-extractor

The tool content is available above. The interactive widget will be added soon.

How to use

1
Paste your meeting notes, email thread, or transcript into the text area. Raw notes work fine — you don't need to clean them up first.
2
Click "Extract action items." In a couple of seconds you'll get a bulleted list.
3
Each bullet uses the format: WHO — WHAT — WHEN. If the source didn't name a person, you'll see "Owner: TBD" so you know to assign it. Same for missing dates.
4
Copy the list into your project tracker (Linear, Asana, a shared doc, a Slack message).
5
For meetings with no decisions (informational only, brainstorming sessions), you'll see "No action items found." That's a feature — the tool refuses to invent tasks where there weren't any.
6
For very long transcripts, summarize section-by-section. A one-hour meeting transcript is fine; a multi-day off-site needs chunking.

📝 TL;DR Generator ✉️ Cold Email Generator 🪝 Email Subject Tester

Frequently asked questions

What's the format of each action item?

WHO — WHAT — WHEN, separated by em-dashes. Example: "Daniel — finalize the Q3 deck — by Tuesday." If a part isn't in the source, you'll see a clear placeholder: "Owner: TBD" for missing assignees, "(no date)" for missing deadlines. That way you can see at a glance where the source was vague and ask the right follow-up questions.

What if there are no action items?

The tool will say "No action items found. The text appears to be informational only." That happens for purely discussion-based meetings, brainstorming sessions, or status-update threads where nothing got assigned. It's a deliberate refusal to fabricate tasks — better to surface a clean "nothing here" than invent action items that weren't decided.

Will it catch implicit action items?

Sometimes. If someone says "I'll look into that" or "we should probably check this," the tool will usually pick those up but flag them as vague. The clearer your meeting language, the cleaner the output. "Daniel will look into pricing by Friday" produces a clean bullet; "someone should probably look at pricing" produces "Owner: TBD — look at pricing — (no date)" which is technically correct but useless — and the tool surfacing that is doing you a favor.

Can I paste an email thread?

Yes. Just copy the whole thread (including the reply chain) and paste. The tool reads the latest messages forward and pulls out commitments — "I'll send the slides tomorrow," "Can you confirm by EOD Friday?" Useful for long client threads where you need to compile what everyone promised.

How accurate is it for transcripts?

Decent. Audio transcripts (Otter, Descript, Zoom auto-transcripts) work well — the tool reads through the noise and identifies decisions. The main failure mode is when a transcript misattributes who said what — if the transcript says "Daniel: I'll send it" but actually Maria said it, the action item ends up under Daniel's name. Spot-check before pasting into your project tracker.

Ratings & Reviews

Rate this tool

Loading reviews…

What this tool does

The Action Items Extractor reads meeting notes, email threads, or transcripts and returns a clean bulleted list of action items. Each bullet has three parts: who owns it, what they're doing, and when it's due. The structure exists because the gap between "we had a meeting" and "we know what's next" is where most projects quietly stall.

The output format

Each action item follows the same shape:

- WHO — WHAT — WHEN

For example:

- Daniel — finalize the Q3 deck — by Tuesday
- Maria — confirm vendor pricing with finance — (no date)
- Owner: TBD — push announcement on Twitter — Aug 15

Missing parts are flagged clearly. Owner: TBD and (no date) tell you exactly which decisions need a follow-up question before this can ship.

What makes a good input

Clear language in the source. "Daniel will send the slides by Friday" produces a clean bullet. "Someone should probably look at this" produces a vague bullet — and surfacing that is doing you a favor.
Time stamps and names. Transcripts with speaker attribution and timestamps produce much better assignment-to-person accuracy.
Focused scope. A 30-minute meeting transcript works well. A six-hour off-site transcript needs chunking (paste 30-minute sections separately).

What doesn't work as well

Brainstorming sessions — the tool will correctly return "no action items found" rather than invent tasks. That's the right answer.
Transcripts with bad speaker attribution — if the transcript misattributes who said what, action items get assigned to the wrong person.
Notes with implicit commitments — "we agreed it'd be good if pricing got reviewed" might or might not get picked up depending on phrasing.

Privacy note

Pasted text passes through the AI worker. We don't store the plaintext — there's a 7-day content-hash cache (hash only, not text) so identical pastes return identical extracts free. We don't sell, share, or train on your meeting notes.