Skip to main content
Blog ·

Recurring tasks aren't to-dos: why each day needs its own snapshot

Set "take out the recycling" to repeat every other Tuesday in a flat to-do app, then miss one. Watch what the app does: nothing is recorded, nothing is filed — the card just slides forward, gathering badge-red, until an obligation that belonged to one specific Tuesday has become a permanent little accusation pinned to today.

That slide is not a bug in those apps. It is the model.

One card, worn smooth

A flat to-do list treats a recurring task as a single object with a repeat rule stapled on. There is one card. Completing it mutates the card — checkbox cleared, due date bumped. Missing it mutates the card too: same card, redder. Either way, yesterday is overwritten by tomorrow.

Which means the card cannot answer the questions that actually come up. Did the recycling go out on the 3rd? When did anyone last clean the gutters — really, not theoretically? How often does the furnace filter get changed in practice, as opposed to on paper? A single recycled card holds none of this. It is a pointer to "next time," and a pointer has no memory.

Days are facts

A recurring task is not one thing. It is a series of appointments with the same obligation — and each appointment is its own fact. Tuesday, July 7 happened. The recycling went out, or it didn't. That is a truth about July 7, and it deserves to be stored on July 7, not smeared into the current state of a card.

This is the model Self-Control is built on. A task is the named routine — its checklist, its day-based schedule. Every day the schedule fires, the app generates an occurrence: a dated snapshot of that checklist with its own, fully independent state. Two waterings in one week are two pages. A missed one is one page, unresolved, exactly where you left it — and the next one still arrives on time, untouched by it.

What per-day independence buys

  • A record you can consult. "When did we last flip the mattress?" becomes something you look up, not something you argue about.
  • No pile-up arithmetic. Nothing rolls forward, so nothing accumulates. A behind-week is a handful of quiet pages marked Previous — never a single card wearing a four-digit badge.
  • Edits that don't rewrite history. Change the routine's checklist today; the days that already happened keep what actually happened on them.
  • Sharing without a scoreboard. A household looks at the same dated page and sees the same state. When someone takes out the trash, it is simply done — no per-person tallies, no one's chain to break.

A quick test for any tracker

Ask it: did this happen on the 3rd? If answering requires scrolling a completed-items graveyard and doing due-date archaeology, the tool is modeling cards, not days — and it will keep describing its own bookkeeping instead of your week.

Every recurring day gets its own page. That single decision is where the rest of Self-Control comes from — the durable history, the forgiving vocabulary, the deliberate absence of streaks. The longer tour of the mechanism is on the routines page.