Action items: how to write, assign and track them — and how the recap keeps the list (2026)

An action item is one task that came out of a meeting: a verb, one owner, one date. "Anna — send the revised estimate to Aster — by Thursday" is an action item. "Follow up on the estimate" is a topic. The difference is whether a person who wasn't in the room can tell, from the line alone, what will happen, who will make it happen and when it is late.

Most meetings produce action items. Few teams keep them. The list gets written at the end of the call, lands in one person's notes, and resurfaces three weeks later as the question "did anyone ever send that estimate?" — asked in the next meeting, which then spends ten minutes reconstructing the last one.

This guide is the craft first — what an action item is, the five things each one carries, how to write them during the call and at its close, how to assign them so they get done, how to track them so the list survives — with a template and examples you can copy. Then the mechanics: where action items live in the tools your team already uses, and what happens to them after the meeting. That second part is where lists go to die, and it is the part the recap of a recurring meeting can do on its own.

What an action item is — and what it isn't

Four things come out of a meeting, and the first job of the person writing is to tell them apart:

A decision is not an action item: "we go with vendor B" changes nothing until "Priya — sign the vendor B order form — by the 14th" exists. An open question is not an action item either, though it often produces one ("Kenji — find out whether the API has a rate limit — by Monday"). And a ticket that was already in the tracker before the meeting is not a new action item; mentioning it in a meeting does not make it one. If the list of action items after a one-hour meeting is longer than ten lines, it contains topics, questions or tickets dressed as tasks.

What every action item carries: the format

A usable action item has five parts. The first three are the line; the last two are what makes it trackable.

1. One verb, one object. Send the estimate. Book the QA round. Draft the copy. A line that starts with "look into", "discuss" or "think about" is not an action — it has no finishing condition. If you cannot say what "done" looks like, the item is a question.
2. One owner — a name, not a team. "Marketing" cannot be asked whether something is done; Lena can. If two people are needed, there are two action items, or one owner who delegates. The owner is the person who will be asked about it next time, so it has to be a person who was asked now.
3. One date — a day, not "soon". "By the 16th" can be late; "asap" cannot. If the date is unknown, the action item is "Anna — propose a date for X — by Friday", which is a real item with a real day.
4. Where it came from. The decision or agenda item that produced it, and — if the record has one — the moment in the meeting where the owner said yes. This is the context a reader needs a month later, when the line "send the estimate" means nothing on its own.
5. Its state. To do, done, not done — and why. An action list without states is a wish list; the state is what the next meeting opens with.

What stays out: the discussion that led to the item, the reasons, the alternatives. Those belong in the notes. The action item is one line, because it is going to be read by someone looking for their own name.

How to write them: during the meeting, at the close, after

During the meeting, write the item the moment someone says yes. Action items are born in a sentence — "I'll send it over Thursday" — and they die in the same sentence if nobody writes it down. The habit that does most of the work: when someone takes something on, read it back aloud, with the date — "so I'm noting: Anna, the revised estimate to Aster, by Thursday" — and let the owner correct it while they still remember agreeing. An item that is read back is an item the owner has agreed to twice.

At the close, run the list. The last five minutes of a meeting with an agenda are reserved for outcomes and owners: every item on the agenda gets one of three states — decided, open, deferred to a date — and every action gets a name and a day. Read the whole list, one line each, in the room. This is where "Marketing to look at the pricing page" becomes "Lena — draft the pricing page copy — by the 16th", because Lena is there to say so. An item that cannot get a name at the close does not go on the list; it goes to the parking lot with the name of the person who raised it.

After the meeting, publish the list the same day — once, in one place. To everyone invited, including the people who weren't there: an action item whose owner missed the meeting is the one most likely to be missed. Then put the list where the next meeting will open it. A list in the facilitator's notebook is a list the team doesn't have; a list in the channel where the team already talks is one everyone can see ageing.

How to assign action items so they get done

Three rules cover almost every failed assignment:

• The owner is the person who said yes — in the room. Assigning an item to someone absent produces a line nobody has agreed to. If the right owner wasn't there, the item is "facilitator — ask Dana whether she can take X — by tomorrow", and Dana's real item is born when she answers.
• One owner, however many hands. "Mateusz and Priya" means each assumes the other. Pick the one who will be asked at the next meeting; the other is help, and help is not on the line.
• The owner repeats it back. Not the facilitator — the owner. "Thursday, the revised estimate, to Aster, yes." Thirty seconds, and it removes the most common dispute at the next meeting: "that's not what I agreed to."

What is not an assignment: an item on a list that the owner first sees in an email the next morning. If that is how items reach their owners, the meeting ended before the close.

How to track action items

Tracking is a routine, not a tool. Four parts:

1. One list per team or per recurring meeting. Not one per meeting — one that the meeting adds to and reads from. The list is the memory of the meeting series.
2. The next meeting opens with the list. Before the first agenda item: every open action, one line each, the owner says done or not done and, if not, why. Two minutes for a list of eight. The reason goes next to the item in a few words — "waiting on legal", "not started" — because the reason is what the room decides about.
3. Three states, and a not-done item is never carried silently. A not-done item is re-dated, reassigned or dropped, in the room, by the person who owns it. Carrying "send the estimate" across four meetings without a decision about it is how a list stops being read.
4. The ageing rule. An item older than the meeting's cadence twice over — two weeks on a weekly — is raised explicitly: either it is bigger than an action item and becomes a project task in the tracker, or it was never going to happen and is dropped. Both are fine. A list where nothing ever leaves is not a list.

The question your tracking has to answer is not "what did we decide" — the recap answers that — but "what, of all we decided, has actually happened, and what is stuck." If the list cannot answer it in two minutes at the start of a meeting, the format is wrong, not the people.

An action items template

The line, for the close of the meeting and the recap:

Action items — [meeting name], [date]
– [Owner] — [verb + object] — by [date] — from [agenda item / decision]
– [Owner] — [verb + object] — by [date] — from [agenda item / decision]
– [Owner] — [verb + object] — by [date] — from [agenda item / decision]

Carried over from [previous date]
– [Owner] — [task] — was due [date] — done / not done: [reason, three to six words] — re-dated to [date] / dropped

The tracker, for the list that spans the series:

Both paste into a document, a spreadsheet, a chat message or a canvas without reformatting. The columns that are usually missing from templates are From and Recorded: where the item came from, and how old it is. They are the two the next meeting needs.

Examples: the same items, before and after

Notice what the right-hand column has in common: a name first, a verb second, a day, and the item it came from. That is the whole craft. Everything else in this guide is about keeping that line alive after the meeting ends.

Where action items live in the tools you already use

Each major platform has a place for action items, and each stops at a different point. Documented behaviour only, from the vendors' own pages, with the month each page was checked:

Two things are the same everywhere. The action items are a document next to the meeting, in the one language the room used; and whether last week's items were done is a question the document does not answer — a person opens it at the next meeting and asks.

How the recap keeps the list

InterMIND is a communication space where a meeting lives in a channel, so the list has an obvious home: the channel's chat, where the agenda went in the day before and the outcomes come back after — and where each member types in their own language and reads the others in theirs. During the call, the list posted as a note goes on everyone's screen next to the video tiles with Share to conference; the sharer edits it live and every participant reads it in their own language. If the agenda or the tracker is drafted somewhere else, it lands in the channel by email — the channel's owner gives it an address of its own, and a message sent to it appears as a regular message with the sender named and attachments kept.

When the call ends, the recap is written from the meeting itself: a summary, the points marked agreed, open or disputed, and the action items — recorded only when someone took responsibility, named or self-assigned, with the owner on the line and the timestamp of the moment they said yes, which opens the transcript at that moment. The deadline, when one was said, stays in the line's words. The recap arrives by email, as a message in the channel and as a link in the calendar event, and every signed-in member reads it in their own language — the record is translated per reader, not written once in the language the room happened to use. A wrong owner is fixed with Edit; every edit keeps author and revision history, and the channel keeps the recap of every past session, so the item from three weeks ago is one click away.

For a channel's recurring meeting, the list is also read back. When the next recap is written, the open action items of the previous session are judged against what was said: an item someone reported finished is marked done; anything else is marked not done with the reason in the words of the meeting, or "not discussed" when nobody brought it up — next to the day it was first recorded. On accounts with this preview, the recap's two lists look like this:

## Action items
- [ ] Send the revised estimate to Aster (Anna) [12:05]
- [ ] Book the Japanese QA round (Kenji) [27:40]

## Carried over
- [x] Offer to the second finalist (Priya) · 2026-10-06 [0:09]
- [ ] Migrate the deals to the new CRM (Dana) · 2026-09-10 — deals still in the old CRM [0:20]

A done item is also marked on the recap where it was first written; the not-done ones travel to the next session. The recap page sums the channel's action items for the last 30 days or all time — the host sees everyone's row, a member sees their own — and at the start of the next session Mia names the open items and their owners, so the list is spoken about rather than found. This part runs for selected accounts while it is being refined.

Where the list has to end up in a system of record, the host adds a recap copy to any address — a CRM or tracker inbound mailbox — and every recap of the meeting or channel is also sent there after a one-time confirmation of the address; the mechanics are in a copy of every meeting recap in your CRM, by email. The same recap reaches Zapier, a webhook or the API with the summary as Markdown, and the reader's own assistant — Claude, ChatGPT, Copilot or Gemini — can read the recaps through the MCP connector, so "add the action items from my last three meetings to my task list" is a prompt in the tool they already use.

A guest joins by link, without an account and at no cost — from a phone, in the browser — and hears the meeting live in their own language. There is no record for a guest afterwards — the account is free, and it is what makes the record reachable. The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days; members who go quiet keep their access at no cost.

• Open a complete recap — a real record rendered by the same code that writes yours, action items included.
• Try the live demo — no signup; speak, and hear the room translated per listener.

Action items as a craft survive every tool: somebody still has to say yes to a task, out loud, with a date. What doesn't have to survive is the second job — retyping the list after the call, in one language, and opening the next meeting by asking whether anyone did what the last one said.

FAQ

What is an action item?

An action item is one task that came out of a meeting, written as a verb with an object, one owner and one date: "Anna — send the revised estimate to Aster — by 16 October". It is distinct from a decision (what the room agreed), an open question (what nobody could answer yet) and a project task that already lives in a tracker. Its purpose is that someone who wasn't in the meeting can tell what will happen, who will do it and when it is late.

What is an example of an action item?

"Lena — draft the new pricing page copy — by 16 October — from decision 2." A name, a verb, a day, and the item it came from. The same thing said badly is "Marketing to look at the pricing page": no person, no finishing condition, no date.

How do you write action items in meeting minutes?

One line each, under their own heading: owner, task, deadline, in that order — "Action: M. Bauer — updated price list to sales — by 5 September." Write the item the moment someone takes it on, read it back aloud with the date so the owner confirms it, and list all items together at the close of the meeting. An action item without an owner is recorded as an open question instead; the full format is in the meeting minutes guide.

What is the difference between an action item and a task?

An action item is born in a meeting and is reviewed by that meeting: it is one line with an owner and a date, and its life is short — days or weeks. A task lives in a tracker with its own status, estimate and history, and may outlive many meetings. An action item often becomes a task ("Mateusz — open the ticket for the export fix — by tomorrow"), but mentioning an existing ticket in a meeting does not make it a new action item.

Who is responsible for action items in a meeting?

Each action item has exactly one owner — the person who said yes to it, in the room — and the facilitator is responsible for the list: reading it back at the close, publishing it the same day, and opening the next meeting with it. An item assigned to someone absent is a line nobody has agreed to; the real item is to ask them.

How do you track action items from meetings?

Keep one list per recurring meeting, not one per meeting; open every meeting with it — each owner says done or not done, and why, in two minutes; give every item one of three states; and never carry a not-done item silently: re-date it, reassign it or drop it, in the room. Any document, spreadsheet or canvas works for the list. In an InterMIND channel the recap writes the list from the meeting and, for recurring meetings on the carry-over preview, reads the previous session's open items back and marks each one done or not done with the reason.

Can Zoom, Teams or Google Meet create action items automatically?

Per their documentation: Zoom's AI Companion meeting summary includes a "Next steps" section on paid Zoom Workplace plans, and during the meeting the preset question "What are the action items?" can be asked; Microsoft Teams meeting notes let attendees assign tasks by tagging people, and the Teams recap lists follow-up tasks; Google Meet's Take notes for me adds "suggested next steps" to the notes document, where a person can assign them. In each case the record is kept in the one language the meeting was held in; Google states that multiple languages in the same meeting are not supported.

Sources: Microsoft — Take meeting notes in Microsoft Teams; Microsoft — Recap in Microsoft Teams; Zoom — Using Meeting Summary with AI Companion; Zoom — Meeting questions with AI; Google Workspace Updates — "Take notes for me" now captures "next steps"; Google Meet — "Take notes for me" in Google Meet; Slack — Meeting agenda template (canvas). Microsoft's notes page, Google's Meet help page and Slack's template checked October 2026; Microsoft's recap page and Zoom's meeting-summary page checked August 2026; Zoom's meeting-questions page and Google's next-steps announcement checked September 2026. Vendors change plans, features and language lists over time; check their pages for the current state.