Skip to content
promptbeginnerFree

Meeting notes to action plan

Convert messy notes or a transcript into decisions, an owned action list, open questions and a ready-to-send follow-up email.

You'll need: Notes or a transcript from the meeting

Fill in your details

Values are inserted into every prompt below. Nothing you type leaves your browser.

4 field(s) left — unfilled variables stay as {{placeholders}}.

  1. 1Paste the notes and run

    Raw transcripts work, but remove small talk at the start if the transcript is very long. Include the attendee list so the model can match names to actions.

    Turn these meeting notes into an action plan.
    
    Meeting: {{meeting_name}}
    Date: {{meeting_date}}
    Attendees: {{attendees}}
    
    Notes:
    {{notes}}
    
    Output in this order:
    1. Summary: three sentences maximum on what the meeting achieved.
    2. Decisions made: bullet list. Only include things that were clearly agreed; put tentative items under Open questions.
    3. Action items: table with Action (starts with a verb) | Owner | Due date | Depends on. Use only attendees as owners. If no owner was named, write "Unassigned". If no date was said, write "No date". Convert relative dates ("next Friday") into actual dates using the meeting date.
    4. Open questions: unresolved issues and who is best placed to answer each.
    5. Follow-up email: under 150 words, addressed to attendees, listing decisions and actions with owners. Plain text, no emojis.
    
    Do not invent commitments, owners or deadlines that are not in the notes.
  2. 2Fix gaps before sending

    Assign every 'Unassigned' action and date every 'No date' item yourself before you send the email. Those gaps are why actions get missed.

Example input

Weekly sync, 27 Oct. Notes: 'Tom showing new homepage, everyone likes option B. Ana worried about the CMS migration timeline, maybe 2 weeks slip. Lee needs final copy by next Fri for the email. Pricing page still TBD, ask finance?'

Example output

Decisions made - Homepage design option B is approved. Action items | Action | Owner | Due | Depends on | | Send final homepage copy to Lee | Unassigned | 2026-11-06 | Option B sign-off | | Re-estimate CMS migration and flag slip | Ana | No date | | | Prepare launch email | Lee | No date | Final copy | Open questions - Pricing page content: needs input from finance (not present). Suggest Priya asks.

Troubleshooting

  • Owners are guessed from context: add 'If you are not sure who owns it, write Unassigned' and re-run.
  • Dates are off by a week: state the weekday next to the meeting date, as in the placeholder.
  • The email is too long: ask for 'decisions and actions only, as two short lists'.

Known limitations

  • Transcripts with poor speaker labels make owner attribution unreliable.
  • Check your organisation's policy before pasting confidential meeting content into a third-party tool.

More from ChatGPT / Claude / Gemini