A task that rolls over once is normal. A task that rolls over five times is giving you information.

The mistake is assuming it is always telling you the same thing. Sometimes it still matters and the day was too full. Sometimes it is too large. Sometimes it is too vague. Sometimes it is waiting on someone. Sometimes it has died quietly and you are carrying it because deleting it feels like admitting defeat.

This is why I do not think “overdue” is a very useful word for most personal work. It collapses too many different situations into one accusation.

Slate tries to make the question more precise: should this task roll forward, be rewritten, be split, be released, or disappear? Those choices lead to different futures.

The list was never supposed to empty

A to-do list is not a queue. It is a buffer.

New work arrives while old work is still current. Ideas appear before they are useful. Small obligations breed in the corners. Someone says “quick thing” and the afternoon is gone.

The goal is not zero. Zero is pleasant when it happens, but it is not a stable operating model for a working life. The better goal is no rotting tasks.

A rotting task is easy to spot. It has survived several reviews without becoming more true. It has been moved forward enough times that the movement no longer counts as a decision. It still has words, but the words no longer create motion.

That is the task to examine.

Why tasks rot

Tasks rot for ordinary reasons. Capture is easier than completion, so you add faster than you finish. People estimate optimistically, especially when the future is more than a few hours away. A day looks spacious from the night before. A week looks generous from Friday afternoon. Both are unreliable witnesses.

Most systems also have no graceful exit door. They know how to keep a task. They know how to complete a task. They do not know how to say, without drama, this no longer belongs here.

The result is a list that gets longer not because the work is important, but because the system has no way to forget.

A five-question rollover check

When a task keeps surviving the day, I find it useful to ask five questions.

First: is it still real? If the honest answer is no, delete it. You can call this prioritization if that makes you feel more adult, but often it is just deleting.

Second: is it too vague? “Work on deck” is not a task. “Rewrite the first three slides around the pricing argument” is closer. A vague task rolls because it does not give you an edge to grab.

Third: is it too large? Some tasks keep moving because they are actually projects wearing a fake mustache. Split the first physical step from the rest.

Fourth: is it waiting on another person or input? If the task cannot move until someone replies, rename it as the real action: “Ask Mira for the latest numbers” is better than “finish forecast.”

Fifth: does it still belong this week? If yes, roll it. If no, release it back to the Idea Quarry. It may be real and still not be part of the week.

Roll it or release it

Rolling means the task still matters, just not today. It deserves another place in the week. The fact that it survived the day is not shameful; it is information.

Releasing means the task does not belong in the week anymore. It may be dead. It may be an idea rather than work. It may be worth remembering without carrying as a commitment.

The problem with many to-do apps is that they roll everything by default and release almost nothing. The list grows because every missed task keeps its chair.

Slate gives undone work a second kind of place. If a task is still alive, rollover carries it forward into the next day. No red badge. No overdue theater. It stays in the flow of the week.

But some tasks expose themselves by being skipped. Once a task keeps drifting, it may no longer be committed work. It may be rough material. That is where the Idea Quarry helps. “Call supplier” might need to roll to tomorrow. “Think about new supplier process” may need to leave the week entirely until it becomes a real next action.

A task in the wrong place keeps asking for the wrong kind of attention.

Forgetting is part of planning

Forgetting has a bad reputation in productivity software. Everything is searchable, recoverable, synced, logged, restored. This is good for trust and terrible for judgment if the interface makes everything equally present forever.

A healthy system remembers without insisting. Slate’s Bin can keep deleted tasks recoverable for months, but the weekly slate does not have to stare at them. The Idea Quarry can hold unfinished material, but it does not pretend every item is today’s work.

The list shrinks when work moves to the place it actually belongs.

The task that never gets done is not always a discipline problem. Sometimes it is a placement problem. Sometimes it is an idea dressed as a task. Sometimes it is a task from a version of the week that no longer exists.

Roll what still matters. Rewrite what is unclear. Release what does not belong in the week. Delete what has quietly died.