An action item is a commitment, not a topic
“Product launch” is a topic. “Engineering lead publishes release documentation before Friday scheduled rollout” is an action. Write tasks as concrete deliverables.
Capture the minimum useful fields
- Deliverable: what will exist when the task is complete.
- Owner: one person or clearly named team.
- Deadline: only if the meeting actually agreed one.
- Dependency: anything that must happen first.
- Source context: the decision, quote, or visual that explains why the task exists.
Do not invent precision
If nobody agreed a date, leave it open. If ownership was unclear, mark that as unresolved. Fabricated deadlines and assumed owners make meeting records look tidy while making execution worse.
Keep the task beside the decision
A task is easier to execute when the person can recover the decision, constraints, and supporting evidence that produced it. This is especially important weeks later when the original conversation is no longer fresh.
Review actions before the next related meeting
A short action review prevents the same unresolved discussion from consuming another meeting. Search by project, owner, or topic and check what changed since the commitment was made.