You forget who you’re waiting on until it’s urgent. Ten minutes now means you stop losing outstanding asks and never do a frantic chase-everyone-at-once week again.
| Default follow-up gap | 3 working days |
|---|---|
| List columns | Who, ask, date asked, follow-up date |
| Useful threshold | Around 4+ open asks at once |
| Cognitive basis | Unfinished tasks keep occupying working memory, per the Zeigarnik effect |
1. Start a Waiting On list
Open a plain note or sheet with four columns: Who, What you asked for, Date asked, Follow-up date. Use three working days later as your default follow-up date unless it’s urgent. Example row: Rajesh, PO approval, asked Sep 28, follow up Oct 1.
2. Give your AI assistant the standing rule, once
In a saved prompt or custom instruction, write: ‘Whenever I paste my Waiting On list, tell me which rows are overdue today and draft a one-line follow-up message for each, in my normal tone.’ You only type this once. After that you just paste the list.
3. Make it a two-minute morning habit
Every morning, paste your current list and ask ‘what’s overdue today?’ AI hands back only the rows past their follow-up date, each with a ready-to-send nudge. You’re not re-reading the whole list, just the parts that need action.
4. Send, edit, or snooze each nudge
Send it as is, tweak a line, or tell AI ‘snooze this 3 more days,’ which pushes the follow-up date out. This takes seconds per item since the drafting is already done.
5. Close the loop the moment someone replies
Delete their row immediately, don’t wait for a cleanup session. The list should only ever show things that are genuinely still open, so you can trust it at a glance.
A worked example
Someone juggling three vendor approvals and two client sign-offs, with no reliable way to remember who they’ve already chased.
Before
Waiting On:
– Rajesh, PO approval, asked Sep 28, follow up Oct 1
– Fatima, signed contract, asked Sep 30, follow up Oct 3
– Arjun, budget numbers, asked Oct 2, follow up Oct 7
After
Overdue today (Oct 4):
1. Rajesh — PO approval, 3 days overdue. Nudge: ‘Hi Rajesh, following up on the PO approval I sent Sep 28, any update?’
2. Fatima — signed contract, 1 day overdue. Nudge: ‘Hi Fatima, checking in on the contract, let me know if anything’s unclear.’
Not yet due: Arjun (follow up Oct 7).
Three ways to bend it
For freelancers chasing payment
Swap ‘what you asked for’ for the invoice number and amount. Ask AI to escalate the tone slightly each time a row gets nudged twice, polite the first time, firmer by the third.
For managers tracking delegated work
Track tasks you’ve handed off instead of asks you’ve sent. AI flags who’s overdue on a deliverable and drafts a check-in that asks for status, not just ‘did you do it.’
For recruiters or salespeople
Track candidates or prospects who went quiet after a call. AI drafts a lighter, lower-pressure nudge for these since the relationship is less transactional than an internal approval.
When it goes wrong
AI keeps nudging people who already replied to me.
The list only knows what you tell it, so delete the row the moment you read a reply. Make that deletion part of reading the reply, not a separate step you’ll skip.
The three-day default feels wrong for some things.
Change it per row. Use one day for urgent approvals, a week or more for vendors who are always slow. The list doesn’t need one rule, just a date in that column.
When not to use this
If you’re only ever waiting on one or two things at a time, or your email client’s built-in snooze and reminder features already work for you, skip this. The list earns its keep once you have enough open threads, usually four or more, that you genuinely can’t hold them in your head. Below that, a system is just more overhead than the problem it solves.
What you can now do
You stop losing track of what you’re waiting on, and follow-ups happen from a calm two-minute check instead of a guilty, scattered scramble.
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
- Open a note or sheet right now and add four columns: Who, What you asked for, Date asked, Follow-up date.
- Write one standing instruction for your AI assistant telling it to flag overdue rows and draft a one-line nudge for each, then save it so you never retype it.
- Paste your list each morning and ask what’s overdue today instead of rereading every row.
- Delete a row the instant you read a reply, folding it into the act of reading rather than a separate cleanup task.
- Set the follow-up date per row based on urgency, a day for pressing approvals, a week or more for slow vendors, rather than applying one fixed default.
Questions people actually ask
How do I get AI to remind me who still owes me a reply?
Keep a simple list with four columns: who you asked, what you asked for, the date you asked, and a follow-up date. Save a standing instruction telling your AI assistant to flag overdue rows and draft a one-line nudge for each whenever you paste that list. After that it’s just a daily paste and a glance at what’s due.
What should I put in a waiting on list?
Four columns cover it: who you’re waiting on, what you asked them for, the date you asked, and a follow-up date you choose. The follow-up date doesn’t need one universal rule, a day for urgent approvals, a week for slow vendors. Keep rows only for things that are genuinely still open, and remove anything once it’s resolved.
How often should I check in on things I’m waiting for?
Once a day is enough. Paste your current list into your AI assistant each morning and ask what’s overdue, and it will return only the rows past their follow-up date along with a ready-to-send nudge for each. That keeps you from rereading the whole list and lets you act on just the handful that actually need attention today.
Do I need this if my email already has snooze and reminders?
Not necessarily. If your inbox’s built-in snooze or reminder tools already surface what you’re waiting on, adding a separate list is extra overhead with no real payoff. This approach starts earning its keep once you’re juggling roughly four or more open asks at once, enough that you can no longer hold them all in your head.
What do I do after someone finally replies?
Delete their row the moment you read the reply rather than waiting for a cleanup pass later. Treat removal as part of reading the message, not a separate chore you’ll likely skip. Skipping this step is the main way these lists go wrong, since the list only knows what you’ve told it and will keep nudging people who’ve already answered.
Sources
- Understanding Claude’s personalization featuresAnthropic (Claude Support)
- Zeigarnik effectWikipedia
What happens next
Expect assistants like Claude and ChatGPT to keep expanding native, account-wide memory and standing instructions, which could eventually let a tracker like this live inside the chat itself rather than requiring a manual paste each morning. Watch whether email clients fold AI-drafted follow-ups into their existing snooze and reminder tools, since that would shrink the gap this workaround currently fills. If that happens, a manual Waiting On list stays most useful for people juggling asks across tools that don’t talk to each other.
