⚡ Productivity

Meeting Notes to Action Plan and Follow-Up Email

Turn messy meeting notes into clear decisions, owners, next steps, risks, and a ready-to-edit follow-up email.

0.0
0Reviews
P
September 1, 2026

Prompt

Act as a thoughtful project manager and executive assistant. Turn the meeting notes below into a concise action plan that the team can use immediately. Preserve what was actually said and clearly mark anything that still needs confirmation.

Inputs:
- Meeting title: [title]
- Date: [date]
- Attendees and roles: [names and roles]
- Raw notes or transcript: [paste notes]
- Known decisions: [optional]
- Desired email tone: [concise / friendly / formal / firm]
- Default deadline window if no date is given: [number of days]

Generate:
1. A three-to-five sentence meeting summary.
2. Decisions that were made.
3. Action items with the task, owner, due date, priority, and a short definition of done. If an owner or date is missing, write TBD and label it as needing confirmation.
4. Open questions and decisions that still need an answer.
5. Risks, blockers, and one practical mitigation for each.
6. A concise follow-up email with a subject line, greeting, summary, action list, confirmation request, and suggested next meeting.

Constraints:
- Do not assign work to a person unless the notes clearly imply that person owns it.
- Do not invent decisions, deadlines, attendees, or commitments.
- Keep the email easy to edit and do not send it automatically.
- Use clear headings and readable bullets rather than a rigid data schema.

Instructions

Replace the words in brackets, paste the meeting notes, and use the prompt with ChatGPT, Claude, or Gemini. Review the email before sending it.

Examples

Example Input

Meeting title: Website launch planning
Date: 2026-09-01
Attendees and roles: Maya (PM), Jordan (Designer), Alex (Engineer)
Raw notes: Launch is planned for October 10. Jordan will finalize homepage designs by September 8. Alex will confirm analytics events next week. Maya will create the launch checklist. Nobody decided who owns customer-support training.
Known decisions: Launch date is October 10.
Desired email tone: concise
Default deadline window if no date is given: 7 days

Example Output

Meeting summary:
The team is planning a website launch for October 10. Jordan owns the homepage designs, Alex will confirm analytics events, and Maya will create the launch checklist. Customer-support training still needs an owner.

Decisions made:
- Website launch date: October 10.

Action items:
- Maya — Create the launch checklist. Due: TBD; confirm the date. Definition of done: checklist is shared with the team.
- Jordan — Finalize homepage designs. Due: September 8. Definition of done: final designs are shared for review.
- Alex — Confirm analytics events. Due: TBD; suggested deadline is September 8. Definition of done: event list is confirmed and documented.

Open question:
- Who owns customer-support training?

Risk and mitigation:
- Risk: Training ownership is unclear. Mitigation: assign an owner during the next project check-in.

Follow-up email:
Subject: Website Launch Planning — Actions and Open Question

Hi team,

Thanks for the planning session. We are targeting an October 10 launch. Jordan will finalize the homepage designs by September 8, Alex will confirm the analytics events, and Maya will create the launch checklist.

Please confirm the due date for the launch checklist and who will own customer-support training.

Thanks.

Reviews (0)

Please login to leave a review.
Loading reviews...