Meeting field guide
Write meeting summaries with action items people can execute
A useful meeting summary separates what the group discussed from what it decided and what each person agreed to do. Action items should be specific enough to execute without replaying the call, but they should never contain an owner, date, or commitment that was not actually established.
What belongs in a meeting summary with action items?
Include a short outcome, confirmed decisions, and a separate action list. Each action should contain one concrete deliverable, one accountable owner, a due date when agreed, and enough context to begin. Put unresolved ownership or timing in an open-questions section.
Separate discussion, decisions, and actions
The three layers are related, but substituting one for another creates confusion.
Discussion explains the options, evidence, and objections that shaped the result. A decision states what the group approved. An action item describes a concrete step someone will take. Keep these in different sections so a reader cannot mistake an idea for authorization.
A decision may require several actions, or none at all. Conversely, a research task can be assigned before any final decision. Preserve these relationships instead of forcing every sentence into a generic bullet list.
- Discussion: the relevant context and alternatives.
- Decision: the approved direction or explicit status.
- Action: a concrete next step.
- Open question: information or authority still missing.
- Checkpoint: when progress or the decision will be reviewed.
Use a precise action-item formula
A task becomes executable when the deliverable, owner, timing, and context are clear.
Start with a verb and describe one observable result. Name a single owner rather than ‘the team.’ Add a due date only when it was agreed or subsequently confirmed. Include a dependency when the owner cannot begin or finish without another input.
Split compound tasks. ‘Update the proposal and get legal approval and send it to the customer’ hides three different handoffs. Separate them so each owner and dependency can be tracked.
- Action: revise the onboarding checklist.
- Owner: Maya.
- Due: Friday, if that date was agreed.
- Dependency: final security language from legal.
- Evidence of completion: approved checklist linked in the project record.
Review AI-extracted actions for intent and attribution
Models are good at finding task-like language, but task-like language is not always a commitment.
Phrases such as ‘we should,’ ‘someone could,’ and ‘I can look at that’ require context. Check whether the speaker accepted ownership, whether another participant later changed the plan, and whether the date was definite or merely suggested.
When information is absent, keep it absent. ‘Owner to be assigned’ and ‘deadline not agreed’ are useful outcomes because they expose a coordination gap. A confident guess hides that gap and can create false accountability.
- Confirm the correct speaker received the task.
- Check that the task survived later discussion.
- Convert relative dates only after confirming the calendar date.
- Do not infer a customer commitment from an internal suggestion.
- Keep a source link for high-impact actions.
Move action items out of the document
A summary is a handoff, not the final task system.
After review, send each action to the place where the team already tracks work. Preserve a link to the meeting context and avoid creating duplicates when an existing ticket already covers the task.
At the next meeting, review open actions before generating a fresh list. Close completed items, reassign work explicitly, and keep unresolved decisions visible. This turns summaries into continuity rather than a growing archive of forgotten notes.
- Publish the checked summary promptly.
- Create or update tasks in the chosen system.
- Notify each owner through the normal workflow.
- Review open actions at the next checkpoint.
- Record changes in owner, due date, or scope.
Questions and answers
What is the difference between a decision and an action item?
A decision states what was approved. An action item states what someone will do next. One decision can produce several actions, and an action can exist before a decision is final.
What if the meeting did not assign an owner?
Mark the item as unassigned and ask the meeting lead to resolve it. Do not assign a person just to make the summary look complete.
Should every action item have a due date?
A date is useful, but it must be agreed or confirmed. If none was stated, record that the deadline is unresolved.
Can AI extract action items from a transcript?
Yes, many tools do, but a reviewer should confirm intent, ownership, dates, and later changes before the list becomes authoritative.
Where should meeting action items be tracked?
Use the task or project system your team already reviews. Link back to the summary or transcript so the owner can recover context.
Sources and further reading
Vendor capabilities can change. Check the linked documentation for the current availability, plan and environment you need.
- Zoom: How to write a meeting summarySource checked:
- Notta: Client meeting summaries and action itemsSource checked:
End meetings with clear ownership, not a longer note.
Separate decisions from tasks, expose missing details, and move reviewed actions into the system where the team works.
Get started