SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Choose the business rule before the syntax
Todoist distinguishes recurring schedules, including completion-based expressions using every!. Completing a recurring task advances its next date. Its documentation also warns that manually rescheduling an occurrence and then completing it can skip intermediate occurrences. Specify what the routine is meant to represent before choosing a date expression.
Example: a fixed review and an interval check
Imagine two non-critical routines. A weekly editorial meeting follows the calendar. A personal equipment inspection is intended a fixed interval after the previous inspection actually happened. Those are different rules even if both often appear one week apart.
Write the intended behavior in plain English: the meeting remains tied to its regular weekday; the interval check is measured from completion. The examples concern ordinary planning and are not a substitute for regulated maintenance schedules.
Inspect three boundary cases
| Case | What to record |
|---|---|
| Completed early | Whether the next date preserves the intended cadence |
| Completed late | Whether a missed occurrence is skipped or needs separate tracking |
| Manually rescheduled | The resulting next date after completion |
Create disposable rehearsal tasks rather than manipulating a real annual commitment. Inspect the date expression before completion and the next displayed date afterward. Keep the result beside the plain-English intention. This guide describes a test recipe, not measured behavior in a live account.
Track missed work explicitly when necessary
If each missed occurrence represents a separate deliverable, a moving recurring task may not be a sufficient record by itself. For example, three undelivered weekly reports are three outstanding outputs, even if a single routine now points to next week. Decide how to represent the backlog rather than assuming recurrence creates the evidence you need.
When preparation must happen earlier, consider keeping the main routine's date stable and representing the preparation separately. If the routine contains subtasks, review the Reset sub-tasks setting so the next cycle contains what you actually intend.
Acceptance rule
Use the recurring task when its next-date behavior matches the operational rule and its history is sufficient for your purpose. Use individually tracked tasks when every occurrence needs its own owner, evidence and acceptance. Recheck the setup when changing cadence or rescheduling a long-overdue item; the most important date is often the next one created after you click complete.
For the complete learning path, visit the Todoist practical guide hub.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.