What is a waiting-for list?

The moment you send a request, the next action belongs to someone else. If that item stays on your task list, it does two harmful things: it clutters the list with work you cannot do, and it trains you to skim past items, which is how the ones you can do get skimmed past too. If you delete it instead, you lose track of the promise entirely and only remember it when the deadline has passed.

The waiting-for list is the middle path. It is a named place for open loops that are not yours to close, reviewed on a schedule, so the active list stays short and honest and the delegated work still gets chased.

The idea comes from David Allen’s Getting Things Done, where waiting-for is one of the core lists alongside next actions and projects. It matters more the more you delegate. Managers, executive assistants and anyone whose work is mostly requests to other people will find that a good waiting-for list is most of their job.

• Capture at the moment of handoff. When you send the email or end the call, add the item immediately. Later, you will not remember that you asked.
• Record who, what and when. ‘Waiting on Priya for the contract draft, asked 14 Sept’ is chaseable. ‘Contract’ is not.
• Set a follow-up date. Every item needs a date by which silence becomes a problem. Attach a reminder to it.
• Keep it separate from active tasks. A status, a tag or a dedicated list all work. The point is that it does not appear when you ask what you can do now.
• Review it weekly. The weekly review is where you scan the list, nudge anything overdue and close anything that came back.
• Link the original request. Keeping the email thread attached saves you searching for it when you follow up.
• Convert on return. When the reply arrives, the item becomes a next action for you or gets closed. It should never sit in waiting after the wait is over.

Fluidwave has Waiting as a task status, and it is typed: a task can be waiting on a call, an email, a message or something else. Setting it takes one action from the task, from the E actions menu, or by asking the assistant. There is a separate Delegate status for tasks you hand to the delegation marketplace, so the two kinds of ‘not mine right now’ do not blur.

Because the status is structured rather than a tag, the app can act on it. The Active filter hides every waiting task along with future-dated ones, so your working list is only what you can do. A dedicated jump takes you straight to the waiting view when it is time to chase. Add a reminder to a waiting task and it resurfaces on the follow-up date without you tracking it.

Most waiting-for items begin as email, and Fluidwave keeps that link. When you turn a thread into a task during AI Triage, the thread stays attached, so following up is opening the task and hitting reply. If the task is linked to a contact, the person you are waiting on is right there too.

See task dependencies for the related case of waiting on another task rather than another person.