Written for people who keep re-writing the same task
Why unfinished tasks should carry over to the next day
Open almost any to-do app tomorrow morning and you get a clean page. It feels good. It is also, quietly, a lie — because the three things you avoided yesterday are not gone. They're just no longer in front of you.
The fresh-start problem
Daily lists are designed around optimism. Each morning you decide what today looks like, and the record of what you decided yesterday gets filed away. That works beautifully for the tasks you actually do. For the ones you don't, it does something worse than nothing: it removes the evidence.
The task you've now postponed eleven times looks identical, on a fresh list, to the one you thought of five minutes ago. Both are one line of text. Nothing on the page distinguishes a new idea from a long-running act of avoidance.
The tasks you skip are the ones worth measuring. They're skipped for a reason — and the reason rarely goes away on its own.
What carrying forward actually changes
When an unfinished task reappears the next day carrying a number — Carried 6 days — three things happen.
Avoidance becomes visible. You can no longer be vaguely aware you're behind. You can see that "call the accountant" has been waiting since a week last Tuesday, and that number is uncomfortable in a way a fresh line of text never is.
It surfaces bad tasks. A task that's been carried fifteen days usually isn't lazy — it's wrong. Too big, badly defined, blocked on something you haven't named, or not actually yours to do. The age is a diagnostic. When you see it, you can break the task up, hand it over, or delete it honestly rather than letting it rot.
It changes what you write down. Once you know a task will follow you and keep count, you get more careful about adding things you have no intention of doing.
Why "just move it manually" doesn't work
Plenty of systems ask you to migrate unfinished tasks by hand — bullet journalling calls it exactly that, and treats the friction as a feature: if a task isn't worth rewriting, it wasn't worth doing.
There's something to that. The trouble is what gets dropped. When you're tired, the tasks you don't bother rewriting are rarely the unimportant ones — they're the ones you're avoiding. Manual migration filters for enthusiasm, not importance, and the difficult work is exactly what falls through.
Automatic carry-over removes the choice. Everything comes with you. You can still delete a task, but you have to do it deliberately, which is a different act from letting it quietly go missing.
Age is not the same as priority
Worth being precise about: how long a task has waited and how much it matters are two different measurements, and conflating them is a mistake. Something can sit for a month because it genuinely doesn't matter much. Something written an hour ago can be the most urgent thing you own.
That's why ConstantUrgency tracks them separately. Priority is a number from one to five that you set. Age is counted for you. A task can be old and unimportant, new and critical, or — the combination worth acting on — old and critical, which is precisely the state most lists are incapable of showing you.
What to do with an old task
When something has been carried long enough to bother you, there are only four honest responses:
- Do it. Often it's smaller than the dread suggests.
- Break it up. Tasks that sit for weeks are usually projects wearing a task's clothing.
- Name what's blocking it. If it can't start until something else finishes, record that — then it stops nagging until it can actually be done.
- Delete it. Deciding not to do something is a real decision. Make it on purpose.
What you shouldn't do is let it disappear on its own. That's the only option that costs you the information.
Try it on your own work
The argument is easy to test. Use it for a week and look at what has accumulated a number next to it. Those tasks are telling you something specific about your work, and it's usually not what you'd have guessed.