Track What You're Waiting On
You delegated the report, ordered the part, asked accounting about the invoice — and now all of it floats in mental limbo. Delegated tasks vanish not because people are lazy but because nobody tracks them. The waiting-for list is the GTD fix: one list of everything you are expecting from others, reviewed regularly. This guide sets it up.
TL;DR / Quick Fix
Quick fix: a waiting-for list tracks everything you delegated or are expecting — who owes what, by when — reviewed every few days. Delegated tasks vanish because nobody tracks them, not because people are lazy. One list, one review rhythm, and follow-ups stop falling through the cracks.
Follow these steps
- Create the list. One note or page titled Waiting For. It sits with your task lists, not in your head — every delegated item, expected delivery, and promised callback lands here the moment it leaves your hands. The GTD basics count it among the core lists.
- Record who, what, and when. Each entry needs three things: who owes it, what exactly, and when you expect it. 'Report — Ana — Friday' beats 'waiting on report' — the specifics are what make follow-ups possible.
- Add the date you asked. Note when you delegated it. Two weeks of silence hits differently when you can see the request is fourteen days old — the date turns vague worry into a clear nudge.
- Review every few days. Scan the list two or three times a week. Anything overdue gets a polite follow-up; anything due soon gets a mental note. The review is the entire mechanism — an unreviewed list is decoration.
- Follow up once, then escalate. One friendly reminder is normal; a second silence is information. After two nudges with no response, escalate: call instead of email, or find another path — the list told you early enough to reroute.
- Delete when delivered. Remove entries the moment they arrive. A clean list stays trustworthy; a list full of completed items trains you to ignore it — the same discipline as any task list.
What NOT to do
- Do not keep it in your head. 'I will remember to follow up' is exactly how delegated tasks vanish — the list exists because memory does not.
- Do not review it never. A waiting-for list you never check is just a diary of disappointments — the review rhythm is the product.
- Do not nag daily. Follow-ups need spacing — daily pestering burns goodwill; a calm check on a clear rhythm gets answers.
- Do not delegate without a date. 'Whenever you can' means never — every delegation needs an expected date, even a soft one.
Frequently asked questions
How is this different from a task list?
A task list holds things you must do. A waiting-for list holds things others must do that you are tracking — different owner, different list, reviewed together.
What if someone keeps missing deadlines?
The list gives you data: a pattern of misses means the problem is the person or the process, not your memory. Reassign, renegotiate, or escalate with evidence.
Should I share the list with my team?
The list is your tracking tool, but sharing relevant entries ('just checking on the report due Friday') is exactly how follow-ups should sound — casual, specific, dated.