Meeting Notes to Action Items
Transform raw meeting notes into structured summaries, action item tables, and follow-up emails in minutes.
The meeting ended 10 minutes ago and everyone already disagrees on what was decided. Your scrawled notes say 'John — follow up on the thing' but you can't remember which thing. Structured meeting summaries with clear owners and deadlines are the difference between meetings that drive action and meetings that repeat.
Who it's for: executive assistants managing meeting follow-ups for leadership, project managers tracking action items across multiple meetings, team leads who need to send clear recaps to stakeholders, chiefs of staff synthesizing leadership meeting outcomes, anyone tired of meetings where nothing gets done afterward
Example
"Turn these raw notes from our product review into action items" → Structured output: 3-sentence decision summary, action item table with 8 items (owner, deadline, priority), 2 open questions flagged for follow-up, key decisions documented for the record, and a ready-to-send follow-up email
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Meeting Notes to Action Items
## Your Role
You are an expert meeting analyst and executive assistant. Your job is to transform raw, unstructured meeting notes into clear, actionable outputs that drive follow-through.
## Core Principles
- Extract only genuine action items (tasks requiring someone to DO something)
- Infer owners from discussion context when not explicitly stated
- Mark deadlines as "TBD - needs confirmation" if not stated
- Include enough context so each action item makes sense standalone
- Write follow-up emails that are professional but warm
## Instructions
When given meeting notes, create three outputs:
1. **MEETING SUMMARY** (1 paragraph)
- What was discussed and decided
- Key outcomes and conclusions
- Suitable for sharing with non-attendees
2. **ACTION ITEMS TABLE**
| Owner | Action Item | Deadline | Context/Notes |
|-------|------------|----------|---------------|
- Only items requiring someone to DO something
- Infer owners from context if not explicit
- Include brief context for standalone clarity
3. **FOLLOW-UP EMAILS**
- One per person with action items
- Subject: "Action Items from [Meeting] - [Date]"
- List their specific items with deadlines
- Professional but warm tone
- Offer to clarify if needed
## Output Format
Always use markdown formatting with clear headers, tables for action items, and separate email drafts for each assignee.
## Commands
- "Process these meeting notes" - Full pipeline: summary + actions + emails
- "Just the action items" - Quick extraction without emails
- "Update from last week" - Compare with previous meeting's open items
- "Add follow-up for [person]" - Generate additional follow-up email
What This Does
Turns messy meeting notes into three polished outputs: a shareable summary paragraph, an action items table with owners and deadlines, and personalized follow-up emails for each assignee. What used to take 30-60 minutes now takes under 5.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Gather Your Notes
Have your raw meeting notes ready — typed notes, transcript, or even bullet fragments.
Step 3: Start Using It
claude
Say: "Process my meeting notes from today's Q4 planning session into a summary, action items, and follow-up emails"
What Claude Extracts
| Source | What It Extracts |
|---|---|
| Raw notes | Decisions, topics, outcomes |
| Names mentioned | Action item owners |
| Dates/deadlines | Timeline for each task |
| Discussion context | Background for follow-ups |
| Open questions | Items needing clarification |
Output Structure
## Meeting Summary
[One paragraph suitable for non-attendees]
## Action Items
| Owner | Action Item | Deadline | Context |
|-------|------------|----------|---------|
| Sarah | Draft Q4 budget proposal | Oct 15 | Based on 12% growth target |
## Follow-Up Emails
[Personalized email per assignee with their items]
Tips
- Process immediately: Run within 5 minutes of the meeting while context is fresh
- Include attendee roles: "Mike (Eng Lead)" helps Claude attribute items correctly
- Don't clean your notes: Raw shorthand works fine — messy input, clean output
- Batch meetings: Process multiple meetings from the same day in one session
Commands
"Process these meeting notes into summary and action items"
"Add Sarah as owner for the budget task with Oct 15 deadline"
"Generate follow-up emails for all action item owners"
"Compare this week's actions with last week's — what's still open?"
Troubleshooting
Action items are vague Add more context: "The discussion about X was specifically about migrating to Y by end of quarter"
Wrong person assigned Specify roles: "Mike is the engineering lead, Sarah handles product"
Missing items Say: "We also decided to postpone the API migration — add that as a tracked decision"