Turn Meeting Notes into a Recap Email with an Action Item Table

Get a ready-to-send recap email with key decisions, an owner/task/due date table, open questions, and any action missing an owner or date clearly flagged.

You getSubject line, greeting line and summary

Prompt

Prompt
You are an experienced executive assistant who writes meeting recaps people actually read.

I will paste my raw meeting notes right after this message. Turn them into a recap email I can send to everyone who attended.

Rules:
1. Keep the summary to 3-5 bullets. Each bullet states a decision or outcome, not a topic that was discussed.
2. Put every action item in a table with Owner, Task and Due date. Each task starts with a verb and describes one deliverable.
3. If an action has no clear owner, write "MISSING - needs owner" in the Owner column. If it has no date, write "MISSING - needs date". Never guess names or dates.
4. List unresolved questions separately and do not present them as decisions.
5. Keep the email under 250 words, not counting the table, in a neutral, friendly tone.

Output format:
- Subject line (include the meeting name and date if the notes give them)
- Greeting line
- Summary: 3-5 bullets
- Action items: table with columns Owner | Task | Due date
- Open questions: numbered list (write "None" if empty)
- Closing line asking attendees to reply with corrections by a specific day

After the email, add one line listing anything in the notes that was unclear or that I should confirm before sending.

Example output

At a glanceWebsite relaunch recap at a glanceAction items from the 14 May planning meeting
Action items assigned
6
Owner, task and due date table
Items missing an owner
2
Redirects and cookie banner
New launch date
17 June
Moved from 3 June for extra QA
Stock photo budget cap
$1,200

Example for: a marketing lead's rough notes from a 45-minute website relaunch planning meeting with five attendees.

Subject: Recap: Website Relaunch Planning - Tuesday, 14 May

Hi all,

Thanks for the time today. Here is a summary of what we agreed and who is doing what.

Summary
  • Launch date moves from 3 June to 17 June to allow two extra weeks of QA.
  • The new pricing page goes live with the site; the comparison chart is cut from version one.
  • Blog migration covers posts from 2022 onward only; older posts will redirect to the archive.
  • Budget for stock photography is capped at $1,200.
Action items
OwnerTaskDue date
Priya NairSend revised launch timeline to leadershipThu 16 May
Marcus BellFinish QA checklist for all 14 page templatesFri 24 May
Dana OrtizDraft final copy for the pricing pageMon 20 May
MISSING - needs ownerSet up 301 redirects for pre-2022 blog postsFri 31 May
Leo TranShortlist stock photos within the $1,200 budgetMISSING - needs date
MISSING - needs ownerConfirm cookie banner meets new consent rulesMISSING - needs date
Open questions
  1. Do we announce the new launch date to customers, or only internally?
  2. Who signs off on final pricing page copy: Sales or Product?

Please reply with any corrections or missing owners by end of day Thursday, 16 May, and I will send an updated version.

Thanks,
Priya


To confirm before sending: The notes say "Leo or Sam on photos" - check it is Leo, and confirm whether the $1,200 cap includes licensing for social use.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Forcing "MISSING - needs owner" instead of guessing exposes dropped tasks before the email goes out.
  • Separating decisions from open questions stops attendees from treating unresolved points as agreed.
  • The final confirm line catches ambiguous names or numbers in rough notes before you hit send.

Use right after a meeting while details are fresh. Paste your raw notes or a transcript summary into ChatGPT, Claude or Gemini after the prompt. Messy shorthand is fine.

Common edits

  • Ask for a shorter Slack or Teams version with just the action table and two summary bullets.
  • Add a Status column (Not started, In progress, Done) to reuse the table in weekly follow-ups.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Email