Guide
How to take meeting notes with Claude
The method that works has two steps: capture rough material during the meeting (messy notes or a transcript), then hand it to Claude right after and get back decisions, action items with owners, and open questions. No bot joins the call. Here are both versions of the workflow and the prompt to steal.
Recorder bots capture one hundred percent of a meeting, which is precisely the problem: nobody rereads an hour. What you need from a meeting is usually five lines: what got decided, who owes what by when, and what stayed open. Claude is exceptionally good at producing those five lines, if you feed it something to work from.
Method 1: rough notes in, structure out
During the meeting, type fragments; nobody's grading them. "pricing 29 agreed / dana annual q / demo fri KG / logo feedback next wk". Right after, paste the mess into Claude with this:
Thirty seconds of typing during the call, ten seconds of structuring after. The flagging clause matters: you want Claude marking "annual q?" as unclear, not inventing a decision you didn't make.
Method 2: the two-minute debrief
No notes at all? Talk it out immediately after: open Claude and narrate the meeting for two minutes, stream-of-consciousness, then ask for the same three-section structure. It works because recall is nearly perfect for about ten minutes after a meeting and terrible by the next morning. This is the method I use for calls where typing would've been rude.
Where the output should live
Not in the chat, obviously; that's how meeting outcomes die twice. The actions and decisions belong in the project's running file, and if you work in Claude Projects, that file belongs in the project knowledge so every future chat starts aware of it. My loop: structure the meeting, then /jot the entries so JotThread files them by project, checkable off with /jot done as they land. The broader setup, one project per workstream with a living file, is in the Projects guide.
Common questions
Can Claude join my meetings and record them?
No, and that's a feature of this workflow, not a gap. Claude works on the material you hand it, which keeps you in control of what enters the record and sidesteps the etiquette and consent questions recorder bots raise.
What about pasting a full transcript?
Works well if you have one from your meeting software. The structuring prompt is the same; expect Claude to do a better job on a transcript than you'd do skimming it, precisely because it reads all of it.
What format should action items take?
A checklist with an owner and a date per item, grouped by project. That's also exactly the shape of a jotthread.md file, which is not a coincidence.
From the meeting to the file.
After Claude structures your meeting, /jot files the actions and decisions by project. $29 once.