To track action items from meetings, write each one down during the meeting with four things: a specific task, one named owner, a due date and a status. Read each item back before the meeting ends so the owner agrees. Keep every item on one running list, not in separate minutes. Open the next meeting by reviewing that list, escalate anything overdue by a set rule, and record the decisions behind each action in a decision log so the reason is not lost.
By Coplain Team
Last updated
Step by step
Keep one running list — before the meeting, open the running action list for that meeting series. One list per series, carried from meeting to meeting, works better than a fresh set of minutes each time, because open items stay visible until they are closed. Number each item and never reuse a number.
Capture each item live with owner, due date and status — when the group agrees something must be done, write it immediately. Start the task with a verb and make it checkable: “Send revised drawing to supplier”, not “drawing”. Give it one named person, not a department or “team”, a real date rather than “ASAP”, and a status of Open.
Read the items back before closing — spend the last few minutes reading each new item aloud with its owner and date. This is where unclear tasks and unrealistic dates get fixed, while everyone is still in the room. If an owner is absent, mark the item as pending their acceptance and confirm it with them the same day.
Send the list the same day — send the updated list, not a narrative summary, within a few hours. Owners should be able to find their items without reading paragraphs. If the meeting is a formal review, attach the list to the minutes so the record is complete; a management review template has a section for this.
Review open items at the start of the next meeting — make the first agenda item a walk through every open item. Each owner says done, on track or late. Close done items with the date closed; do not delete them. Doing this first keeps old commitments from being crowded out by new topics.
Escalate overdue items by a fixed rule — agree a rule in advance, for example: one missed date gets a new date and a reason; a second missed date goes to the owner’s manager or the meeting sponsor. A rule makes escalation routine rather than personal. If items keep slipping for the same reason, chart the reasons with a Pareto chart generator and fix the biggest one.
Link decisions to a decision log — when the meeting makes a decision, write it in a decision log with the date, the decision, the options considered, who decided and the reason. Give each decision an ID and put that ID on the action items it creates. Months later, anyone can see why an action existed.
Why action items get lost
Most lost actions fail in one of a few ways: no single owner, no date, a vague task, or a list that nobody reads until the next crisis. Minutes written as paragraphs make all four worse, because the commitments are buried in the discussion. A short list with four fields is easier to write, easier to read and easier to check.
The same idea appears in formal quality systems. ISO 9001:2015 asks that management review outputs include decisions and actions, and corrective action processes track each action to closure. A corrective action log is an action list with stricter rules on root cause and verification.
What each action item needs
Keep the fields few so people actually fill them in during the meeting:
ID: a number that is never reused.
Action: starts with a verb and says what done looks like.
Owner: one named person who will report on it.
Due date: a calendar date.
Status: Open, Done or Late, plus the date closed.
Source: the meeting date, and a decision ID if one created it.
Status, escalation and closing
Status should be a fact, not a feeling. Done means the output exists and someone could check it. Late means the date has passed. Avoid “in progress” as a final state; ask for the new date instead. When an item is closed, keep it on the list with its closed date. The closed items are the evidence that the meeting produces results, and in an audit they show the system works. The internal audit guide explains how auditors sample records like these.
Escalation is not punishment. An item that has slipped twice usually has a blocker the owner cannot remove alone: a missing budget, a supplier, a conflicting priority. Escalating it to someone who can remove the blocker is the point.
Decisions and actions belong together
An action list says what will happen. A decision log says why. Without the decision, people reopen settled questions or undo actions they do not understand. Keep both in the same place, or at least cross-referenced by ID. If a decision changes a released document, the formal change still goes through an engineering change notice; the decision log records the reasoning that led to it.
Worked examples
Example: Example: a fictional weekly quality meeting action list
Meeting: weekly quality review, 2027-05-12. All parts, roles and dates are invented for illustration. Decision D-07 was “Move bracket BR-114 to 4 mm gusset”.
A-31 · Send rev D drawing for BR-114 to the supplier · Owner: design engineer · Due 2027-05-14 · Status: Done, closed 2027-05-13 · Source: D-07
A-32 · Update the control plan for the new gusset weld · Owner: quality engineer · Due 2027-05-19 · Status: Open · Source: D-07
A-33 · Quote a second fixture for the test rig · Owner: test lead · Due 2027-05-05 · Status: Late, second miss, escalated to the operations manager · Source: 2027-04-28 meeting
A-34 · Add gauge SG-12 to the calibration schedule · Owner: metrology technician · Due 2027-05-21 · Status: Open · Source: 2027-05-12 meeting
A-35 · Brief second shift on the revised inspection step · Owner: second-shift supervisor · Due 2027-05-17 · Status: Open, owner absent, accepted by email the same day · Source: D-07
Count at the start of the 2027-05-19 meeting: 5 items, 1 done, 1 late, 3 open; the late item is the first one discussed.
Result: Every item has one owner and a date, three items trace back to decision D-07, and the late item has already been escalated by rule instead of being rediscussed from scratch.
Common mistakes
Assigning an item to a team or department. Name one person who will report on it, even if others help.
Using “ASAP” or “next week” as a due date. Write a calendar date the owner has agreed to.
Burying actions inside paragraph minutes. Keep a separate numbered list and attach it to the minutes.
Starting a fresh list every meeting. Carry one running list so open items stay visible until closed.
Deleting items once they are done. Mark them Done with a closed date and keep them as the record.
Recording actions without the decision behind them. Log decisions with an ID and reference it on each action.
Frequently asked questions
What is an action item in a meeting?
A specific task agreed in the meeting, with one owner and a due date, that someone can check as done or not done.
Who should own the action item list?
The meeting chair or a named note-taker keeps the list, but each owner is responsible for their own items and their status.
How do I handle overdue action items?
Use a rule agreed in advance: a first miss gets a new date and a reason, and a second miss is escalated to someone who can remove the blocker.
Should action items go in the meeting minutes?
Attach them as a separate list. Minutes record discussion; the action list records commitments and is carried from meeting to meeting.
What is the difference between an action log and a decision log?
The action log records what will be done, by whom and when. The decision log records what was decided, by whom and why.
Sources
ISO 9001:2015 Quality management systems — Requirements (clause 9.3, management review), ISO
A Guide to the Project Management Body of Knowledge (PMBOK Guide), Project Management Institute