GTD Inbox Setup: A Step-by-Step Guide (2026)

A GTD inbox is the single holding area where every unprocessed thought, paper, and request lands before you decide what it is and what to do with it. A setup that actually gets emptied has three parts: a small set of capture points, a fixed processing routine, and a daily cadence that drains the inbox back toward zero. This walkthrough covers all three, in order.

For the broader method this sits inside, see our guide on Getting Things Done digital.

What is a GTD inbox, and why do most setups fail?

A GTD inbox is the capture bucket from David Allen's Getting Things Done method: one designated place where every unprocessed input lands until you clarify it. Most setups fail for a single reason. The inbox quietly turns into storage. Items sit for weeks, the pile grows, and processing it starts to feel like a project of its own.

The inbox has exactly one job: hold things between the moment you notice them and the moment you decide what they mean. In Allen's five-stage model (capture, clarify, organize, reflect, engage), the inbox only covers the first stage. When items skip clarification, the inbox becomes a guilt pile, and the trusted system collapses because you stop believing anything inside it will ever be handled.

How many GTD capture points do I actually need?

Two to four. Allen's rule of thumb is as few in-baskets as you can get by with and as many as you genuinely need. Every capture point beyond four adds a processing obligation you will eventually skip, and a skipped inbox is a broken inbox.

A working set for most knowledge workers:

Capture point	What lands there	How it empties
Physical tray	Mail, receipts, printed papers	Daily sort into action or reference
Pocket notebook	Ideas away from screens	Transcribed during the daily window
Email inbox	Requests, attachments, decisions	Tasks extracted, thread archived
Voice capture app	Thoughts on the move	Auto-filed or waiting in the digital inbox

One rule binds them all: every capture point must empty into the same processing routine. A capture point that never gets emptied is not a GTD capture inbox. It is a landfill with good intentions.

How do I process a GTD inbox instead of just filling it?

Process top-down, one item at a time, and never put an item back. For each item ask two questions: what is this, and is it actionable? The answers route the item into one of five exits, and the item leaves the inbox through exactly one of them.

1. Clarify. Name what the item actually is. "Something about the lease" is not clarified. "Decide whether to renew the office lease by October" is.
2. Trash or incubate. Not actionable? Delete it, file it as reference, or park it on a someday maybe list.
3. Do it now. Actionable and under two minutes? Reply, confirm, sign, done. The two-minute rule is the highest-throughput exit in the whole system.
4. Delegate. Actionable but not yours? Hand it to the right person and set a follow-up reminder.
5. Defer with a next step. Actionable, yours, longer than two minutes? Attach the next physical action and file it under its project.

The sequence matters more than the speed. Clarify always comes first, because every other decision depends on knowing what the thing is. Skipping straight to scheduling is how unclarified items end up on your calendar as vague dread.

What cadence gets a GTD inbox to zero?

One daily window of 10 to 15 minutes, plus a weekly review of 30 to 60 minutes. The daily window handles new arrivals through the processing sequence. The weekly review handles drift: stale next steps, dead projects, capture points that stopped emptying. Daily keeps the inbox empty; weekly keeps the whole system trustworthy.

Put the daily window on the calendar like a meeting. Late afternoon works well because the day's captures have landed and nothing new is likely to arrive before morning. The rule inside the window is simple: process top to bottom, never skip, never re-sort by mood. If you want the AI-assisted version of this daily ritual, where a router files most items before you ever see them, our playbook on inbox zero with AI covers the thresholds and timing.

Should voice capture be one of my GTD inboxes?

Yes, if you think faster than you type, which most people do. Voice is currently the lowest-friction entry point into a GTD capture inbox: a thought goes from your head into the system in two to four seconds, hands-free, before it evaporates. The faster capture gets, the fewer thoughts you carry around unprocessed, and carrying thoughts is exactly what the inbox exists to prevent.

This is the use case quik.md is built around. You speak a thought, and the AI files it into the right project with a next step written, or parks it in a calm inbox when it is not sure. Browser speech recognition and a daily AI-organize allowance are on the free plan, so a voice inbox costs nothing to try. Because everything exports as markdown, your GTD inbox stays portable if you ever switch tools. The AI inbox use case page walks through the routing behavior, and our pillar on AI task managers compares how different tools handle the same capture-to-clarify loop.

A voice inbox does not replace the daily processing window. It fills the inbox faster, which makes the cadence more important, not less.

How do I know my GTD inbox setup is working?

Three signals tell you the setup holds. First, the daily window takes 15 minutes or less most days. Second, you stop re-reading items you already processed, because you trust the exits they took. Third, thoughts stop following you home, because capture is cheap enough that nothing lingers in your head waiting for a keyboard.

Two signals tell you it is breaking. If the daily window regularly exceeds 20 minutes, your capture volume has outgrown your processing time and something needs to shrink, usually the number of capture points. If the backlog is more than two days deep, declare a reset: archive everything older than 30 days into a reference folder and restart the daily window today. Genuinely important items resurface on their own. The rest were never going to get done, and the archive keeps them findable without keeping them loud.

FAQ

What goes in a GTD inbox?

Anything you have not decided about yet: ideas, requests, papers, voice notes, emails that need a decision. The GTD inbox holds unprocessed inputs, not tasks. Once you have clarified what an item is and what the next action is, it leaves the inbox and goes to a project list, a calendar, a reference file, or the trash.

How often should I empty my GTD inbox?

Daily. One focused window of 10 to 15 minutes is enough for most people once the processing sequence becomes automatic. The count does not need to hit zero every night, but nothing should sit in the inbox longer than about 48 hours. Past that point, the inbox starts behaving like storage and trust in the system erodes.

Can I have more than one GTD inbox?

Yes, but keep the total between two and four. David Allen's rule is as few in-baskets as you can get by with and as many as you genuinely need. A physical tray, a notebook, an email inbox, and one digital capture app is a workable set. Every capture point beyond four is a processing obligation you will eventually skip.

What is the difference between a GTD inbox and a to-do list?

A GTD inbox holds things you have not decided about yet. A to-do list holds decisions you have already made. The inbox answers the question what is this; the list answers the question what should I do next. Mixing the two forces you to re-decide every item every time you glance at it, which is where the mental fatigue comes from.

Does GTD inbox setup work with digital tools only?

Yes. GTD predates smartphones, but the method is tool-agnostic. A digital-only setup works if it preserves the two properties that matter: capture is fast enough that you never hold a thought in your head, and every capture point empties into one processing routine. Voice capture apps are currently the fastest digital entry point.

Related reads

• Inbox zero with AI: a 2026 playbook that holds
• Getting Things Done digital
• The AI inbox use case
• AI task managers: the pillar guide

References

• What is GTD?, Getting Things Done, David Allen's official site.
• Getting Things Done, David Allen, 2001.
• Inbox Zero series, Merlin Mann, 43 Folders, 2006.