Notes on Clio, task lists, deadlines and the small operational habits that decide whether automation helps or hurts. Written for the person who actually runs the firm.
Every trigger, condition and action in Clio Manage's automated workflows, the 1,000-automation limit, which plan you need now that Clio has renamed all four, and the five things the feature was never built to do.
No. A Clio Manage task has one Assign to field, it cannot be a group, and it cannot be blank. What Clio does offer instead, including the two native routes most firms have not set up, and where each one runs out.
No. Clio calendar events recur, Clio tasks do not, and Clio's own documented answer is to duplicate them. Four workarounds, and the one distinction that decides which you actually need.
Clio Manage has no conditional logic anywhere, not in task lists, not in workflows, not in document templates. The real branching engine is in Clio Draft, sold separately. The workarounds, and the arithmetic that collapses them.
The exact API mechanics, the custom_field_values association, the fields parameter, which types support range filters, plus the value-instance-id trap that silently duplicates data instead of updating it.
No product news you don’t need. Unsubscribe in one click.
