Build a decision log from several meetings' notes
Combines notes from multiple meetings into one running log of decisions, dates, owners, and status so nothing gets relitigated.
The prompt
Build a decision log from the notes of several meetings so my team has one place to see what has been decided.
Project or team: [NAME]
Meeting notes, labeled with date and meeting name: [PASTE EACH SET OF NOTES]
Existing decision log (if any): [PASTE or "none"]
Rules:
- Only log real decisions: something agreed by the person or group with authority. Proposals, preferences, and "we should probably" go in a separate "Not yet decided" list.
- If a later meeting changed an earlier decision, keep both entries: mark the earlier one "Superseded" and link it to the new one.
- Flag contradictions between meetings that nobody resolved.
- Do not invent owners, dates, or reasons. Use **[NOT STATED]** where the notes are silent.
Return:
1. The decision log as a table I can paste into Excel or a shared doc:
| ID | Date | Meeting | Decision | Decided by | Rationale (short) | Affects | Status (Active / Superseded / Under review) | Related actions |
2. Not yet decided: items discussed repeatedly with no decision, and how many meetings they have come up in.
3. Conflicts to resolve: decisions that contradict each other or were reversed without explanation.
4. A short note on how to keep this log updated after each meeting (who adds entries, when, and what counts as a decision).
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Meetings prompts
What to fill in
- NAME
- PASTE EACH SET OF NOTES
- PASTE or "none"
- NOT STATED
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Find unresolved issues in meeting notes and follow-up questions to close themLists every open loop a meeting left behind, why it is stuck, who should close it, and the exact follow-up questions to send.
- Turn a meeting discussion into a decision record people can sign offWrites up what a meeting decided, the options considered, the reasoning, and the trade-offs, ready for stakeholders to confirm.
- Map each stakeholder's needs, agreements, and conflicts from a meetingSummarizes each person's needs and position from a discussion and shows the areas of alignment and conflict to work on.
- Find where a meeting went off-topic and how to run it tighterShows where a meeting drifted off-topic, how much time it cost, and specific changes to keep the next one on track.