From meeting notes to tasks: a simple action-item workflow
Action items get lost between the notes and the task tracker. Capture them in one format, move them within a day, and link the task back to the meeting.
On this page
Key takeaways
- Use one action-item format: action, owner, due date, link.
- Move items into the tracker within a day, with a link back to the notes.
- Check automated task creation by hand at first.
- Review last meeting’s items at the start of the next one.
One format for every action item
An action item that names a person and a date can move into any tracker. One that says “look into pricing” cannot. Agree on a format and use it in every meeting.
| Field | Example | Why |
|---|---|---|
| Action | Send revised proposal | Starts with a verb, so it is clearly a task |
| Owner | Priya | One person, not a team |
| Due | Nov 12 | A date, not “soon” |
| Link | Meeting notes URL | Context for whoever picks it up |
Move items within a day
Whoever took notes moves action items into the team’s tracker the same day, with a link back to the notes. If your note-taker can create tasks automatically, check the first few by hand to make sure owners and dates came through.
Close the loop next meeting
Start the next meeting by reviewing last time’s action items. Atlassian’s meeting notes template, like most, keeps a section for exactly this.
Frequently asked questions
Should action items live in the notes or the tracker?
Both: written in the notes, tracked in the tracker, linked to each other.
What if an item has two owners?
Pick one person who is accountable and mention the other in the task.
