From Raw Notes to a Clean Action-Item List
Most people read back through raw notes, a meeting, a brainstorm, a phone call, and manually pull out what needs to happen next. That works, but it means every action item gets extracted by eye, one more time, from notes that were never organized around action in the first place.
Tip
Ask Claude to separate action items from everything else in the notes: decisions already made, context that explains why, and anything discussed but not resolved. Mixing all three into one list is what makes notes hard to act on later.
Raw notes contain actions, decisions, and context, tangled together. A task list only needs one of those three.
Why a recap isn't the same as a task list
A meeting recap or a summary paragraph captures what happened. A task list captures what happens next. Those overlap, but they're not the same output, and asking for one when you need the other means doing the real extraction work yourself afterward, reading the recap and mentally sorting which lines are actually actions.
Say a working session covered a launch date, a disagreement about scope that got tabled, and three concrete follow-ups. A recap would describe all of that in the order it happened. A task list needs only the three follow-ups, each with enough detail to act on later without rereading the whole recap to remember what "follow up with the vendor" actually meant at the time.
Before: paste in raw notes, ask Claude to summarize them, reread the summary and manually copy out anything that looks like a task.
After: ask Claude to extract action items directly, with the fields you actually need to act on them, separated from everything that isn't an action.
A process for extracting action items
- 1
Paste in the raw notes exactly as they are
Don't clean them up first. Fragments, shorthand, and out-of-order thoughts are fine. Claude can work with notes in the state you actually took them, and cleaning them up yourself first defeats the point of asking for help extracting structure.
- 2
Specify the fields you want for each action item
Ask for what the task is, who owns it if that's clear from the notes, and any deadline mentioned. Without this, Claude will guess at a reasonable format, which usually means a plain bullet list missing the fields you'd actually need to act on it later.
- 3
Ask it to separate actions from decisions and open questions
A decision that was already made doesn't need a task; it needs to be recorded so it isn't relitigated later. An open question that wasn't resolved isn't an action either. It's something to flag, not something to check off.
- 4
Review for anything the notes implied but didn't state directly
If the notes say "need to hear back from legal before we can move," that's an action even though it's phrased as a fact. Ask Claude to flag implied follow-ups like this rather than only extracting lines that explicitly say "will do."
Here are my raw notes from today's working session. Pull out a list of action items, each with what needs to happen, who owns it if the notes say, and any deadline mentioned. List decisions that were made separately, and flag anything discussed but not resolved as an open question instead of a task.
”This same process works regardless of where the notes came from. A brainstorm session's notes will usually produce mostly open questions and a handful of firm actions; a status call's notes usually produce more owned tasks with real deadlines attached. The extraction technique doesn't change between the two, only what comes out of it.
Inside Claude Tutorial
Separating actions from context is a transferable habit.
Asking for one specific kind of output, instead of a general summary you sort through yourself, comes up constantly. The app builds this habit through short lessons that apply it to different kinds of everyday tasks.
When the notes don't name an owner
Not every action item has a clear owner in the original notes. Rather than let Claude guess who's responsible, which can quietly assign a task to the wrong person, ask it to mark ownership as unclear so a human makes that call instead.
Does every action item have a clear next step, not just a topic
Is ownership marked as unclear anywhere the notes didn't say, instead of guessed
Are decisions listed separately from actions, not mixed into the same list
Would someone who wasn't in the room understand each item without more context
For any action item where the notes don't clearly say who owns it, mark the owner as "unclear" instead of guessing based on who talked about it most.
”Turning this into a habit, not a one-time ask
The real value shows up once this becomes routine rather than something you only do after a big meeting. The same four-field request, task, owner, deadline, source, works whether the notes are from a fifteen-minute call or a two-hour planning session, which makes it worth saving as a template you reuse instead of retyping the instructions every time the same kind of notes show up.
A small addition worth making once the basic version is working: ask Claude to note which source each action item came from, useful once you're running this on notes from more than one meeting in the same week and need to trace a task back to where it originated.
Add a "source" field to each action item noting which part of the notes it came from, so I can trace it back if I need more context later.
”Continue reading
- Turning Meeting Notes Into a Follow-Up in Minutes: for turning the same kind of raw notes into a follow-up email instead of a task list.
- Building a Claude Workflow You Can Reuse Every Week: saving this exact extraction request as a template instead of retyping it each time.
- Brainstorming Better Ideas With Claude: another everyday task that gets sharper with a specific, structured request instead of an open-ended one.