Recurring tasks

Recurring tasks are tasks that automatically recreate themselves on a schedule after completion or at fixed intervals. They’re the operational backbone of any repeatable workflow: weekly team standups, monthly invoice submissions, quarterly report reviews, daily EOD updates.

The quality of a tool’s recurring task engine matters more than most reviews acknowledge — especially for teams running compliance workflows, client update cycles, or any work that happens on a fixed cadence.

How recurrence works (and the difference between tools)

Basic recurrence: “Repeat every Monday.” When Monday arrives, a new task appears.

Completion-based recurrence: “Repeat 7 days after completion.” If you complete the task on Thursday instead of the scheduled Tuesday, the next occurrence is the following Thursday — not the following Tuesday. Useful for tasks that depend on actual completion (e.g., “send follow-up email 3 days after onboarding call”).

Complex patterns: “Every last business day of the month,” “every 2nd Tuesday,” “every 3 weeks.” Most tools handle basic patterns; few handle complex ones cleanly.

Tool comparison on recurrence quality

Todoist (best in category): Natural language input handles nearly every pattern: “every last day of the month,” “every other week on Monday and Thursday,” “every 1st of the month except January.” The completion-based recurrence is first-class. Recurring tasks are a core feature, not an afterthought.

ClickUp (strong): ClickUp supports recurrence with weekly, monthly, and custom interval options. The UI requires more clicks than Todoist (a dialog vs natural language), but the coverage is comprehensive. ClickUp’s automation engine can replicate complex recurrence patterns that the native recurring-task UI doesn’t support.

Asana (adequate): Asana supports daily, weekly, monthly, and yearly recurrence. Complex patterns (every 2 weeks, every 2nd Tuesday) are not natively supported and require workarounds. For teams with complex recurring work, this is a genuine limitation.

monday.com (limited): monday.com supports recurring items via automations (not native task recurrence). “When a due date arrives, create a new item” is the pattern. This works for simple cases but breaks down for completion-based recurrence.

Trello (via Butler): Trello’s Butler automation handles recurrence with “every day/week/month, create a card in [list].” Not as elegant as Todoist but functional for common patterns.

Why recurring tasks reveal tool quality

The way a tool handles recurring tasks reveals its design philosophy:

• Customer-facing services (invoicing, reporting, check-ins) rely heavily on fixed-cadence recurring tasks. A missed invoice or a skipped client report is a real cost.
• Operations teams run their entire workflow on recurring tasks: weekly metrics pull, daily standup agenda, monthly review calendar. A tool that handles recurrence poorly adds manual overhead.
• GTD practitioners (see GTD →) use recurring tasks as the backbone of their weekly review system. The quality of the recurrence engine determines whether the system stays trusted.

The completion-based vs date-based distinction

This is the subtlest but most consequential difference in recurrence quality.

Date-based: Task recurs on the scheduled date regardless of when (or if) you completed the previous occurrence. Used for fixed-deadline work: “monthly accounts payable is always due on the 28th.”

Completion-based: Task recurs N days after you complete it. Used for relationship-maintenance work: “follow up with the client 2 weeks after the last call.” If you miss the follow-up by a week, the next one is still 2 weeks from whenever you actually complete the task — not from the original schedule.

Todoist supports both. Most other tools support only date-based recurrence.

Go deeper

• GTD → — the productivity method that makes recurring tasks a cornerstone of a trusted system
• Todoist review → — the best recurring-task engine in the category
• What is task management software? → — full category overview