Start with capture, because it never stops. Part 2 had you do one big brain-dump to seed the system. But tasks don’t arrive in one batch; they arrive all day, mid-meeting, mid-shower. And the rule from Part 2 still holds: the moment a commitment lands, it has to get out of your head, or it opens the loop and starts nagging.

Now, you don’t have to give a task its final form the moment you capture it. The catch-point is part of your system, but it’s the front door, not the whole house. When a commitment lands, you drop it in its raw form as it occurred to you, a single line, no project, no impact, no dates. You are not stopping to think; you’re just getting it out of your head so the loop closes. You capture into a catch-point, a fast, temporary holding pen that sits in front of the main system. TaskBeacon calls this the Inbox. Mine is a lightweight list where I jot down just about everything: real tasks, things I’ve handed off to someone else and need to track, whatever crosses my mind. It’s deliberately sloppy, because its only job is to hold the thought until I process it properly later. I don’t stop to decide the task’s project or impact or due date at the moment. That would pull me out of whatever I’m doing, and the whole point is to not get pulled out. I write the line and get back to work.

And it doesn’t matter what form the thought arrives in. Sometimes what pops into your head is a clean, doable task. But just as often it’s a whole project (“Mom’s birthday”), or a project with its first step already attached, or a new task for something, or just a fuzzy idea of a task. All of it goes in the catch-point exactly as it came, unrefined. You do not stop to work out which kind of thing it is, or what the real next action should be, that’s the job of processing, later. Stopping to figure it out now derails you, either you abandon whatever you were doing to chase the new thing, or you stall the capture itself and lose the thought.

You may be thinking, “hey earlier you had said that unclear tasks stay open in your head until you make it specific.” Yes, that is true, thankfully, writing “taxes” in your catch-point genuinely eases your mind even though it’s a vague, unactionable word, because you trust it’s in a queue you’ll process. Your brain files it under “handled, will be dealt with,” and lets it go. But that same word, “taxes,” dropped straight into your live task list as if it were a real task, would do the opposite. Every time you saw it there, sitting among things you’re actually meant to act on, you’d feel the fog of not knowing what to do about it, and you’d drift to something more concrete instead, the exact avoidance we diagnosed back in Part 2. The catch-point relieves you because it’s understood to be raw. The live list only earns that trust once each item has been processed into something you can actually act on. Processing is the bridge between the two.

Entering a task properly, giving it a project, an impact, the shape, takes a few deliberate seconds and a bit of thought, and if you make yourself do that every time something pops up it will become too disruptive to your day and you’ll stop capturing. So you need a catch-point. Notes app, text file, paper, a voice memo to yourself, the tool doesn’t matter. What matters is that capturing is instant and processing happens later, reliably.

There’s another payoff as well. Because I already know my current top priorities, when something new lands in the catch-point, I can tell almost instantly whether it competes with my top tasks at the moment. Most things don’t so they wait in the catch-point for processing. Once in a while something is genuinely more urgent, and I can do it right then and there. But the point is that a new task becomes a two-second triage decision instead of a distraction. In this way, a trusted system doesn’t just surface what to do next; it lets you weigh every interruption against everything else without losing focus.