ChatGPT Prompts for Meeting Notes: Summaries, Action Items, Recaps

Published: July 2026 | 7 min read

Meeting notes are the memory of an organization. Good notes capture decisions, track action items, and keep absent stakeholders informed. But most people are terrible at taking notes — they write down too much of the wrong thing and miss the decisions that matter. These prompts help you use AI to transform meeting transcripts, raw notes, or recordings into structured, useful documentation.

Meeting Summaries

1. Meeting Notes from Transcript

Role: Professional meeting note-taker
Task: Convert this meeting transcript into structured meeting notes.
Transcript: [Paste transcript or raw notes]
Meeting context: [Type of meeting — standup, planning, review, brainstorm, client call]
Output format:
1. Meeting Title
2. Date/Time: [from transcript or placeholder]
3. Attendees: [extract names]
4. Meeting Purpose (1-2 sentences)
5. Key Decisions Made (bullet list — what was decided, not what was discussed)
6. Discussion Summary (organized by topic, 2-3 sentences per topic, not chronological)
7. Action Items (table: action, owner, due date, status)
8. Parking Lot (items raised but not resolved — for future meetings)
9. Next Meeting: [date/time if mentioned]
Rules:
- Capture decisions, not opinions
- Attribute statements to named people
- Do not include filler ("uh", "um", "I think maybe we should possibly...")
- If something is ambiguous, note it as "[unclear]" rather than guessing
- Keep total length under 500 words
Format: Ready to email to attendees.

2. Executive Meeting Summary

Role: Executive assistant writing for leadership
Task: Create an executive summary from this meeting.
Meeting: [Type, attendees, duration]
Notes/transcript: [Paste raw notes or transcript]
Format:
1. TL;DR (2-3 sentences: what happened, what was decided, what needs attention)
2. Decisions (bullet list: each decision with brief rationale)
3. Action Items (table: action, owner, deadline, priority)
4. Risks/Issues Raised (what could go wrong, who is watching it)
5. Financial Impact (any budget/cost/revenue implications discussed)
6. Stakeholder Impact (who is affected by these decisions?)
7. Open Questions (what still needs to be answered)
8. Next Steps (what happens before the next meeting)
Tone: Concise, no jargon, actionable.
Constraint: Under 300 words. An executive should be able to read this in 60 seconds and know what happened.

3. Standup Summary Generator

Role: Agile team member summarizing standup
Task: Summarize this daily standup.
Notes: [Paste each person update: name, what they did, what they are doing, blockers]
Format:
1. Date
2. Attendees: [names]
3. Completed Yesterday: [bullet list by person]
4. Working On Today: [bullet list by person]
5. Blockers (CRITICAL — this is what the team needs to see):
   - [Blocker] — [Who is blocked] — [Who can help] — [Urgency]
6. Decisions/Announcements: [anything that was not a status update]
7. After Standup Action Items: [what needs a follow-up conversation, who, when]
Format: Slack/email-ready summary, under 200 words.
Rules:
- Blockers go first in the action items (people skip to the bottom)
- If no blockers, say "No blockers" (do not just omit the section)
- Keep individual updates to one line each

Action Item Management

4. Action Item Extractor

Role: Meeting action item specialist
Task: Extract all action items from this meeting.
Meeting notes: [Paste notes or transcript]
For each action item:
1. Action (specific task — not vague "look into" or "follow up")
2. Owner (who is responsible — one person, not a team)
3. Due date (if mentioned; if not, flag as "needs deadline")
4. Priority (Critical/High/Medium/Low — based on context)
5. Dependencies (what must happen first, or who needs to provide input)
6. Success criteria (what does done look like? how do we verify?)
7. Related decision (which meeting decision triggered this action?)
Also identify:
- Items that sound like actions but are actually decisions (move to decisions)
- Items assigned to a group ("the team will..." — who specifically?)
- Items with no owner (flag for assignment)
- Items with no deadline (flag for deadline setting)
Format: Action item table ready for the PM system (Jira, Asana, etc.).

5. Action Item Follow-Up Generator

Role: Project coordinator following up on action items
Task: Write follow-up messages for outstanding action items.
Action items (from last meeting): [List with owner, action, due date, status]
For each incomplete item:
1. Owner name
2. Action description
3. Original due date
4. Current status (overdue? on track? no update?)
5. Follow-up message (tailored to urgency):
   - On track: gentle reminder
   - Overdue (1-3 days): firm reminder with impact statement
   - Overdue (4+ days): escalation with request for update by end of day
6. Channel (Slack DM / email / comment in ticket — based on urgency)
Output:
1. Individual follow-up messages (ready to copy-paste)
2. Summary for next meeting (which items are done, in progress, overdue)
3. Escalation list (items that need leadership attention)
Format: Ready-to-send messages + meeting prep summary.

Specialized Meeting Types

6. Retrospective Notes

Role: Agile coach documenting a retrospective
Task: Create structured retrospective notes.
Retrospective data:
- Sprint: [number/dates]
- Format: [Start/Stop/Continue or 4Ls or Sailboat]
- Raw input: [Paste sticky notes, voting results, discussion points]
Output:
1. Sprint Summary (1 paragraph: what happened this sprint)
2. What Went Well (bullet list with any metrics mentioned)
3. What Did Not Go Well (bullet list, no blame, focus on process)
4. Action Items (table: action, owner, next sprint target, status)
5. Team Sentiment (overall mood, energy level, concerns)
6. Themes (2-3 recurring patterns from the discussion)
7. Carryover from previous retro (what was supposed to be done, was it?)
Format: Retrospective document for the team and PMO archive.
Rules:
- No finger-pointing — focus on process, not people
- Every action item must have an owner
- Keep under 400 words

7. Client Meeting Recap

Role: Account manager writing a client meeting recap
Task: Write a client meeting recap email.
Meeting: [Client name, attendees (internal + client), date, type]
Notes: [Paste raw notes — what was discussed, what client asked for, what we said]
Email format:
Subject: Recap: [Meeting topic] — [Date]
1. Hi [client name],
2. Thank you for your time today. Here is a summary of what we discussed:
3. Key Discussion Points (bullet list, 3-5 items)
4. Decisions Made (what we agreed on)
5. Action Items (table: who does what by when — include both sides)
6. Next Steps (what happens next, next meeting date if scheduled)
7. Open Items (anything we need to follow up on or get back to them about)
8. Closing (professional, offer to correct/add anything)
Tone: Professional, warm, clear. The client should be able to forward this email to their boss and look good.
Constraint: Under 400 words. If there were any contentious moments, frame them positively.

8. Brainstorming Session Notes

Role: Innovation facilitator documenting a brainstorm
Task: Organize and synthesize brainstorming session output.
Session: [Topic, duration, number of participants]
Raw ideas: [Paste all ideas generated — sticky notes, chat messages, whiteboard photos]
Output:
1. Session Summary (topic, participants, duration, method used)
2. Idea Inventory (all ideas, grouped by theme):
   For each theme:
   - Theme name
   - Ideas within this theme (bullet list)
   - Idea originator (if known)
3. Top Ideas (ranked by group vote or facilitator assessment):
   For each top idea:
   - Idea description
   - Why it is promising
   - Potential challenges
   - Next step (research, prototype, assign owner)
4. Patterns and Insights (recurring themes, unexpected connections)
5. Parking Lot (interesting ideas that do not fit the current scope — save for later)
6. Action Items (what happens next with the top ideas)
Format: Brainstorm summary ready to share with participants and stakeholders.

Follow-Up & Communication

9. Post-Meeting Email Generator

Role: Professional communication assistant
Task: Write a post-meeting follow-up email.
Meeting: [Type, attendees, purpose, date]
Key points: [What was discussed, decided, left open]
Email sections:
1. Subject line (descriptive: "Follow-up: [Topic] — [Key outcome]")
2. Greeting (professional)
3. Thank you (for time, input, decision)
4. Meeting summary (3-5 bullet points, what was discussed and decided)
5. Action items (table: action, owner, due date)
6. Open questions (what still needs answers)
7. Next steps (what happens next, next meeting)
8. Attachments/links (docs, slides, recordings)
9. Closing (professional, response requested by [date])
Tone: Professional, concise, action-oriented.
Constraint: Under 250 words. Scannable (bold headers, short paragraphs).

10. Meeting Agenda Generator

Role: Meeting facilitator
Task: Create a meeting agenda for [meeting type].
Meeting: [Type — 1:1, team sync, project kickoff, decision meeting, review]
Duration: [minutes]
Attendees: [roles/number of people]
Objective: [What needs to happen by the end of this meeting?]
Agenda format:
1. Meeting title
2. Date/time/duration
3. Attendees (roles)
4. Meeting objective (1 sentence: what success looks like)
5. Pre-read materials (what to review before the meeting, with links)
6. Agenda items (time-boxed):
   For each item:
   - Time (start-end)
   - Topic
   - Presenter/owner
   - Type (Discussion/Decision/Update/Brainstorm)
   - Desired outcome (what should be achieved)
   - Materials needed (slides, doc, dashboard)
7. Action items review (from last meeting, 5 min)
8. Buffer (5 min for overflow)
Rules:
- Every item has a time box
- Every item has a desired outcome
- If it is a decision item, state what decision is needed
- If pre-reads are needed, send them 24 hours in advance
Format: Ready-to-send agenda email.

11. Decision Log Entry

Role: Project documentation specialist
Task: Create a decision log entry for [meeting decision].
Decision: [What was decided]
Meeting: [Date, attendees]
Entry format:
1. Decision ID (D-001 format)
2. Date
3. Decision Title (short, descriptive)
4. Context (why this decision was needed — 2-3 sentences)
5. Decision (what was decided — specific, not vague)
6. Alternatives Considered (what else was on the table, why not chosen)
7. Rationale (why this option — what tipped the balance)
8. Decision Maker (who made the final call)
9. Consulted (who provided input)
10. Informed (who needs to know)
11. Implications (what changes because of this decision)
12. Follow-up Actions (what needs to happen to implement this decision)
13. Review Date (when should we revisit this decision?)
Format: Decision log entry ready for the project documentation.

12. Meeting Effectiveness Review

Role: Meeting productivity consultant
Task: Analyze the effectiveness of [recurring meeting].
Meeting: [Type, frequency, duration, attendees, purpose]
Data available: [Notes from last 5 meetings, action item completion rate, attendee feedback]
Analysis:
1. Purpose check: Is the meeting purpose still valid? Could this be async?
2. Time utilization: How much time is spent on:
   - Updates (could be written/async?)
   - Decisions (requires real-time discussion?)
   - Brainstorming (benefits from group dynamics?)
   - Blocked items (waiting on someone not in the room?)
3. Action item completion rate: [X% completed by next meeting?]
4. Attendee analysis:
   - Are the right people in the room? (anyone who is just listening?)
   - Is anyone missing who should be there? (action items stalled because they are absent?)
   - Are there too many people? (more than 7 = decision-making slows)
5. Recommendations:
   - Keep, modify, or kill (with rationale)
   - If keep: what to change (shorter? less frequent? fewer people? better agenda?)
   - If modify: specific changes
   - If kill: what replaces it? (async update? smaller meeting? no replacement needed?)
Format: Meeting audit report for the meeting owner.

Best Practices

For more productivity content, see our AI prompts for email drafting and ChatGPT prompts for report writing.