Meeting Notes with Action Items (Clarity & Accountability)

This prompt transforms meeting discussions into clear, actionable notes. It captures key decisions with context, extracts action items with clear owners and deadlines, documents open questions, and provides enough context for people who weren't there to understand outcomes.

GPT / Claude / Gemini5 variables
Prompt
Create meeting notes with action items for {MEETING}.

Input:
- Meeting: {MEETING_TITLE}
- Date: {DATE}
- Attendees: {ATTENDEES}
- Discussion points: {NOTES}

Rules:
- Synthesize, don't transcribe everything
- Make decisions explicit with context
- Action items must have owner and deadline
- Note open questions and blockers
- Keep it scannable for quick reference

Output format:

MEETING: {MEETING_TITLE}
Date: {DATE}
Attendees: [Present: names | Absent: names]
Purpose: [Why we met]

DISCUSSION SUMMARY

Topic 1: [Name]
- [Key point discussed]
- [Important consideration raised]
- [Outcome or direction]

Topic 2: [Name]
- [Continue format...]

DECISIONS MADE
1. [Decision]
   Context: [Why we decided this]
   Impact: [What this means]

2. [Next decision...]

ACTION ITEMS

High Priority:
□ [Specific task] - Owner: [Name] - Due: [Date]
□ [Specific task] - Owner: [Name] - Due: [Date]

Medium Priority:
□ [Specific task] - Owner: [Name] - Due: [Date]

OPEN QUESTIONS / BLOCKERS
- [Question that needs resolution]
  Who can answer: [Name or team]
- [Blocker preventing progress]
  How to unblock: [Next step]

NEXT STEPS
- [Immediate follow-up needed]
- Next meeting: [Date, purpose]

PARKING LOT (for future discussion)
- [Topic we didn't have time for]

Meeting: {MEETING_TITLE}
Date: {DATE}
Attendees: {ATTENDEES}
Quick brief
Purpose

Document meetings so everyone knows what was decided and what happens next.

Expected output

Meeting notes containing: meeting metadata (date, attendees, purpose), concise discussion summary by topic, clear decisions made with context, specific action items with owner and deadline, parking lot items or open questions, and next meeting scheduled if applicable.

Customize before copying

Replace these placeholders with your own context before you run the prompt.

{MEETING}{MEETING_TITLE}{DATE}{ATTENDEES}{NOTES}
Works well with
GPT
Claude
Gemini
Variations
Add decision rationale section for strategic choices.
Include risks or concerns discussed.
Make it client-facing (external meeting recap).
Add link to supporting documents or recordings.
What this prompt helps you do
This prompt transforms meeting discussions into clear, actionable notes. It captures key decisions with context, extracts action items with clear owners and deadlines, documents open questions, and provides enough context for people who weren't there to understand outcomes.
When to use it
Use for project meetings, client calls, strategy sessions, sprint planning, board meetings, or any meeting where decisions and actions matter. Essential when multiple stakeholders need alignment on outcomes.
How it works
The prompt organizes notes into: meeting context and attendees, discussion summary organized by topic, explicit decisions made with rationale, action items with owner and due date, open questions or blockers, and next steps or follow-up meetings scheduled.
Best practices
Take notes in real-time or immediately after. Focus on decisions and actions, not everything said. Make action items specific and achievable. Assign one owner per item. Set realistic deadlines. Send notes within 24 hours. Follow up on action items before next meeting.
Common mistakes
Transcribing everything instead of synthesizing. Vague action items like 'think about X.' No clear owners (everyone owns = no one owns). Unrealistic deadlines. Burying decisions in paragraphs. Not following up on action items. Assuming everyone remembers context.
What you should expect back
Meeting notes containing: meeting metadata (date, attendees, purpose), concise discussion summary by topic, clear decisions made with context, specific action items with owner and deadline, parking lot items or open questions, and next meeting scheduled if applicable.
Limitations
Can't capture everything said or every nuance. Quality depends on note-taker's understanding. Requires discipline to send promptly. May miss undercurrents or politics. Can't force accountability, only document it.
Model notes
Compatible with all major models. GPT creates clear structures. Claude synthesizes discussions well. Gemini sometimes identifies implicit action items. Works for any meeting type.
Real-world applications
Project managers use this for standup and planning meetings. Account managers use it for client calls. Executives use it for leadership team meetings. Teams use it for retrospectives. Anyone uses it to create accountability.
How to tell if it worked
Successful notes mean action items get completed, attendees agree on what was decided, people who missed meeting understand outcomes, and follow-up meetings build on documented progress. If confusion persists or actions stall, notes weren't clear.
Where to go next
Use Meeting Agenda to prepare beforehand. Pair with Project Status Update for ongoing tracking. Follow with Stakeholder Communication for broader sharing.