How to capture action items so they actually get done

What makes a meeting action item work

The meeting went well. Everyone agreed the onboarding emails need fixing and that someone should talk to the design agency. Two weeks later, at the next meeting, nobody has done either, and nobody is quite sure whose job it was.

An action item gets done when it has three things: one owner, a clear verb and a deadline. Write it in that shape the moment it comes up, read all of them back in the last two minutes of the meeting, send the list out the same day, and open the next meeting by checking it. That's the whole system. The rest of this guide shows each step.

The format: owner, verb, deadline

University committee guidance is a good model here. The University of Manchester's guidance says minutes should be action focused and indicate responsibility for actions, key deliverables and timescales, and that actions should normally include a target date for completion, in most cases by the next meeting (University of Manchester).

In practice, write every action as one sentence: [Owner] will [verb] [specific thing] by [date].

• Vague: "Onboarding emails: look into it." Clear: "Priya will rewrite the first two onboarding emails and share drafts by Thursday 14 May."
• Vague: "Agency follow-up." Clear: "Tom will email the design agency for a revised quote by Monday."
• Vague: "Check the numbers." Clear: "Ana will compare March sign-ups with February and post the result in the team channel by Wednesday."

One owner, even when several people help. "Priya and Tom" usually means each thinks the other has it. Name the person who'll report back, and list helpers in the same line if needed.

Why vague actions stall

A vague action can't be finished, because nobody can say what done looks like. It also can't be scheduled, because there's no date to plan around. So it sits.

Deadlines need care too. People are reliably optimistic about how long work will take. In one classic study, students writing an honours thesis predicted on average that they'd finish in 33.9 days, and actually took 55.5 days (Buehler, Griffin & Ross, 1994). That was a thesis, not a task from a team meeting, but the habit is the same. Let the owner set the date, ask them if it's realistic given everything else on their list, and pick a date they can meet rather than the one that sounds keen.

Capture them during the meeting

Don't leave action items for the write-up afterwards. By then the details have blurred and the owner has left the room. While the meeting runs:

1. 1Start each action on a new line with the word ACTION, so they're easy to pull out later.
2. 2When someone says "we should", ask two questions on the spot: "Who's taking that?" and "By when?"
3. 3Write the action in the owner, verb, deadline shape straight away.
4. 4If nobody will own it, write it down as an open question instead. An action without an owner isn't an action.

The two-minute recap at the end

Save the last two minutes of every meeting for reading the actions back. For each one, the owner says "yes, by then" out loud. It takes very little time and catches the common problems: the wrong owner, a date that clashes with someone's holiday, two people who each thought they were doing the same thing.

There's another benefit. In a series of experiments, unfinished goals caused intrusive thoughts and interfered with unrelated tasks, and letting people form specific plans for those goals eliminated those effects (Masicampo & Baumeister, 2011). Those were laboratory tasks, not team meetings, but the authors' conclusion fits: committing to a specific plan may leave more mental capacity for other work. A clear owner and date is a specific plan.

Send them out the same day

The Manchester guidance recommends drafting minutes as soon as possible after the meeting, and providing a list of actions to the colleagues who need to take steps. It also suggests keeping actions in a separate action log, not just inside the minutes. A short action log works for most teams:

• Action, in the owner, verb, deadline shape.
• Meeting it came from, with the date.
• Status: open, done, blocked or dropped.
• A one-line note on what happened.

Send the actions in a short message, separate from the full notes, so they're the first thing people see.

Follow up from your notes

Open the next meeting by going through the action log, before anything else. Each owner gives a one-word status and a sentence if needed. Done items close. Blocked items get help or a new date. Items that no longer matter are dropped on purpose, which is better than letting them quietly rot.

Between meetings, the question is often "what did I agree to do for that client?" Searching for it works if you wrote the action clearly and titled the note well. Our guide to finding what was said in a meeting has a simple template for that.

If your actions are spread across many meeting notes, Lumyo can help you find them. You choose which notes a chat reads, such as one project's meetings from last month, and ask what was agreed. Each answer cites the note it came from, and tapping the source opens the exact line, so you can check the wording before you chase anyone.