How to Write Action Items That Actually Get Done (+ Template)

The meeting ends on a high note. Everyone agreed on what to do next, heads were nodding, somebody said "great, let's make it happen." Two weeks later nothing has moved, and nobody can quite remember who was supposed to do what.

If that scene feels familiar, you're not bad at meetings. You're bad at writing action items, and so is almost everyone else. One industry analysis estimated that roughly three-quarters of action items generated in meetings quietly disappear. The reasons are boringly predictable: the task was vague, no single person owned it, there was no due date, or it got buried in notes nobody ever reopened. The good news is that those are all fixable in the time it takes to type one sentence. This is a guide to writing action items that survive contact with a busy week.

The anatomy of an action item that survives

A good action item isn't a topic or a hope. It's a small, finished-or-not unit of work. The fastest way to tell whether you've written one is to ask: could a person who wasn't in the room read this and know exactly what to do, by when? If the answer is no, you've written a reminder, not an action item.

The teams that consistently close the loop tend to include the same five ingredients. Miss one and the item gets shaky:

• A clear action verb. Send, draft, approve, schedule, fix. Not "look into" or "circle back."
• A specific outcome. Something you could check off without arguing about whether it's done.
• A single named owner. One human being, not a department or "the team."
• A due date. An actual calendar date, not "soon" or "next sprint."
• Where it's tracked. The one place this lives so it can be reviewed later.

That last one gets skipped constantly, and it's the quiet killer. An action item with a perfect verb, owner, and date still dies if it's written in a doc nobody reopens. Decide where these live before you start capturing them.

Three bad-vs-good rewrites

The difference between a dead action item and a live one is usually a handful of words. Here are three pairs pulled from the kinds of vague lines that show up in real meeting notes, rewritten so they'd actually move.

Before: "Follow up with the client."

Follow up about what? Which client? By when, and who's doing it? This is the most common non-action-item in existence.

After: "Dana will email Acme a revised proposal with the new pricing tier by Thursday June 25."

Now there's an owner, a verb, an outcome you can verify, and a date. Anyone reading the notes knows what "done" looks like.

Before: "We should improve onboarding."

"We" owns nothing, "should" commits to nothing, and "improve onboarding" could mean fifty different things. This is a goal, not a task.

After: "Raj will draft a one-page onboarding checklist and share it in the #product channel by Monday June 29."

A goal got broken into a first physical action with a name attached. Big ambitions still need a small, specific next step to start moving.

Before: "Team to review the contract."

When a whole team owns something, everyone assumes someone else has it. Diffused ownership is how items rot.

After: "Marcus will review the vendor contract and flag any blockers in the deal channel by Tuesday June 30."

One owner, and the outcome is a visible artifact, the flagged blockers, so you'll know it happened.

Tip: Assign one owner, never a group. If an action item is owned by "marketing" or "the three of us," it's effectively owned by no one. Name a single person, even for shared work. They can pull in collaborators, but they're the one who reports back on it. Unambiguous ownership by one individual, not a team, is one of the five core elements every effective action item shares.

The two places action items die

Strip away the details and almost every dropped action item fails at one of exactly two points. Knowing which one is killing yours tells you what to fix.

Failure point one: it gets said but never written. Someone commits to something out loud, the room moves on, and the words evaporate the moment the call ends. Nobody was assigned to catch it. This is why capturing action items in real time, during the meeting rather than from memory afterward, matters so much. If it isn't written down before people scatter, it didn't happen.

Failure point two: it gets written but never followed up. The item makes it into the notes, the notes get filed, and the doc never gets reopened. Even when teams capture action items well, most lack any mechanism to close the loop, no reminders, no check-in before the due date, no escalation when something's overdue. A written action item that's never revisited is just a more organized way of forgetting.

Most teams obsess over the first failure and ignore the second. But a task that's captured and abandoned is no better off than one that was never written at all. You need to plug both holes, and the second one is mostly a process problem, not a wording problem.

One source of truth, reviewed out loud

Here's the part most "how to run better meetings" advice skips. Where your action items live matters more than how elegantly you phrase them. The research on why items disappear keeps pointing at the same culprit: there's no single source of truth, so tasks get scattered across meeting notes, chat messages, email threads, and individual to-do lists. When an item lives in four half-places, it effectively lives nowhere.

The fix is unglamorous and works. Pick one place, a project tool, a shared doc, a tracker, whatever your team will actually open, and make it the only place action items live. Every item from every meeting goes there with its owner and due date. No exceptions, no "I'll just keep this one in my notebook."

Then add the single most effective habit in this whole article: review open action items out loud at the top of the next meeting. Before you dive into new business, you spend ninety seconds going down the list. Done, done, slipping, why. That one ritual creates the gentle social accountability that reminders never quite manage. People finish things they know they'll be asked about by name in front of the group.

Tip: Phrase it as the next physical action. "Plan the launch" is a project, and projects feel heavy, so they get postponed. Ask instead: what's the very next physical thing someone has to do? Usually it's small, like "book the kickoff call" or "send the brief to design." Writing the action item as that concrete next step, rather than the whole mountain, makes it far more likely to actually get started this week.

A template you can reuse forever

If you remember nothing else, remember this one format. Write every action item as:

[Owner] will [action] by [date].

That's it. The structure does the work for you. You can't write "[Owner]" without picking one person. You can't write "[action]" without a verb and an outcome. You can't write "[date]" without committing to one. The format quietly refuses to let you be vague. A few filled-in examples:

• Priya will send the revised Q3 budget to Finance by Friday June 26.
• Marcus will share the signed vendor contract in the deal channel by Tuesday June 30.
• Dana will book the customer kickoff call by end of day Wednesday June 24.

For routine work that's enough. For anything unusual or high-stakes, add a quick one-line "why" and note where it's tracked, since context helps the owner make smart calls when something gets in the way. But don't let the desire for a perfect format stop you from writing the simple version. A plain "[Owner] will [action] by [date]" captured in the meeting beats a beautifully structured task captured never.

The hardest part of all this isn't the wording. It's catching every commitment as it's spoken without dropping out of the conversation to type. This is where an AI notetaker like Laxis earns its keep: it records and transcribes the meeting, then automatically pulls out the action items with their owners and due dates and syncs them to your notes and CRM, so a task no longer depends on one person remembering to write it down while everyone else keeps talking. It closes that first failure point, the said-but-never-written gap, without anyone having to play scribe.

Stop losing action items to bad notes Laxis joins your Zoom, Meet, or Teams calls, transcribes in 40+ languages, and auto-extracts action items with owners and due dates, then drafts the follow-up and syncs to HubSpot or Salesforce. There's a free plan to start. Try Laxis Free

The bottom line

Notice that almost nothing in here is about being more disciplined or trying harder. The teams that get action items done aren't more virtuous; they've just removed the places where items can slip. A single owner removes the "I thought you had it." A real date removes the "I didn't realize it was urgent." One tracked list reviewed out loud removes the "I forgot we even agreed to that." Discipline is a tax you pay forever. A good system you pay for once.

Frequently asked questions

What is an action item?

An action item is a single, discrete task that came out of a meeting or conversation and needs to be completed. A good one has five parts: a clear action verb, a specific outcome, one named owner, a due date, and a place where it's tracked. "Discuss the budget" isn't an action item. "Priya will send the revised Q3 budget to Finance by Friday June 26" is.

Why don't action items get done?

They usually fail at one of two points: the task is spoken in the meeting but never written down, or it's written down but never followed up on. Vague wording, group ownership instead of a single person, and a missing due date all widen the gap. One industry analysis estimated that roughly three-quarters of meeting action items quietly disappear, largely because they get scattered across notes, chat, and email with no single source of truth.

What is a good action item template?

Use the format "[Owner] will [action] by [date]." For example: "Marcus will share the signed vendor contract in the deal channel by Tuesday June 30." It forces one owner, a concrete verb, a real deadline, and an outcome you can verify. Add a one-line "why" and note where it's tracked when the task is unusual or high-stakes.

Should an action item be assigned to a team or one person?

One person. When a task is assigned to a group, everyone assumes someone else has it and nothing happens. Name a single owner even for shared work; that person can pull in others, but they're the one who reports on it. A clear owner is one of the five core elements of an effective action item.

How quickly should action items be sent after a meeting?

Within 24 hours, while the discussion is still fresh and people remember what they agreed to. The longer the gap, the more detail blurs and the easier it is for an item to be quietly dropped. Sharing the action items, owners, and due dates the same day also gives people a chance to correct anything that was captured wrong.