Give dependencies a place of their own
You can finish your part of a task and still be unable to move it forward. Perhaps a colleague needs to review a draft, a client needs to answer a question, or a supplier needs to confirm a delivery. If you leave each handoff in your inbox or try to remember it, you may notice the delay only when the next stage of work is due. A waiting-for list is a small record of work that is currently in someone else’s hands.
The list is not a way to supervise other people. Its purpose is to help you manage your own commitments: what you need back, why it matters, and when it would be useful to check again. Keep it separate from your ordinary task list if that makes the distinction clearer. A task list says what you can act on now; a waiting-for list shows what you cannot complete until something arrives.
Record enough detail to make the next step obvious
For each item, note the person or team you contacted, what you requested, the date you asked, and the project it affects. Add a follow-up date based on when you reasonably need a response, not simply when you hope to receive one. A short entry might read: “Website draft: waiting for Maya’s comments on the introduction; sent Tuesday; check Friday; revise draft after reply.” Use your actual dates in the list so you do not have to work them out later.
A useful entry should answer two questions at a glance: “What am I waiting for?” and “What will I do when I get it?” If a request has a firm deadline, include it. If the reply could arrive through several channels, note where you sent the request so you can find the original message. Avoid copying sensitive details into a shared list unless the people who can see it need that information. A link to the relevant document or message may be enough.
Make adding an item part of the handoff
The easiest time to capture a dependency is just after you send the request. Before moving to another task, add a line to your waiting-for list. This small habit prevents a common problem: assuming that sending a message is the same as finishing the work. If the request is made in a meeting or conversation, record the agreement afterward, including who will provide what. When the expectation is unclear, a brief confirmation can help both people work from the same understanding.
Keep the tool simple enough that you will actually use it. A note, spreadsheet, or task app can all work. You do not need a separate entry for every casual question. Include items whose absence could hold up a project, affect a commitment, or require a follow-up. If you are waiting on several pieces from one person, you can group them under a project as long as each needed response remains easy to see.
Review the list and follow up with context
A waiting-for list helps only if you look at it. Choose a review rhythm that fits your work, such as a quick scan at the start of each day and a longer check before planning the week. During the review, look for replies that have already arrived, items whose follow-up dates are approaching, and dependencies that have changed. Close completed entries, update those with new information, and move any work you can now do onto your active task list.
When it is time to follow up, make the message easy to answer. Refer to the original request, state what you need, and explain any relevant timing: “I’m checking on the introduction comments I sent Tuesday. Could you let me know whether you can review them by Friday? I’m planning the next revision.” If that timing no longer works, ask what would be realistic. A clear follow-up is often more useful than a vague “Any update?” and need not suggest that the other person has done something wrong.
Use delays to plan, not just to remind
Not every delay needs another message. Sometimes the better move is to work on a part of the project that does not depend on the reply, adjust your plan, or ask whether another person can provide the missing information. If a dependency repeatedly holds up the same kind of work, consider changing the handoff: request input earlier, specify the decision you need more clearly, or agree on a review window before sending the material.
Start with a few current dependencies rather than trying to reconstruct every unanswered message. Write each one so that a future review will tell you what to do, then check the list at a consistent time. The goal is not to eliminate waiting. It is to keep waiting from becoming invisible, so you can use your attention on work that is ready to move.
