Can Clio tasks recur? What to do instead

No. Clio Manage tasks cannot be set to recur. Clio's own help centre puts it plainly: tasks cannot be set to recur in the same way that calendar events can, and the documented way to make a task repeat is to duplicate it. There is no daily, weekly or monthly pattern on a task, and no scheduled trigger anywhere in Clio that could supply one.

Below: what Clio does recur, the four workarounds, and the distinction that decides which one you need, because "recurring task" describes two completely different requirements that firms keep confusing.

Below: what Clio does recur, the four workarounds, and the distinction that decides which one you actually need, because "recurring task" turns out to describe two completely different requirements that firms keep confusing.

What Clio does recur

Calendar events. A Clio calendar event takes a recurrence pattern, every week, every second Tuesday, every month on the 15th, and Clio generates the series. Edit one occurrence or the whole series. This is a real recurrence engine and it works.

Nothing else. Not tasks, not task lists, not automated workflows. Every automated workflow trigger is a matter event, the matter being created, a stage change, a hand-off from Clio Grow, never a clock. So you cannot get recurrence in through the automation door either. And Clio Manage has no automatic task reminders at all, so you cannot even fake a rhythm with nagging.

That asymmetry is the whole problem. The thing you can recur is the thing that shows up in a calendar and gets ignored; the thing that shows up in someone's task list, with an owner and a completion state, is the thing that cannot.

The distinction that decides everything

Before picking a workaround, work out which of these two you have. They look identical when described in a sentence and they need opposite solutions.

Most searches for "Clio recurring tasks" are the second row and are already solved: what you want is a task list template applied at a matter stage, covered in the guide to Clio's automated workflows. If that is you, stop here, you do not have a recurrence problem, you have a template you have not built yet.

The rest of this page is the first row: genuinely time-based, firm-level work. Trust reconciliation. Monthly billing runs. Quarterly conflict-check audits. Annual insurance renewals. Work that belongs to the firm rather than to a matter, that has to happen on a rhythm, and that nobody should have to remember.

The four workarounds

Duplicate the task

Clio's own documented answer: complete this month's task, duplicate it, move the due date forward a month. Roughly fifteen seconds of work, and Clio's help centre describes duplication as the way to "set tasks to repeat".

Where it stops being enough: it depends on a human remembering, and the moment it is most likely to be forgotten is the moment it matters most, the month things are busy. It also leaves no record of a missed cycle. If nobody duplicated the reconciliation task in July, there is no July task sitting overdue; there is simply nothing, which is indistinguishable from nothing needing to be done.

Use it for a handful of monthly items owned by one organised person.

A recurring calendar event as the prompt

Create the recurrence on the calendar, where recurrence works, and let the event prompt whoever owns the work. Optionally have them create the task when they start.

Where it stops being enough: a calendar event is not a task. It does not appear in a task list, it cannot be reported on as outstanding, and it disappears into the past whether or not anybody did anything. For anything with a compliance dimension, trust accounting especially, "there was a calendar entry" is not a record of the work.

Use it for prompts, not for obligations.

A task list template you re-apply

Build the set of monthly tasks as a task list, then apply it to a standing internal matter, most firms have a "Firm administration" or "Office" matter for exactly this. One action per cycle instead of one per task.

Where it stops being enough: same dependency on somebody remembering, but amortised across ten tasks instead of one, which is a real improvement. Two rougher edges. Relative due dates inside a task list are set against the trigger date of another task in the list, so the whole set shifts together when you apply the list late, three days late means every deadline three days late, which for a month-end reconciliation with a hard date is wrong in a way nobody notices. And once a task list has been assigned you cannot change its tasks' due dates, so correcting that drift means deleting and re-applying rather than editing.

Use it when the cycle has several tasks and a forgiving date.

A scheduled job outside Clio

Zapier, Make, n8n or a script on a cron schedule, creating the tasks through the Clio Manage API. This is the only option that genuinely removes the human from the loop.

Where it stops being enough: you now own an integration. Credentials expire, the Clio API rate-limits, a run fails at 3am and nobody sees it, and the person who built it leaves. For one monthly task, a Zap is fine. For eleven cycles with different rhythms, different owners and dates that need to respect firm holidays, you have built a small internal product with no error handling and no owner. That is the calculation to make honestly before you start, it is the same one we walk through in the guide to Clio's automated workflows.

When the workarounds stop working

Three signals, in increasing order of seriousness.

You have more than about five recurring cycles. Below five, one organised person and a duplicate-the-task habit is genuinely fine and costs nothing. Above five, the habit becomes a job, and it is a job with no visible output, you only find out it lapsed when something is missed.

The date has to be right, not approximate. Anything anchored to a real deadline, month end, a filing window, a renewal date, cannot tolerate the drift that relative due dates introduce every time you apply a list late. This gets worse if you count in business days, which quietly stretches every cycle a firm holiday touches; there is a whole argument about that in how a due date should be decided.

A missed cycle has to be visible. This is the one that decides it for most firms. Duplication and calendar events both fail silently. If the answer to "how would we know if the June reconciliation never happened?" is "we wouldn't", the workaround is not a workaround, it is an unmonitored risk with a task-shaped hole where the evidence should be.

How Taskflow handles it

Taskflow's triggers are matter stages and calendar events rather than a clock, so it solves the second column of that table, the per-matter repetition, rather than pretending to be a scheduler. For genuinely time-based firm work, a recurring Clio calendar event as the trigger is the pattern we recommend and support: the event recurs in Clio, each occurrence fires the template, and the tasks land with real dates, real assignees resolved by rule, and a run record showing whether the cycle actually ran. The triggers documentation covers what a recurring event does and does not re-fire.

Questions people also ask

Can Clio calendar events recur?

Yes. Calendar events support recurrence patterns and series editing. This is the only recurrence engine in Clio Manage, and the basis of two of the four workarounds above.

Can an automated workflow run on a schedule?

No. Every Clio automated workflow trigger is a matter event: the matter being created, a matter stage change, or a matter moving from Clio Grow to Clio Manage. There is no scheduled trigger, so recurrence cannot be reached this way.

Does duplicating a Clio task copy its due date?

The duplicate carries the original's fields, so the due date needs changing every time. That single manual step is where the workaround fails, because it is silent when skipped.

Can Zapier create recurring tasks in Clio?

Yes. A scheduled Zap can create a Clio task on any rhythm Zapier supports. You take on the integration: credentials, rate limits, silent failures. Reasonable for one or two cycles, expensive to own for ten.

What about recurring tasks per matter, like a monthly client update?

That is the harder case: time-based and matter-scoped, so it multiplies with your caseload. A recurring calendar event on each matter is the native route, and it means creating one series per matter by hand. It is the strongest argument for automating this rather than working around it.

Does Clio have a task template we can just re-apply?

Task lists are the closest thing, and yes, re-applying one to a standing internal matter is the best purely native answer for firm-level recurring work. Watch two things: the due dates inside the list are relative to another task's trigger date, so the whole set drifts if you apply it late, and you cannot edit those dates once the list has been assigned.