Turn Meeting Notes Into Decisions—Without Inventing Tasks

Ask for a decision log before asking for an action plan. Rough meeting notes often mix ideas, objections and commitments. Turning all of them into tasks can create obligations nobody agreed to.

The goal is a faithful record. You can generate suggestions later, under a separate heading, once the agreed decisions are clear.

Use the attached meeting notes only.
Create three sections: confirmed decisions, agreed actions and open questions.
For each decision or action, include the supporting note or timestamp.
Only assign an owner or deadline when explicitly stated.
Use "unassigned" or "not agreed" for missing details.
Do not turn ideas, proposals or conditional statements into commitments.
Put optional suggestions in a separate section, clearly labeled as suggestions.
Flag contradictory notes for human review.

Upload the notes you are permitted to use and confirm the attachment is readable. If you need identities anonymized, replace them consistently before uploading. The meeting decision-log prompt provides another copyable starting point.

Illustrative input:

• “We should consider a Friday launch.”
• “Mina will check the landing-page copy by Thursday.”
• “No launch date until the payment test passes.”

Expected extraction:

Type	Entry	Owner	Deadline
Agreed action	Check landing-page copy	Mina	Thursday
Decision	Do not set launch date before payment test passes	Not stated	Not agreed
Open question	Is Friday feasible after the test?	Unassigned	Not agreed

The model should not create “launch on Friday” as an agreed task. This is a hand-written expected example, not a recorded product result. Dates such as Thursday also need a calendar date if the log will be used outside the meeting week.

Check every entry against the source. Ask the meeting owner to resolve ambiguous commitments. Preserve the original notes alongside the approved log so a polished summary never becomes the only record.

This technique works with rough notes and transcripts, but missing or inaccurate transcription remains a limitation. No prompt can recover an agreement that the source never captured. For a fuller evidence workflow, use our source-grounded research brief guide.

Research reviewed 6 October 2026. Interfaces, features and plan limits can change. The exercises and frameworks here are original editorial examples, not measured product benchmarks.

Transcript-to-ledger walkthrough, including one suggestion correctly excluded. This is an exercise brief, not a claim that the external platform run has been performed. Keep your source input, attempted output and failure cases together. Use permitted or fictional material.

Record what you actually observed, what remains unverified, and which change you would try next. Do not substitute a conceptual cover image for result evidence.

Download fictional samples and checklists · Choose a practical learning path

Fictional input / controlled setup: Fictional transcript: Mina: Can we launch Friday? Omar: Friday works if QA passes. Mina: We still need someone to own QA.

Reference check: Decision: conditional Friday launch. Condition: QA passes. Owner: unassigned. Open question: who owns QA? No assigned action or completed QA can be inferred. Use the meeting sample download for a larger exercise.

Evidence boundary: This card is an editorial reference and reproducible exercise, not an observed result from a named AI model. Record actual results before making performance claims.