Meeting → Action Plan
Turn scattered notes into decisions, owners, next steps, and a send-ready follow-up.
Meeting notes are scattered (bullets, chat paste, half-sentences) and you need decisions, owners, deadlines, plus a short follow-up email you can send in minutes.
- Raw notes (messy is fine)
- Meeting context (topic + date if known)
- Default timezone / “this week” meaning if deadlines are vague
Jump to prompt ↓ · Find the example ↓
Steps
- Replace the placeholders with relevant, non-sensitive source material.
- Paste the prompt into your approved chat assistant.
- Compare every fact, owner, number and date against the input. Edit before using.
Turn these meeting notes into a clear action plan. Output exactly these sections: 1) Decisions made (bullets; say “None explicit” if unclear) 2) Action items — each with: Owner | Task | Deadline | Status (Open) 3) Open questions 4) Follow-up email — short, send-ready, under 120 words, summarizing decisions + asks Rules: - Do not invent owners, dates, or commitments that aren’t in the notes - If owner/deadline is missing, mark as TBD and list under Open questions - Use names exactly as written in the notes - Prefer verbs that start with action (Send, Draft, Schedule, Confirm) Meeting context: [topic + date] Notes: [paste messy notes] - Do not add new commitments, causes, meetings or deadlines. Preserve uncertainty. - Keep proposals separate from agreed actions; mark missing information as TBD.
Saves stay in this browser. Cross-device syncing is planned.
Limits, compatibility & evidence
- The response is a draft; it can omit or misread details.
- Do not add commitments, infer decisions or treat proposed actions as agreed.
- Use an employer-approved tool and remove confidential or personal information.
ChatGPT · Claude · Gemini · Microsoft Copilot (and similar). Best when you paste the full note dump in one go.
Evidence
Illustrative example reviewed for fidelity on 18 September 2026. No recorded execution in external AI tools; compatibility is a text-format expectation, not a tested-model claim.
ExampleSee a realistic input → output +
Meeting context: Retention standup — 2026-09-05 Notes: - dashboard confusion coming up a lot in onboarding calls - Sarah: will pull top 10 ticket themes by Wed - John: two enterprise accounts at risk — Acme + Northwind — needs CS briefs - decide: pause new feature emails until onboarding FAQ ships - team to draft FAQ outline this week? - follow up with VP next week on renewals noise
1) Decisions made - Pause new feature emails until the onboarding FAQ ships. 2) Action items - Sarah | Pull top 10 ticket themes | Wed (exact date TBD) | Open - TBD | Follow up with VP on renewals noise | Next week (exact date TBD) | Open 3) Open questions - Who will prepare the CS briefs for Acme and Northwind? John reported the need; no owner was assigned. - Is drafting the FAQ outline this week agreed? The notes phrase it as a question. - Who owns the VP follow-up and what is the exact date? - What counts as the FAQ being shipped? 4) Follow-up email Subject: Retention standup follow-up We agreed to pause feature emails until the FAQ ships. Sarah will pull the top 10 ticket themes by Wed. CS briefs are needed for Acme and Northwind; ownership is unconfirmed. Please confirm whether the FAQ outline is agreed for this week and who owns the VP follow-up next week.
Advanced versionAsk for a tracker-ready table + escalation indicator: +
Same rules as the Meeting → Action Plan prompt, plus: 5) A markdown table: Owner | Task | Deadline | Dependency | Escalation? (Yes/No) 6) Escalation = Yes only if notes imply revenue risk, blocked launch, or executive ask Meeting context: [topic + date] Notes: [paste]
Your companion kit / Pro preview
The meeting follow-through kit
Prepare the agenda · Build an action register · Draft the follow-up · Prepare the weekly update.
See what’s inside →Paid membership is being prepared.