AI Prompts for Claude for Meeting Summaries

I have a recurring meeting of type [DESCRIBE — WEEKLY TEAM STANDUP / CLIENT REVIEW / EXECUTIVE STRATEGY SESSION / SALES CALL / PROJECT KICKOFF]. Build me a note-taking template specifically for this meeting type. The template should have sections that make it easy to capture: context, decisions made, action items with owners, open questions, and key discussion points — in a structure that maps to how this type of meeting typically flows.

Here is the agenda for my upcoming meeting: [PASTE AGENDA]. Create a note-taking structure aligned with this agenda. For each agenda item, include a sub-section with fields for: main discussion point, decision or outcome, action items, and parking lot items. Format it so I can fill it in quickly during the meeting.

I run [NUMBER] meetings per week across [DESCRIBE MEETING TYPES]. I want a consistent system for how I label and tag notes so I can find them later. Suggest a simple taxonomy: meeting types, priority tags, and status labels (e.g., decisions-pending, follow-up-required). Keep it to fewer than ten total categories so it actually gets used.

I have a meeting with [DESCRIBE PARTICIPANTS] about [TOPIC]. Here are the background materials: [PASTE RELEVANT DOCS, EMAILS, OR NOTES]. Write a one-page pre-meeting brief that: summarizes what has happened so far, identifies the key open questions the meeting should answer, lists the decisions I need to make or get, and flags any tensions or conflicts I should be prepared for.

I take notes in [TOOL — NOTION / GOOGLE DOCS / OBSIDIAN / PAPER]. After the meeting I need to: [DESCRIBE YOUR PROCESS — SEND A SUMMARY EMAIL, UPDATE A PROJECT TRACKER, FILE IN A SHARED FOLDER]. Design a note-taking workflow that minimizes the time between raw notes and a shareable summary. What should I capture live versus reconstruct after?

Here are my rough notes from a [DESCRIBE MEETING TYPE] meeting: [PASTE NOTES]. Turn these into a clean meeting summary with these sections: Meeting context (one sentence), Key discussion points (three to five bullets), Decisions made (explicit and numbered), Action items (owner, task, deadline), and Open questions or parking lot items. Infer reasonable structure where my notes are incomplete.

Here is a transcript from a [DESCRIBE MEETING TYPE] meeting: [PASTE TRANSCRIPT]. Write a meeting summary under 300 words that captures: the purpose of the meeting, the most important decisions or conclusions reached, all action items with owners and deadlines (if mentioned), and any unresolved questions. Do not include all the discussion — just what matters.

Here is a transcript or set of notes from a meeting: [PASTE]. Extract every explicit or implied action item. For each one, identify: the task (what needs to be done), the owner (who committed to it — or who is most likely responsible if not stated), the deadline (if mentioned or inferable), and any dependencies. Format as a numbered list I can paste into a task tracker.

Here are my meeting notes: [PASTE]. Extract every decision that was made — explicit decisions (where someone said "we have decided to...") and implicit ones (where a course of action was agreed to without being formally stated). Format as a decision log: Decision number, what was decided, who made the decision, date, and any conditions or caveats attached to the decision.

Here are my meeting notes: [PASTE]. Help me separate three things: facts that were stated (things that are confirmed or established), opinions or positions that participants expressed (things someone believes but that are debatable), and open questions (things that were raised but not resolved). This will help me write a summary that does not inadvertently present someone's view as a decision.

Here is the summary from our [DESCRIBE MEETING TYPE] meeting: [PASTE SUMMARY]. Write a follow-up email to the team that: thanks people for their time (briefly), lists decisions made (in a scannable format), lists action items with owners and deadlines, and identifies any upcoming milestones. Tone should be direct and businesslike, not padded with filler.

We had a meeting with [CLIENT NAME] to discuss [TOPIC]. Here are my internal notes: [PASTE NOTES]. Write a professional summary email I can send to the client. It should cover: what we discussed, the decisions or agreements reached, the next steps with owners on each side, and the date of the next touchpoint. Tone should be professional and confident — not overly apologetic or hedging.

I need to send a Slack message to [CHANNEL/TEAM] about the outcome of a [DESCRIBE MEETING]. Here are the key points: [PASTE NOTES]. Write a concise Slack message (no more than five short bullet points) that tells the team: what was decided, what is happening next, and any action they need to take. Skip context the channel already has.

I had a [DESCRIBE MEETING TYPE] meeting and need to report up to [EXECUTIVE LEVEL]. Here are the full notes: [PASTE]. Write a three-paragraph executive summary: paragraph one is the context and purpose, paragraph two is the key outcome or decision, paragraph three is what happens next. Assume the reader has thirty seconds and will skim.

Here are the action items from our meeting on [DATE]: [LIST ACTION ITEMS WITH OWNERS]. These are overdue or approaching their deadline. Write a short, non-passive-aggressive follow-up message (Slack or email) that reminds the owners, gives them a clear path to update status, and maintains a collaborative tone without letting people off the hook.

I have action items from multiple meetings over the past [TIMEFRAME]. Here they are: [PASTE LIST]. Organize these into a master tracker with columns: item, owner, deadline, status, source meeting. Flag any items that are overdue, any that are blocked on someone else, and any that appear in multiple meetings (recurring issues). Format as a table.

Here are summaries from the last [NUMBER] team meetings: [PASTE SUMMARIES]. Look for patterns: What topics keep coming up but never get fully resolved? What decisions get revisited repeatedly? What action items keep getting pushed? Identifying these patterns will tell me what systemic issues I should address so I stop re-discussing the same problems.

I want to run a quarterly review of my meeting practices. Create a simple framework with five to seven questions I can use to assess: whether each recurring meeting is still necessary, whether the right people are in the room, whether meetings are producing decisions or just discussion, and whether action items are being completed. Format as a template I can revisit every quarter.

I lead a team of [NUMBER] people and want to establish clear meeting norms. The biggest problems we have right now are: [DESCRIBE — TOO MANY MEETINGS / NO CLEAR DECISIONS / ACTION ITEMS NOT FOLLOWED UP / ETC.]. Write a one-page meeting norms document that covers: which meetings should have agendas in advance, who is responsible for notes, how action items are tracked, and what makes a meeting skip-worthy versus required attendance.

My calendar currently has [DESCRIBE MEETING SCHEDULE — NUMBER OF MEETINGS PER WEEK, TYPES]. I feel like I have too many meetings to do deep work. Help me audit my meetings. Ask me five questions that will help identify which meetings I can eliminate, delegate, shorten, or convert to async. Then help me draft the message I will send to each meeting organizer.