Writing meeting action items that get done

This guide shows how to turn what people say in meetings into action items, with weak and strong examples, how to handle tasks nobody took, and how to make sure the list is looked at again.

The four parts

An owner

One named person, not a team and not "we". The owner does not have to do all the work; they have to make sure it is done and be the person others ask about it. If an item involves several people, pick the one who is answerable and name the others in the text.

A verb

Start with what the owner will do: send, draft, decide, book, review, ask, fix. A verb turns a topic into a task. "Pricing page" is a topic; "rewrite the free-tier section of the pricing page" is a task.

Be wary of verbs that describe activity without an end: "look into", "think about", "explore", "work on". If that is genuinely what was agreed, add what the result will be: "look into the date format bug and say whether it can be fixed for 2.5".

A deliverable

What exists when the item is done: a sent email, a document, a decision, a booked meeting, a merged change. The test is whether someone else could tell, without asking, that the item is finished.

A date

A day, not "soon" or "next week". If the owner did not give one in the meeting, ask before it ends. An item without a date competes with everything else the owner has, and loses.

Weak and strong examples

Each strong version can be answered with "done" or "not done", and everyone knows who to ask.

Writing them in the meeting

Listen for commitments: "I'll", "I can", "leave it with me", "let me check". When you hear one, write it down with the name and ask for a date if none was given. Reading the list back in the last two minutes of the meeting catches the ones you misheard and turns soft agreements into real ones: "Tom, that's the pull request reviews by Wednesday noon?"

If someone says "someone should…" and nobody responds, do not write it down with a guessed owner. Either ask the room — "who's taking that?" — or record it as an open question.

When nobody committed to anything

Some meetings end with nobody agreeing to do anything. That is worth writing down plainly: "No actions agreed." It is not a failure of the notes; it is an accurate account of the meeting, and it may be the most useful thing to know about it.

What you should not do is invent items to fill the section. An action item with an owner who did not agree to it is worse than none. The owner does not know it is theirs, everyone else thinks it is covered, and nothing happens. Tasks that were discussed without an owner go under Open questions, with a note that nobody took them, so the next meeting can decide.

Keep the list short

A meeting that produces fifteen action items has usually produced three real ones and twelve wishes. Before sending, look at each item and ask whether the owner would recognise it as something they agreed to. If not, move it to open questions.

Long lists also hide the important items. If one action blocks everything else, put it first.

Send them and check them

Action items are only useful if the owners see them. Send them the same day, either in the meeting notes (see the meeting notes template) or, for people outside your organisation, in a follow-up email after the meeting that confirms what was agreed.

Then check them. The simplest habit is to start each recurring meeting by going through the last meeting's list: done, not done, or no longer needed. Items that keep slipping are a sign the owner, the date or the item itself is wrong, and that is a conversation to have rather than a date to push again.

For items that come from a decision the team will need to refer back to, record the decision itself in a decision log so the reason survives after the task is done.

A template

## Action items

- [ ] <Owner> — <verb> <deliverable> — by <date>
- [ ] <Owner> — <verb> <deliverable> — by <date>

## Open questions (no owner yet)

- <Task or question> — raised by <name>, nobody took it

Action items from a transcript

A transcript makes it easier to find commitments you missed while talking, and to check the exact words someone used. It also makes it easy to be too generous: a transcript is full of "we could" and "maybe I'll", and not every one of those is a commitment.

The same risk applies, more strongly, to action items written by an AI from a transcript. Summaries can turn a suggestion into a task, or assign an owner because of who spoke nearest to it. Check each item against the transcript before sending, and delete the ones nobody agreed to. Can you trust an AI meeting summary? goes through how to check one.

Notey writes a summary with action items from a meeting's transcript when you ask. The action items are listed by person, each one editable, and if nobody committed to anything the summary says so rather than inventing items. The notes are labelled as AI-generated, and an item you edit is marked as edited by you.

A quick test before you send

For every item on the list:

1. Is there exactly one named owner?
2. Does it start with a verb?
3. Could someone else tell when it is done?
4. Is there a date?
5. Would the owner agree they said they would do it?

If any answer is no, fix it or move it to open questions.

Frequently asked questions

What makes a good action item?

One named owner, a verb, a specific deliverable and a date. "Priya — send Northwind the revised timeline — by Friday" is an action item. "Timeline follow-up" is a topic.

Can an action item have two owners?

It can involve several people, but it should have one owner who is answerable for it. Two owners usually means each assumes the other is doing it.

What if nobody agreed to do anything in a meeting?

Write that down. "No actions agreed" is accurate and useful. Tasks that were discussed but not taken belong under open questions, not as action items with an owner nobody agreed to.

How do you follow up on action items?

Send them the same day, in the notes or a follow-up email, and start the next meeting by going through the previous meeting's list. An item that is never checked tends not to get done.

Can AI write action items from a meeting transcript?

It can draft them, but check each one against what was said. The common failure is an item nobody actually committed to, or an owner assigned by guesswork.