Meeting Notes & Summaries

What You’ll Learn

• How to turn raw transcripts or rough notes into structured, actionable meeting summaries
• How to extract decisions, action items, and owners from unstructured conversation
• How to tailor summaries for different audiences — from detailed team notes to one-paragraph executive briefs

The Use Case

Most meetings produce two outputs: a recording nobody watches and a set of half-remembered action items that slowly fade from everyone’s memory. The meeting notes problem is real — someone has to take them, they’re tedious to write well, and if they’re not done within hours of the meeting, critical context is lost forever.

Claude can close this gap dramatically. Whether you have a raw transcript from an auto-transcription tool, a set of bullet-point notes you jotted during the call, or even a rough audio recording summarized in text, Claude can transform that unstructured input into a clean, structured summary that actually gets read and acted on.

This is particularly valuable for recurring meetings (weekly standups, sprint reviews, client calls), large team meetings with many participants and parallel threads, and any meeting where decisions were made that need to be documented for people who weren’t in the room. It’s also valuable for one-on-ones where you want to keep a clean record of commitments and feedback over time.

The workflow scales: a 15-minute standup can be summarized in 30 seconds. A two-hour strategic planning session with 12 people might take 5–10 minutes of prompting to get right. Either way, it’s faster and better than doing it manually.

Step-by-Step Guide

Step 1: Gather your raw input

Claude can work with several types of input — use whichever you have:

• Auto-generated transcript — from Zoom, Google Meet, Otter.ai, or similar tools. These are the richest input and produce the best output.
• Rough notes — bullet points you typed during the meeting, even if incomplete or out of order.
• Your memory — if you have no transcript, you can describe the meeting to Claude conversationally and ask it to structure your recollections.

If using a transcript, you don’t need to clean it up first. Raw transcripts with speaker tags, filler words, and run-on sentences are fine — Claude handles them well.

Step 2: Provide meeting context before the transcript

Before pasting your transcript, give Claude the meeting’s metadata. This lets it correctly interpret what it’s reading:

• Meeting name and date
• Attendees and their roles
• The meeting’s stated purpose or agenda
• Any important background Claude should know

Example context: “This is the transcript of our weekly product team standup on March 18, 2026. Attendees: Sarah (PM), Marcus (Engineering Lead), Priya (Design), Tom and Lena (engineers). The standup format is: what did you do yesterday, what are you doing today, any blockers.”

Step 3: Specify the output format you need

Different meetings and different audiences need different summaries. Be explicit about what you want:

• Full meeting notes — comprehensive, organized by agenda item, suitable for team members who missed the meeting
• Action item list — focused extraction of tasks, owners, and deadlines
• Executive summary — 1–3 paragraphs covering decisions made and why, for stakeholders who weren’t in the room
• Decision log — just the decisions made, with brief rationale and who decided
• Follow-up email — a ready-to-send email summarizing the meeting for participants

You can ask for multiple formats in one prompt: “Give me the full meeting notes first, then below that, a separate section with just the action items as a checklist.”

Step 4: Review and correct

Claude’s summary will be structurally sound, but it may misattribute a quote, miss a nuance, or extract an action item that was actually rejected. Always review the output against your original notes or memory. For high-stakes meetings, have one other attendee review it before distributing.

If something is wrong, correct it conversationally: “The decision in item 3 was actually to delay the launch to Q3, not Q2. Please fix that and regenerate the summary section.”

Step 5: Distribute in the right format

Once your summary is accurate, ask Claude to format it for your distribution channel:

• Email: “Format this as a clean email with the action items as a bulleted checklist at the top.”
• Notion/Confluence: “Format this in Markdown with proper headers and checkboxes for action items.”
• Slack: “Give me a condensed version I can post in Slack — keep it under 300 words and use plain text, no markdown headers.”

Prompt Template

Please summarize the following meeting transcript/notes.

**Meeting context:**
- Meeting name: [e.g., "Q2 Product Planning"]
- Date: [Date]
- Attendees: [Names and roles]
- Purpose: [What was this meeting supposed to accomplish?]

**Output format I need:**
[ ] Full meeting notes (organized by agenda item)
[ ] Action items list (task, owner, deadline)
[ ] Executive summary (3 paragraphs max)
[ ] Decision log (decisions + rationale)
[ ] Follow-up email draft

**Special instructions:** [Any specific things to watch for, terminology to use, or sections to emphasize]

---

[PASTE YOUR TRANSCRIPT OR NOTES HERE]

Tips & Best Practices

1. Always include attendee roles — Claude can make smarter inferences about who owns what action item when it knows that Marcus is the Engineering Lead and Sarah is the PM. Without roles, it can only use names, which produces less useful output.

2. Ask Claude to flag unclear items — Add “If anything in the transcript is ambiguous — especially around decisions or action item ownership — flag it with [UNCLEAR] rather than guessing.” This prevents confident-sounding errors in your final notes.

3. Use a recurring template for recurring meetings — If you have a weekly team standup, design your summary format once and save the prompt. Every week, just paste the new transcript. Your team will start to expect a consistent format, which makes the notes far more useful.

4. Split very long transcripts — For meetings over 90 minutes, the transcript may be too long to process well in one pass. Split it by agenda section and summarize each section separately, then ask Claude to synthesize a master summary from the section summaries.

5. Turn summaries into project memory — Don’t let meeting notes exist only in email threads. Ask Claude to extract the key decisions and add them to your project’s running decision log. Over time, this creates a searchable record of why your project is the way it is.

Try It Yourself

Find a meeting you had in the last week — either grab the auto-transcript if you have one, or spend 3 minutes writing rough notes from memory about what was discussed, decided, and assigned.

Paste the prompt template above into Claude with your meeting context, check the boxes for “Full meeting notes” and “Action items list,” then paste in your raw material.

Review the output and ask Claude to make one improvement — either fixing an inaccuracy, adjusting the tone, or adding a section you want. By the end, you’ll have clean meeting documentation from materials that might otherwise have been lost.