Some tasks can’t be worked on right now, and pretending otherwise just clutters your view with things you’re powerless to act on or just don’t make sense to do right now. But you still need to capture them; otherwise you’ll keep turning them over in your head, wondering whether it’s finally the right time to write them down. Two different situations put a task in this state, and both are worth recording, because a recorded “not yet” is a task the system can keep out of your face until it’s ready.
The first is a dependency: one task can’t start until another finishes. You can’t fill out your tax return until you’ve collected your W-2s. You can’t submit it until you’ve filled it out. Record that “fill out return” waits on “collect W-2s,” and your system can help you hide it until the W-2s are in hand. No more looking at a task you can’t even start yet.
Some apps support task dependencies, and if they do they should be able to filter out tasks that are still blocked by another task. If not, and if you are using a paper based method, I recommend only writing down the next step, and leaving a breadcrumb of what you think the next task will be once the current task is complete.
The second timing facet is the start date: the task isn’t blocked by other work, it’s blocked by the calendar. Take “collect W-2s” itself, there’s no point seeing it in November, the forms won’t exist until late January. So you give it a start date of, say, February 1st, and it stays out of sight until then. It’s not that you’re scheduling when you’ll do it, you’re recording the earliest moment it could be done, so it doesn’t nag you for the three months it’s impossible. Notice that one task, “collect W-2s,” is doing both jobs at once: it’s blocked by a date, and it’s the blocker for the task after it. That’s normal. Eligibility chains like this happen all the time. A start date can also just buy someone time: “follow up with Sam on the report” might get a start date three days out, since Sam needs a few days to actually review it before a nudge makes sense. Both do the same job from your side of things: they answer “can I even work on this yet?” with “not until X,” where X is either another task complete or a date. Everything that isn’t eligible gets to disappear until it is. When your system can handle this well you can add every task you can think of without worrying about cluttering up your system with things you can’t start right now.
Most apps don’t support start dates, so one workaround is to use a tag for the date the task can start. Then all you need to do is search for that tag (eg #2026-11-03 on November 11, 2026) and mark those tasks as unblocked. Apps that support this feature out of the box certainly make the process easier.
If you are going with a paper system, or don’t want to use tags to track start date, I suggest you keep a calendar and write tasks on the date they can start. That way you can just review your calendar each day and copy them over to your main list on the day they can start.