Productivity
Turn meeting notes into decisions and actions
Separate decisions, action items, and unresolved questions.
by Appndo
Tested on GPT-6.1 Sol, Claude Opus 5.5, Gemini 3.8 Flash · Verified Oct 28, 2026
The prompt
Summarize these meeting notes for everyone involved, including people who missed the meeting:
{{notes}}
Return four sections:
1. Decisions: what was decided, one line each.
2. Action items: a table with task, owner, deadline, and any dependencies the notes state. Write "unspecified" when the notes do not say, and mark owners or deadlines the notes leave uncertain as "tentative".
3. Open questions: what is still unresolved, and who should answer it if the notes say.
4. Follow-up message: a short message built only from sections 1–3. Add no dates or owners, and list the items that still need an owner.
Use only information in the notes. If the notes conflict, give both versions and who said each instead of picking one. Keep it concise.How to use it
Paste rough notes or a transcript, after removing confidential details you cannot share with your AI provider. Confirm owners marked tentative with the people involved before you send the follow-up message.
Example
Inputs
- notes
- Mobile app v2.3 launch sync - Tue Oct 21 Present: Priya (PM), Marcus (eng lead), Dana (design), Leo (marketing), Sam (QA, joined late) - Priya: release target still Nov 10. Marcus thinks ok if the payments SDK upgrade lands this week. - SDK upgrade: Marcus's team, he said "should be done by Fri". Blocked on Stripe sandbox keys - someone needs to ask finance. no one took it. - Dana showed new onboarding screens. General agreement to go with version B (3 steps not 5). Leo wanted A/B test but Priya said no time, ship B, revisit after launch. - Landing page copy: Leo to draft. Leo said he'd have it by Friday Oct 24. Later in meeting Priya said marketing copy due Nov 3 for legal review... Leo nodded. not clear which. - Push notifications: Dana raised that the permission prompt shows on first launch, wants it moved after onboarding. Marcus said doable but maybe not for 2.3. Not decided. - Sam (late): regression suite has 14 flaky tests. Needs to fix before code freeze. Code freeze date?? Priya thought Nov 5, Marcus said "week before release". - App store screenshots - need new ones for onboarding B. Dana or Leo? - Leo asked about press embargo, Priya to check with comms. - Budget for paid launch campaign: Leo asked for $15k, Priya said she'd need to get approval from Hannah. no date. - Next sync Thursday. - Also: Android tablet layout bug (#4412) - Marcus says known, low priority, won't block release. agreed.
Output
1. Decisions
- Keep the Nov 10 release target; Marcus says it is feasible if the payments SDK upgrade lands this week.
- Ship onboarding B (3 steps); revisit A/B testing after launch.
- Android tablet layout bug #4412 is low priority and will not block release.
2. Action items
| Task | Owner | Deadline | Dependencies |
|---|---|---|---|
| Complete payments SDK upgrade | Marcus’s team | Friday (tentative; Marcus: “should be done”) | Stripe sandbox keys |
| Ask finance for Stripe sandbox keys | unspecified | unspecified | unspecified |
| Draft landing page copy | Leo | Tentative: Friday Oct 24 (Leo); Nov 3 for marketing copy legal review (Priya)—whether these are separate deadlines is unclear | unspecified |
| Fix 14 flaky regression tests | Sam | Before code freeze; freeze tentative: Nov 5 (Priya), “week before release” (Marcus) | unspecified |
| Create app store screenshots for onboarding B | Tentative: Dana or Leo | unspecified | Onboarding B |
| Check press embargo with comms | Priya | unspecified | Comms input |
| Seek approval for $15k paid launch campaign | Priya | unspecified | Hannah’s approval |
3. Open questions
- Who will ask finance for the sandbox keys?
- Are the copy deadlines separate milestones or conflicting deadlines?
- Will the notification permission prompt move after onboarding in v2.3? No decision.
- What is the code freeze date? Priya said Nov 5; Marcus said “week before release.”
- Who owns the new app store screenshots: Dana or Leo?
- What is the press embargo? Priya to check with comms.
- Will Hannah approve the campaign budget, and when?
4. Follow-up message
We’re proceeding with onboarding B and revisiting A/B testing after launch. The tablet layout bug will not block release. Please resolve the SDK keys blocker, copy deadlines, code freeze timing, notification prompt scope, press embargo, and campaign approval. Still needing a confirmed owner: requesting sandbox keys and creating app store screenshots.
One real run with the example above. Results vary between runs and models.