Resource
Meeting Action Items Template
Copy a meeting action items template that turns AI notes into owners, dates, blockers, source links, and next checks.
- Focus
- AI Meeting Notes
A meeting action items template is useful only if it prevents vague commitments.
AI meeting notes often produce action lists that look clean but still fail in practice. "Follow up with client" is not an action item. A useful action item says who owns it, what they will do, when it is due, and where the source context lives.
Use this template after you review the meeting summary template, not before.
Copyable action items template
| Owner | Action | Due date | Source context | Status | Next check |
|---|---|---|---|---|---|
| [Name] | [Specific verb + deliverable] | [Date] | [Timestamp, note link, or decision line] | [Not started / in progress / blocked / done] | [When and where this will be checked] |
| [Name] | [Specific verb + deliverable] | [Date] | [Timestamp, note link, or decision line] | [Not started / in progress / blocked / done] | [When and where this will be checked] |
The two fields most teams skip are "source context" and "next check." Those fields are what keep the action list from becoming another forgotten meeting note.
Plain text version
Meeting: [meeting name]
Date: [date]
Action list owner: [name]
Action items:
1. [Owner] will [specific action] by [date].
Source: [timestamp, note link, or decision line]
Next check: [channel, meeting, or date]
2. [Owner] will [specific action] by [date].
Source: [timestamp, note link, or decision line]
Next check: [channel, meeting, or date]
Blocked items:
- [Owner] is blocked by [dependency]. Next step: [what must happen].
Not action items:
- [Discussion point that does not require action.]
- [Decision already made, no follow-up needed.]
The "not action items" section looks odd at first, but it helps. AI tools often turn decisions, ideas, and open questions into tasks. Separating them keeps the list honest.
What counts as an action item
| Meeting note | Action item? | Rewrite |
|---|---|---|
| "We should update the onboarding doc." | Not yet | "Maya will update the onboarding doc checklist by Friday." |
| "Customer asked about SSO." | Only if someone must reply | "Alex will send the SSO support note to Jordan by Tuesday." |
| "Decision: keep launch date." | No | Record it under decisions, not tasks. |
| "Need design approval." | Yes, if an owner is named | "Priya will get final design approval from Lee by Thursday." |
AI prompt for extracting action items
Paste a reviewed meeting transcript, AI notes, or meeting summary under this prompt.
Extract only real action items from these meeting notes.
Rules:
- Do not invent owners.
- Do not invent due dates.
- Do not turn decisions into tasks.
- If an owner or date is missing, mark it as "needs confirmation."
- Keep each action item specific enough that someone can complete it without rereading the transcript.
Return this format:
Owner | Action | Due date | Source context | Needs confirmation?
Meeting notes:
[paste notes here]
This prompt is strict on purpose. If the AI cannot find an owner or date, that is not a failure. It is the signal that the team needs to clarify the commitment.
Review rules
Before you paste action items into a task tool:
- Delete anything that is only a discussion point.
- Move decisions into the meeting summary.
- Mark missing owners or dates as "needs confirmation."
- Keep source links only when they help someone verify context.
- Assign one person to own the action list itself.
- Send a short follow-up if people outside the meeting need the list.
Best next step
Use the automate meeting follow ups with AI workflow after this action list is reviewed. For a reader-friendly recap, start with the meeting summary template. If the actions need to go out by email, use the meeting follow up email template.
If your AI notes keep missing owners, compare the capture workflow in Fireflies vs Otter before switching tools.