Best way to keep a running list of action items across weekly meetings
Keep one action list per meeting series, with an owner, a date and a one-line outcome on every item, and one named tracker between meetings.
Smalt AI team ·
Keep one action list for the whole meeting series rather than a new list for each meeting. Every item needs an owner, a specific date and a one-line outcome, and one named tracker should check the action list between meetings. Open each meeting by reviewing what is still open, and close it by confirming what was added.
Use one action list per series
When every meeting gets its own notes page, open items stay behind in last week’s notes. Someone has to reread them to find out what is outstanding, and in practice nobody does. A single action list that belongs to the series, such as “Tuesday ops sync”, keeps open items visible until they are closed.
Notes can still be written per meeting. The notes record what was said, and the action list records what is owed.
What every item needs
Each row carries the same four fields: one owner (a person, not a team), a calendar due date, an action written as a one-line outcome, and a status of open, done or blocked. “Next meeting” is not a date, because the next meeting can move or be cancelled. A sample action list for a weekly ops meeting, with invented rows:
| Owner | Action | Due date | Status |
|---|---|---|---|
| Owner A | Refund checklist updated in Notion | 2026-11-17 | Open |
| Owner B | Carrier delay report sent to the ops channel | 2026-11-13 | Done |
| Owner C | Supplier contract renewal date confirmed | 2026-11-20 | Blocked |
| Owner D | Monday dashboard export scheduled | 2026-11-16 | Open |
Paul Axtell, writing in Harvard Business Review, advises confirming a specific action and completion date for each item before the meeting ends. He also suggests asking people to flag early if they will miss a commitment, which the “blocked” status makes cheap to do. Dated items that must not slip, such as contract renewals, deserve a date on the action list and not a vague reminder.
Name one tracker
Shared responsibility for an action list usually means nobody checks it. Axtell recommends naming one person to monitor and follow up between meetings. The role can rotate monthly, as long as the current tracker is written at the top.
The tracker’s job is small: message owners whose dates are close, mark items done, and bring the open items to the next meeting. When an owner goes quiet, a short written nudge works better than a hallway reminder, and chasing an overdue confirmation follows the same pattern. Axtell also suggests keeping a tally of completed items and aims for about 85% completion. That is his advice, not a measured result. There is no reliable published completion-rate statistic we could cite, so this post uses none.
Run each meeting the same way
- Open by reading the open items, oldest first.
- Have each owner say done, on track or blocked, and discuss only the blocked ones.
- Add the new items, then read them back with owner and date.
- If an item has no owner by the end, assign one then or write “no owner” so the gap stays visible.
A small survey gives some support for using meeting outcomes later. Král, Králová and Šimáček surveyed 128 respondents across 18 organizations and found that using meeting outcomes in later work was strongly associated with perceived meeting effectiveness (p<0.001), while informal follow-up chats did not help. The data is self-reported and comes from a small sample in one region, so treat it as a pointer, not proof.
Pick the tool where your team already works
The action list can live in a shared spreadsheet, in Jira, Asana or Linear, or in a task tool tied to your calendar. Choose the one your team already opens every day.
Two vendor features are worth knowing about:
- Microsoft: task lists added to the “Follow-up tasks” section of a Teams or Outlook meeting sync with a Planner plan, and each task list becomes a bucket. Moving a task out of a bucket created from the notes removes it from the meeting notes but leaves it in the plan.
- Google: meeting notes created from a Calendar event are attached to that event and shared with guests. Changes do not sync between the doc and the event, and an event has only one notes doc.
Neither page documents how open items carry over between occurrences of a recurring meeting. That does not mean no tool does it. Our recommendation is a separate, persistent action list for the series, linked from each invite, so it does not depend on how a calendar handles recurrence.
Doing it with an AI coworker
If your team writes meeting notes in a doc, you can ask Smalt to turn them into tasks. A request such as “Turn this morning’s meeting notes into tasks” asks for tasks in Jira, Asana or Linear with an owner and a due date on each, plus a short list of anything that had no owner. Other examples of work to hand off are on the use cases page.
The unowned items are the part worth reading first, since they are the ones most likely to stall. Tasks are not held for approval, so check the project and assignees before you share it.
What to check before you rely on it
- Ambiguous owners. Notes that say “we will” or name only a team give nothing to assign. Fix these in the meeting.
- Dates inferred from phrases. “By Friday” and “end of month” need a person to confirm the actual date, especially across time zones.
- Duplicates. If an item appears in the notes, the project tool and a calendar task list, pick one source of truth and delete the rest.
- Stale items. An action list that only grows gets ignored, so the tracker should close or drop old items each week.
- Your own setup. The vendor behaviour above comes from help pages as written. Test a recurring meeting in your own tools before depending on it.
Smalt is an AI coworker that takes jobs like this end to end and hands back the finished file.