Meeting Action Items Template (Free) — And Why Templates Fail
You searched for a template, so here it is — free, copy-paste, no email gate. But stay for the second half of this post, because the data says the template is not your problem: most action items fail after they're written down, not before.
The template
Copy this into your meeting notes, wiki, or Teams channel. Every row must have all five columns filled in — an action without an owner or a deadline is a wish, not an action.
| Action (specific deliverable) | Owner (one name) | Deadline (date) | Status | Carried from |
|---|---|---|---|---|
| Send revised pricing proposal to Acme | Sarah | Thu 10 Jul | In progress | — |
| Fix staging deploy pipeline | James | Tue 8 Jul | Overdue 4 days | Last week's sync |
| Draft Q3 hiring plan | Mike | Fri 11 Jul | Done | — |
The “Carried from” column is the one most templates miss — and it's the most important. More on that below.
Get the template in your inbox
We'll send you the action-items template — plus one practical accountability tip a month. No spam, unsubscribe anytime.
By subscribing you agree to our privacy policy.
The five rules that make the template work
We call this the SWORD check — run every action item through it before the meeting ends:
Specific
A clear deliverable, not a vague activity. “Send the proposal”, not “look into pricing”.
Who
Exactly one named owner. “The team” owns nothing. Two owners means zero owners.
Output
A testable result — it exists or it doesn't. If you can't verify it, rewrite it.
Realistic deadline
A date (and time if it matters). “ASAP” and “next week” are not deadlines.
Documented publicly
Posted where the whole team can see it — a Teams channel, not a private notebook — within 5 minutes of the meeting ending.
Now the uncomfortable part: why templates fail
Every team that downloads a template does the same thing: uses it diligently for two weeks, then the person maintaining it gets busy, one meeting gets skipped, and the sheet quietly dies. It's not a discipline problem — it's a design problem. The template depends on a human doing four jobs forever:
- Capturing every action during the conversation (while also participating in it)
- Posting it publicly after every single meeting
- Checking last week's sheet before every new meeting
- Chasing the people whose items are overdue — including their own boss
The fourth job is the one nobody does. Chasing peers is socially expensive, so overdue items just… stay overdue. That's why 72% of meeting actions never get completed.
The fix: automate the loop, keep the template
The structure above is exactly right — owner, deadline, status, carried-from. The fix is removing the human from the maintenance loop. Loopion does the four jobs automatically: it joins the meeting, extracts every action with two-pass AI, posts the structured recap into your Teams chat, and — the part no template can do — when the meeting recurs, it reposts everything still outstanding with a days-overdue counter. The “chasing” happens in public, by software, so no person has to be the bad guy.
That's the accountability loop — the template, running itself, forever.