Meeting Summary Prompt for Claude

What this prompt does

Meetings generate decisions and obligations — but most notes are a mess of partial sentences and things that seemed obvious in the room but are cryptic two days later. This prompt takes whatever you have (rough notes, a bullet dump, or a full transcript) and produces a structured summary with exactly what people need: what was decided, what happens next, and who owns it.

Works with Claude, ChatGPT, and Gemini. Claude's output tends to be cleaner when working with transcripts; ChatGPT handles rough bullets well.

The prompt

Summarize the following meeting notes into a structured document:

[PASTE YOUR NOTES OR TRANSCRIPT HERE]

---

Meeting context:
- Meeting type: [e.g., "weekly team sync," "client kickoff," "project retrospective"]
- Attendees: [NAME — ROLE, NAME — ROLE]
- Date: [DATE]

Format the output as:

**Meeting Summary — [Meeting Name] — [Date]**

**What was discussed** (3–5 bullet points, outcomes-focused — not a play-by-play)

**Decisions made** (numbered list — only include real decisions, not topics that were discussed without resolution)

**Action items** (table format: | Action | Owner | Due date |)

**Open questions** (anything unresolved that needs follow-up)

Rules:
- Be specific. "Discussed marketing budget" is useless. "Agreed to increase Q3 paid spend by 15%" is useful.
- If a decision or action item is implied but not explicit in the notes, add a note that says "[NEEDS CONFIRMATION]"
- If you can't determine an owner for an action item, write "TBD"
- Total length: under 300 words unless the meeting was complex

How to use it

1. Paste whatever you have — raw notes, bullets, even a Zoom transcript. The prompt handles messy input.
2. Fill in the context fields — attendees and meeting type shape how the AI prioritizes what's important.
3. Review the [NEEDS CONFIRMATION] flags — these catch things that were mentioned but not formally agreed on. Don't delete them without checking.
4. Send immediately after the call — summaries sent within 30 minutes get read. Summaries sent the next day get filed.
5. Add a short personal line at the top when forwarding externally — "Quick summary from today's call — flag anything I missed."

Example output

Meeting Summary — Product Roadmap Sync — May 28, 2026

What was discussed

• Q3 feature priorities: dropped waitlist tool from scope, moved analytics dashboard to August
• Agreed the current onboarding flow is losing users at step 4 (email confirmation)
• Engineering raised concern about API rate limits for the planned integrations
• Discussed whether to hire a second designer before August launch

Decisions made

1. Analytics dashboard ships August 12 — not July 31
2. Email confirmation step to be redesigned by engineering team, not design
3. Designer hire: decision deferred to budget review June 15

Action items

Open questions

• Will the analytics dashboard need a design review before August 12? [NEEDS CONFIRMATION]
• Who is the point of contact for the API rate limit issue on the vendor side?

Variations

For client meetings (external)

Add to the prompt:

"This summary will be shared with the client externally. Make it professional and concise. Avoid internal shorthand. End with a 'Next steps we're handling' and 'What we need from you' section."

For one-on-ones

"Format this as a brief recap rather than a structured document. Two sections: what we talked about (3 bullets max) and what I'm doing next (action items only)."

For board or leadership updates

"Extract only the strategic decisions and top 3 action items. Skip operational detail. The audience is senior — assume they know the context."

Common pitfalls

• Don't: Paste a 60-minute transcript and expect a perfect summary without any formatting guidance — the output will be too long.

• Try instead: Add a word limit or specify "focus on decisions and action items only."

• Don't: Accept the summary and forward it without reviewing the [NEEDS CONFIRMATION] flags first.

• Try instead: Check each flag against your memory of the meeting — these are often the most important points.

Who uses this prompt

• Managers: Post-meeting distribution to teams and stakeholders
• Consultants: Client call documentation and follow-up emails
• Teachers: Staff meeting recaps and parent-teacher conference notes
• Project managers: Sprint reviews, stakeholder syncs, retrospectives
• Freelancers: Client briefing notes and scope-of-work documentation