Meeting Action Items
Turn meeting notes into owners, deadlines, and next steps.
A meeting produces two artifacts: decisions and work. Most notes capture the discussion and lose both. The result is a document that feels complete and changes nothing.
Here is a method for extracting the work, whether you are cleaning up your own notes or fixing a team habit.
Start with the two-column rule
Before the meeting, open a note with two headings:
DECISIONS
- ...
ACTIONS
- ...During the meeting, do not try to write prose. Put a line in the relevant column when something is decided or assigned. This one habit eliminates most of the extraction work later.
If the meeting is already over, reconstruct the two columns from the notes you have. Read for verbs, not topics.
The phrases that hide action items
Action items rarely announce themselves. They hide in these patterns:
| Phrase | What it usually means |
|---|---|
| “I'll send…” | Task with an owner and an implicit date |
| “Can you check…” | Request; owner is the person addressed |
| “We need to…” | Task with no owner — the dangerous kind |
| “Someone should…” | Task with no owner and no commitment |
| “Let's circle back” | A decision to defer; needs a date |
| “I'll look into it” | Task with a vague scope and no date |
| “That's on me” | Task with an owner, often no date |
The last three are where follow-up goes to die. They need a name and a date before the meeting ends.
Convert sentences into task rows
A useful action item has four fields:
- Task — starts with a verb.
- Owner — one person, not a team.
- Due — a date, not “soon.”
- Source — the sentence it came from, for context.
For example:
“Priya will send the revised pricing deck by Friday.”
becomes:
| Task | Owner | Due |
|---|---|---|
| Send the revised pricing deck | Priya | Friday |
Note what was removed: “will” and the owner clause. The task starts with the verb. The owner is a separate field, so it can be sorted and filtered.
Handle the three hard cases
No owner. Write “Unassigned” and read the list aloud at the end. The silence after an unassigned item is usually enough to produce a volunteer.
No date. Ask: “When should this be done?” If the answer is “soon,” propose a date. A task without a date is a wish.
Two owners. Split it. Shared ownership is a way to ensure nobody does it.
Separate decisions from actions
A decision is a fact about the future: “We're delaying the launch to November 18.” An action is work: “Alex will update the launch page.”
Mixing them creates two problems. Decisions get re-litigated because nobody can find the record, and actions get lost in the narrative. Keep a separate decisions list, even if it is three bullets.
A decision needs a date and a scope, not an owner. An action needs an owner and a date, not a rationale.
The five-minute close
Before people leave, do this:
- Read the action list aloud.
- Confirm each owner and date.
- Ask: “What did we decide?” and read the decisions list.
- Send the list in the chat within five minutes.
The send is the important part. A list that lives only in your notes is not a commitment; it is a draft.
Automate the extraction, not the judgment
You can paste rough notes into Meeting Action Items and get a table with owners, dates, and decisions. It is good at finding the patterns above and bad at knowing whether an item is real. That judgment stays with you.
The tool is most useful when the notes are already decent. If the notes say “discussed pricing” and nothing else, no extractor can recover the task. The two-column habit is still the highest-leverage change.
A template for the follow-up message
Decisions
- Launch moved to Nov 18.
- Pricing stays at $7.99 for the first 100 customers.
Actions | Task | Owner | Due | | --- | --- | --- | | Send revised pricing deck | Priya | Fri, Nov 13 | | Confirm vendor contract | Alex | Tue, Nov 17 | | Update launch page date | Sam | Mon, Nov 16 |
Reply here if anything is wrong. Otherwise, see you at the next sync.
Short, scannable, and easy to turn into tickets. That is the whole job.