Meeting notes explain what people discussed. An action-item register answers a different question: what was decided, who owns the next step, when is it due, and what will show that it is complete? Keeping those records separate makes follow-through easier to review.
Create one stable record for each meeting
Start with a meeting ID, date, title, participants, facilitator, note taker, and the location of the agenda, notes, recording, or approved minutes. A stable meeting ID lets every decision and action point back to the same source without repeatedly copying long filenames or links.
Separate decisions from actions
A decision is an agreed result. An action is work assigned after or during that decision. Record them in different tables.
- Decision: what was approved, rejected, deferred, or accepted.
- Action: the specific next step needed.
- Discussion: context that may be useful but is neither a decision nor an assignment.
This distinction prevents a long discussion paragraph from hiding the actual commitment.
Write action items so another person can review them
A useful action item starts with a verb and produces an observable result. “Research options” is difficult to close. “Compare three options and send the table to the committee” has a clearer finish condition.
For each action, record one primary owner, the assigned date, due date, priority, status, blocker, related decision ID, and source pointer. Other contributors can be named separately, but shared ownership should not make the primary owner ambiguous.
Define completion evidence before closing the row
Status alone is easy to misunderstand. Add a completion-evidence field for the delivered file, sent message, published page, approval record, receipt, or other observable output. Mark an item complete only after recording where that evidence can be found.
Use a small status vocabulary
Choose a short list such as Not Started, In Progress, Waiting, Blocked, Complete, and Cancelled. Keep explanation in a separate note field. Consistent statuses make it possible to filter overdue work and distinguish delay from a deliberate cancellation.
Run a short follow-through review
Before the next meeting, filter the register for overdue, blocked, and waiting items. For each one, either record a new concrete next action, revise the due date with a reason, escalate the blocker, or close it with evidence. Carrying every open item into a new set of narrative minutes recreates the same ambiguity.
Preserve the original source
The register should point to meeting records, not replace them. Keep approved minutes, agendas, attachments, and recordings under their normal retention rules. If a decision is later corrected, append the correction and preserve the earlier entry instead of silently rewriting history.