Gather a few things See what you’ll need
- A tray or envelope for incoming paper
- Notebook
- Pen
- Calendar
- A place for reference material
Choose an exercise 4 things to try as you read
GO A LITTLE FURTHERDefine what you are going to examine
Define what you are going to examine
Choose five items or one short page, leaving the rest in its existing inbox. Set that boundary before starting. Bring existing action, calendar, reference, and someday locations within reach. For a trial, a labelled reference envelope may suffice; the items themselves will show what organization they require.
Describe the thing before choosing its destination
Ask what this item represents before choosing its destination. The same blue paper sample might be a choice to make, a color reference, or material you no longer need. Add a few context words if you cannot tell.
One meeting sheet can hold both a measurement and a promise to ask about access. Keep the sheet in a single reference location and extract the available action with a link back, so neither job disappears.
Compare the optionsInspect what happens after capture
Inspect what happens after capture
Which stage of the inbox would you like to see?
Read the words in this example
- Captured, not yet decided
- Blue paper sample
- Call about room access
- Idea: fold-out map
The captures have not yet been assigned roles.
A sample, a question, and an idea can share one temporary inbox.
“Create the destination first: write the action, file the reference, or record the deferred idea.”
ONE WORKED EXAMPLE
One meeting sheet with two jobs
You are processing a meeting note that includes a display measurement and a promise to ask which entrance opens at nine. Both details will matter when setting up next week.
Before
Filing the sheet keeps the measurement but hides the promised question; copying only the question loses the dimensions that explain the display plan.
After
The sheet goes into the display reference folder. Your action list says “Ask hall coordinator which entrance opens at nine — display folder, meeting note.” The original capture is marked with its destinations after the action and reference are actually placed.
What changed—and what to check
Separating the action from its supporting reference makes the next step visible while preserving a route back to the full information.
Try this check. Find the open action from your task list, then follow its reference to the original measurement without searching the inbox.
Turn vague work into something you can begin
Turn “room access?” into a concrete uncertainty: which entrance opens at nine? If unanswered, record “ask hall coordinator which entrance opens at nine,” with the display project reference. If already asked, record the outstanding reply on waiting-for. Completing a quick action during processing is optional; a clear decision and correct placement also finish the processing step.
Write your versionClarify one vague capture
Clarify one vague capture
Edit the worked example into a note you can use.
Original capture:Room access?
Available action:Ask hall coordinator which entrance opens at nine
Destination:Call list p. 24 / hall display
Your words have a place now.
If the request is already sent, record the expected reply as a wait.
- Words on this card
- 22
Give each capture a fitting home
Imagine the blue sample is a future cover’s color reference. Label and file it with cover notes, indexing the location if useful. Put the room-access question on the call list. Save an uncommitted fold-out map idea in someday with its reason.
A duplicate receipt used as scrap can be discarded after checking for information still needed. Each item is processed when its next use no longer depends on rediscovery in the inbox.
Make the destination real
Create the destination first: write the action, file the reference, or record the deferred idea. On a notebook capture, add “action p. 24” or “reference envelope: covers.” Use a processing mark distinct from task completion, or write the destination in words. Processing “call about access” leaves the call open at its action location.
See the differenceKeep processed separate from done
Keep processed separate from done
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 checkmark
- What did this mark mean?
- x Call about access
After — A clear destination
- Processed into action
- Capture → call list p. 24
- Call action: still open
Read the whole example before and after the change.
Processing and completing the work are different events. A destination note preserves the difference.
GO A LITTLE FURTHERRecord the missing decision instead of recirculating it
Record the missing decision instead of recirculating it
If an item keeps returning to the inbox, name the decision or information it still needs. A map sketch might depend on whether the organizer actually wants a printed map. Record that question and keep the sketch in a labeled temporary place.
Give a deliberate deferral a reason and review point. “Later” without either tells you little more than the original pile did.
GO A LITTLE FURTHERCheck placement instead of counting finished tasks
Check placement instead of counting finished tasks
Check the selected five items by destination rather than by completed tasks. Can you find each reference, see each action still open, and explain any deferred decision? Check needed information before discarding anything.
Mark where this processing range ends and leave untouched captures in the existing inbox. The next session can start there without reopening decisions that already have usable homes.
Try a what-ifWhere does the next step belong?
Where does the next step belong?
Check whether the request has actually been made before calling it waiting-for.
An inbox note says “waiting for hall access details,” but you have not yet asked the coordinator. You want the next-use location to reflect what can happen now.
Compare the three choices
Where does the next step belong?
- On the action list as the question to send
There is no outstanding request yet. Record the available action; use waiting-for once a reply is actually owed.
- On waiting-for with today’s date
A date makes the note clearer, but would still imply a request has been made when it has not.
- In reference with the room measurements only
The measurements belong in reference, but filing them does not surface the unanswered question you can now ask.
Waiting-for describes an outstanding response; an unasked question is still an available action.
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
GTD separates capturing information from clarifying and organizing it. The linked inbox discussion also distinguishes deciding about work from completing it.
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 discussionTime to Process the Inbox
The discussion distinguishes deciding what a captured item means from doing every task it contains.
- Method referenceWhat Is GTD?
Clarify whether an input is actionable, identify its next action and any larger project, then organize or retain it appropriately.
Supports the decision sequence shared by next-action and inbox guides; their paper templates and worked examples are editorial.
Source checked 2026-09-05.



