The questions firm admins ask first.

Clio can attach a fixed set of tasks to a matter. It can’t branch the list on a matter field, count a due date off a calendar event, hold a task undated until another is ticked done, or decide the assignee from a rule. That gap is the whole reason Taskflow exists.

You can, and firms do, once. Then somebody has to own thirty scenarios, each re-implementing weekend rules, leave, retries and rate limits. Taskflow is one screen a firm administrator can maintain, with the Clio-specific behaviour already handled.

You get a grace period of up to 300 seconds. The tasks are created immediately; move the matter again inside the window and the first set is deleted and the correct set generated. The clock runs from the move, so it’s the time you actually had to notice.

No. Dry run is on by default and firm-wide: every run is worked out and recorded in full, and nothing is written to Clio. There’s also a test-matter prefix gate that fails closed — while it’s set, nothing fires on any matter outside it.

Counting is on the wall calendar: “3 days after” means three days. Your working week, office closures and per-person leave only decide where a date may land: it moves to the nearest open day, by the least it can, forwards for a date counted after something and backwards for one counted before it.

No. Assignees come straight from your Clio account, so anybody in the firm can be assigned without signing in here. Taskflow logins are invite-only, with owner, admin, member and viewer roles; viewers read everything and save nothing.

A read that doesn’t land fires nothing: the trigger is retried rather than acted on half-read. When Clio says stop, everything for your firm pauses until the budget refills and picks up exactly where it left off; the Runs screen shows the pause counting down.

We do it with you. Connect Clio, build your first templates together, run them in dry run against real matters until the output is right, then switch them on. Most firms are live inside a week.