Writing & Content
Meeting Notes to Action System
Transform messy meeting notes into structured documentation with clear ownership, dependencies, and follow-up triggers.
When to use this prompt
After any meeting to create accountable documentation that actually drives follow-through.
The Prompt
You are an expert at extracting signal from noise in meetings. Transform these notes into documentation that drives action and accountability.
MEETING CONTEXT:
- Meeting type: {{type}}
- Attendees: {{attendees}}
- Meeting purpose: {{purpose}}
- Pre-meeting context: {{context}}
RAW NOTES:
{{notes}}
OUTPUT FORMAT:
## Meeting Summary
**Date:** [extract or note if not provided]
**Attendees:** [list with roles if mentioned]
**Meeting Type:** {{type}}
**Duration:** [if mentioned]
### TL;DR (2-3 sentences)
[The single most important outcome + key tension resolved + critical next step]
---
## Decisions Made
[List decisions in this format:]
| Decision | Rationale | Made By | Reversible? |
|----------|-----------|---------|-------------|
| [Specific decision] | [Why this choice] | [Who decided] | [Yes/No + conditions] |
**Decisions NOT made (tabled):**
- [Topic] → Reason deferred → When revisiting
---
## Action Items
[Extract EVERY commitment made. Be aggressive—implicit commitments count.]
| # | Action | Owner | Deadline | Dependencies | Status |
|---|--------|-------|----------|--------------|--------|
| 1 | [Specific, measurable action] | [Name] | [Date or "TBD—needs date"] | [What must happen first] | Pending |
**IMPORTANT:** If deadline wasn't specified, flag it: "⚠️ No deadline set—follow up to confirm"
---
## Discussion Summary by Topic
### [Topic 1]
**Context:** [What prompted this discussion]
**Key points raised:**
- [Person]: [Their main point/concern]
- [Person]: [Their main point/concern]
**Conclusion:** [How it was resolved or where it landed]
### [Topic 2]
[Same structure...]
---
## Open Questions
[Things raised but not resolved]
| Question | Raised By | Assigned To | Target Date |
|----------|-----------|-------------|-------------|
| [Specific question] | [Name] | [Name or "Unassigned"] | [Date] |
---
## Risks & Concerns Flagged
[Explicit or implicit risks mentioned]
| Risk | Raised By | Mitigation Discussed | Owner |
|------|-----------|---------------------|-------|
| [Risk] | [Name] | [What was suggested] | [Name or TBD] |
---
## Parking Lot
[Topics raised but intentionally deferred]
- [Topic] — To be discussed: [when/where]
---
## Follow-up Required
**Before next meeting:**
- [ ] [Action] — Owner: [Name]
**Communication needed:**
- [ ] Share this summary with: [stakeholders not present]
- [ ] Update [system/doc] with: [decisions made]
**Next meeting:** [Date/time if scheduled, or "TBD—[person] to schedule"]
---
## Raw Notes Archive
[Include cleaned-up version of original notes for reference]Try it in:
Variables to customize
| Variable | Description | Example |
|---|---|---|
{{type}} | Type of meeting | Sprint planning / Stakeholder review / 1:1 / Brainstorm |
{{attendees}} | Who was present | Product (Sarah), Engineering (Mike, Jane), Design (Tom) |
{{purpose}} | Why this meeting happened | Align on Q2 roadmap priorities and resource allocation |
{{context}} | Background needed to understand the meeting | Follow-up from last week where we identified 3 competing priorities |
{{notes}} | Raw notes or transcript | [Paste meeting notes, transcript, or recording summary] |
Expected output
Comprehensive meeting documentation with decisions, action items with owners/deadlines, risks flagged, and clear next steps.
Variations
Executive brief
Summarize this meeting for executive leadership: {{notes}}. Format: 3-sentence BLUF, key decisions (with who made them), risks requiring attention, resource asks. Under 200 words. Tone: Factual, no spin, flag what needs their attention.Async standup summary
Extract standup updates from these notes: {{notes}}. Format per person: Completed yesterday → Working on today → Blockers (with who can unblock). Flag any blockers that need escalation.