Agiled Docs

The current task workspace does not expose a native recurring task scheduler. Use task templates, project templates, and automation workflows for repeatable work.

Choose the lightest repeat pattern that fits the work. Templates are better for human-started repeat work; workflows are better when a system event should create the task.

Use Task Templates

Create a task template for work that repeats with the same title, description, priority, status, or project context. When the work needs to happen again, start from the template and adjust the date or assignee.

Task templates work well for review tasks, QA steps, invoice follow-up, publishing checklists, onboarding work, and monthly admin tasks.

After creating a task from a template, always review due date, assignee, project, priority, and description. Template defaults are useful, but repeated work often needs current-period context.

Use Project Templates

Use project templates when the recurring work is larger than one task. A project template can give the team a repeatable delivery structure, then tasks can be updated for the current customer or period.

Choose The Owner First

Before creating repeat work, decide who owns the repeated task and who reviews whether it still matters. Recurring work without an owner quickly becomes queue noise. If ownership changes by customer, project, or month, make that handoff part of the template or workflow instructions.

For finance, HRM, support, and customer delivery work, include the period or record context in the task title so old repeat tasks are easy to distinguish from current work.

Add Review Dates

Recurring work needs review. Add a review date or owner to templates and workflows so someone checks whether the recurring pattern still matches the current process.

Use Workflows for Automation

Use workflows when the task should be created by an event, such as a form submission, deal stage change, ticket creation, or other supported trigger.

For scheduled recurring work, review the available workflow scheduling options in your workspace before relying on a manual calendar reminder.

Start with a draft workflow and one safe test record. Confirm the created task has the expected title, owner, due date, priority, project, and linked record before publishing or scheduling the workflow.

If the workflow sends notifications or creates customer-facing work, test the entire run before enabling the schedule. Repeated automation can quickly create noise when the first version is wrong.

Keep Repeat Work Clean

Use clear names that include the work period when needed.
Set due dates after creating the task from a template.
Assign the task to the current owner.
Link the task to the right project, contact, account, or deal.
Update the template when the same change is needed repeatedly.

Avoid Duplicate Recurring Work

Choose one system to create the repeat task. Do not use a calendar reminder, task template routine, and workflow for the same work unless each one has a different purpose. Duplicate recurring tasks make teams ignore the queue.

Review recurring work monthly. Archive templates or pause workflows when the process changes so old repeat tasks do not keep appearing.

If users ignore recurring tasks, check whether the task is duplicated, too vague, assigned to the wrong person, or no longer needed.

Monthly Review

Review repeat work monthly:

Check whether the task still needs to happen.
Confirm the owner is current.
Update due-date rules or template wording.
Pause workflows that create stale tasks.
Remove duplicate reminders from calendars or other tools.

Recurring Task Patterns