Meeting Summary
Meeting Notes Into Actions
Convert messy notes into decisions, owners, and a follow-up email people will read.
The Prompt
meeting-notes-into-actions.md
Turn these meeting notes into something the team can execute. Meeting: {{title}} Attendees: {{attendees}} Notes / transcript: {{notes}} Our usual action format: {{format}} Deliver: 1. 5-line summary 2. Decisions (what was agreed - not "discussed") 3. Open questions still unresolved 4. Action table: action | owner | due | first step 5. A follow-up email (120 words) ready to send If an action has no owner in the notes, list it under "needs owner" instead of inventing one.
Negative prompt
Included when you copy the prompt
Do not invent owners, due dates, or decisions that are not in the notes. Do not list "discussed X" as a decision. Do not assign an owner when the notes do not name one - use "needs owner". Do not write a long recap email; keep the follow-up near 120 words. Do not drop open questions or merge them into fake agreements. Do not reformat actions in a system other than {{format}} when one is provided.
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 4 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
meeting-notes-into-actions.md
Prompt preview
Turn these meeting notes into something the team can execute. Meeting: {{title}} Attendees: {{attendees}} Notes / transcript: {{notes}} Our usual action format: {{format}} Deliver: 1. 5-line summary 2. Decisions (what was agreed - not "discussed") 3. Open questions still unresolved 4. Action table: action | owner | due | first step 5. A follow-up email (120 words) ready to send If an action has no owner in the notes, list it under "needs owner" instead of inventing one.
Examples
Example input
Meeting: Pricing v2 go/no-go Attendees: Maya (PM), Jordan (Eng), Sam (Sales), Priya (Finance) Notes / transcript: - Maya: Usage data shows 22% of teams hit the free project cap monthly; sales wants a "Team Plus" at $29/seat. - Sam: Two enterprise deals blocked on SSO - need SSO on Pro or a clear upsell path by Sept 30. - Jordan: SSO is ~3 sprints if we buy WorkOS; build-from-scratch slips roadmap. - Priya: Comfortable with WorkOS cost if we raise Pro to $18/seat from $14; needs board one-pager. - Agreed: Ship Team Plus beta to 10 friendly accounts in August; hold public launch. - Agreed: Buy WorkOS pending Priya's cost note by Friday. - Parking lot: annual discount % - revisit next finance review. - Maya to draft beta invite email; Sam to nominate 10 accounts by Wed. Our usual action format: Linear issue + owner + due date
What you should get
1. Summary Team reviewed free-cap pressure and enterprise SSO blockers. Chose a limited Team Plus beta in August (not public launch). Approved buying WorkOS for SSO if Finance clears cost by Friday, alongside a possible Pro price move to $18/seat. Annual discount left open. Owners set for beta invites and account list. 2. Decisions - Run Team Plus beta with 10 friendly accounts in August; no public launch yet. - Proceed with WorkOS purchase contingent on Priya's cost note by Friday. - Defer annual discount % to the next finance review. 3. Open questions - Exact Team Plus feature boundary vs Pro for beta. - Whether Pro price change to $18/seat is approved (needs board one-pager). - SSO on Pro vs only on a higher tier for upsell path. 4. Action table (Linear) | Action | Owner | Due | First step | | Draft Team Plus beta invite email | Maya | Wed | Outline offer + success criteria in Linear | | Nominate 10 beta accounts | Sam | Wed | List accounts in Linear with reasons | | WorkOS cost note + Pro $18 one-pager | Priya | Friday | Pull WorkOS quote vs seat uplift | | Needs owner: Confirm SSO packaging (Pro vs upsell) | - | before beta | Add Linear issue after Maya/Sam sync | 5. Follow-up email Subject: Pricing v2 - decisions & owners Hi all - quick recap from Pricing v2 go/no-go. We will run a Team Plus beta with 10 friendly accounts in August (no public launch). WorkOS is a go for SSO if Priya's cost note clears by Friday; Pro may move to $18/seat pending that board one-pager. Annual discount stays parked for the next finance review. Owners: Maya - beta invite draft (Wed). Sam - 10 accounts (Wed). Priya - WorkOS/Pro pricing note (Friday). SSO packaging still needs an owner - reply if you will take it. Linear issues to follow. Thanks - Maya
When to use this prompt
Use it when
- You need help with managers.
- You need help with pms.
- You need help with ops.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
1. Summary Team reviewed free-cap pressure and enterprise SSO blockers. Chose a limited Team Plus beta in August (not public launch). Approved buying WorkOS for SSO if Finance clears cost by Friday, alongside a possible Pro price move to $18/seat. Annual discount left open. Owners set for beta invites and account list. 2. Decisions - Run Team Plus beta with 10 friendly accounts in August; no public launch yet. - Proceed with WorkOS purchase contingent on Priya's cost note by Friday. - Defer annual discount % to the next finance review. 3. Open questions - Exact Team Plus feature boundary vs Pro for beta. - Whether Pro price change to $18/seat is approved (needs board one-pager). - SSO on Pro vs only on a higher tier for upsell path. 4. Action table (Linear) | Action | Owner | Due | First step | | Draft Team Plus beta invite email | Maya | Wed | Outline offer + success criteria in Linear | | Nominate 10 beta accounts | Sam | Wed | List accounts in Linear with reasons | | WorkOS cost note + Pro $18 one-pager | Priya | Friday | Pull WorkOS quote vs seat uplift | | Needs owner: Confirm SSO packaging (Pro vs upsell) | - | before beta | Add Linear issue after Maya/Sam sync | 5. Follow-up email Subject: Pricing v2 - decisions & owners Hi all - quick recap from Pricing v2 go/no-go. We will run a Team Plus beta with 10 friendly accounts in August (no public launch). WorkOS is a go for SSO if Priya's cost note clears by Friday; Pro may move to $18/seat pending that board one-pager. Annual discount stays parked for the next finance review. Owners: Maya - beta invite draft (Wed). Sam - 10 accounts (Wed). Priya - WorkOS/Pro pricing note (Friday). SSO packaging still needs an owner - reply if you will take it. Linear issues to follow. Thanks - Maya
Common mistakes
- Leaving title, attendees, notes vague - the model then invents placeholders.
- Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules.
- Stopping when the first draft appears instead of checking it against the success criteria below.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: title, attendees, notes, format. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with ChatGPT, Claude, Gemini. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- 1. Summary Team reviewed free-cap pressure and enterprise SSO blockers. Chose a limited Team Plus beta in August (not public launch). Approved buying WorkOS for SSO if Finance clears cost by Friday, alongside a possible Pro price move to $18/seat. Annual discount left open. Owners set for beta invites and account list. 2. Decisions - Run Team Plus beta with 10 friendly accounts in August; no public launch yet. - Proceed with WorkOS purchase contingent on Priya's cost note by Friday. - Defer …
- What are common mistakes with this prompt?
- Leaving title, attendees, notes vague - the model then invents placeholders. Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules. Stopping when the first draft appears instead of checking it against the success criteria below.
Best for
- Managers
- PMs
- Ops
Related Prompts
More prompts like this — same topic and style.