Meeting notes in 90 seconds
From raw notes to structured action items with owners and deadlines
After this, you'll be able to paste raw meeting notes into Claude and receive a structured output of action items (with owners and deadlines), key decisions, and open questions in under 90 seconds.
Before you start
Before diving in, complete Write your first onboarding document so you have practiced getting structured, multi-section output from Claude.
The idea
The fastest way to lose a meeting's decisions is to let Claude guess who owns each action item. Paste your raw notes in and Claude structures them into owners, deadlines, and decisions in about 90 seconds, but it infers ownership from context and will occasionally pin a task on the wrong person. The skill is making it flag the gaps instead of filling them with confident guesses.
Here is the before and after: A project manager pastes her messy 45-minute sync notes and Claude returns clean action items, but two are assigned to whoever spoke last, not whoever actually owns them. The fix is in the prompt: she asks Claude to mark any item missing a clear owner or deadline as [MISSING OWNER] or [MISSING DEADLINE] instead of guessing. Now the output flags the three items she needs to confirm, and the rest is ready to send after a 2-minute review.
Now try it: Paste the raw notes from your most recent meeting into Claude and run the prompt from the exercise below, which builds in the [MISSING OWNER] and [MISSING DEADLINE] flags for you.
The 90 seconds is the easy part; the value is catching the owner Claude guessed wrong before your team does.
Try it (8 min)
Watch out for
- Waiting until you have 'clean' notes to try this. Claude handles messy, incomplete, and abbreviation-filled notes well. The messier your notes, the more time you save by not cleaning them before pasting.
- Skipping the meeting context lines at the top. Without attendee names, Claude cannot assign owners and will use generic placeholders.
- Treating the first output as final without checking for misattributed owners. Claude infers ownership from context and occasionally attributes an action to the wrong person when multiple people were discussing the same topic.
- Using this only for team syncs. The same structure works for client calls, vendor meetings, investor updates, and any meeting where follow-through matters.
- Pasting confidential client or employee details without checking your plan's data settings first. Before processing sensitive notes, confirm your workspace's data and privacy settings; treat anything you would not email externally as needing that check.
Paste this into Claude
Here are my raw notes from a meeting that just ended. Please process them into a structured summary. MEETING CONTEXT: - Meeting type: [e.g., weekly team sync, client check-in, project kickoff, retrospective] - Attendees: [list names and roles] - Duration: [e.g., 45 minutes] - Date: [today's date] RAW NOTES: [Paste your raw notes here. Typos, abbreviations, and incomplete sentences are fine.] Please extract and format as three sections: 1. ACTION ITEMS: each formatted as [Owner]: [Task] by [Deadline or "no deadline set"] 2. DECISIONS MADE: bullet points, each a complete sentence describing what was decided and by whom 3. OPEN QUESTIONS: questions that were raised but not resolved, with who is responsible for finding the answer If any action item is missing a deadline or owner, flag it with [MISSING OWNER] or [MISSING DEADLINE] so I can fill it in before sending.
What good looks like
- Every action item has a named owner, even if you had to infer it from context
- Missing owners and missing deadlines are flagged rather than omitted
- The decisions section uses complete sentences, not fragments
- The open questions section identifies who is responsible for resolving each question
- You could send this output (with a 2-minute review) instead of spending 20 minutes editing manually
When this breaks
- Fails when the raw notes contain no names or role identifiers, because Claude cannot assign owners without knowing who was in the room. Always include attendee names and roles, even as a quick one-line list at the top.
- Degrades when you paste notes from several meetings into one request, because Claude blends action items across contexts and may attach them to the wrong meeting or owner. Process one meeting per conversation.
AI can help with this
Use Claude, ChatGPT, Gemini, Microsoft Copilot, Codex, Notion AI, or another approved work AI based on the system your team actually uses. Paste the lesson prompt with one real process or workflow, require the assistant to separate facts from assumptions, then verify the owner, exception path, and human review point before you use the output.
You can now
You can complete the lesson outcome against a real operations process, source, or recurring workflow.
- You can verify that every action item has a named owner, even if you had to infer it from context.
- You can verify that missing owners and missing deadlines are flagged rather than omitted.
- You can verify that the decisions section uses complete sentences, not fragments.
- You can verify that the open questions section identifies who is responsible for resolving each question.
Key takeaways
Raw meeting notes become a structured action-item summary in about 90 seconds. The remaining work is verification: confirm the owners Claude inferred and fill the gaps it flagged, then send.
- Messy notes work. Do not clean them before pasting. Paste them raw and let Claude structure them.
- Always include attendee names and roles. Without names, Claude cannot assign owners.
- Flag missing owners and deadlines rather than omitting them. Incomplete action items are worse than flagged gaps.
- The three-section format (action items, decisions, open questions) captures everything a meeting produces and nothing it does not.
- This structure works for every meeting type: team syncs, client calls, retrospectives, and vendor meetings.
Go deeper