Most people have too many places where things land. A notebook for meetings, a phone for voice memos, a desktop full of sticky notes, an email inbox doubling as a task list, a “later” folder that never gets opened. When a new thought arrives, it goes wherever is fastest, not wherever makes sense.
The GTD capture step is the fix for this. It is the first of the five steps in David Allen’s Getting Things Done framework — and the one that determines whether everything else works. If your capture system is not trusted, your mind never fully lets go of what it is holding. That background noise — the three things you are trying to remember while in a meeting — is the cost of a capture system that has not earned your trust yet.
The goal of a GTD capture system is to get everything out of your head and into one place you will actually review. Not several places. Not eventually. A single trusted inbox, processed on a reliable cadence.
Why most capture systems fail
The failure mode is not a shortage of capture tools. Most people have too many. Email, a to-do app, a notebook, voice memos, screenshots, shared Slack channels — any of these might catch something on a given day.
The problem is that no single one is fully trusted. You remember making a voice memo but are not sure which project it was under. You wrote something in your notebook last Thursday but did not transfer it. The sticky note is still on the monitor but you stopped reading it two weeks ago.
A capture system fails when you do not trust it. When it does not catch everything, your mind compensates by holding on. The open loops stay in your head because the system has not proven it will catch them. That is the mental noise that follows you into meetings and into family evenings — the same feeling described in the post on stopping feeling overwhelmed at work.
The GTD capture model — one trusted inbox
GTD solves this with a single rule: one capture point, or as few as you can get away with. In practice, this usually means three surfaces that all feed one digital list:
- A physical inbox tray for anything paper-based
- A notebook or phone app for thoughts that arrive away from your desk
- Your email inbox — used as a capture surface only, never as a task manager
The number of capture surfaces matters less than the commitment to reviewing them. A system with two capture points you empty every day beats a system with one theoretical inbox you check when you remember it exists.
This connects directly to the brain dump method — the capture step is essentially a structured, daily version of a brain dump, turned into a habit rather than an occasional rescue operation.
How to set up your GTD capture system
Step 1: Map every current capture point
Write down every place where tasks, ideas, and commitments currently land. Email, notebooks, apps, sticky notes, phone notes, your head. Most people find seven or more. This is not a problem yet — it is a starting inventory.
Step 2: Consolidate to three or fewer
Choose one digital list for incoming items and one physical inbox for paper. Everything else routes to these two, or gets retired. The goal is not minimalism — it is reliability. You need to check them and trust that everything is there.
Step 3: Set a daily collection time
Capture does not work without processing. Decide when you will empty each capture point — ideally once per day. A morning triage works well for most business owners: open the inbox, clear the physical tray, review the digital list, and move everything into the GTD processing workflow before the day starts.
Step 4: Capture immediately, always
The system only earns trust if it catches things before your mind tries to hold them. When something arrives — an idea in a meeting, a task from a call, a commitment made over dinner — it goes into the capture system before you do anything else. Not “I will add it later.” Now, before the conversation ends.
Step 5: Run a weekly mind sweep
Even a reliable capture system misses things, because some thoughts arrive too slowly to trigger an immediate capture action. The GTD weekly review includes a mind sweep: a deliberate pass through every area of your life and work to surface anything that did not make it into the inbox. The sweep is the safety net that keeps the system complete.
Capture and processing are two separate steps
One of the most common capture system mistakes is processing at the point of capture. You write something down, immediately start thinking about what to do with it, and end up either making a decision on incomplete information or spending ten minutes on something that should take thirty seconds.
GTD separates these deliberately. Capture is writing it down. Processing happens later, in a dedicated block, when you apply the five decisions (Do, Defer, Delegate, Drop, Diary) to everything in the inbox at once. The two work better apart because capture needs to be frictionless and processing needs to be deliberate.
Keep a capture session to under ten seconds per item. If you are writing more than a sentence, you are already processing — and you are slowing down the capture habit enough that it will eventually break. The processing step, covered in depth through the GTD context lists and natural planning model, is where the real decisions happen.
Where GTD capture fits in the full system
Capture feeds every other step in GTD. The context lists stay current because the capture system routes items into them. The someday/maybe list gets ideas from the capture step that are not actionable now but worth revisiting. The weekly review only works if the inbox is complete enough to trust.
If you are comparing GTD against other frameworks, the full GTD vs Building a Second Brain comparison covers how the capture step differs between the two approaches — and why that difference matters for business owners who need action over archive.
Using Claude to support your GTD capture system
Claude sits most usefully inside the processing step, not the capture step itself. Capture should be fast enough that pulling up an AI model introduces friction rather than removing it.
The processing pass is where Claude earns its place. Feed it your full inbox alongside your open projects and current commitments, and ask it to flag anything that appears to be missing a next action, anything that conflicts with a current project, or anything that should be escalated before your weekly review. This is the pattern in the post on giving Claude a job, not a question — handing it the full picture rather than isolated queries.
The weekly mind sweep also works well with Claude. After you have done the sweep manually, hand the output to Claude and ask it to cross-reference against your project list and calendar for anything you may have missed. It holds the full context; you provide the human judgment about what actually matters.
What changes when the capture system is trusted
The shift is not dramatic. One day you notice that you are no longer reciting a mental list while trying to pay attention to your children. Another day you notice that a client call ended and you captured the three actions before you even closed your laptop.
That is what a trusted capture system produces — not more productivity, but less of the background processing that costs attention when you have not budgeted it. The open loops close because there is somewhere reliable for them to go. That reliability is also what the NP System is built around: a framework where the capture step is the entry point for everything else, so strategic work can get the attention it actually deserves.
Frequently asked questions about GTD capture
What is GTD capture?
GTD capture is the first step in David Allen’s Getting Things Done framework. It means collecting every task, idea, commitment, and open loop from your head and environment into a trusted external inbox before processing it. The goal is to ensure your mind can fully release what it was holding.
How many capture points should you have in GTD?
GTD recommends as few capture points as possible — ideally one physical inbox for paper-based items and one digital inbox for everything else. The number matters less than whether you trust each capture point enough to review it daily and empty it consistently.
What is the difference between capture and processing in GTD?
Capture is writing something down. Processing is deciding what it means and what to do with it. GTD keeps these deliberately separate — capture is designed to be fast (under ten seconds per item) while processing happens in a dedicated block using the five Ds triage method.
How often should you empty your GTD capture system?
Daily processing is the GTD standard. Each capture point should be reviewed and emptied at least once per day, feeding everything into the processing workflow. A weekly mind sweep during the GTD weekly review catches anything that did not trigger an immediate capture action during the week.
Can you use Claude AI with a GTD capture system?
Claude is most useful at the processing stage, not the capture stage itself. Feed it your full inbox alongside your open projects and ask it to flag missing next actions, project conflicts, or escalations. The weekly mind sweep is another strong use case — Claude cross-references your sweep output against your project list for anything missed.
If this is the first time you have looked at the GTD framework seriously, the NP System walks through how capture, processing, planning, and execution connect for business owners specifically — including how Claude fits into each phase once the system is in place. The course is free and takes about three hours to work through at your own pace.
