Meeting notes to decisions and action items

Turn messy meeting notes or a transcript into clear decisions, owners, deadlines, open questions and a follow-up message.

LLazyPrompt(@lazyprompt)Business & StrategyExtractWorks with any model
No ratings yetSign in to rate
Save 0 Fork Report
Prompt template
Process these meeting notes into a clean record.

Meeting: {{meeting}}
Date and attendees: {{attendees}}
Raw notes or transcript:
{{notes}}

Produce:
1. **Summary**: 3 to 4 sentences on what the meeting was about and what was concluded.
2. **Decisions made**: bullet list. Only include something as a decision if the notes show agreement; otherwise move it to open questions.
3. **Action items**: a table with columns Action, Owner, Deadline, and Notes. If the owner or deadline was not stated, write "Unassigned" or "No date given" rather than guessing, and list those items again under "Needs an owner".
4. **Open questions and disagreements**: what remains unresolved, who raised it, and the next step to resolve it.
5. **Risks or blockers** mentioned.
6. **Follow-up message**: a short email or Slack message in a {{tone}} tone, ready to send to attendees, listing decisions and each person's actions.

Do not add information that is not in the notes. Where the notes are ambiguous, quote the unclear phrase and ask me about it at the end instead of resolving it yourself.
Example output
**Summary:** The team reviewed the search bug, the quarter's scope and onboarding design. Dark mode was dropped for this quarter; beta customer selection is still pending. **Decisions** - Dark mode project dropped for this quarter. **Action items** | Action | Owner | Deadline | Notes | |---|---|---|---| | Fix search bug | Tom | Friday (tentative) | "Maybe" in notes | | Share onboarding mockups | Lee | No date given | | | Update pricing FAQ | Unassigned | No date given | Ravi raised the need | **Needs an owner:** pricing FAQ update; date for mockups. **Open questions:** Which customers join the beta (decide next week)? Expected support load after the pricing change (Ravi). **Risks:** support volume spike after pricing change. **Follow-up message:** Hi all, quick recap from today: we agreed to drop dark mode this quarter. Tom is aiming to fix the search bug by Friday, and Lee will share onboarding mockups. We still need an owner for the pricing FAQ, and we will choose beta customers next week. Shout if I missed anything. **Questions for you:** Is Tom's "maybe" a firm Friday commitment?

Why it works

Telling the model not to guess owners or dates makes the gaps visible, which is where most follow-up fails. Paste a transcript and keep the follow-up message short so people read it.

Licensed CC0 (public domain) Version 1 · history