Keep a Waiting On List to Stop Chasing Other People
For two weeks in March I tallied every time I checked whether somebody had got back to me. Not the replies themselves, just the checking: opening a thread to see if the designer had sent the file, scrolling to find out whether the invoice...

For two weeks in March I tallied every time I checked whether somebody had got back to me. Not the replies themselves, just the checking: opening a thread to see if the designer had sent the file, scrolling to find out whether the invoice question had been answered, asking a colleague in passing if the legal review had come back. Thirty one checks in ten working days, most of them four to six minutes once you count the re-reading. Around two and a half hours.
Worse than the hours were the three items that fell off entirely. A supplier quote I never chased, which cost us the better price. A reference request that sat for eleven days until the candidate followed up with me, which was embarrassing. And a signature I assumed somebody else was handling. None of those appeared on any list I kept, because none of them was a task I could do. That is the specific hole a waiting on list fills, and almost no productivity system ships with one.
Why your task list cannot hold these items
A task list holds actions you can take. Call the plumber. Write the summary. Each item has a verb that belongs to you. An item like designer has the homepage file has no verb that belongs to you, which is why it either sits at the bottom of the list making you anxious, or gets deleted in a tidying session and then forgotten.
People try three workarounds and all three leak. Leaving the email unread, which works until the inbox has forty unread messages and none of them means anything specific. Flagging or starring, which creates a pile with no dates in it. Or trusting memory, which is fine for two items and fails at six, because the ones you forget are precisely the ones nobody is prompting you about.
The list itself is unremarkable. Four columns: what you are waiting for, who owes it, the date you asked, and the date you will chase. I keep mine as a plain table in the same note as my weekly plan, about eleven items on an average Monday. The format matters far less than the fact that it lives in one place and gets read on a schedule.
Per item reminders are the wrong tool
Standard advice is to set a reminder every time you send a request. Most task apps make this easy and the follow up feature in mail clients exists for exactly this. I did it for about five months and stopped.
Three problems, in order of how much they annoyed me. Each reminder fires on its own, so a single Wednesday brings four interruptions that each break whatever I was doing to chase something that takes ninety seconds. Second, the reminder arrives without context about everything else I am waiting on from the same person, so I send three separate nudges to one colleague in a day, which is irritating for them and makes me look disorganised. Third and most important, individual reminders hide the pattern. You never notice that one vendor takes nine days on average, because you never see their items next to each other.
A single sweep of the whole list twice a week solves all three. I do mine Tuesday and Friday, before lunch, and it takes between six and twelve minutes. Everything owed by the same person goes in one message. Interruptions drop to two a week from roughly nine, and the pattern becomes visible because you are reading all the rows at once.
How long to wait before you chase
Chasing too early makes you the person everyone dreads hearing from, and chasing too late means the thing has already gone cold. These intervals are what has worked for me and they are not research, just a tally of what produced a reply without friction.
| Who owes it | First chase after | Second chase | What to change on the second |
|---|---|---|---|
| Colleague on your team | 2 working days | 4 working days | Switch channel, ask in person or by call |
| Another department | 3 working days | 7 working days | Copy the person who needs the outcome |
| External supplier or client | 5 working days | 10 working days | State what happens if it does not arrive |
| Anything with a fixed deadline | Halfway to the deadline | Two days before | Offer to proceed without it |
| Something you asked as a favour | 7 working days | Do not chase twice | Assume no and find another route |
The last row took me years to accept. A second chase on a favour converts a willing person into an avoidant one, and the real cost is the relationship rather than the item.
Keep the chase message short and name the thing, not the delay. One line about what you need, one line about why the date matters, nothing about how long it has been. Any sentence beginning with the word just makes the message weaker. I use a variation of a dozen words and it works about as well as anything longer.
What the list tells you after a month
The time saving is real but modest. I got back somewhere near two hours a week of checking, which is worth having and is not life changing. The genuinely useful output was the data.
Four things became obvious in my first month. One supplier averaged nine working days to answer anything, so I stopped building plans that assumed four. Two colleagues answered same day every time, which meant I had been padding estimates against them for no reason. A recurring approval step added six days to every project it touched, which turned out to be one person's Thursday batch process rather than any real review. And about a fifth of my items were things nobody had actually agreed to do, where I had sent a request and assumed acceptance.
That last category is the one I would look for first if you try this. An unacknowledged request is not a commitment, and a list makes the gap visible within a week. The fix is usually a single sentence asking for a date rather than agreement, which also gives you something to put in the fourth column.
Where this intersects with the rest of a week is in planning. Once you can see that an approval reliably costs six days, you stop promising delivery dates that depend on it arriving in two. That is the same discipline as a calendar audit, applied to dependencies instead of meetings, and the two together explain most of the gap between the week you planned and the week you had.
Starting it without building a system
Do not install anything. Open the note you already use for your week, write four column headings, and spend ten minutes filling it from your sent mail over the last fortnight. Most people find between eight and fifteen items, and two or three they had genuinely lost.
Then put the sweep in your calendar as a recurring twelve minute block, twice a week, at a time you are already at a keyboard and not in deep work. Mine sits just before lunch because the energy for it is low and the interruption cost is low.
Delete rows the moment the thing arrives. A list with completed items in it stops getting read within three weeks, which I know because mine died that way the first time I tried this in 2021. The second attempt survived because I kept it short enough to read in one glance, and because I stopped using it for anything other than things owed to me by other people. If your problem is that too much is owed by you rather than to you, that is a different problem, and the scripts in our piece on turning down extra work are the better place to start. More on the planning side sits in the time management section.
FAQ
How is this different from a project tracker?
A tracker holds the whole project including your own work. The waiting on list holds only items blocked on someone else, which is what makes it short enough to read in thirty seconds and useful enough to read twice a week.
What if my team already uses a shared board?
Keep the personal list anyway. Plenty of the things you wait for never reach a board: an answer in a thread, a verbal yes, a document someone promised in a corridor. Those are the ones that go missing.
Does this work if people ignore chases?
It does not make anyone reply, but it turns a vague feeling into evidence. After a month you can say a specific step takes nine days on average, which is a far better conversation than saying things feel slow.
How many items is too many?
Past about twenty the list stops being read. If you are consistently above that, the issue is usually that you are the coordination point for too many threads, and the answer is fewer open requests rather than better tracking.
More in Time Management
Time Management
How to Manage Your Time on a Rotating Shift Schedule
The first time I tried to help someone plan around shift work, I made a fool of myself.
Time Management
Parkinson's Law and How Shorter Deadlines Get Work Done
You gave yourself the whole afternoon to write a two page report, and somehow it took the whole afternoon.
Time Management
Pareto Principle for Time Management Without Guesswork
You finish another full week, every hour accounted for, and still feel like nothing important moved.