How to tell when a task should be deleted
Delete a task when it has been rescheduled more than three or four times with no progress, when you cannot remember why you added it, or when nothing would actually happen if it never got done. Keep it if it has a real consequence attached, even if you have been avoiding it. Avoidance is a reason to shrink a task, not delete it.
Not every task deserves to survive
A task list that never loses anything grows heavier every week, since new tasks get added constantly while very few naturally exit on their own. Completion removes some, but a meaningful fraction of any list is made up of tasks that are never going to be completed, only rescheduled, avoided, and rescheduled again. Deleting those is not a failure of the list, it is required maintenance, the same way a garden needs weeding even though nothing did anything wrong by growing. A list that only ever grows is not a more thorough record of your life, it is a slower one to read every time you open it.
The reschedule count is the clearest signal
A task rescheduled once or twice is normal; life is unpredictable and dates get moved for good reasons. A task rescheduled a fourth or fifth time, with no partial progress in between, has demonstrated something: whatever is standing between you and this task is not being solved by giving it a new date. At that point, a fifth reschedule is not meaningfully different from letting it sit overdue. Delete it, or break it into something small enough that the pattern actually breaks, like turning "organize the garage" into "clear one shelf in the garage."
The memory test
Scroll to an old task and ask, honestly, whether you remember why it is there. "Look into new phone plan," added four months ago with no further notes, often fails this test completely: you cannot recall what prompted it, what plan you were considering, or whether the original reason still applies. A task that has lost its own context is rarely worth reconstructing that context for. Delete it; if the underlying need resurfaces, it will be easier to add fresh, with current information, than to revive an old task built on assumptions from months ago.
The consequence test
Ask what specifically happens if this task never gets done, ever. For a genuinely important task, an honest answer produces something concrete and uncomfortable: a bill goes unpaid and accrues fees, a form deadline passes and something is lost, a relationship absorbs a repeated letdown. For a large share of stale tasks, the honest answer is nothing: no one is inconvenienced, no cost accrues, life continues identically either way. A task like "read that article a coworker sent three weeks ago" almost always fails this test. Failing it is permission to delete, not a character flaw. The test works precisely because it asks about a real outcome instead of a feeling of obligation, and obligation is a much weaker signal than an actual consequence.
What avoidance actually indicates, versus irrelevance
It is worth distinguishing a task you are avoiding from a task that does not matter, since they can look identical on the surface: both sit unfinished for weeks. The difference shows up in the consequence test. A phone call you are avoiding because it is uncomfortable, but which has a real outcome attached (a doctor's referral, an overdue bill negotiation), should not be deleted just because it keeps getting pushed. It needs a smaller first step instead, covered in getting past the emotional wall of a dreaded task. A task with no real outcome attached, sitting unfinished purely because it never mattered enough to prioritize, is the one safe to delete.
A worked list of five candidates
Take five old tasks: "learn Spanish," rescheduled six times over a year with zero progress and no memory of a real motivation behind it, delete. "Call insurance about the claim," rescheduled twice, real money involved, keep and shrink to "find the claim number" as a smaller first step. "Organize old photos," three months old, no consequence either way, low emotional charge when considered for deletion, delete. "Reply to landlord about the lease," one week old, real deadline, keep as is. "Try that new recipe," two months old, no consequence, mild wistful feeling but no actual plan, delete, and add it back fresh if you actually plan to cook it soon.
Deleting versus moving to a backlog
Not every task that fails these tests needs outright deletion. Something with genuine long term appeal but no near-term relevance, like a book you want to read eventually, fits better in a backlog than either the daily list or the trash. In Drifta, Backlog exists for exactly this category: tasks that are not urgent enough to earn a place on Daily Tasks or Up Next, but are not nothing either. Reserve actual deletion for tasks that failed the memory test or the consequence test outright, and let the backlog hold anything that only failed the urgency test.
Common questions
What if I feel guilty deleting a task I once thought was important?
The guilt usually fades within a day, and it is a smaller cost than carrying a task that has already proven, through repeated rescheduling, that it is not going to happen. If it turns out to matter later, it can always be added back.
How many times should a task be rescheduled before I consider deleting it?
Three or four reschedules with no actual progress is a reasonable line. At that point the pattern is established: either the task needs to be broken into something smaller, or it does not belong on the list at all.
Is deleting a task the same as giving up on it?
Not usually. Most deleted tasks were never going to happen regardless of whether they stayed on the list, so deleting them just makes that already-true fact visible. A task that genuinely still matters tends to resist deletion, since deleting it produces a flicker of actual concern rather than relief.
This article shares practical organizing ideas. It is not medical advice. For diagnosis or treatment questions, talk with a qualified clinician.