How to write action items in meeting minutes (with examples your team will follow)

TL;DR: Effective action items follow a five-part formula: Owner, verb plus object, deadline, context, and priority. Generic templates alone won't fix your team's follow-through. The real work is translating messy meeting dialogue into concrete deliverables, and 41% of to-do list tasks are never completed. This guide shows real before-and-after rewrites and how AI tools like Granola help surface action items without losing the thread of the conversation.

Most teams leave meetings with a vague list of next steps that no one owns. The problem is not commitment, it's translation. Real meeting dialogue is messy, conditional, and full of implied responsibilities. Converting that dialogue into clear deliverables requires a consistent formula, and in back-to-back meetings, doing that manually means you stop participating in the conversation.

This guide covers the five-part formula, real before-and-after rewrites, where tasks belong in meeting minutes, and how Granola helps you surface them so nothing slips.

What makes an action item actually actionable?

An action item is a specific, assigned task with a deadline. It is not a discussion topic, a strategic observation, or a general next step. Project management standards define action items as clear, unambiguous instructions: Direct about what needs to happen and who is responsible.

The SMART framework captures these requirements: Specific, Measurable, Achievable, Relevant, and Time-bound. Each element prevents a different failure mode. Vague tasks get deprioritized. Tasks without deadlines drift indefinitely.

The 5-part action item formula

Every effective action item contains five components. Miss any one of them and tasks often fall through.

1. Owner: One named individual accountable for the task.
2. Verb plus object: The specific deliverable described with a clear action verb.
3. Deadline: An absolute date, and time where it matters.
4. Context: Why this task exists and what "done" looks like.
5. Priority: Whether this task blocks other work or can wait.

Owner: Single person responsible

Shared ownership is no ownership. When an action item says "Marketing and Sales to align on messaging," both teams assume the other will move first. Assigning one named person, not a team and not a role, creates clear accountability. That person can loop in contributors as needed, but they answer for whether the task gets done.

Verb plus object: Specific deliverable

Action items work as instructions, so they need a verb that triggers immediate action. Review, draft, send, confirm, and schedule are strong starters. Avoid vague verbs without clear outputs. The object defines exactly what gets produced: A revised proposal, a Slack message to finance, a signed contract.

Deadline: When it's due

A task without a deadline is a wish. Deadlines create urgency and allow owners to plan their workload. Format matters too: "ASAP" means different things to different people across different time zones, which is why absolute dates are almost always better.

Context: Why it matters

Context tells the owner why the task exists and what a successful output looks like. Without it, owners either over-engineer the task or deliver something that misses the point. If the action item feeds directly into a board presentation on Friday, the owner needs to know that before they start.

Bad vs good action items: Illustrative examples

Industry data shows 71% of meetings fail to produce meaningful outcomes. One place that gap opens up is at the moment tasks are captured: Vague language, missing owners, and no deadlines turn commitments into noise before anyone leaves the room. The following table shows example meeting language rewritten as properly structured action items using the five-part formula.

The pattern across all five rewrites is the same: Bad action items are captured at the speed of conversation without translation. Good ones apply the five-part formula to what was actually said.

Where do action items go in meeting minutes?

Meeting minutes document organizational decisions and task assignments for the record. Where action items sit within those minutes determines whether anyone reads them. Three placements work well, and each serves a different purpose.

At the top for visibility

Executives scanning minutes after a board meeting or investor call will not read every word. Listing action items at the very top ensures time-pressured readers see their commitments before anything else. This format works well for high-stakes meetings where follow-through determines whether a deal closes or a project moves forward.

In-context within discussion notes

Embedding action items directly under the topic that generated them preserves the reasoning. A reader reviewing notes two weeks later can see exactly why a task was created, not just what the task is. This works well for product roadmap sessions and customer research calls where context shapes how the task gets executed.

Separate action items section

A standalone section at the end of the document makes it easy to copy tasks into a project management tool, a shared Notion page, or a CRM. This format supports weekly task reviews and works well with automation workflows.

How to assign action items correctly

Every task needs one accountable owner. That person can delegate subtasks and pull in contributors, but they answer for whether the task gets done. The RACI model distinguishes between Accountable (the single owner who answers for the outcome) and Responsible (the people who do the work). For meeting minutes, name the Accountable person only. They manage the rest.

In practice: "Dana to draft the messaging brief, with input from Sam and Kenji." The minutes name Dana. Dana decides how to involve the others. This keeps the task record clean without losing the reality that it is a collaborative deliverable.

Setting deadlines that work

Deadlines determine task priority and allow owners to plan their workload. The format matters as much as the date itself.

Absolute dates vs relative dates

Absolute dates display as a specific calendar date and time. Relative dates describe a position relative to now, like "next Friday." For external handoffs and investor commitments, absolute dates help eliminate misinterpretation.

Before next meeting vs specific date

For recurring team meetings, "before next Tuesday's standup" works when the whole team knows the schedule. For tasks that feed into customer deliverables or investor calls, tie the deadline to a specific date and time. If a slipped deadline blocks someone else downstream, use an absolute date.

Time zones for distributed teams

Add an explicit time zone to every deadline for distributed teams. "June 6, 5 PM" means different things in London and San Francisco. A common approach is to standardize on the primary business location's time zone and apply it consistently across all meeting documentation.

Tracking action items between meetings

Writing the action item is step one. Without a tracking system, tasks survive one meeting and disappear before the next.

Review open items at meeting start

Starting every recurring meeting with a five-minute review of outstanding action items from the previous session creates accountability. Owners know they will be asked for an update, which increases the chance the work gets done. It also surfaces blocked tasks early, before they become bottlenecks for the whole team.

Status updates: Done, in progress, blocked

Three statuses cover almost every situation:

• Done: The deliverable exists and was shared with the relevant people.
• In progress: Work is underway and on track for the deadline.
• Blocked: The owner cannot proceed and needs something from the meeting to move forward.

Each status requires a different response: Acknowledge completion, confirm the timeline, or resolve the blocker before the meeting ends.

Rolling over incomplete items

When a task misses its deadline, roll it forward with an updated deadline and a brief note on why it was delayed. This creates a visible history that helps leaders identify patterns. Recurring delays from the same owner often signal a capacity or clarity problem, not poor commitment.

AI-assisted action item extraction with Granola

Back-to-back meetings create a specific problem: The moment you start writing detailed notes, you stop participating in the conversation. You miss the follow-up question that would have changed your understanding of what the customer needed.

Granola is an AI notepad built for people in back-to-back meetings. You jot rough notes during the meeting, and when it ends, Granola enhances those notes using transcript context captured from your device audio. No visible participant joins the call. No "this meeting is being recorded" announcement interrupts the conversation.

"It doesn't disrupt the flow at all. I can keep taking my own notes, and I never have to worry about missing anything important." - Verified user on G2

How your rough notes guide the AI

The human-in-the-loop approach separates Granola from fully automated summaries. When you type "pricing follow-up" in the notepad during a meeting, Granola uses that signal to find every pricing discussion in the transcript and pulls the specific commitments made. Your rough note guides the AI. The transcript provides the context. The result reflects what actually happened, not a generic summary of the whole conversation.

"The follow-up action items are especially useful. Huge time saver." - Verified user on G2

How Granola surfaces assignees, deadlines, and context

Granola's AI-enhanced notes help identify action items from your meetings. After the meeting, open Granola Chat and ask "What were the three action items from this call?" to get source-linked citations from the exact moments in the transcript where commitments were made. For teams using shared folders, you can query across an entire folder: "What action items are still open from this month's board meetings?" Every answer links back to the conversation it came from.

Live example: Meeting transcript to action items

Consider a product roadmap session with three people discussing feature prioritization. Here is how the workflow looks end to end.

• Raw transcript excerpt: "...so I think Marcus needs to pull the usage data from the last quarter before we can make a final call on the notification feature. Can you do that by end of next week, Marcus? Yeah, I can have it Thursday..."
• Rough note jotted during the meeting: "Marcus - usage data for notifications"
• Granola-enhanced action item: Marcus to pull quarterly usage data for the notification feature and share with the product team by June 5 at 5 PM EST, before the prioritization decision is finalized.

Manual vs AI action item quality

Manual note-taking during meetings forces a trade-off: Capture everything and miss the conversation, or stay present and miss the details. Granola removes that trade-off. Because you still jot the rough notes that guide the AI, your judgment about what matters stays in the loop, while Granola fills in the context that would otherwise require you to stop participating.

"What I like best about Granola is how effortlessly it handles meeting notes without disrupting the flow of the conversation... the ability to enhance my quick notes or ask follow-up questions (What were the action items?) is something most competitors don't do as well." - Brahmatheja Reddy M. on G2

For confidential meetings, board sessions, and executive recruiting calls where a visible transcription tool would change the dynamic, Granola's device audio approach captures everything without announcing itself. You can also set up customizable templates and Recipes to pull together action items consistently across all your meeting types.

Action item checklist

Use this checklist to validate every action item before it leaves the meeting:

• One named individual is assigned as owner (not a team or a role)
• The task starts with a clear action verb: Draft, send, review, confirm, or schedule
• The deliverable is specific enough that the owner knows when they are done
• An absolute deadline is set with a date, time, and time zone
• Context explains why the task matters and what it feeds into
• Priority is noted if the task blocks other work
• The task appears in meeting minutes in at least one location: Top summary, in-context notes, or standalone section

Ready to surface action items from your next meeting without losing the thread of the conversation? Try Granola for free. Download the Mac, Windows, or iPhone app, connect your calendar in under five minutes, and let Granola enhance your notes the moment the meeting ends. No bot joins your call.

FAQs

What if no one volunteers for an action item?

The meeting leader assigns it directly or tables the project until someone has capacity. An unassigned action item is not an action item.

How many action items per meeting is too many?

Aim for two to three per person per meeting. If the total list exceeds what the team can realistically review at the next session, the meeting generated more commitments than the team can execute.

Should action items be in the meeting invite?

Meeting invites typically contain the agenda and pre-read materials. Action items belong in the post-meeting notes or follow-up summary so they reflect what was actually decided, not what was planned.

How do I follow up on overdue action items?

Follow up directly with the owner asking for a revised date. Don't wait until the next meeting, because one delayed task can block others from moving forward.

Key terms glossary

Deliverable: The specific output produced when an action item is complete. A deliverable must be concrete enough that both the owner and the stakeholder can confirm it has been produced.

SMART framework: A goal-setting standard where each task is Specific, Measurable, Achievable, Relevant, and Time-bound. In meeting minutes, the framework surfaces the most common failure modes: Vague tasks get deprioritized, tasks without deadlines drift, and tasks without a named owner go unstarted.

RACI: An acronym for Responsible, Accountable, Consulted, and Informed. In the context of action items, the key distinction is between Accountable (the single person who answers for the outcome) and Responsible (the people who do the work). Meeting minutes name the Accountable person only.