List of action items: 25+ examples and the formula that makes them stick

A list of action items is only worth keeping when every line is a single-owner, dated commitment: one named person, an active verb, a specific deliverable, and a real date. That is the whole job. Action items almost never fail because you picked the wrong productivity framework. They fail one step earlier, at capture and assignment: nobody wrote the item down accurately while it was being said, or it got left ownerless and undated, so it quietly died.

So the genuinely best approach is the opposite of what most "action item" advice tells you. Don't start by choosing SMART or Eisenhower or Kanban. Start by capturing the items verbatim as the conversation happens, then attach an owner and a date to each one before anyone leaves the call. Everything below is built around that order. You'll get the formula, a long list of copy-paste examples by meeting type, and the honest version of how to automate capture in Google Meet, Microsoft Teams, and Zoom.

What an action item actually is (and what it is not)

An action item is a discrete task that comes out of a decision or discussion, has exactly one owner, has a due date, and produces a clear outcome. That last part matters: when the item is done, you can point at a thing that exists. A generic to-do has none of those guarantees. The difference between the two is ownership, a deadline, and traceability back to the moment it was agreed (Workamajig, as of 2026-06-12).

The mix-up that wrecks most lists is treating discussions, decisions, and action items as the same thing. They aren't, and keeping them separate is the first real skill here.

A decision is the outcome. An action item is the concrete next step someone takes because of that decision. Following the example above, the decision is "we're pushing the launch to July 14," and the action item is "Priya updates the project plan and notifies the client by Wed Jun 18." A meeting that produces decisions but no action items just produced talk.

The anatomy of a good action item: a copy-paste formula

Every action item that survives follows the same shape. Memorize it and you can write a clean one in five seconds.

Five rules make the formula work:

1. Start with an active verb. Send, draft, confirm, review, schedule, ship. The verb tells the owner what "done" looks like. "Onboarding doc" is not a task; "draft the onboarding doc" is.
2. Exactly one owner. Never a team, never "we," never two names with a slash. Two owners means zero owners, because each assumes the other has it. If two people genuinely have parts, write two items.
3. A real calendar date, not "ASAP." "Soon," "this week," and "when you get a chance" all mean "deprioritized by default." Pick a date. If you don't know the right one, ask in the meeting; that conversation is itself useful.
4. One sentence, one deliverable. If an item has an "and" doing heavy lifting ("draft the deck and send it to the client and book the review"), split it. Each piece can be blocked or finished independently.
5. Add the why when there's a trade-off. The context line lets the owner make smart calls when the task hits a snag, instead of guessing or stalling.

Here is the same item before and after the formula:

Before:  Follow up with the client about pricing.
After:   Dana emails the client the updated pricing
         tiers by Thu Jun 19, flagging that the
         enterprise tier price changed.

Before:  We should fix the signup bug.
After:   Raj patches the duplicate-charge bug on
         signup and deploys to staging by Mon Jun 23.

Before:  Look into the new vendor.
After:   Lena books a 30-min demo with the new vendor
         and shares notes in the project doc by Fri Jun 20.

A real list of action items: 25+ examples by meeting type

This is the part you came for. Every example is written in the formula, so each line doubles as a template you can edit. Swap the names, deliverables, and dates.

Project kickoff meeting

- Priya circulates the finalized project charter to all
  stakeholders by Wed Jun 18.
- Marcus sets up the shared project folder and invites the
  team by end of day Jun 17.
- Aisha drafts the RACI chart for the first phase and posts
  it for review by Fri Jun 20.
- Tom confirms the kickoff budget figure with finance by
  Tue Jun 17.
- Priya schedules the weekly status meeting series through
  launch by Thu Jun 19.
- Jordan writes the project risks list (top 5) and shares
  it in the kickoff doc by Mon Jun 23.

Client or sales call

- Dana sends the recap email with the revised pricing tiers
  to the client by Thu Jun 19.
- Sam drafts the SOW reflecting the agreed scope and routes
  it to legal by Fri Jun 20.
- Dana books the technical deep-dive with the client's IT
  lead for the week of Jun 23.
- Sam shares the 3 customer references the client asked for
  by Wed Jun 18.
- Dana confirms the client's procurement timeline and logs
  it in the CRM by Tue Jun 17.
- Sam updates the proposal to remove the onboarding line
  item per the client's request by Thu Jun 19.

Team standup or status meeting

- Raj unblocks the staging deploy by getting the new API key
  from ops by noon Jun 17.
- Lena reviews the open PR on the billing service by end of
  day Jun 17.
- Marcus moves the three stale tickets to "won't do" and
  notes why in each by Jun 18.
- Aisha pairs with Tom on the failing test suite Thu morning
  and reports back at Friday standup.
- Jordan updates the sprint board so it matches reality
  before the Jun 20 demo.

Manager 1:1

- Sam shares the promotion criteria doc with the report by
  Fri Jun 20.
- Lena drafts a development goal for Q3 and brings it to the
  next 1:1 on Jun 27.
- The manager (Dana) intros the report to the design lead
  for a mentorship chat by Jun 24.
- Lena blocks two hours of focus time on the shared calendar
  starting Jun 18.
- Dana raises the report's tooling request with IT and
  reports the answer by Jun 23.

Board or leadership meeting

- The CFO (Tom) circulates the revised Q3 forecast to the
  board by Mon Jun 23.
- Priya drafts the hiring plan for the next two quarters and
  shares it ahead of the July board meeting.
- Dana prepares the customer-churn deep-dive for the next
  session by Jul 10.
- Tom confirms the audit firm engagement and emails the
  board the timeline by Jun 25.

Notice the pattern across all of them: a name leads every line, a verb follows, the deliverable is concrete, and there's a date you could put on a calendar. If you want a fill-in-the-blank version to reuse every meeting, the action items template and the meeting action items template give you the columns; this list gives you the wording.

Why most action-item lists fail (it's capture, not the framework)

Here's the part that contradicts most of what gets written about action items. The internet is full of advice that says the fix is a productivity system: run your list through SMART, sort it with the Eisenhower matrix, manage it in Kanban or GTD. Those are fine. SMART itself is older than most people realize, introduced by George T. Doran in a 1981 Management Review article as Specific, Measurable, Assignable, Realistic, Time-related (Project Smart, as of 2026-06-12). But every one of them is a downstream execution system. They operate on a list that already exists. They do nothing if the list was never captured correctly in the first place.

And that is exactly where lists die. Three failure points, in order of how often they bite:

• The item was never written down accurately. You were participating in the meeting (which is your actual job), so you half-caught the commitment, or you trusted your memory. The exact wording, the owner, and the conditions agreed in the room are all gone by the time you sit down to write notes.
• The item has no owner. It got assigned to "the team" or to "we," which means nobody. Diffusion of responsibility does the rest.
• The item has no date. "ASAP" sorts to the bottom of every list forever.

How to capture action items automatically in your meeting platform

The three big platforms all have a native AI feature that pulls action items out of a meeting. They genuinely work. The catch, in every case, is that they're paid and locked to one ecosystem, which is worth knowing before you assume your team already has this.

• Google Meet (Gemini "Take notes for me"). It generates meeting notes with a Summary, Decisions, a Next steps section that "lists the actionable items and assigned tasks," and Details. The notes doc saves to the organizer's Drive and attaches to the Calendar event. It needs an eligible Google Workspace subscription, handles one language at a time (no mixed-language meetings), and is recommended for meetings of 15 minutes to 8 hours (Google Meet Help, as of 2026-06-12).
• Microsoft Teams (Recap + intelligent recap). The Recap bundles the recording, transcript, files, notes, a custom summary, and follow-up tasks; Copilot can generate follow-up tasks from the main action items and suggest who to assign each to, which you can edit first. Intelligent recap (the part that produces those tasks) requires a Teams Premium add-on or a Microsoft 365 Copilot license, and the AI notes and tasks expire per your org's retention policy (Microsoft Support, as of 2026-06-12).
• Zoom (AI Companion). Its Meeting Summary builds a post-meeting recap from the transcript that includes topics, key points, and action items, delivered to the host afterward to share with participants (Zoom, as of 2026-06-12).

The honest read: each of these only captures inside its own walls. If your week runs across Google Meet, Teams, and Zoom (most people's do), you're either paying three vendors or you're locked to one.

A platform-independent way to capture and assign

This is where a dedicated notetaker earns its place, and it's the one spot where I'll point at our own. Scribbl records, transcribes, and summarizes Google Meet from your browser with no bot joining the call, and it auto-extracts the action items into the summary so the list is captured verbatim while you stay present in the conversation. Because it isn't tied to a single platform's paid AI add-on, the desktop app adds Zoom and Microsoft Teams too, so you capture the same way no matter where the meeting lives. It's free for individuals, and you can see the tiers on the pricing page.

To be clear about what this does and doesn't solve: automatic capture fixes the first and biggest failure (the item never got written down accurately). It does not, on its own, fix ownerless or undated items. You still have to do the human part. Which brings us to the loop.

From list to done: a lightweight tracking loop

A captured list is the start, not the finish. The loop that actually moves items to done is short and unglamorous.

Two habits make the loop hold. First, keep one running list per project or client relationship rather than re-deriving it from scratch each meeting; that running list is also your record of who delivered and who didn't. Second, when you assign, delegate cleanly: a clear owner, a clear deliverable, and the authority to do it. If you want the deeper version of either, see how to delegate tasks effectively and action item tracking. For getting the capture itself right, how to take better meeting notes covers the rest of the recap, not just the tasks.

Frequently asked questions

What is an action item versus a to-do?

An action item comes out of a specific meeting decision or discussion, names exactly one owner, has a due date, and produces a clear outcome you can point at when it's done. A to-do is any task on a personal list with none of those guarantees. The traceability (it's tied to a decision the group made) and the single named owner are what separate the two.

How many action items should a meeting produce?

There's no magic number, but a useful gut check: a healthy hour-long working meeting usually produces somewhere between two and seven action items. Zero means you held a discussion that didn't commit anyone to anything. Twenty means you're either logging every passing comment as a task or the meeting should have been three meetings. If a meeting reliably produces zero action items, it might not need to be a meeting.

Can I just use Google Meet, Teams, or Zoom's built-in AI to capture action items?

Often, yes, and they do a decent job inside their own platform. The two things to check: each one is gated behind a paid tier (an eligible Google Workspace edition for Gemini, Teams Premium or Microsoft 365 Copilot for Teams intelligent recap, a paid Zoom plan for AI Companion), and each only works inside its own ecosystem. If your meetings span more than one platform, a platform-independent notetaker keeps the capture consistent. See Google Meet AI note taker for the Meet-specific walkthrough.

Should action items go in the meeting notes or in a separate tool?

Both, in sequence. Capture them in the notes (or have them captured for you) so they're tied to the discussion and decision that produced them. Then push them into wherever your team actually does work: the task manager, the ticket queue, the project board. Notes are the record; the task tool is the execution. The failure mode is leaving them only in a notes doc nobody reopens. For pairing tasks with the rest of the record, see the meeting minutes format with action items.

What's the single most common mistake when writing action items?

Leaving an item ownerless or assigning it to "the team." A task owned by everyone is owned by no one, and it's the first thing to slip. The fix is mechanical: every line starts with one person's name. If two people genuinely share the work, write two items with two owners. Pair that with a real date (never "ASAP"), and you've eliminated the two causes behind most dropped action items.