PRODUCTIVITY

Days to result

The Waiting For List

Track every ball in someone else's court so nothing falls through the cracks

delegation accountability tracking follow-up dependencies

Problem it solves

low productivity

Best for

Managers, project coordinators, and anyone who delegates work or depends on others for inputs. Essential for anyone who has experienced the frustration of discovering too late that someone else dropped the ball.

Not ideal for

Solo workers with no dependencies on others. Less critical if you have very few delegated items, though even personal life has Waiting For items (packages ordered, responses from friends, etc.).

Overview

Why this framework exists

The Waiting For List is a deceptively powerful component of the GTD system that tracks every commitment that is currently in someone else's court. Rather than tracking discrete action steps, it captures deliverables, responses, and outcomes you're expecting from others -- the tickets you've ordered from the theater, the scanner arriving for the office, the OK from a client on a proposal, the K-1 tax form expected from a trust company.

Allen considers this one of the most crucial categories to manage in your entire personal system. The Waiting For list should be kept close at hand alongside your own Next Actions lists because responsibility for the next step on any project frequently bounces back and forth between you and others. A call you make (from your Calls list) results in a requested proposal (now on Waiting For). The proposal arrives (reviewed via Read/Review) and is sent to your boss for approval (back on Waiting For). And so on.

Critically, Allen recommends recording the date on everything you hand off to others. The ability to say 'I called and ordered that on March 12' provides accountability and prevents disputes. The list is reviewed during the Weekly Review to assess whether follow-up action is needed -- a nudge email, a status check call, or an escalation to someone else. Without this systematic tracking, delegated items disappear into a black hole of 'I thought someone was handling that.'

Core principles

4 total

Your role with Waiting For items is to review the list regularly and assess whether you need to take follow-up action -- a check-in, a nudge, or an escalation.
Always record the date when you hand something off. This small habit pays enormous dividends in accountability.
Delegation is not always downstream. You might be waiting for input from your boss, a peer, or an external party.
The responsibility for next step bounces between you and others frequently; the Waiting For list tracks whose court the ball is in.

Steps

4 steps

Create your Waiting For list
Set up a dedicated list (in the same system as your Next Actions lists) for tracking everything you're expecting from others. Each entry should include what you're waiting for, from whom, and the date it was delegated or requested.
Pro tipKeep this list in the same system and format as your Next Actions lists so you can review them together during your Weekly Review.
Add items immediately when you delegate or hand off
Every time you delegate a task, request a deliverable, place an order, or make a request of anyone, immediately add it to your Waiting For list with the date. This includes verbal requests, emails, and even casual agreements made in conversation.
Pro tipFormat entries as 'W/F: [deliverable] from [person] - [date]' for quick scanning. Example: 'W/F: Proposal from vendor Smith - 3/12'.
WarningIf you don't capture Waiting For items at the moment of delegation, you'll lose track of them. The moment after delegation is the easiest time to record; waiting even an hour introduces forgetting.
Review during Weekly Review and assess follow-up needs
During your Weekly Review, scan every item on the Waiting For list. For each one, assess: Has it been received (check off)? Is it overdue (follow up)? Is the timeline still reasonable (wait)? Do I need to take alternative action (reassign or escalate)?
Pro tipA simple follow-up email or phone call at the right time can prevent a major crisis later. The Waiting For list gives you the visibility to follow up proactively rather than reactively.
Transfer items back to Next Actions when responsibility returns to you
When a Waiting For item is received, remove it from Waiting For and determine the next action on the broader project. This might create a new item on your Next Actions lists or complete the project entirely.

Checklist

Saved in your browser

Do I have a dedicated Waiting For list separate from my Next Actions?
Am I recording the date of delegation on every Waiting For item?
Am I reviewing the Waiting For list during every Weekly Review?
Am I following up proactively on overdue items rather than waiting for crises?

Examples

2 cases

The tax preparation dependency chain

A professional puts 'do my taxes' through the clarify process and realizes the next action is dependent on receiving the final K-1 form from Acme Trust. He can't proceed until it arrives. Instead of putting 'do taxes' on his Next Actions list (where it would be unpursuable), he writes 'W/F: K-1 from Acme Trust' with today's date on his Waiting For list.

OutcomeDuring his Weekly Review, he notices the K-1 has been outstanding for three weeks. He adds 'Call Acme Trust re K-1 status' to his Calls list. When the K-1 finally arrives, it moves off Waiting For and 'do taxes' becomes an active project with defined next actions.

The project handoff ping-pong

A manager calls a vendor to request a proposal for a piece of work (action from her Calls list). After the call, she adds 'W/F: Proposal from XYZ Vendor - 4/15' to her Waiting For list. When the proposal arrives, she reviews it (Read/Review pile) and sends it to her boss for approval, adding 'W/F: Boss approval on XYZ proposal - 4/22' to Waiting For.

OutcomeAt no point does the project disappear from her system. Whether the ball is in her court (Next Actions) or someone else's (Waiting For), she has visibility and can follow up proactively. The date stamps provide accountability at each handoff.

Common mistakes

3 traps

Tracking Waiting For items on the same list as your own actions

If Waiting For items are mixed with your own Next Actions, you'll constantly be re-scanning items you can't act on, creating frustration and wasted cognitive cycles. Keep them separate but in the same system.

Delegating without recording

Verbal delegation without any tracking is the most common source of dropped balls in organizations. Even a casual 'Could you look into that?' creates an open loop that needs tracking if you care about the outcome.

Never following up on Waiting For items

The list is only useful if reviewed and acted upon. Simply recording items and never checking the list is record-keeping, not management. The value is in the regular follow-up that the review triggers.

Origin story

How this framework came to be

Allen noticed that one of the most common sources of dropped balls in organizations was the gap between delegation and follow-up. People would delegate tasks verbally or via email and then have no systematic way to track whether the work was actually done. The Waiting For list emerged as the simplest possible solution: a single place where every delegated or dependent item is tracked with its date, recipient, and expected deliverable.

Source

Traced to primary

Related frameworks

Browse all Productivity →