Meeting Decision Log vs Action Items: Examples and Template

A practical workflow

1. Identify the outcome before writing the task

   For each discussion topic, ask what the participants actually agreed. Record the choice in a sentence that can stand on its own. If the conversation only explored possibilities, keep it as an open question or a proposed decision. A transcript can help you locate the exchange, but a fluent summary alone does not establish that a decision was approved.

2. Record enough context to revisit the choice

   Give the decision an identifier and note its date, reason, status, and the person or group that approved it. Add a source link or timestamp where available. Atlassian's decision documentation template includes context, roles, and status; the compact fields here are an editorial adaptation for a smaller meeting record, not a requirement to use a particular project tool.

3. Write actions as observable work

   Start each action with the task that must be completed. Record an owner and an agreed deadline, then connect it to the decision it supports. Atlassian describes action items as specific tasks or next steps assigned during or after discussions. A vague reminder such as Review later needs clarification before it becomes a useful commitment.

4. Mark missing agreement explicitly

   If no owner or date was confirmed, write that it is unconfirmed and identify what needs clarification. Use an explicit calendar date rather than a phrase such as next week once the date has been agreed. Include a time zone for a deadline that crosses regions. These fields should reflect the meeting, not fill gaps with an AI-generated guess.

5. Review the record when the plan changes

   Check the decision and its linked tasks together at the next review. If a new decision replaces the old one, keep the earlier record and mark it as superseded so the history stays understandable. Update task status separately: a completed task does not, by itself, mean that every part of the decision has been implemented.

What to check

An approver and a task owner have different roles; do not assume they are the same person. Preserve qualifications such as subject to review when they affect a decision's status. Before sharing AI-generated notes, verify the passages that establish approval, responsibility, and timing against the source and the participants' understanding.

Frequently asked questions

Is a decision log the same as meeting minutes?

No. Meeting minutes can cover attendance, discussion, decisions, and actions. A decision log focuses on agreed choices and their context, often across more than one meeting.

Can one decision create several action items?

Yes. Keep the decision as one record and link each follow-up task to it. Give every task its own owner, deadline, and status when those have been agreed.

What if the meeting did not choose an owner or deadline?

Mark the missing information as unconfirmed and seek clarification. Do not turn an incomplete discussion into an assigned commitment simply to finish the notes.