Keep a Waiting For list with delegation date and expected completion — review weekly to follow up on overdue items
Maintain a separate Waiting For list tracking items delegated to others with delegation date and expected completion date, reviewing it weekly to follow up on overdue items.
Why This Is a Rule
Delegated items occupy a dangerous blind spot in most productivity systems. You've handed off the work, so it's no longer on your action list. But the item is still your responsibility — if the delegate doesn't deliver, you're accountable for the gap. Without a tracking system, delegated items disappear into a cognitive void: you vaguely remember asking someone to do something but can't remember when, what exactly, or when it was supposed to be done.
The Waiting For list externalizes this tracking into a dedicated structure with two critical metadata fields: delegation date (when you handed it off — establishes the timeline and prevents "I'm sure I asked recently" when it's been three weeks) and expected completion date (when you need the result — creates the trigger for follow-up). Together, these fields convert a vague memory ("I think I asked Sarah about that") into a precise tracking record ("Delegated to Sarah on March 5, expected by March 15").
The weekly review cadence ensures nothing falls through the cracks without requiring daily checking. Scanning the Waiting For list weekly takes 2-3 minutes and catches any item past its expected completion date. The follow-up is then a specific, timely, reasonable inquiry rather than a panicked last-minute "Where's that thing I asked for?"
When This Fires
- When delegating any task or request to another person
- During weekly review when checking on delegated items
- When you realize you've been waiting for something but can't remember when you asked or when it was due
- Complements Organize actions by execution context (@computer, @phone, @errands) not by project — you execute based on where you are and what tools are available (context lists) as a parallel tracking system for items you can't act on yourself
Common Failure Mode
Mental tracking of delegated items: "I'll remember to follow up with Sarah." You won't — or you will, but at a random time that's either too early (annoying) or too late (past the deadline). The Waiting For list replaces unreliable mental tracking with systematic external tracking that fires reminders at the right time.
The Protocol
(1) Every time you delegate a task or make a request that requires someone else's action, add it to your Waiting For list with three fields: What (the specific deliverable), Who (the person responsible), Dates (delegation date + expected completion date). (2) During weekly review, scan the entire Waiting For list. For each item: past expected date → follow up today. Approaching expected date → verify it's on track. Well before expected date → no action needed. (3) When following up, reference the specific item and dates: "Hi Sarah, I sent the timeline request on March 5 — are we on track for the March 15 delivery?" (4) When the item is delivered, remove it from the list and process the deliverable. (5) If you find yourself with 20+ items on the Waiting For list, you may be delegating faster than others can deliver — reduce delegation rate or increase follow-up frequency.