Recurring work without a pile of duplicates

The behavior

1. 01

   Create the card once

   Give it the description, checklist, owner, label, estimate, and recurrence rule the work needs.

2. 02

   Finish the current occurrence

   Move it to the done state as part of the normal board workflow.

3. 03

   Let Tarsen create the next one

   The next occurrence is created from the recurrence rule instead of appearing before the previous one is complete.

4. 04

   Work the new card

   The next occurrence gets its new schedule and can be assigned or edited like any other card.

Good fits

• —Weekly customer follow-up.
• —A founder’s review of metrics or cash.
• —A release checklist that comes back after each release.
• —A studio’s recurring client handoff or reporting task.
• —Team maintenance that should be visible but not duplicated in advance.

What it is not

Recurring cards are not a general automation engine. They do not express arbitrary triggers, conditions, actions, or integrations. That narrowness is intentional: the feature keeps recurring work reliable without turning the board into a workflow builder.

If the work needs a different checklist, owner, or estimate every time, edit the new occurrence. The recurrence rule creates the next starting point; it does not remove judgment from the task.

Use it with Mission Mode

Because the next occurrence appears after completion, a missed week does not flood Mission Mode with old copies. The board shows the work that exists now, and the daily plan can reason over it without a hidden stack of duplicates.