Meeting action items forgotten: how to make them stick
Short answer: action items die because they live in notes that nobody opens again. Write each one in the meeting as a single line with an owner and a due date, put it in one shared list, and review that list at the start of the next meeting. Items that stay in the notes get forgotten. Items in a list get seen.
At a glance
Swipe sideways to see all columns.
| Item | Number | What it means for you |
|---|---|---|
| List view threshold | 5,000 items | Views can be blocked when they must read more items than this. Keep views filtered. |
| Items in one list | 30 million | One team list for all meetings will not fill up in practice. |
| File attached to a list item | 250 MB | Notes or slides attached to an action item can be large, but not over this. |
| Unique permissions in one list | 5,000 recommended, 50,000 supported | If some items must be private, keep these item-level permissions few. |
Why action items disappear
A meeting ends with good intent. Everyone agrees on what needs to happen. Then the day fills up. The notes, if there are any, go to a document or an email thread. A week later nobody remembers who said they would do what.
There are four common causes:
- The item has no owner. "We should update the vendor" belongs to everyone, so it belongs to no one.
- The item has no date. Without a date, it is never late, so it is never urgent.
- The item lives in the notes. Notes are for reading once. They are not a to-do list.
- Nobody checks. If the next meeting does not start by looking at the last items, people learn that they do not matter.
Signs this is happening in your team
- The same topic comes up again and again with no result.
- People say "I thought you were doing that."
- Someone writes notes, but the notes are not read.
- The lead keeps a private list and chases people one by one.
Step 1. Write items so they can be done
A good action item is one sentence. It starts with a verb and names a result. Compare these:
- Weak: "Look into the vendor issue."
- Strong: "Call the vendor and get the new delivery date."
Each item needs three parts: what, who and by when. If one part is missing, ask before moving to the next topic. This takes seconds in the meeting and saves days later.
Step 2. Capture items live
Pick one person to type items during the meeting. Do it where everyone can see it, on a shared screen. When the item is on screen, people fix wrong words right away. At the end, read the list out loud. Ask: does everyone agree this is right?
Do not wait until after the meeting to write items down. By then the details are blurry.
Step 3. Keep all items in one list
Do not put items in each meeting's notes. Use one list for the whole team. A SharePoint list works well. It needs only a few columns:
- Item (the one-line action)
- Owner
- Due date
- Status (Open, Done, Dropped)
- Meeting date
One list means you can filter by person, by status or by late items. You do not have to open ten sets of notes to find what is open.
Step 4. Send the list out right away
After the meeting, send a short message with a link to the list, filtered to the items from that meeting. Do not paste the whole notes. A link with a count is enough: "5 new items, 2 are yours."
Step 5. Start the next meeting with the list
Begin every meeting by looking at open items for two to five minutes. For each one, the owner says: done, not done, or needs help. This is the step that makes the rest work. When people know the list will be read aloud, they do the work.
Rules for this review:
- Done items are marked Done and not discussed.
- Late items get a new date or are dropped on purpose.
- If an item has been moved three times, ask whether it still matters.
Step 6. Add a reminder
You can have a reminder sent so people do not rely on memory. A scheduled Power Automate flow can find items due soon or past due and message each owner once a day. Keep it to one message per person. Many messages get ignored. For the full setup, see "Late tasks nobody notices: setting up late alerts".
Make "drop it" an allowed answer
Some items should not be done. Plans change. Give people a way to close an item as Dropped with a short reason. This keeps the list clean and honest. A list full of old items that everyone ignores is as bad as no list.
Honest limits
A list does not make people do the work. It makes the work visible. If a team has too many meetings or too many priorities, items will still slip. Also, if the person typing the notes is also leading the discussion, items get missed. Split those roles when you can. Start with one recurring meeting, not all of them, and fix what does not work before you expand.
When to get help
You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: $5,000 for one, built in 2 weeks. See "What a SharePoint tracker costs". Bring one example of the problem to a free call.
I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.
See trackers I built: Tools I built
FAQ
Updated 2026-10-27.
Who should write down the action items?
One person, chosen at the start of the meeting. Rotate the job so it is fair. The note taker should not also run the meeting if you can avoid it.
How many action items is too many?
If a meeting makes more items than the team can finish before the next one, the topics are probably too big. Split large items into smaller steps, each with one owner.
Can I use Microsoft Teams or Planner instead of a list?
Yes. The tool matters less than the rules: one place, one owner, one date, and a review at the next meeting. Choose what your team already opens each day.
What if people do not update their items?
Review the list out loud at the start of each meeting. Asking "done, not done or needs help" is usually enough to change habits.
Sources
- Microsoft Learn, Get started with triggers in Power Automate
- Microsoft Learn, Limits of automated, scheduled, and instant flows
- Microsoft Support, List View Threshold for large lists and libraries
- Microsoft Learn, SharePoint limits - Service Descriptions