You finish a call. Five things were agreed, three of them informally, one of them urgent. You have notes — half-written because you were also talking. By the next morning, you remember two of the five. The rest resurface when someone follows up asking where their thing is.
This is not a discipline problem. It is a systems problem. The gap between “the meeting ended” and “the action items are assigned and tracked” is where most commitments disappear. Open loops from meetings are one of the biggest sources of mental noise for business owners — not because the work is hard, but because the capture step is slow and imperfect.
I use Claude to close that gap, and the workflow is straightforward once you have set it up. The key is giving Claude the transcript, not the notes. Notes carry what you chose to record. Transcripts carry everything that was said — including the asides, the verbal agreements, and the informal “can you just quickly” requests that never made it to anyone’s list.
Why Notes Alone Don’t Work
The problem with relying on your notes is that you wrote them while doing something else. You were listening, thinking about what to say next, or managing the dynamic in the room. Notes are a filtered record of what felt important in the moment. The transcript is the source of truth.
Most business owners I work with have the same pattern: good meetings, patchy follow-through. Not because they are disorganised — they are not — but because the extraction step is slow. When it is slow, it gets done partially. When it is done partially, commitments fall through.
Claude accelerates the extraction so it gets done completely, every time, in about five minutes per call. The consistency is what makes it a system rather than a one-off.
The Setup: Transcript First
The tool I use for transcription is Otter.ai. It connects to Zoom, Google Meet, and Microsoft Teams, and the transcript arrives automatically after every call. If you are not using a transcription tool yet, this is the first thing to set up — the transcript is the input, and without it the rest of this does not work.
Once the transcript exists, the Claude step takes roughly ninety seconds for a forty-minute call. Copy the transcript text, open Claude, and run the prompt below.
The Prompt That Structures the Output
The prompt I use asks Claude to extract four specific categories. The output shape matters as much as the extraction itself — if you ask for “action items”, you get a general list. If you ask for four structured things, you get four structured things.
Here is the prompt:
“Read this meeting transcript and extract the following. Action items: one line each, with the owner named and the deadline if one was mentioned — flag any item where no owner was named. Decisions made: what was agreed, by whom, and on what basis. Open questions: things that came up but were not resolved. Follow-up sends: anything someone said they would send, share, or check.”
That structure forces Claude to read the transcript for four different things, not just the obvious ones. The follow-up sends category catches a large number of commitments that never appear in standard action lists — “I will send you the brief”, “can you share that link”, “let me find that number” — all of which create expectation on the other side of the call.
This is a specific application of the broader principle: give Claude a job with defined outputs, not an open question. The more precisely you define what you want back, the more reliably you get it.
What the Output Looks Like
The output is clean, scannable, and immediately usable. Each action item includes the responsible person, the task, and the deadline if one was discussed. The decisions section documents what was agreed so you have a record if it is ever contested. The open questions list gives you an agenda starter for the next meeting.
One thing worth noting: Claude flags action items where no owner was named. This is genuinely useful because unnamed commitments are the most likely to be dropped — everyone assumes someone else is handling it. Seeing them flagged makes the ambiguity visible immediately rather than two weeks later.
For a call with several people and forty minutes of transcript, the whole extraction takes about ninety seconds. The output is ready to review before your next calendar slot starts.
Connecting the Output to Your Task System
The action list from Claude is not the end of the workflow — it is the input to wherever you track your commitments. Each action item becomes a task, assigned to the right person, with the deadline from the call. I use Asana for this; the specific tool matters less than having a consistent destination.
The reason this works as a system rather than a one-off is that every call produces the same output shape. Your action items, your team’s action items, client commitments, your own promises to others — all go through the same extraction before they enter the tracking system. Nothing relies on someone remembering to update a list manually.
This is the same principle behind using Claude as a project manager with two files — the value is not in any single interaction but in the consistent structure that runs across every interaction. Once the extraction step is wired, it happens every time, not just when you remember to do it.
Processing the Output with the 5 Ds
Once Claude has produced the structured list, each action item still needs a decision. The 5 Ds framework — Do, Defer, Delegate, Drop, Diary — applies here exactly as it does to your inbox. The difference is that you are now working from a clean, structured list rather than a memory of the call, which makes the triage faster and less likely to miss something.
Items that are yours and urgent get scheduled. Items that belong to someone else get delegated with a deadline. Items that have no clear owner get flagged for the next meeting. Items that are no longer relevant get dropped. The whole process runs in ten minutes if the extraction has been done well.
Frequently Asked Questions
Do I need a transcript tool, or can I paste in notes?
Notes will produce a partial list. The transcript produces a complete one. If you do not have a transcription tool, Otter.ai has a free tier that covers most small-business meeting volumes. The additional cost is low relative to the commitments it recovers.
How long does the extraction take?
For a forty-minute call, about ninety seconds once the transcript is pasted. Longer calls take proportionally longer — a ninety-minute call with several participants might take three to four minutes. The point is that it is fast enough to run immediately after every call, before the next thing starts.
What if speaker names are not clear in the transcript?
Otter identifies speakers by name if they are in your account or connected to a calendar invite. If the transcript shows “Speaker 1” rather than a name, tell Claude who each speaker was at the top of the prompt — one line each. Claude will apply the names to the extracted output. This adds thirty seconds and is worth doing for any multi-person call.
Can I use this for client calls as well as internal ones?
Yes, and it is particularly valuable for client calls precisely because the commitment gap is more visible. When a client expects something and does not receive it, the cost is higher than an internal miss. Running the extraction after every client call and sending a brief follow-up summary with the agreed items is a straightforward way to build trust and avoid ambiguity.
Is this part of a wider Claude productivity system?
Yes. Meeting extraction is one job in a larger stack. The Claude AI productivity system covers how to structure Claude so it runs recurring jobs — planning, reporting, writing, triage — rather than responding to one-off questions. The NP System provides the structural layer that makes all of these jobs fit together across your business and personal contexts.
The Next Step
If your meetings currently produce action items that disappear, the fix is not better note-taking. The fix is a reliable extraction step that runs after every call, regardless of how good or bad your notes were.
Set up Otter, run the prompt above on your next two calls, and compare the list you get to what you would have captured manually. The difference makes the case better than any explanation.
If you want to build the wider capture and processing system that makes meeting follow-through one part of a larger structure, the NP System free course is the place to start. It covers the four phases — Capture, Process, Plan, Do — that turn Claude from a useful tool into a reliable operating layer across your whole business.
Get the free NP System course here.
For further reading, see the guide on giving Claude a job, not a question.
