How to track action items from meetings
Dylan de Heer
Most teams do not have a capture problem. They have accurate notes, sometimes a full transcript, and a list of things everyone agreed to do. Then nothing happens, and three weeks later the same items come up again in the same meeting.
Tracking is the part between agreeing and doing, and it fails for reasons that have nothing to do with how good the notes were.
Why action items go missing
Four causes, and in practice it is usually one of these rather than forgetfulness.
No owner. "We should look at pricing" belongs to nobody. Anything phrased with "we" will still be unowned next month.
No date. An item with an owner but no date is a wish. It never becomes urgent, so it never moves.
It lives in the notes. Notes are a record of a moment. Nobody rereads Tuesday's notes on Thursday, so an item that only exists there is functionally invisible the day after it was written.
Too many. A meeting that generates a long list of actions has effectively generated none, because nobody can hold a long list in their head. If your list runs that long, the meeting produced a discussion rather than decisions.
Capture the item properly in the room
The fix is mostly at the point of capture, not later. An item is trackable when it has three parts:
A verb. Not "pricing", but "send the revised pricing sheet".
One name. Not two, not a team. If two people own it, neither does.
A date. A real one. "Next week" becomes never.
Say it out loud before the meeting ends. "So Sam is sending the revised pricing to Maria by Thursday" takes a few seconds and does two things: it confirms Sam agrees, and it gives everyone else a chance to say that Thursday is impossible. That is the cheapest correction you will ever make.
If you are writing these down as you go, mark them so your eye finds them later. A consistent symbol you can search for beats underlining. There is more on that in taking better notes in meetings.
Move them out of the notes the same day
This is the step that actually separates teams who finish things from teams who do not.
Within a few hours, take every action out of the notes and put it wherever your team genuinely looks. That might be a project tool, a shared list, or a task app. Which one matters much less than whether people already open it without being asked.
The meeting where this matters most is the one that creates the most actions at once. A project kickoff meeting sets owners and dates for work that runs for months, and it is also the meeting people are least likely to have minuted properly, because everyone is still working out what the project is.
The test is simple. If your team checks a tool every morning, actions belong there. If the tool is opened only when someone remembers to, actions will die in it just as quietly as they died in the notes.
A single list beats a good tool. Actions spread across three systems get tracked in none.
Give someone the follow-up, not the whole team
Shared responsibility for chasing is the same problem as shared ownership of an item. Somebody has to be the person who looks at the list before the next meeting and asks about anything that has not moved.
That role is small. It is a few minutes before the meeting, not a job. But it has to belong to a named person, and ideally the same person each time, because the value comes from continuity rather than effort.
Start the next meeting with the last list
The most effective tracking habit is also the least technical. Open the recurring meeting by reading the previous actions and their status, before anything new is discussed.
It takes a couple of minutes. It also changes behaviour, because people know it is coming. An item that will be read out by name next Tuesday gets done by Monday in a way that the same item buried in a document does not.
Anything that has slipped twice is worth a decision rather than a third chase: either it matters and needs a different owner or a smaller scope, or it does not matter and should be dropped. Carrying an item indefinitely teaches everyone that the list is optional.
Where recording helps, and where it does not
If capture is your weak point, and specifically if you are running the meeting and cannot both facilitate and write, a recorder removes the tradeoff. The summary and the action list exist by the time the call ends, so nothing depends on you having caught it in the moment.
If your weak point is what happens after, a recorder will not fix it. An automatically extracted list still has to be moved somewhere people look, still needs owners and dates, and still needs someone to ask about it. Tools are good at capture and poor at accountability.
That is worth being clear about because it is where a lot of teams spend money and see nothing change.
If capture is the gap, Weeve records and writes the summary with action items on your Mac, with no upload step, which matters when the meeting is a client conversation and a recording of it would otherwise sit on someone else's servers. The free Starter plan covers 10 recordings a month. It is Mac only, and needs Apple Silicon with macOS 14 or later.
Two honest limits. Weeve extracts action items into the notes, it does not push them into your task tool, so the move is still manual. And the extraction is a model reading a conversation, so it needs a look before you treat it as the list.
If you want the list to arrive somewhere automatically, that is a workflow you build on top, and there is an example using Hermes that turns a week of meetings into one digest.
A workflow that holds up
Put together, the whole thing is five steps and about ten minutes a week.
State each action out loud before the meeting ends, with a name and a date
Mark them in your notes so they are findable
Move them into one shared place the same day
One named person checks the list before the next meeting
Open that meeting by reading the previous list
Nothing here is clever. The difficulty is that every step is easy to skip and skipping any one of them breaks the chain, which is why the failure looks like a tracking problem rather than a habit problem.
FAQ
What is the difference between an action item and a decision?
A decision is something that is now true. An action item is something someone has to do. Decisions belong in the meeting summary so people know the state of things. Actions belong wherever your team tracks work, because they need chasing.
Who should own tracking, the manager or the person who ran the meeting?
Whoever will actually be there next time. Continuity matters more than seniority, because the value is in noticing what has not moved, and that requires remembering last time.
How many action items should a meeting produce?
Few enough to read aloud at the end without anyone losing track, which usually means naming three or four rather than a dozen. If you consistently produce more, the meeting is trying to cover too much.
Should I assign action items during the meeting or afterwards?
During, out loud, while the person can object. Assigning afterwards means the first time someone learns they own something is in an email, which is how items get quietly ignored.
Do AI notetakers track action items automatically?
They extract them. Extraction is not tracking. Most tools, including Weeve, will pull a list of actions out of the conversation and put it in the notes, but moving that list somewhere people look, and asking about it later, is still a human job.
