Turn meeting notes into action items people can actually finish
Turn vague meeting notes into agreed actions with an owner, a result and a date. Includes a fictional action register and a careful AI drafting prompt.
An Alembic resource · Version 1.1
A meeting action register people can actually use
Turn meeting notes into accepted actions, separate decisions and open questions, and retain the evidence needed to close each item.
Leave with a commitment someone has accepted
Give each action an observable deliverable, one owner and a date. Ask the owner to confirm it. If they were absent, record that acceptance is still needed instead of writing a commitment on their behalf.
Keep three different records:
- Action: a result somebody will produce, such as sending two available booking dates.
- Decision: a choice an authorized person has actually made, including its scope.
- Open question: an answer the team still needs, with a person responsible for obtaining it.
“Send date options” can be complete while “Which date did the customer choose?” remains open. A summary that merges those into “booking changed” has lost the point.
Use this starter row in your next meeting:
| Deliverable | Owner / acceptance | Due | Dependency | Completion evidence |
|---|---|---|---|---|
| [Observable result] | [One person; confirmed or pending] | [Date and timezone] | [Missing input or decision] | [Leave blank until it exists] |
The full resource adds a complete register, separate decision and question logs, and a fictional workshop handover. An optional prompt drafts rows from approved notes, flags missing or conflicting information and leaves acceptance for the people involved.
Use the blank action register CSV or inspect the fictional example CSV. The CSVs contain the action table; the complete guide also contains the decision and question logs.