Meeting Notes to Action Items

What You Get

A prompt that takes a raw meeting transcript (from Otter, Fathom, Fireflies, or your own notes) and turns it into structured notes with decisions, action items, owners, and deadlines — in a format people will actually read.

The Prompt

Copy and paste this into Claude. Replace the bracketed sections with your own info.

You're a meeting notes expert. Your job is to turn messy transcripts into clear, actionable summaries that people will actually use.

Here's what I need you to do:

**The transcript:**
[Paste the entire meeting transcript here]

**Meeting context:**
- Type of meeting: [client call / team sync / strategy session / 1:1 / other]
- Attendees and their roles: [List them, e.g., "Sarah (PM), Mike (engineer), Hazel (client)"]
- Output format I want: [Notion / email / Slack message / other]

**Your instructions:**
Create a structured summary with these sections:

1. **Summary (2–3 sentences max)**: What happened. What we decided. Why it matters.

2. **Key Decisions**: Number them. Make them crystal clear. Examples: "Pricing will be tiered (basic/pro/enterprise)" or "Launch date is May 15."

3. **Action Items Table**: 
   - Columns: Task, Owner, Deadline, Priority
   - Each task should be specific enough that someone can do it without re-reading the transcript
   - Be ruthlessly concise with task descriptions
   - Mark priority as High / Medium / Low

4. **Discussion Topics for Follow-Up**: Anything important that came up but didn't have a clear decision or owner yet.

5. **Parking Lot**: Things we talked about but decided not to act on right now. Include why we're parking it if relevant.

**Critical rule**: Be ruthlessly concise. Nobody reads 3-page meeting notes. If a discussion point didn't lead to a decision or action item, summarize it in one sentence or skip it. The action items are the most important output.

Special instructions for [client call / team sync / strategy session / 1:1]:
- [Client call: Capture all commitments and promises. Flag anything that could be a scope creep or expectation gap.]
- [Team sync: Focus on blockers and who's unblocked to move forward. Call out dependencies.]
- [Strategy session: Prioritize decisions and next steps over discussion summaries.]
- [1:1: Note career/growth topics separately from project blockers.]

How to Use It

Step 1: Run it fast. Process the transcript within 30 minutes of the meeting while context is fresh. Don’t wait until end of day.

Step 2: Match the meeting type to your output. This matters more than you think. A client call needs different output than a team sync. Client calls should capture commitments and expectations. Team syncs should capture blockers and owners. Strategy sessions should capture decisions and next steps. The prompt adjusts for this.

Step 3: Send it out immediately. Use the formatted output as your follow-up email or Slack message. Reply-all to the meeting invite with the action items table. Your team will actually know what they’re supposed to do.

Example Output

Meeting: 30-minute client check-in call with Acme Corp
Attendees: You (Hazel), Alex (Acme’s product lead), Jamie (Acme’s marketing manager)

Summary

Alex confirmed they want a homepage redesign by end of May and are willing to do user testing in April to validate messaging. Jamie will prep a competitive analysis before our next call to inform the creative direction.

Key Decisions

1. Homepage redesign is the priority project (not blog optimization).
2. User testing happens in mid-April with Acme’s customer base.
3. Budget is approved for copywriting contractor + design work.

Action Items

Discussion Topics for Follow-Up

• Budget for ongoing analytics tooling after launch (came up, but Acme wants to decide after seeing initial results)
• Whether to migrate from HubSpot to a different CMS (Alex mentioned it; agreed to revisit in Q3)

Parking Lot

• Blog redesign (decided to pause until after homepage ships)
• Premium membership feature (interesting idea, but Acme has limited dev capacity)

Tips

Send notes within an hour. Speed beats perfection. An imperfect summary sent the same day is worth more than a perfect one sent three days later.

Add a flag for sales and client calls. Modify the prompt to include: “Flag any commitments, promises, or scope changes we made. If we said yes to something not in the original scope, mark it clearly so we don’t miss it in invoicing.”

Pair this with your calendar. Before the meeting, paste in the agenda or previous notes into Claude. You’ll get pre-structured notes that map directly to what you planned to cover.

If your meetings don’t produce action items, you might not need that meeting. Dead meeting? No decisions, no owners, no deadlines. Cancel the next one and use email instead. You’re welcome.

Next Step

Want to build a complete meeting workflow — transcript processing, action item tracking, and custom follow-up templates for your specific team?

Book a Build Session — $350 for a 90-minute working session where we customize this prompt to your meeting types, integrate it with your tools (Notion, email, Slack), and set up templates your team will actually use.

Built with Claude. Every prompt in this playbook library has been tested in the latest Claude model.