Recurring Tasks in Kanban: The Same Card Every Week, Solved

Every board has them: the standup prep card, the monthly invoice card, the newsletter card. Handling recurring tasks on a kanban board is awkward because kanban was designed for work that finishes — a card enters on the left, exits on the right, done. Recurring work never finishes; it just comes back. This post walks through the three patterns teams actually use — duplicating by hand, card templates, and archive-to-respawn recurring cards — plus five concrete workflows you can copy.

Why kanban fights repetition

A kanban card is supposed to represent one unit of work flowing once through your process. Recurring chores break that in two ways. Either you drag last week's card back to the first list — and now the checklist is still checked, the due date points at the past, and three months of comments make it impossible to tell this week's notes from May's — or you recreate the card each time, until a busy week comes and nobody does. Both failure modes end the same way: the routine silently stops happening, and the board stops being trustworthy. If you're still setting up your first flow, read how to organize projects with kanban first; this post assumes the basics.

Three ways to handle recurring tasks on a kanban board

1. Duplicate the card by hand

The zero-setup option: copy the last occurrence, uncheck everything, fix the dates. It works for things that repeat quarterly. For weekly work it degrades fast — copies drift from the original, someone forgets to uncheck an item, and the whole system depends on one person remembering on a Monday morning.

2. Card templates

Templates fix the consistency half of the problem. In Decknote you can save any card as a template — description structure, labels, checklist — and stamp out a fresh copy whenever the routine comes around. Every occurrence starts identical and unchecked. What templates don't fix is memory: a human still has to create the card and set the date. They're a solid free-plan answer for routines that already have an external trigger, like a client email that arrives every month.

3. Archive-to-respawn recurring cards

The pattern that closes the loop: finishingthe card is what schedules the next one. In Decknote (a Pro feature) you set a recurrence — daily, weekly, biweekly or monthly — on any card with a date. When you archive the card because the work is done, the next occurrence is created automatically: checklists reset to unchecked and the start and due dates advance by the interval. Because the trigger is completion rather than a clock, occurrences never pile up into a guilt-inducing stack while you're on holiday. Archive nothing, get nothing; archive the card, and next week's version is already waiting.

Five recurring workflows that map cleanly

Weekly standup prep

One card due every Monday, assigned to the facilitator, with a checklist: gather blockers, update the numbers, post the agenda. Rotate the routine by changing the assignee before archiving. Anyone who wants a heads-up adds themselves as a watcher.

Monthly client invoicing

A card per client, monthly recurrence, due on the 1st. Checklist: pull hours, draft the invoice, send it, confirm payment. Add a number custom field for the amount and it shows up as a sortable column in Table view — a running ledger of every month, for free.

Weekly newsletter or content publishing

Draft, edit, schedule, send — as a checklist on one weekly card. Attach the assets and the final links to the card itself, write the outline in the card's page with the /slash menu, and archive on send. Next week's issue appears with the dates moved forward.

Biweekly maintenance chores

Dependency updates, backup restore tests, log review — the work nobody prioritizes until it bites. A biweekly card keeps it visible. When one checklist item turns out to be a real project (that major version upgrade), convert the item into its own card and get it prioritized like any other work.

Daily ops checklist

Opening routines for a shop, a morning support-queue sweep, an end-of-day close-out. Daily recurrence, archive when done, tomorrow's card is ready before you are. The board becomes the log: the archive holds every completed day.

Keep routines from drowning the board

• Give recurring cards a “Routine” label and save a personal view that filters it out, so project work is one click away from a clean board.
• Switch to Calendar view to see upcoming occurrences next to real deadlines before you commit to a busy week.
• Use the due-status filterto see today's recurring load at a glance across any view.

One honest note on pricing: recurring cards are part of Decknote Pro, which is $5/month flat per board owner (or $48/year) with a 14-day trial — and because it's not per-user, your Pro unlocks recurring cards for everyone on your boards. Templates, checklists, custom fields and filters are all on the free plan, so the manual patterns cost nothing to try. For more small setups like these, see tips and tricks for Decknote.

Create your free Decknote account and try all of this on your own board — no credit card required.