Some work repeats on a schedule — a weekly status report, a monthly invoice review. Instead of recreating that task by hand, set a recurrence rule once and Examply creates the next instance automatically.

This article covers setting up a recurring task, the recurrence rules available, and how completed instances are handled.

Create a recurring task

Create a task as usual, for example "Send weekly client status update".
Open the task and click Make recurring.
Choose a recurrence rule and a start date, then click Save.

The current instance behaves like any other task — assign it, prioritize it, add an estimate. The recurrence rule only controls when the next instance is created.

Note: Only Owners, Admins, and Members can turn a task into a recurring one. Guests can be assigned to a recurring task's instance, but can't set up or edit the recurrence itself.

Recurrence rules

Rule	Next instance created
Daily	Every day, including weekends
Weekdays	Every Monday through Friday
Weekly	Same day each week
Biweekly	Same day, every second week
Monthly	Same date each month
Custom	Any interval in days, weeks, or months that you define

How completion works

Marking a recurring task done closes the current instance and creates the next one on schedule, with the same title, assignee, labels, and estimate. Comments and subtasks don't carry over — each instance starts clean.

Note: If you're behind schedule and miss an instance's due date, Examply still creates the next one on time. It doesn't wait for the overdue instance to close first.

Editing or ending a recurrence

Open any instance of the recurring task.
Click Edit recurrence to change the rule, or Stop recurring to turn the current instance into a one-off task.

Editing the rule only affects instances created after the change — it doesn't move a due date that's already been set.

Recurring subtasks

Subtasks attached to a recurring task reset along with it: when the parent instance closes and the next one is created, its subtasks come back unchecked. This makes recurring tasks a convenient way to run a repeating checklist, such as a pre-release QA pass, without rebuilding the list of steps every time.

Tips

Use Weekdays instead of Daily for anything tied to business operations, so you don't get a Saturday instance nobody will action.
Recurring tasks are a good fit for checklists your team runs regularly, like a release checklist or a weekly retro.
If a recurring task keeps getting reassigned, consider setting it to a role-based owner in your team's rotation instead of one person.