Convert messy meeting notes into structured action items with owners
#action-items
#productivity
#team-management
Views
11.6K
Copies
4.0K
Likes
1.5K
Comments
0
Copy rate
34.0%
Prompt
You are a chief of staff who turns chaotic meeting transcripts into crystal-clear action items. Take the following raw meeting notes and produce a structured output.
Meeting notes:
"""
[meeting_notes]
"""
Meeting context: [meeting_context]
Output format:
1. Meeting summary (3 sentences max)
2. Decisions made (numbered list)
3. Action items table: Item | Owner | Deadline | Priority | Dependencies
4. Open questions that need follow-up
5. Next meeting agenda suggestions
Rules:
- Infer owners from context clues in the notes
- If no deadline is mentioned, suggest a reasonable one based on priority
- Flag any conflicting statements you notice
- Mark anything ambiguous with [CLARIFY] tag
Customise this prompt
Fill in 2 variables to personalise this prompt
Preview
You are a chief of staff who turns chaotic meeting transcripts into crystal-clear action items. Take the following raw meeting notes and produce a structured output.
Meeting notes:
"""
[meeting_notes]
"""
Meeting context: [meeting_context]
Output format:
1. Meeting summary (3 sentences max)
2. Decisions made (numbered list)
3. Action items table: Item | Owner | Deadline | Priority | Dependencies
4. Open questions that need follow-up
5. Next meeting agenda suggestions
Rules:
- Infer owners from context clues in the notes
- If no deadline is mentioned, suggest a reasonable one based on priority
- Flag any conflicting statements you notice
- Mark anything ambiguous with [CLARIFY] tag
Example output
# Meeting Summary
Weekly product sync covering the Q3 roadmap reprioritization, mobile app performance issues, and the upcoming enterprise client onboarding. The team agreed to delay the analytics dashboard redesign to focus on mobile performance. A hiring decision for the senior iOS role was escalated to the VP.
---
## Decisions Made
1. **Mobile performance is now P0** — analytics dashboard redesign moves from Q3 to Q4
2. **Enterprise onboarding pilot** starts July 15 with Acme Corp as the first customer
3. **API rate limiting** will ship as-is (current thresholds) — no further tuning before enterprise launch
4. **Design system v2** stays on track but loses one designer (Maya) for 3 weeks to support mobile
5. **Hiring:** Senior iOS role approved to move to final round with the top two candidates
---
## Action Items
| # | Item | Owner | Deadline | Priority | Dependencies |
|---|---|---|---|---|---|
| 1 | Profile the top 5 slow screens on iOS and Android | Jake (mobile lead) | July 3 | P0 | — |
| 2 | Set up Acme Corp staging environment | Sarah (infra) | July 10 | P0 | Requires enterprise license key from legal |
| 3 | Write onboarding runbook for enterprise pilot | Priya (PM) | July 12 | P1 | Needs input from Sarah on infra setup |
| 4 | Schedule final-round interviews for iOS candidates | Tomas (hiring mgr) | July 5 | P1 | Recruiter to confirm candidate availability |
| 5 | Move analytics dashboard epics to Q4 in Linear | Priya (PM) | June 30 | P2 | — |
| 6 | Update design system timeline with Maya's reallocation | Chen (design lead) | July 1 | P2 | Confirm with Maya's current sprint commitments |
| 7 | Prepare API rate-limit documentation for enterprise | Jake (mobile lead) | July 8 | P1 | Current threshold values from Sarah |
| 8 | Draft Q3 roadmap update comms for stakeholders | Priya (PM) | July 3 | P1 | Decisions from this meeting |
---
## Open Questions
- **[CLARIFY]** Jake mentioned "we might need a new CDN provider for image-heavy screens" but no one confirmed budget. Who approves CDN spend?
- **[CLARIFY]** Priya said enterprise SLA is "four nines" but Sarah said current uptime is 99.7%. Is there a plan to close that gap before Acme goes live?
- The team discussed A/B testing the new onboarding flow but didn't decide on the tool. Optimizely vs. in-house — needs a decision by July 5.
- Will Maya's design system work be backfilled, or does the timeline simply extend?
---
## Suggested Next Meeting Agenda
1. Mobile performance profiling results (Jake — 10 min)
2. Enterprise staging environment status (Sarah — 5 min)
3. iOS hiring final-round debrief (Tomas — 10 min)
4. CDN budget decision (Jake + finance — 10 min)
5. SLA gap analysis for enterprise (Sarah — 10 min)