Turn meeting notes into decisions, owners and dates
Most notes record what was said. This prompt extracts what was decided, who owes what, and what is still open.
any
A transcript that says “we discussed pricing” is worthless a month later. The useful artifact is four lines: the decision, the owner, the date, and the thing nobody resolved. This prompt produces exactly that, and refuses to invent owners when the notes do not name one.
From the notes below, extract only what is supported by the text.
Produce four lists:
1. DECIDED: one line per decision, in the form
"<decision> | owner: <name or none stated> | by: <date or none stated>"
2. OPEN: questions raised and not resolved, one line each, with who raised it.
3. ACTIONS: commitments made, in the form
"<action> | owner: <name> | due: <date or none>"
4. RISKS: anything someone flagged as a concern, quoted in at most 12 words.
Rules:
- If an owner or date is not in the notes, write "none stated". Do not guess.
- Do not merge two decisions into one line.
- Drop small talk, scheduling and anything said twice.
- At the end, list what the notes are missing to be actionable, at most three
bullets.
Notes:
{{notes}}
How to use
- Paste raw notes or a transcript, not your summary: the prompt needs the disagreements.
- The “missing” list at the end is the agenda for the next meeting.
- If everything lands in OPEN, the meeting produced no decisions. That is worth knowing.
Fill before you run
{{notes}}
More in Work
WorkTurn a topic into a user story with acceptance criteriaThe story format, the acceptance criteria and the edge cases the team will ask about.WorkThe key events in a transcript, in orderWhat happened, when, and who acted.WorkText into a Mermaid diagramThe right diagram type for the content, then the source that renders.