Most meetings produce one of two things: action items that move the work forward, or vague intentions that quietly evaporate. The difference comes down to how the action items are written, who owns them, and where they get tracked. This guide covers exactly what an action item is, how to write one that actually gets done, four real-world examples, three copy-and-paste templates, and the tracking systems that turn meeting decisions into shipped work.
Table of contents
- Key takeaways
- What is an action item?
- Why action items matter
- What every action item must include
- Action items vs tasks vs to-dos vs meeting notes
- 4 real examples of action items
- From a marketing review
- From a sprint planning meeting
- From a 1:1
- From a customer success call
- How to write effective action items
- The SMART framework
- The RACI shortcut for ambiguous ownership
- The formula that always works
- Action verbs that work (and ones that don't)
- Lock action items in during the meeting
- 3 ready-to-use action item templates
- 1. One-line format (for chat or quick recap)
- 2. Table format (for project tracking)
- 3. Email recap with action items section
- How to track action items so they actually get done
- One source of truth
- Update rhythm
- Deadline reminders
- Carry-over policy
- Close-out criteria
- Action item tracking tools: a quick guide
- 5 common action item mistakes
- Frequently asked questions
- What's the difference between an action item and a task?
- Should every action item have a deadline?
- Where should action items be tracked?
- Can AI generate action items automatically from a meeting?
- How many action items per meeting is too many?
- How do you assign an action item if no one volunteers?
- Conclusion
Key takeaways
An action item is a concrete deliverable with one owner and one deadline — anything missing those isn't an action item, it's a conversation.
The SMART framework keeps action items specific; RACI clarifies ownership when more than one person is involved.
Use the formula [Action verb] + [Specific deliverable] + [By date] to write any action item in under 10 seconds.
Tracking is where most teams fail — a single source of truth and a weekly review rhythm matter more than any individual tool.
What is an action item?
An action item is a specific, time-bound piece of work assigned to a single person during or after a meeting. It exists to convert a discussion into something measurable. "We should improve onboarding" is a goal. "Aisha will draft the new onboarding email sequence by May 15" is an action item.
Why action items matter
Action items are the only part of a meeting that survives the meeting. The discussion happens, opinions are exchanged, and a week later nobody remembers exactly what was said — but if Aisha had a clear deliverable due Wednesday, that work either got done or became a visible problem. Without action items, a meeting was just a conversation; with them, a meeting was a unit of work.
What every action item must include
Three required fields. Skip one and the action item starts to drift:
The task — written as a specific verb plus a concrete deliverable. "Draft the onboarding email sequence" beats "work on onboarding" by a mile.
The owner — exactly one named person. "The marketing team" or "Mike and Sarah" is shared accountability, which in practice means no accountability. Pick a single person; if it's truly a team task, that person owns coordination.
The deadline — a specific date. "Soon," "next week," and "ASAP" don't count.
Two optional but useful fields:
Status — Not started / In progress / Blocked / Done. Lets a tracker show progress at a glance.
Priority or success criteria — for high-stakes items, define what "done" looks like. ("Onboarding email sequence" is vague — "5-email sequence covering signup → first value → upgrade prompt, ready for review by May 15" isn't.)
Action items vs tasks vs to-dos vs meeting notes
These four terms get used interchangeably and shouldn't be:
Term |
What it is |
Owner |
Lives where |
|---|---|---|---|
Action item |
A deliverable assigned in a meeting |
One named person |
Meeting recap + tracker |
Task |
Any discrete unit of work, with or without a meeting |
Usually assigned |
Project tool (Jira, Asana, Linear) |
To-do |
Personal reminder for the writer |
Self only |
Notes app, sticky note |
Meeting notes |
The full record of what was discussed |
Note-taker |
Doc, wiki, AI summary |
An action item is a type of task — specifically, one that came out of a meeting and has accountability attached. Most teams blur the distinction; the ones that ship reliably keep them clear.
4 real examples of action items
Examples are the fastest way to learn the difference between vague and clear:
From a marketing review
Sarah Patel — Run an A/B test on the new ad creative against the original — by May 23.
Mike Chen — Pull 3-year Q3 seasonality data for the conversion baseline — by May 12.
Aisha Rahman — Draft the revised performance dashboard with new attribution model — by May 19.
From a sprint planning meeting
James Liu — Break down ENG-441 (search relevance) into estimates — by Tuesday standup.
Aisha Rahman — Confirm with QA the test plan for the new checkout flow — by Wednesday.
The whole team — Update Jira sprint board with story points before sprint kickoff Thursday — owner: Mike Chen.
From a 1:1
Manager — Send connection intro to the senior PM in the analytics team — by Friday.
Report — Submit the updated career framework draft for review — by next 1:1.
From a customer success call
Account Manager — Send Acme Corp the proposed Q3 expansion pricing — by May 14.
Solutions Engineer — Document the custom SSO setup as a runbook — by May 16.
Acme Corp (Sarah, internal champion) — Confirm budget approval with their CFO — by May 21.
Notice the pattern: every line is one verb, one specific deliverable, one owner, one date.
How to write effective action items
The SMART framework
Borrowed from goal-setting, SMART works just as well for action items:
Specific — exactly what is the deliverable?
Measurable — how will we know it's done?
Assignable — who owns it (singular)?
Relevant — does this advance the meeting's goal?
Time-bound — by when?
The RACI shortcut for ambiguous ownership
When more than one person is involved, RACI keeps roles clear:
Responsible — does the work.
Accountable — owns the outcome (one person only).
Consulted — provides input.
Informed — kept in the loop.
For most action items, you only need to identify the Accountable person — that's the named owner. RACI is most useful when an action item involves three or more people and roles get fuzzy.
The formula that always works
If you take nothing else from this guide, take this:
[Owner] — [Action verb] [Specific deliverable] — by [Date]
Every effective action item fits that format. "Aisha — Draft the onboarding email sequence — by May 15." Done.
Action verbs that work (and ones that don't)
Use specific verbs that imply a deliverable:
Producing something: Draft, Write, Build, Create, Design, Develop, Prototype.
Reviewing or deciding: Review, Approve, Validate, Confirm, Sign-off.
Communicating: Send, Email, Schedule, Notify, Brief, Document.
Investigating: Audit, Analyze, Benchmark, Test, Measure.
Implementing: Deploy, Launch, Migrate, Roll out, Implement.
Avoid these vague phrases — they almost guarantee no progress:
"Look into…" — into what, producing what?
"Explore…" — same problem, fuzzier.
"Circle back on…" — defers without committing.
"Dig deeper…" — no deliverable.
"Think about…" — that's not an action item, that's a thought.
"Have a conversation with…" — name the outcome, not the medium.
If a vague phrase is what comes out of the meeting, push for the deliverable: "What does 'looking into the pricing model' produce, and by when?"
Lock action items in during the meeting
The single highest-leverage habit in meeting hygiene: don't end a meeting without reading the action items aloud. The note-taker reads each one — owner, task, deadline — and the room confirms or corrects. Three minutes at the end saves hours of follow-up confusion.
3 ready-to-use action item templates
1. One-line format (for chat or quick recap)
[Owner] — [Verb] [Deliverable] — by [Date] [Owner] — [Verb] [Deliverable] — by [Date] [Owner] — [Verb] [Deliverable] — by [Date]
2. Table format (for project tracking)
| # | Task | Owner | Deadline | Status | Priority | |----|-----------------------------------|----------------|-------------|--------------|----------| | 1 | [Task description] | [Name] | [Date] | Not started | High | | 2 | [Task description] | [Name] | [Date] | In progress | Medium | | 3 | [Task description] | [Name] | [Date] | Blocked | Low |
3. Email recap with action items section
Subject: [Meeting] action items — [Date]Hi team,
Quick recap from today. Action items below — please confirm by EOD if any of yours need adjusting.
ACTION ITEMS
- [Owner] — [Verb] [Deliverable] — by [Date]
- [Owner] — [Verb] [Deliverable] — by [Date]
- [Owner] — [Verb] [Deliverable] — by [Date]
DECISIONS
- [Decision 1]
- [Decision 2]
Next check-in: [Date / time]
Thanks, [Your name]
How to track action items so they actually get done
One source of truth
Pick one place where every action item lives, and use it consistently. The most common failure mode is action items scattered across email threads, Slack messages, and three different docs — at which point the question "what did we decide last week?" becomes unanswerable.
Update rhythm
Build a weekly cadence: 5 minutes at the end of every team meeting to review open action items — what's on track, what's slipped, what's blocked. Without a rhythm, the tracker becomes a graveyard.
Deadline reminders
Use whatever automation your tracker offers. Asana sends reminders the day before; Linear shows overdue items in red; even a Google Sheet with conditional formatting works. The point is not to rely on humans remembering dates.
Carry-over policy
When a deadline slips (and some always will), pick one of three responses: re-commit with a new date, kill the action item if it's no longer relevant, or escalate if it's blocked. Never let an item drift with no decision — that's how trackers rot.
Close-out criteria
Decide explicitly when an action item is "done." For deliverables, "done" usually means "approved by the requester." For investigations, "done" means "summary shared." Vague close-out is how items linger as "in progress" forever.
Action item tracking tools: a quick guide
Pick the simplest tool that does the job. Most teams over-tool action items.
Spreadsheet (Excel, Google Sheets) — perfect for teams up to about 20 people. Easy to set up, no learning curve, infinitely customizable.
Project management tools (Asana, Trello, Notion, Linear, Jira, ClickUp) — necessary once you have multiple cross-team projects, dependencies, or want better notifications and views. Notion is good for documentation-first teams; Linear and Jira lean toward engineering; Asana and Trello sit in the middle.
AI meeting tools — automatically extract action items from a recorded meeting and write them to your tracker. Handy for recurring sync-heavy roles, less useful if your tracker already has the right rhythm. See our breakdown of AI meeting note takers if this is the route you'd like to take.
When to upgrade from a spreadsheet to a project tool: when items are crossing teams, when you need automatic notifications, or when you've outgrown a single shared sheet (more than ~30 active items at a time).
5 common action item mistakes
Vague language. "Investigate the pricing issue" produces nothing. "Submit a 1-page recommendation on price-elasticity for our top 3 SKUs" produces a deliverable.
No single owner. "Marketing will handle it" means nobody handles it. Assign one person.
No deadline (or a fake one). "ASAP" is not a deadline. Pick a date.
Tracked in too many places. One source of truth, always. Slack mentions and email threads don't count as tracking.
Never closed. Action items should reach a definitive state — done, killed, or escalated. Items stuck in "in progress" for three weeks are a process failure.
Frequently asked questions
What's the difference between an action item and a task?
An action item is a task that came out of a meeting and has explicit accountability — owner and deadline — attached. Every action item is a task; not every task is an action item. Tasks live in your project tool; action items show up there too, but they specifically connect back to a meeting decision.
Should every action item have a deadline?
Yes. An action item without a deadline is a wish. If a deadline is genuinely uncertain, agree on a date by which the deadline itself will be set — that's still time-bound, just one level removed.
Where should action items be tracked?
One place, consistently. For small teams, a single Google Sheet or Notion table works. For larger or cross-functional teams, use your existing project tool (Asana, Linear, Jira) so action items live alongside other work. The specific tool matters less than the discipline of one source of truth.
Can AI generate action items automatically from a meeting?
Yes. Modern AI meeting tools extract action items with task, owner, and deadline (when stated). Recall is around 70–80% on clearly stated items. Always review the AI's output before publishing — names, deadlines, and owners are the three fields most likely to be wrong.
How many action items per meeting is too many?
For a typical 60-minute team meeting, 3–7 action items is healthy. More than 10 usually means the meeting was trying to do too much, or items are too granular. If a meeting routinely produces 15+ items, the underlying problem is meeting design, not action-item discipline.
How do you assign an action item if no one volunteers?
The chair assigns it. Silence is not consent — if a meeting closes a discussion without a named owner, the action will not happen. The chair's job is to break the silence: "OK, I'll put this on Mike's plate unless someone else wants it." Mike either accepts or proposes a different owner. Never let a silence become an unowned action item.
Conclusion
Action items are the unit of measurement for whether a meeting was worth holding. The recipe is simple — verb, deliverable, owner, deadline — but the discipline is what's hard. Use the templates above, lock items in before the meeting ends, and review them weekly. Most teams that ship reliably are not running better meetings; they're running better action items.