AI prompts for meeting notes help you turn raw transcripts, rough notes, or recorded calls into structured summaries, action items, and follow-up emails. This page is for team leads and professionals who run regular meetings and want consistent, reusable prompts that work across ChatGPT, Claude, Copilot, and Gemini. No prompt engineering background required.
What is in this pack
This pack contains 20 prompts organized into five categories: basic summaries, action items and owners, stakeholder-facing recaps, async updates, and difficult or sensitive meetings. Each prompt is ready to copy and use today, with variables in brackets so you can swap in your own context.
The prompts are designed for the most common meeting types: standups, project check-ins, client calls, and all-hands updates. A few cover edge cases that standard templates miss, like summarizing a meeting where no decisions were actually made, or writing a recap that protects a candid internal discussion from wider distribution.
One honest caveat up front: AI summaries work poorly when the source material is thin. If your notes are three bullet points and a name, no prompt will produce a useful output. Garbage in, garbage out applies here more than almost anywhere else.
For broader prompt collections organized by role, see prompts by role or the AI prompts for business page.
The prompts, by category
These prompts are grouped by the job they do. Pick the category that matches where you are in your meeting workflow.
| Category | Prompts | Best for |
|---|---|---|
| Raw transcript cleanup | 4 | Zoom, Teams, or Fireflies exports |
| Action item extraction | 4 | Any meeting with follow-ups |
| Decision logging | 4 | Project reviews, steering meetings |
| Stakeholder summaries | 4 | Sending up or out to people who weren't there |
| Async and recurring meetings | 4 | Standups, weeklies, board updates |
One candid note before you start: these prompts work well when your transcript or notes are reasonably complete. If the recording dropped out for ten minutes or your notes are a few scattered bullet points, the model will fill gaps with plausible-sounding text that may not reflect what was said. Review every output before you send it.
For prompts organized by the role running the meeting, browse the full prompt library by role. Teams in marketing and business operations will find closely related packs at AI Prompts for Marketers and AI Prompts for Business.
Raw transcript cleanup
Strip filler and format a raw transcript
Variables: [TRANSCRIPT], [MEETING NAME], [DATE]
Clean up the following raw meeting transcript from [MEETING NAME] on [DATE].
Remove filler words, false starts, and crosstalk. Fix obvious transcription errors.
Preserve speaker names and the sequence of the conversation.
Do not add information that is not in the transcript.
Output the result as a readable dialogue with speaker labels.
Transcript:
[TRANSCRIPT]When to use it: Immediately after you export a raw transcript from Zoom, Teams, or a transcription tool like Otter.ai. Change first: The instruction "do not add information" is the most important line. Keep it.
[NEEDS REAL OUTPUT]
Summarize a transcript into five bullets
Variables: [TRANSCRIPT], [MEETING TYPE]
Read the following transcript from a [MEETING TYPE] meeting.
Write exactly five bullet points summarizing what was discussed.
Each bullet should be one sentence. Do not include action items here.
Focus on the substance of the discussion, not the process.
Transcript:
[TRANSCRIPT]When to use it: When you need a fast summary to paste into a Slack message or email thread. Change first: Adjust the number of bullets to match how much ground the meeting covered.
Create a structured meeting record
Variables: [TRANSCRIPT OR NOTES], [MEETING NAME], [ATTENDEES], [DATE]
Using the notes or transcript below, create a structured meeting record for [MEETING NAME] held on [DATE].
Attendees: [ATTENDEES]
Include these sections:
- Purpose of the meeting (one sentence)
- Key topics discussed (brief bullets)
- Decisions made (list each one clearly)
- Open questions (anything unresolved)
- Next steps (owned by a named person where possible)
Source material:
[TRANSCRIPT OR NOTES]When to use it: For any meeting that needs a written record, especially ones where decisions were made. Change first: Add a "Background" section if attendees need context before reading the record.
Identify what was off-topic
Variables: [TRANSCRIPT], [MEETING OBJECTIVE]
The stated objective of this meeting was: [MEETING OBJECTIVE]
Read the transcript below and list any discussion that did not contribute to that objective.
Be specific: name the topic and roughly where in the transcript it appeared.
Do not editorialize. Just list the items.
Transcript:
[TRANSCRIPT]When to use it: When meetings regularly run long and you want evidence to share with the team. Change first: This prompt works best when you had a written agenda. If you didn't, it's less reliable.
Action item extraction
Extract action items with owners and deadlines
Variables: [TRANSCRIPT OR NOTES]
Read the meeting notes or transcript below.
Extract every action item mentioned, whether explicit or implied.
For each one, list:
- The action (what needs to be done)
- The owner (who said they would do it, or who was assigned)
- The deadline (if one was mentioned; otherwise write "not stated")
Format as a table. Do not invent owners or deadlines.
Source material:
[TRANSCRIPT OR NOTES]When to use it: After any meeting that involved task assignments. Change first: If no deadlines were stated, follow up with the prompt below to suggest realistic ones.
[NEEDS REAL OUTPUT]
Suggest deadlines for undated action items
Variables: [ACTION ITEM LIST], [MEETING DATE], [NEXT MEETING DATE]
The following action items were captured from a meeting on [MEETING DATE].
The next meeting is on [NEXT MEETING DATE].
For each item without a stated deadline, suggest a realistic deadline based on the next meeting date and the nature of the task.
Explain your reasoning in one sentence per item.
Action items:
[ACTION ITEM LIST]When to use it: When the action item list has gaps and you need a starting point for follow-up. Change first: Replace the suggested deadline if you know the team's actual capacity.
Flag action items that lack an owner
Variables: [ACTION ITEM LIST]
Review this list of action items from a recent meeting.
Identify every item that does not have a named owner.
List those items and suggest who might own each one based on the context, if the context is available.
If you cannot suggest an owner, say so.
Action items:
[ACTION ITEM LIST]When to use it: Before distributing meeting notes, to catch anything that will fall through the cracks. Change first: Add team roles to the prompt if you want more useful owner suggestions.
Convert action items into a follow-up email
Variables: [ACTION ITEM TABLE], [MEETING NAME], [YOUR NAME]
Using the action item table below, write a short follow-up email to send after [MEETING NAME].
The email should:
- Thank attendees briefly (one sentence)
- List each action item with its owner and deadline
- Ask owners to confirm or flag if anything has changed
- Close with your name: [YOUR NAME]
Keep the tone professional but direct. No more than 200 words total.
Action items:
[ACTION ITEM TABLE]When to use it: Immediately after the meeting, while context is fresh. Change first: Adjust the word limit if your team culture prefers more or less detail.
Decision logging
Extract decisions with rationale
Variables: [TRANSCRIPT OR NOTES]
Read the following meeting transcript or notes.
List every decision that was made, including:
- What was decided
- Why (the stated reason, if any was given)
- Who made or confirmed the decision
- Any conditions or caveats attached
If a decision was discussed but not finalized, note it as "pending" and describe what is still unresolved.
Source material:
[TRANSCRIPT OR NOTES]When to use it: For project reviews, architecture discussions, or any meeting where choices have downstream consequences. Change first: Add "List decisions in chronological order" if sequence matters.
[NEEDS REAL OUTPUT]
Write a decision log entry
Variables: [DECISION], [DATE], [DECISION MAKER], [CONTEXT], [ALTERNATIVES CONSIDERED]
Write a formal decision log entry for the following decision.
Decision: [DECISION]
Date: [DATE]
Decision maker(s): [DECISION MAKER]
Context: [CONTEXT]
Alternatives considered: [ALTERNATIVES CONSIDERED]
Format it as a structured record suitable for a project wiki or shared document.
Be factual and concise. Do not editorialize.When to use it: When your team maintains a decision log in Notion, Confluence, or a similar tool. Change first: Match the field names to whatever your team's template uses.
Summarize decisions for a stakeholder who missed the meeting
Variables: [DECISION LIST], [STAKEHOLDER NAME], [STAKEHOLDER ROLE]
The following decisions were made in a meeting that [STAKEHOLDER NAME] ([STAKEHOLDER ROLE]) did not attend.
Write a plain-language summary of each decision that gives them enough context to understand what was decided and why, without needing to read the full transcript.
Assume they are familiar with the project but were not in the room.
Decisions:
[DECISION LIST]When to use it: When a key person was absent and needs to be brought up to speed quickly. Change first: Swap the context sentence to match the stakeholder's actual familiarity with the project.
Identify decisions that contradict earlier ones
Variables: [NEW DECISION LIST], [PREVIOUS DECISION LOG]
Compare the new decisions below against the previous decision log.
Identify any new decisions that appear to contradict, reverse, or modify an earlier decision.
For each conflict, describe what changed and flag it clearly.
Do not suggest which decision is correct. Just surface the conflicts.
New decisions:
[NEW DECISION LIST]
Previous decision log:
[PREVIOUS DECISION LOG]When to use it: On long-running projects where decisions accumulate and contradict each other over time. Change first: If your decision log is long, paste only the relevant entries rather than the full log.
Stakeholder summaries
Write an upward summary for a senior leader
Variables: [MEETING NOTES], [LEADER NAME], [LEADER'S PRIMARY CONCERN]
Summarize the following meeting notes for [LEADER NAME], who was not in the meeting.
Their primary concern is: [LEADER'S PRIMARY CONCERN]
Lead with what is most relevant to that concern.
Include decisions made, risks raised, and next steps.
Keep the total length under 150 words.
Use plain language. Avoid jargon.
Meeting notes:
[MEETING NOTES]When to use it: When you need to brief a director or executive without forwarding them a full transcript. Change first: The leader's primary concern is the key variable. Get that right and the rest follows.
[NEEDS REAL OUTPUT]
Write a client-facing meeting recap
Variables: [MEETING NOTES], [CLIENT NAME], [YOUR COMPANY NAME]
Write a meeting recap email to send to [CLIENT NAME] following our recent meeting.
Use the notes below as the source.
Include:
- A one-sentence summary of the meeting's purpose
- Key points discussed
- Agreed next steps, with owners and dates where available
- Any items that need a response or decision from the client
Sign off from [YOUR COMPANY NAME]. Keep the tone professional and the length under 250 words.
Do not include anything from the notes that was marked as internal.
Notes:
[MEETING NOTES]When to use it: After any client call or project check-in. Change first: Add a "Do not include" list if your notes contain sensitive internal commentary.
Translate technical decisions into plain language
Variables: [TECHNICAL DECISION SUMMARY], [AUDIENCE DESCRIPTION]
The following decisions were made in a technical meeting.
Rewrite them in plain language for [AUDIENCE DESCRIPTION], who does not have a technical background.
Explain the practical impact of each decision: what changes for them, if anything.
Avoid jargon. If a technical term is essential, define it in parentheses.
Technical decisions:
[TECHNICAL DECISION SUMMARY]When to use it: When an engineering or data team needs to communicate outcomes to a business or product audience. Change first: Describe the audience precisely. "Non-technical" is less useful than "finance team with no software background."
Write a summary for a team member on leave
Variables: [MEETING NOTES], [PERSON'S NAME], [THEIR ROLE], [WEEKS ABSENT]
[PERSON'S NAME] ([THEIR ROLE]) has been on leave for [WEEKS ABSENT] weeks and is returning soon.
Summarize the key outcomes from the meeting notes below that are relevant to their role.
Note any decisions or changes that affect their current workload or priorities.
Keep it to bullet points. Be direct.
Meeting notes:
[MEETING NOTES]When to use it: When someone returns from leave and needs to catch up without reading through weeks of notes. Change first: Add context about what projects the person owns so the model can filter more accurately.
Async and recurring meetings
Convert standup notes into a written async update
Variables: [RAW STANDUP NOTES], [TEAM NAME]
Convert the following standup notes into a written async update for the [TEAM NAME] team.
Format it with three sections: Done, Doing, Blocked.
One or two bullet points per person per section. Cut anything that does not affect the rest of the team.
Keep the total length under 200 words.
Standup notes:
[RAW STANDUP NOTES]When to use it: For distributed teams that hold standups asynchronously or want a written record. Change first: Add a "Decisions" section if your standups regularly produce them.
Summarize a weekly meeting for the team newsletter
Variables: [MEETING NOTES], [NEWSLETTER NAME OR AUDIENCE]
Write a short summary of this week's team meeting suitable for [NEWSLETTER NAME OR AUDIENCE].
The tone should be informative but readable, not formal.
Cover the most important updates, decisions, and upcoming milestones.
Maximum 100 words. No bullet points; write in short prose paragraphs.
Meeting notes:
[MEETING NOTES]When to use it: When you publish a weekly digest or team newsletter and want to include meeting highlights. Change first: Adjust the word count and format to match your newsletter's style.
[NEEDS REAL OUTPUT]
Generate a recurring meeting agenda from last week's notes
Variables: [LAST WEEK'S NOTES], [MEETING NAME], [MEETING DATE]
Using last week's meeting notes as context, generate a draft agenda for [MEETING NAME] on [MEETING DATE].
Include:
- Standing items that recur each week (based on what appeared last week)
- Open action items that are due or overdue
- Topics that were deferred or left unresolved
Format as a numbered agenda with a rough time allocation for each item.
Last week's notes:
[LAST WEEK'S NOTES]When to use it: At the start of each week, before you set the agenda for a recurring meeting. Change first: Add or remove standing items based on your team's actual format.
Write a retrospective summary from meeting notes
Variables: [RETRO NOTES], [SPRINT OR PERIOD NAME]
Summarize the following retrospective meeting notes for [SPRINT OR PERIOD NAME].
Group the output into three sections: What went well, What did not go well, What we will try next.
Use the language from the notes where possible. Do not editorialize or reframe feedback.
Keep each section to a maximum of five bullet points.
Retro notes:
[RETRO NOTES]When to use it: After sprint retrospectives or end-of-quarter reviews. Change first: If your retro format uses different categories, replace the three sections with your team's actual headings.
Real example outputs
The five prompts marked [NEEDS REAL OUTPUT] below need captured outputs from an actual model run before this page publishes. Here is what to collect for each one, and what the "what to notice" line should highlight.
| Prompt | What to capture | What to notice |
|---|---|---|
| Core summary | Full model response for a 45-min product review meeting | Whether it correctly separates decisions from discussion |
| Action item extractor | Output from a meeting with 6+ owners | Whether it assigns one owner per item, not a group |
| Async update | Slack-length output from a cross-functional sync | Whether it drops jargon that only attended parties would understand |
| Executive briefing | Output condensed from a long transcript | Whether it leads with the decision, not the agenda |
| Follow-up email | Drafted email from a project check-in | Whether the tone reads as human-written without editing |
Run each prompt against a real transcript from your own meetings. Paste the unedited first response. The "what to notice" commentary should be honest: if the model misattributes an action item or buries the key decision in paragraph three, say so. That kind of candor is what makes example outputs useful.
How to adapt these for your team
The prompts above work out of the box for most meetings. A few small changes make them significantly more useful for your specific context.
Swap the generic role labels. "Stakeholder" means different things in a product team versus a consulting firm. Replace it with whatever your organization actually calls people: "client," "sponsor," "squad lead."
Lock in your format once. If your team always uses Notion, or always pastes summaries into Slack, add that constraint to the prompt. "Format the output as plain text with no markdown" saves one editing step every time.
Add a terminology line. A single sentence at the top of any prompt ("Our team uses 'pod' instead of 'squad' and 'sprint review' instead of 'retrospective'") stops the model from introducing vocabulary that confuses your colleagues.
Decide what counts as an action item. Some teams only log tasks with a named owner and a due date. Others capture softer commitments too. Tell the model which standard you use, and it will apply it consistently.
If your team runs several meeting types regularly, saving a shared folder of these prompts means everyone pulls from the same baseline instead of writing variations from scratch.
Save this folder to your workspace
If your team runs recurring meetings, the real payoff comes from storing these prompts somewhere everyone can find them, not just the person who first discovered them. One consistent template used by five people produces far cleaner notes than five people each prompting from scratch.
A practical folder structure for meeting notes:
| Folder | What goes in it |
|---|---|
| Weekly standups | Standup summary, blocker extraction, action item prompts |
| Client meetings | Client-facing recap, next-steps email, decision log |
| Planning sessions | OKR capture, risk flagging, owner assignment |
| Retrospectives | Theme extraction, sentiment summary, follow-up tracker |
Start with one folder for the meeting type your team runs most often. Get the prompts dialed in there before expanding. You can browse the full prompts by role library to find formats that fit adjacent workflows, or check the AI prompts for business collection if your meetings skew toward planning and operations.
Frequently asked questions
Do these prompts work in ChatGPT, Claude, and Copilot?
Yes, every prompt in this pack is written to work across all major AI assistants including ChatGPT, Claude, Microsoft Copilot, and Gemini. None rely on plugins or special features. Paste the transcript, fill the brackets, and run it.
What if my meeting had no transcript?
Write a rough summary from memory first, then use the cleanup prompts. The output quality drops without a real transcript, but a few bullet points are enough for the action-item and follow-up prompts to produce something useful.
Will the AI make up action items that were not discussed?
It can, especially with long or messy transcripts. Always review the output against your notes before sending it to anyone.
Are these prompts suitable for external client meetings?
Check your organization's policy on pasting external conversations into AI tools before using any prompt here. When in doubt, anonymize names and company details first.
How do I share these prompts with my whole team?
Convergence shared folders let you store, organize, and push prompts to everyone on your team from one place, with no copy-pasting required.