How to write an action items list, with a template you can copy

The four fields every action item needs

An action item is not a note. It is a promise with a name and a date attached. Most lists fail because one of the four fields is missing, and the missing field is almost always the same one: nobody wrote down how you would know the thing was finished.

Here is what each field is for.

• The action, verb first. Start with what someone does: send, draft, book, rewrite, decide, test. If the line starts with a noun ("budget", "vendor call"), it is a topic, not an action item.
• One owner, by name. A single person. Not "the team", not "marketing", not two names joined by "and". Shared ownership is the polite way of saying nobody owns it.
• A real date. A day on the calendar. "ASAP", "next sprint" and "soon" are not dates. If the true answer is "before the next meeting", write the date of the next meeting.
• A done-condition. One short line describing what will exist when the item is finished: a file shared, a number posted, an email sent, a booking in the calendar. This is the field people skip, and it is the one that ends arguments.
• Status, optional but useful. Open, Done, or Blocked. If you use Blocked, say what it is blocked on and who can unblock it, otherwise it is just a nicer word for forgotten.

The action items list template

Copy the whole block below. Replace the bracketed text. Keep the column order, because it reads left to right the way a person thinks: what, who, when, and how we will know.

Put four lines above the table so the list still makes sense when someone finds it three weeks later. Meeting: [name of the meeting]. Date: [day month year]. Present: [first and last names, comma separated]. Next review of this list: [date of the meeting where these get checked].

Under the table is the same list written as plain text, one line per item. Use that version in a chat window or an email body, where tables break apart. The pattern is owner, then verb, then object, then date, then the done-condition in brackets.

• [Name]: [verb] [what], by [date]. (Done when: [condition].)
• [Name]: [verb] [what], by [date]. (Done when: [condition].)
• [Name]: [verb] [what], by [date]. (Done when: [condition].)
• Unassigned: [verb] [what]. Owner to be named by [date] by [the person running the meeting].
• Carried from [date of earlier meeting]: [Name]: [verb] [what], new date [date]. Second time this has moved.

A filled example

This is a real-shaped list from a made-up meeting: a weekly checkout redesign sync at a mid-sized online retailer, held on Tuesday 2 September 2026. Present: Maya Okonkwo (product), Daniel Ferreira (engineering), Ruth Halstead (support), Tom Beaumont (design). Next review: Tuesday 9 September 2026.

What did not make the list, and how to word what did

Three other things were said in that meeting and none of them became an action item. "We should think about pricing at some point" is a topic, so it goes on the next agenda. "Everyone please read the research doc" is an instruction to a group with no finish line, so it becomes a line in the recap message instead. "Daniel is worried about the timeout" is a concern, and concerns belong in the notes; the action item it produced is number 3, with a name and a date on it.

A list of six real items gets worked. A list of twenty-two, where six are real, teaches everyone to ignore the list. Cutting is most of the job. If you also keep a full record of the discussion, that belongs in your meeting minutes template and only the commitments come here.

For the items that survive, test every line like this: if the owner reads it in ten days with no memory of the meeting, can they start work immediately? If they would have to ask a question first, the line is not finished. Four common failures and the fix for each.

Owners, dates and done-conditions, the three that go wrong

One owner, always. Two names on one item means each person assumes the other started. If the work genuinely needs two people, split it into two items, or name one owner and mention the second person inside the task text: "Draft the migration plan with Ana". The owner is the person you would ask about it, not always the person doing the most work.

A real date, and a date you believe. Ask the owner for the date instead of assigning one. A date someone picks themselves gets met far more often than a date handed to them. If they say "end of the month", write the actual day. If an item has no natural deadline, use the date of the next meeting, because a list where half the items say "ongoing" is not a list.

A done-condition, written as a thing that exists. "Reviewed the contract" is an opinion. "Comments left in the shared contract doc" is a fact anyone can check without asking. Good done-conditions almost always name an artefact: a file, a message, a booking, a number, a ticket, an approval. When the done-condition is clear, chasing stops being a conversation about effort and becomes a yes or no question.

• Owner: one name, the person you would ask for an update.
• Due: a calendar date, ideally proposed by the owner out loud in the meeting.
• Done when: an artefact that exists, not a feeling that it is handled.
• Write it during the meeting, not after. Read each item back before moving on. Half the ambiguity dies right there, while everyone is still in the room.
• Keep the owner's own words where you can. "Send the numbers" beats a tidied-up "provide analytics data", because the owner recognises the sentence they said.

Variant 1: the RACI-flavoured list

Use this when work crosses teams and the argument is not "what needs doing" but "who is allowed to say it is finished". You keep the same four core fields and add two columns.

Responsible is the person doing the work. Accountable is the single person who answers for it and signs it off, often the manager or whoever called the meeting. Only one name in each of those two columns. Consulted or informed is everyone else who needs a say or a heads-up.

Do not use this shape for a normal weekly meeting. It costs about three times as much to fill in, and on a small team the Responsible and Accountable columns hold the same name, which tells nobody anything.

Variant 2: the personal commitments list

This is the version you keep for yourself after a day of back-to-back meetings. It has two halves: what you owe other people, and what other people owe you. Most people only track the first half, which is why the second half quietly disappears and then arrives as a surprise.

The first half is a normal action list filtered to your name, with one extra column recording which meeting it came from.

• The second half is your waiting-on list, and it needs four fields of its own.
• What I am waiting for: the artefact, not the topic. "The signed contract", not "the contract thing".
• Who owes it: one name.
• Promised by: the date they said, in their words, on the day they said it.
• What I do if it slips: the next step, decided now while you are calm. Usually "ask once more", "raise it with their manager", or "drop it and move on".
• Read both halves once a day for two minutes. That is the whole system, and it is the only reliable way to notice that something you are blocked on went quiet nine days ago.

Chasing without nagging

Chasing feels rude because it usually arrives as a vague poke: "any update on that thing?" A clear done-condition turns it into a closed question, which is much easier to send and much easier to answer. Follow this rhythm and you will rarely need to chase the same item twice.

1. 1Send the list within an hour of the meeting, while people still remember agreeing to things. A list that turns up two days later reads like an accusation. Use the plain-text version above if you are sending it as a message, and keep the wording you read out in the room.
2. 2Ask each owner to confirm their own line. A one-word "yes" from each person turns your notes into their commitment. Silence is not agreement, it is usually someone who never opened the message.
3. 3Send one reminder two working days before the date, containing only that person's items. Never send the full list to the whole group as a reminder, because everyone reads a group reminder as being about someone else.
4. 4On the due date, ask the closed question. "Are the five decline strings in the copy doc?" is answerable in one word. "How's the copy going?" invites a paragraph that does not tell you whether it is done.
5. 5If it slips, move the date once, in writing, to a new date the owner chooses. A moved date with a reason is fine. A date that quietly evaporates teaches the group that dates are decoration.
6. 6On the second slip, change the item instead of the date. Make it smaller, hand it to someone else, or kill it. An item that has moved twice is telling you something true about its priority, and no amount of chasing will change that.

Carrying items forward, and items nobody owns

Open items from the last meeting go at the top of the next list, not the bottom, and they keep their original date next to the new one. Seeing "originally due 12 Sep, now 26 Sep" does more work than any status label. Count the carried-forward items at the top of every review. If that number grows three meetings in a row, the group is committing to more than it can do, and the fix is fewer items, not harder chasing.

Then there is the item nobody wants. Somebody says "we should really look at the refund flow", everyone nods, and it lands in the notes with no name attached. That item will still be sitting there in November. Deal with it before the meeting ends.

• Default to the person who raised it. They cared enough to say it out loud. If they cannot own it, they usually know who should.
• If nobody in the room can own it, the person running the meeting owns finding an owner, with a date on that. "Maya to name an owner for the refund flow review by Friday" is a perfectly good action item.
• Never write "TBD", "everyone" or "the team" in the owner column. Those are the three ways an item dies while still looking alive.
• Be willing to kill it. "We agreed not to do this now" is a decision worth recording, and it costs nobody anything. Put it in the minutes as a decision, not on the action list.
• Cap the live list. Most weekly meetings can carry five to eight open items. Past that the list stops being read and starts being archived.

If you would rather not type the list at all

Filling this in by hand works, and for a short meeting you should just do it. The problem is the meeting where you are also the person talking. You cannot chair a discussion, argue your point, and capture six commitments with the right owner and date attached. Something gets lost, and it is usually the item somebody agreed to in one sentence on the way to another topic.

Noter AI records the meeting from your phone, either in the room or by sending a bot into a Zoom, Teams, Google Meet or Webex call, and then produces this structure for you. Pick the To-do list output style and the recording comes back as a task list instead of a wall of prose: the commitment, who made it, and any deadline that was actually said out loud. Action items are pulled out on every note anyway, so they are there even if you choose a different output style.

Two things make the result usable rather than approximate. Every line is timestamped and tagged with a speaker, so when someone disputes an item you tap the line and hear the sentence they said. And the transcript is editable: fix a misheard surname or a product name, re-run the summary, and the task list picks up the correction instead of repeating the mistake. You can also ask questions across all your notes at once, which is how you answer "what did I commit to this week" without opening six documents.

Then export to PDF, Word or plain text, or copy the formatted list straight into your recap message. If you want the process rather than the app, the neighbouring guide on getting meeting action items automatically walks through it step by step, and there is a separate page comparing seven tools on how well they extract action items if you are still choosing between them.

Pricing is $9.99 a month or $49.99 a year, flat, not per seat. Action items are the one output nobody wants rationed, and several tools in this category meter the AI layer with credits or a monthly summary allowance, so a heavy fortnight can leave you writing the list by hand anyway. Nothing here is metered. On the yearly plan the whole thing costs about $4.17 a month, which is roughly the price of one forgotten commitment. Run the free trial on a real meeting and compare the list it returns against the one you would have typed.