How to Set Up a Repeating Task (Step-by-Step)

To set up a repeating task, open the task, find its repeat or recurrence control, choose a frequency (daily, weekly, monthly, yearly, or a custom interval), then set an end condition: never, a specific date, or after a set number of occurrences. Save it, complete the first instance, and confirm the next due date lands where you expected.

What you need before you set up a repeating task

Setting up a repeating task comes down to three decisions: the frequency, the end condition, and whether your tool builds the next instance from the original schedule or from the day you actually finish the work. That third decision gets skipped most often, and it quietly changes how the task behaves for months.

Todoist frames recurring dates around work that repeats regularly, like monthly reports or weekly recycling, rather than recreating the same task each cycle. That's the test. Would you type this task again by hand? If yes, it's a candidate.

• Frequency: a plain interval (every week) or a pattern (last Monday of every third month).
• End condition: never, a date, or a repetition count. Google Tasks and Google Calendar support all three.
• Completion logic: some tools recalculate from the completion date, others from the interval.
• Input method: typed natural language, or a structured recurrence menu.

Here's how the major tools differ once the task is live, which is the part most setup guides leave out.

Recurring task behavior across major tools, as of September 2026

Tool	How the next occurrence is set	End conditions / limits	Setup entry point
Todoist	Manually rescheduling a recurring task, then completing it, recalculates the next occurrence from the completion date	Not published	Natural language ("every Monday", "monthly") or the date picker's Repeat option
Asana	Task duplicates after completion; new due date set by the recurrence interval	Not published	Not published
Google Calendar	Edits apply to one event or all events in the series	730 occurrences maximum	Not published
Google Tasks	Limited number of upcoming occurrences shown; new ones appear as time passes	Never, on a date, or after a set number of occurrences	Not published
Microsoft Planner	Only current occurrence visible; next appears after you mark it complete	Not published	Not published
Microsoft Project	Created from a Daily, Weekly, Monthly, or Yearly recurrence pattern	"End after" a typed number of repetitions	Task > Recurring Task

Sources: Todoist, Asana, Google Calendar, Google Tasks, Microsoft Planner, Microsoft Project.

Step 1: Decide if the task should actually recur

A task should recur when the work arrives on a fixed schedule with roughly the same scope every time. If the scope shifts each cycle or the timing is irregular, keep it as a one-time task and reuse a template instead. A bad recurrence rule generates false reminders, and you'll learn to ignore them fast.

Microsoft's Project documentation puts the case plainly: if a task happens every couple of days or every month, any regular schedule really, you can set it up once as a recurring task. The corollary matters just as much. Irregular repeating work needs a separate task for each occurrence.

Daily habits, weekly check-ins, monthly invoice runs, quarterly reviews: those recur. A client deliverable that happens to land most months does not.

Step 2: Choose your frequency and pattern

Screenshot: Todoist homepage, September 2026.

Frequency is the core of the setup. Every tool offers presets (daily, weekly, monthly, yearly), and most add a custom pattern layer for schedules like "every three days" or "the second Thursday of every other month." Set the preset first, confirm it renders the dates you want, and only open the custom builder when the preset can't express the schedule.

1. Daily: every day, weekdays only, or every X days. Outlook accepts any number between 1 and 999.
2. Weekly: every X weeks on chosen weekdays. Outlook caps the week interval at 99.
3. Monthly: a fixed date, or a relative pattern like the first Wednesday of each month, the second Thursday of every other month, or the last Monday of every three months.
4. Yearly: anniversaries, renewals, annual filings.

If your app parses natural language, skip the menu. Todoist says typing "every Monday" or "monthly" creates the recurrence directly. No picker, no dropdown. Handy when you already know the pattern in words.

Step 3: Set an end condition so the series doesn't run forever

An end condition stops the series: never, a fixed end date, or a repetition count. Leaving a recurrence open-ended is the most common setup mistake, and six months later you're dismissing a reminder for a report nobody reads. Default to the count whenever the work has a known number of cycles.

Google Tasks and Calendar offer all three options in the repeat control. Microsoft Project asks for the count explicitly: pick End after, then type the number of times the task will repeat.

One hard ceiling to know: Google Calendar limits repeating events to 730 occurrences. A daily event runs out in roughly two years, so a multi-year daily series will hit that wall before you notice.

Put a quarterly review on your calendar to audit open-ended recurrences. Ten minutes of pruning beats months of alarm fatigue.

Step 4: Understand how completion creates the next occurrence

Completion logic decides where the next due date lands. Todoist schedules an "every day" recurrence from the date you complete the task. In Asana, the task duplicates itself after you mark it complete, and the new due date is determined by the recurrence interval you set. Same setup, different results.

The Todoist behavior goes further. Reschedule a recurring task by hand, complete it, and the next occurrence is calculated from that completion date rather than your original plan. Finish Monday's task on Thursday and the series has moved to Thursdays. For habits that's usually what you want, because the streak follows real behavior. For a report due every Monday, it's a slow slide.

Asana also shows only the next upcoming occurrence on the calendar rather than the whole future series. Microsoft Planner works the same way: the current occurrence is visible, and the next one appears once you mark it done.

Neither model is better. Pick completion-anchored for habits and elastic routines, interval-anchored for deadlines other people depend on.

Step 5: Avoid the edge cases that break recurring task setups

Two failure modes catch experienced users: nested recurrence and careless edit scope. Asana warns that if a parent task repeats, its subtasks should not also repeat, because the combination can duplicate the recurring subtask exponentially. Set recurrence at one level only.

Edit scope is the second trap. Change a repeating event in Google Calendar and you're asked whether the change applies to that one event or every event in the series. Answer carelessly and you've either moved a single instance you meant to move permanently, or rewritten two years of history. If you're managing layered work, our guide to tasks and subtasks covers where nesting helps and where it hurts.

Practical safeguard: test any new recurrence on a throwaway task. Create it, complete it, look at the next due date. Thirty seconds of verification tells you more than any help article.

Step 6: Match the repeating task workflow to the right tool

The setup pattern barely changes between tools (open the task, set frequency, set an end rule), but the interface changes the speed. Some apps take typed input, some use structured dropdowns, and team platforms layer automation on top. Pick based on how you prefer to enter a schedule and who else needs to see it.

• Todoist: type the pattern inline or use the visual repeat picker, available on all platforms in all 18 supported languages.
• Microsoft To Do in Outlook: select Repeat, then daily, on weekdays, weekly, monthly, yearly, or a custom repetition.
• Microsoft Project: Task > Recurring Task, then Daily, Weekly, Monthly, or Yearly in the Recurrence pattern section.
• Trello: Butler automation can create a recurring card when a card moves, a label is added, or a checklist item is checked off. Recurrence driven by workflow state instead of the calendar.
• Zapier: useful when recurring work spans disconnected systems. Zapier can create tasks automatically when a repeat date arrives in Google Calendar or Google Sheets.

Still choosing a home for this? Our tool comparison for 2026 weighs these on more than recurrence.

Step 7: Use repeating tasks to plan workload, not only reminders

Repeating tasks standardize process: same title, same checklist, same cadence. That lets you estimate how much of your week is already spoken for before new work arrives. The catch is visibility. Asana shows one occurrence at a time, and Google Tasks surfaces only a limited number of upcoming tasks, so the calendar understates your real recurring load.

So count it manually, once. List every recurring task, multiply by frequency, total the hours per month. Most people are surprised at how much of the week recurring admin already owns.

Then keep the boundary clean. Stable categories like reporting, reviews, maintenance and invoicing belong in recurrence. Variable project work stays as one-time tasks. Mix them and your capacity estimate turns into fiction.

Dooit: setting up a repeating task with natural language

Screenshot: Dooit homepage, September 2026.

Disclosure: Dooit is our own product, included here for transparency.

Dooit handles recurrence as part of typing the task. Write the schedule into the task text, using phrases like "every Monday," "tomorrow," or "next Friday," and natural language parsing sets the recurrence without a menu. Every action in Dooit completes in under 50ms, so setup happens at typing speed.

1. Type the task and its recurrence together, for example "Submit report every Monday."
2. Switch between Kanban board and list view with one keystroke to see recurring tasks next to one-time work.
3. Pair recurring tasks with daily habit tracking and streaks when the goal is consistency rather than a due date.
4. Fix a wrong pattern with undo and redo, part of 20+ keyboard shortcuts.
5. Real-time sync keeps the same schedule current on desktop and the mobile app.

For a wider view, see our recurring task management guide.

Frequently asked questions

Which types of work suit repeating task workflows best?

Work that runs on a regular schedule. Todoist cites monthly reports, weekly recycling, and birthdays as typical cases, and Microsoft describes recurring tasks as a way to set up regularly scheduled work once instead of rebuilding it. Zapier frames the same idea as scheduling and tracking repeating work without manual upkeep.

What is another word for a repeating task?

Recurring task, repeated task, repeatable task, and recurring reminder. Productivity and calendar tools use these interchangeably for a task or event that regenerates automatically on a set schedule instead of being created by hand each time.

What is an example of a repetitive task?

A weekly status report, monthly invoice reconciliation, recycling every Tuesday, or a daily standup note.

How do you repeat a task a specific number of times?

In task tools, you use a repetition count as the end condition. Microsoft Project asks you to pick End after and type the number of times the task will repeat, and Google Tasks can end a recurrence after a set number of occurrences. Programming loops are a separate topic the documentation cited here doesn't cover.

Do recurring tasks work differently in team tools versus personal apps?

Often, yes. Team tools tend to show a single occurrence at a time: Asana displays only the next upcoming occurrence on the calendar, and Microsoft Planner surfaces the next one after you complete the current task. That's fine for execution, but it hides total recurring load when you're planning capacity.

One honest limitation: recurrence only works when the schedule is genuinely stable. Automate a task whose timing drifts and you'll spend more effort rescheduling instances than you saved, and the false reminders will train you to ignore the real ones. It pays off on the boring, predictable core of your week.

If you'd rather set recurrence with a typed phrase than a dropdown, try Dooit.