Most of us track what we have to do far better than what we are waiting to receive. A waiting-for list fills that gap: a plain record of favours, deliveries, approvals and replies owed to you by other people. First-time list keepers keep asking much the same things, so these are the answers, answered with a bias toward what the evidence of everyday experience suggests actually works.
What exactly is a waiting-for list?
It is a short inventory of requests you have made that depend on somebody else. Each line holds the item, the person or team who owes it, the day you asked and the day you plan to follow up. Nothing else is needed. The value comes from the fact that the list exists outside your head, where it cannot quietly evaporate while you are busy with something louder.
How is it different from a to-do list?
Your to-do list holds jobs within your control. A waiting-for list contains outcomes you do not. The distinction matters because the two fail in different ways. To-do items fail when you procrastinate; waiting items fail when nobody notices the delay. Mixing them hides the second kind of failure, because a line reading “contractor quote” looks like an action you could take, when really it is a reply you cannot hurry without asking.
Why do things stall when we do not track them?
There are three ordinary reasons. First, the sender assumes silence means the other side is working on it. Second, the recipient assumes the sender will chase if it is urgent. Third, both are occupied and the thread slips beneath newer messages. None of these involves bad faith, which is exactly why they are so common. A list interrupts the pattern by giving the sender a calendar-based reason to check, independent of anyone’s mood or memory.
What kinds of things belong on it?
Any item whose next step sits with someone else. Typical entries include:
- A supplier confirming a delivery slot or price.
- A colleague returning feedback on a draft.
- A service provider promising to call back about a booking.
- A refund, deposit or reimbursement you expect to arrive.
- A group decision that you cannot proceed without.
If you are curious how widely these dependencies spread in ordinary business planning, a piece like this overview of working through business technology choices shows how many outside parties a routine project touches before it is finished.
How long should I wait before following up?
There is no universal figure, and a confident universal rule is really a guess. A practical method is to ask yourself, at the moment of sending, how long a reasonable person would take, then add a margin. Record that date as your nudge date. Over time, compare your guesses to what actually happened. If a particular supplier always needs twice your estimate, adjust. The list turns informal impressions into a small body of your own data.
Is it rude to chase people?
Not when it is done plainly. A good follow-up is brief, restates what you need, mentions why the timing matters and invites the recipient to say if something is blocking them. The tone of a reminder is largely a choice. Many people welcome one, because it saves them from the awkwardness of having forgotten. Silence is usually the ruder outcome, since it leaves the other person unaware of a commitment they made.
What if the list gets too long?
A long list is useful information. It tells you that you are depending on many outside parties at once, which is a risk in itself. When it grows, sort by nudge date and attend only to the lines that are due. Close items that no longer matter, and tell the other party if you do. If several lines point at the same person, bundle them into one conversation rather than sending five separate nudges.
Where should I keep it?
In whatever spot you will actually open without being reminded. Some people prefer a paper page folded into a diary; others use a notes app or a two-column spreadsheet. A reasonable test is whether you can add a line in under ten seconds. If adding takes longer, you will skip it on busy days, which are precisely the days it matters. Whichever format you pick, keep one master location rather than scattering lines across several apps.
Can a household or small group share one?
Yes, and it often works better than expected. A shared list for a trip or a home project makes dependencies visible to everyone, so there is less quiet duplication and less “I thought you were handling that”. Keep ownership clear: every line should name one person responsible for the follow-up, even if several are involved in the underlying task. Shared lists that omit owners tend to turn into wish lists.
Planning a longer journey is a good practice ground. A piece such as a travelogue about touring Colombia by motorcycle from city to coast hints at the number of rentals, routes and confirmations that need to arrive before anyone sets off, each a natural candidate for a line.
Does this only apply to work?
Not at all. Large personal projects involve long chains of replies too. Buying a home, for instance, depends on many parties answering at their own pace. A website named Propraahi presents itself as a place for property research aimed at home buyers in India, and anyone using a resource of that kind to plan such a purchase would still benefit from a private record of questions asked and answers still pending. The site itself is simply one example of how many life projects hang on other people’s replies.
What are the usual mistakes?
Four recur. People record the item but not the owner, so they cannot tell whom to chase. They omit the date asked, so lateness is a feeling rather than a fact. They never review, so the list becomes decoration. And they delete lines too early, losing the evidence of how slow a particular channel is. The fix for each is mechanical: add the missing field, set a review time, and keep a short history of closed items.
Should I tell people I keep a list?
You do not have to announce it, but there is no harm in mentioning it when it helps. Saying “I keep track of open requests, so I will check in on Thursday” sets a friendly expectation and gives the other person a date to aim for. Expectations stated early are far more likely to be met than those that exist only in your head. In group settings, describing the habit often prompts others to adopt it, which improves the odds that your own requests are handled promptly.
How much detail is enough?
Enough that you could hand the list to an outsider and they could tell exactly which lines to chase. One line per item is a sensible limit. If a line needs a paragraph of explanation, keep the explanation in the original message and write only a pointer, such as the subject line or the date of the conversation. Short lines are far easier to scan quickly, and scanning speed is what determines whether you actually review the list.
What would a typical week with the list involve?
On Monday you scan the list, pick out lines whose nudge date has arrived and send two or three short messages. During the week you add new lines as requests go out and cross off those that come back. At the end of the week, spend two minutes reading what remains open and ask whether any items deserve a call rather than another email. That is the whole routine, and it rarely takes more than a quarter of an hour in total.
Is there any sign the habit is paying off?
Watch for fewer unpleasant surprises. Once the habit takes hold, you stop discovering late in the day that something you expected never happened. You also begin to notice patterns: certain channels respond fast, certain requests need a phone call, certain deadlines need a longer cushion. Those observations, built from your own entries instead of guesses, are the measurable benefit. If after a month nothing has changed, shorten your nudge intervals or review the list more often.
The short answer to most of these questions is the same. Write down who owes you what and when you will check, then actually check. The rest is detail that you can adjust as you learn how the people and organisations around you tend to behave.

