Gather a few things See what you’ll need
- Notebook
- Pen
- Calendar
- Relevant message or meeting note
Choose an exercise 4 things to try as you read
Separate asking from waiting
Check whether the request was made, acknowledged, and agreed in specific terms. Thinking about asking is still your own next action. GTD materials use a waiting-for list for outstanding dependencies; a community forum discussion distinguishes that overview from a dated follow-up reminder. The list answers what is outstanding, while the reminder tells you when to look.
Compare the optionsFollow the spare-key dependency
Follow the spare-key dependency
Which stage of the exchange is current?
Read the words in this example
- Request not yet made
- Ask Noor for the spare key
- Needed: before Saturday
- Action list / p. 22
The request is still your action.
Do not call an unmade request a wait.
ONE WORKED EXAMPLE
The reply arrived, but not the measurement
You asked a friend for the width of a table you may borrow for a display. A friendly reply arrives, saying they will measure it after work.
Before
The waiting row is crossed out because a message came back, even though you still do not have the width needed to plan the display.
After
“Sam: table width; asked Mon; replied Mon, will measure after work; my check Tue morning; for display layout.” The row stays open. When the measurement arrives, add it to the display notes and mark the wait received. Any fit decision becomes your own next action.
What changed—and what to check
The expected result defines completion. An acknowledgment updates the exchange without being mistaken for the information you requested.
Try this check. Read the expected result beside the received message and check whether the request has actually been fulfilled.
Record enough to recognize the exchange
Write enough to recognize the exchange: “Noor: spare hall key; asked 4 Sep; for Saturday setup; check Thu evening.” Keep an agreed delivery date separate if there is one. Try that full entry before ruling columns: a hanging paragraph may fit a small notebook better, and it needs room for the next agreement or receipt note.
Write your versionWrite a recognizable waiting entry
Write a recognizable waiting entry
Edit the worked example into a note you can use.
Who or what:Noor
Expected result:Spare hall key for Saturday setup
Review point:Asked 4 Sep; check Thu evening
Your words have a place now.
Label your chosen check separately from any delivery date somebody promised.
- Words on this card
- 20
“Receipt and verification are separate finishing points.”
Distinguish a promise from your own check
Label an agreed delivery date as the other person’s expectation and your chosen review date as “check.” Thursday evening might leave time for another arrangement before Saturday setup. Match the interval to the situation: weekly review suits some waits, while others need a dated reminder. A closed notebook cannot alert you, so use a reminder you will actually encounter.
See the differenceKeep a check date distinct from a promise
Keep a check date distinct from a promise
Read the whole example before and after the change. The tinted lines show revised wording.
Tinted lines contain wording that differs between the two examples.
Before — An ambiguous date
- What does Thursday mean?
- Noor / key / Thursday
After — A labelled review
- Two different dates
- Requested: 4 September
- Promised: Thursday collection
- My check: Thursday evening
Read the whole example before and after the change.
An unexplained date can create a false assumption about the agreement. A labelled review point tells you when to look without inventing a promise.
Work through the request and its ending
Imagine you ask Noor on 4 September for Saturday’s spare key. Noor agrees to Thursday collection. Record the agreement and calendar a specific collection time if one is arranged. The item remains outstanding until collected.
Then add “received Thu” and close the wait. If the correct door is still uncertain, add “test key at hall” to your action list. Receipt and verification are separate finishing points.
Use the record to ask a precise question
At review, check whether the result has arrived in another place before asking again. If needed, use the stored context to ask a precise question about the key and Saturday setup. Record the new agreement. Sending that follow-up completes the message action; the key remains outstanding until it arrives or the need changes.
GO A LITTLE FURTHERDecide what would make the entry end
Decide what would make the entry end
After repeated reviews, decide whether the result remains necessary and what alternative exists. A staffed entrance might end the key wait: “cancelled: staff entry arranged.” If the key is still needed, clarify the request, arrange another source, or revise the plan. Replace indefinite “chase” entries with a concrete decision or next action.
GO A LITTLE FURTHERFinish with one live dependency
Finish with one live dependency
Move received and cancelled entries out of the active view while leaving their notes readable. When the page fills, transfer only live dependencies with the person, expected result, and essential dates, then mark the old row moved. The fresh page should show what still needs a result, not every request you have ever made.
Try a what-ifThe arrangement no longer needs the key
The arrangement no longer needs the key
Consider this page before choosing your next move.
The hall now confirms that staff will open the entrance for your setup. The old key request is still on your waiting-for page, but the key is no longer needed for this plan.
Compare the three choices
How should that row end?
- Mark the key received so the row leaves the active list.
That would close the row with an event that did not occur.
- Keep chasing the key because it was originally requested.
The old request can remain part of the record, but following it indefinitely ignores the replacement arrangement.
- Mark it cancelled with “staff entry arranged” as the reason.
The need has been deliberately replaced. This closes the dependency accurately without claiming receipt.
A dependency can end because its need is replaced, as well as because its result arrives.
What would you try?
Choose an option to see what it would do. You can explore all three.
Something for a future page?
The Washi Tape ShopAffiliate links: we may earn a commission if you buy through these links.
Where this idea began
The method references explain the underlying ideas. Community links show the questions and experiences that helped shape this guide; they are not a popularity ranking. The worked examples here are our own.
- Community discussionUnderstanding the Waiting For List
Participants distinguish reviewing an outstanding dependency from scheduling a dated follow-up.
- Practitioner exampleWaiting For Advice
The coach describes tracking delegated or outstanding matters on a Waiting For list and following up when needed.
A personal coaching example, not evidence that others will meet deadlines. The guide’s columns and reminder wording are adaptations.
Source checked 2026-09-05.



