The same task has been open for weeks and nobody noticed. Because action items scattered across separate meeting docs quietly die, and this takes ten minutes to fix for good.
| Stale threshold used | 14 days |
|---|---|
| Action items never completed | 44% |
| Owned and dated completion rate | 90% |
| Claude context window | 1 million tokens |
1. Start one running file
Stop creating a fresh notes document for every meeting. Make a single file, in a Google Doc, Notion page, or even a plain text file, and call it ‘Open Items’. This becomes the one place every meeting’s action items land, forever.
2. Log items with date and owner
After each meeting, paste that meeting’s action items at the top of the file with today’s date and who owns each one. For example: ‘8 Oct, Rahul, send revised budget by Friday’. Takes two minutes while the meeting is still fresh in your head.
3. Ask AI to find what’s stuck
Before your next meeting, copy the whole file into an AI assistant and ask: ‘List every item here older than 14 days that isn’t marked done, grouped by owner.’ It will surface exactly what has been quietly sitting there.
4. Raise the stale ones first
Open the meeting with that list instead of waiting for someone to bring it up. Saying ‘the budget item from three weeks ago is still open’ lands very differently than hoping nobody remembers.
5. Mark things done as you close them
The moment an item is finished, write DONE next to it in the file. This keeps the log short and keeps the AI’s answers accurate, since it only knows what you tell it.
A worked example
A product manager runs a weekly sync and used to start a new notes doc every Monday.
Before
Week 1 notes: ‘Backend to fix login bug.’ Week 2 notes (separate doc): ‘Backend still looking at login bug.’ Week 3 notes (another separate doc): ‘Login bug, backend says soon.’ Nobody connected the three.
After
AI scan of the single Open Items file: ‘Login bug fix, owner Backend, first logged 21 days ago, mentioned 3 times, still not marked done. Flag as stale.’ The PM opens the Monday meeting with that line instead of letting it slide a fourth time.
Three ways to bend it
For managers running 1:1s
Keep one Open Items file per direct report instead of per meeting. Before each 1:1, ask AI which commitments from past weeks are still open, so coaching conversations stop repeating themselves.
For freelancers on client calls
Log every client ask in one running file per client. Before each call, ask AI to list anything the client asked for more than 10 days ago that you haven’t delivered, so you raise it before they do.
For teachers after parent meetings
Keep one file of follow ups promised to parents. Before the next meeting with the same family, ask AI what’s still outstanding from last time.
When it goes wrong
The file is getting huge and messy.
Archive anything marked DONE into a separate ‘Closed Items’ file once a month. Keep the live file short so both you and the AI can scan it fast.
AI says something is still open but I actually finished it.
That just means you forgot to mark it DONE. The AI only knows what the file says, so make marking items done part of closing the meeting, not an afterthought.
We already use Jira or Asana for this.
Then use that tool’s own overdue filter instead. This trick is for the lightweight meetings that never make it into a proper tracker in the first place.
When not to use this
If your team already runs every task through a real project tracker with due dates and status fields, this manual log is extra work for no benefit, just use the tracker’s overdue view. This technique is for the in-between meetings, the quick syncs and calls, where nothing formal is tracking commitments at all.
What you can now do
You walk into every meeting already knowing which old promises are still unpaid, instead of finding out the hard way.
Part of Making Life Easier With AI, a weekly walk-through of one small thing AI can take off your plate.
Take this further
Act as a blunt hiring manager who has read ten thousand resumes, not a career coach. I will paste my full resume and the job description I want. Rewrite the whole resume for that role, section by section, in this order: summary, experience, skills, education. Rules: every experience line leads with impact, not duty. Use bracketed placeholders like [8 percent] for any number I did not give you, and list at the end every placeholder I need to replace with a real figure. Keep it to one page of text. Plain formatting only, no tables or columns, so screening software can parse it. After the rewrite, tell me the three weakest claims that need evidence before I send this anywhere. My resume: [paste resume]. The role: [paste job description].
Takeaways
- Create a single ‘Open Items’ file today and stop opening a new notes doc for every meeting.
- Add the date and owner to every action item the moment you log it, not after the fact.
- Before your next meeting, paste the file into an AI assistant and ask for everything older than 14 days that isn’t marked done.
- Write DONE next to an item the second it’s finished, as part of closing the meeting.
- Archive DONE items into a separate ‘Closed Items’ file once a month to keep the live file fast to scan.
Questions people actually ask
How do I get AI to flag action items that are stuck?
Keep every meeting’s action items in one running file instead of separate notes docs, with the date and owner next to each line. Before your next meeting, paste that whole file into an AI assistant and ask it to list anything older than 14 days that is not marked done, grouped by owner, so you walk in already knowing what is overdue.
What should each line in my open items file look like?
Each entry needs three things: the date you logged it, who owns it, and a short description of the task, for example 8 Oct, Rahul, send revised budget by Friday. That format gives an AI assistant enough structure to calculate how old an item is and group overdue items by the person responsible for them.
Will the AI know if I already finished a task?
No, an AI assistant only knows what is written in your file, so if you finish something and forget to note it, the tool will keep flagging it as open. Make writing DONE next to a finished item part of closing out the meeting, not something you plan to do later.
Do I still need this if my team uses Jira or Asana?
Probably not for tracked work. If a task already lives in a project tracker with due dates and status fields, use that tool’s built in overdue filter instead. This running file and AI prompt approach is meant for the informal syncs and quick calls where nothing is being tracked at all.
How big can my open items file get before AI stops handling it well?
Modern AI assistants such as Claude can hold roughly a million tokens of context, equivalent to hundreds of thousands of words, so a single running file of meeting action items is unlikely to hit that limit. Still, archive anything marked DONE into a separate closed items file once a month so the live file stays fast to scan.
Sources
What happens next
Expect AI note taking tools like Granola and Fellow to push this kind of stale item detection further into native features rather than something you prompt for by hand. As context windows keep expanding, like Claude’s roughly one million token window, the running file approach will scale to far more meetings before anyone needs to archive anything. Watch whether teams relying on a lightweight log like this one eventually migrate into a formal tracker once their open items list outgrows a single file.
