Clio Automations: What to Set Up First and Where AI Fits

Set up three Clio automations first, in this order: a task list for every new matter, a task list when a matter moves to its next stage, and a generated document such as the engagement letter. Manage AI fits beside them: it drafts client updates from matter activity and creates tasks, time entries and notes from plain-language prompts.

The ranking is by hours saved per matter, not by what looks clever. Check your plan before any of it: in Clio's plan comparison (the most recent copy I could read, dated 20 October 2026), automated workflows and matter stages appear only on Signature and Elite, while document templates, matter templates and the AI features start at Core. All three automations also depend on groundwork, and in a small firm the groundwork is where the time goes.

Follow me on Instagram@sagnikteaches

What Clio's built-in automations are, and what they need

Per Clio's help centre, automated workflows combine tasks and document templates with matter stages so that routine steps happen when a matter is created or changes stage. They are set up in Settings, under Automated Workflows, in the "Made by Clio" tab. Three types are listed.

Connect on LinkedInSagnik Bhattacharya

Some practical rules from the same help material. Firm administrators and primary subscribers create and manage the automations. A firm account can hold up to 1,000 of them, so the limit is not a concern for a small firm. For the task-list automation the practice area is required and the responsible attorney is optional, and every condition you set must be met for the automation to fire. The help page says the feature is on select plans; Clio's plan comparison listed it on Signature and Elite only when I last could read it, so confirm on the live pricing page before you plan the project.

Subscribe on YouTube@sagnikteaches

The people who receive the tasks also depend on how each task in the list was set up, so assign roles inside the task list as well as in the automation. A task with no assignee that nobody sees is the commonest reason a new automation seems to do nothing. The help page adds one more trap: if a task is assigned by role and the matter has no originating attorney, responsible attorney or responsible staff filled in, Clio shows an error instead of assigning it, so complete those fields when you open a matter.

Rank automations by time saved, not by novelty

Estimate the saving before building anything. For each candidate, write: how many times a month the trigger happens, how many minutes the manual step takes, and how often it is forgotten. The product of the first two is your saving; the third is your risk.

The ranking you build will differ, but two points hold in most firms. Document generation at the first stage saves the most minutes, because the engagement letter is long and identical every time. Stage-change task lists save fewer minutes but prevent the most embarrassing misses, such as a forgotten closing letter or an unprompted file review. Put an asterisk by anything that is "often" forgotten; those go first even if the hours are small.

The setup order for a small firm

1. Clean up practice areas and matter stages. Every automation keys off them. Aim for five to eight stages per practice area, named so that moving to the next one means something happened ("Instructions received", "Draft sent", "Completed").
2. Write three task lists. New matter, one mid-matter stage and closing. Each task has a short name, a due-date rule and an assignee role.
3. Build the "new matter" task-list automation. Test it on a dummy matter.
4. Build the stage-change task-list automations for the one or two stages where work is most often missed.
5. Write the engagement letter template and build the generate-a-document automation. Test with a dummy client.
6. Add the closing-letter document automation.
7. If you use Clio Grow, add the matter-template automation for conversions.
8. Review after a month and retire tasks nobody completes.

Roughly a day of setup for the first six steps, if the stages and task lists already exist in your head. If they do not, add another half day to write them down. That writing is useful in its own right, because it forces the firm to agree what "done" means at each stage.

A worked example: a four-fee-earner residential firm

Say a four-fee-earner firm opens about 18 residential matters a month, each with the same first dozen tasks: ID checks, conflict check, engagement letter, request for the title documents, and so on. Before automation, the person opening the matter types or copies those tasks, which takes about 12 minutes and omits one task in roughly one matter in six. After the automation, opening a residential purchase adds the 12-task list with roles assigned and due dates relative to the start. The setup took two hours for the list and 20 minutes to build the automation.

The saving: 18 matters x 12 minutes is 216 minutes, about 3.6 hours a month, and the one-in-six omission rate drops to close to zero. Over a year that is around 43 hours, before counting the cost of an omitted task. The figures are illustrative, but the method works for yours: count triggers, time the manual step and estimate the miss rate.

The task list, filled in

Task list: Residential purchase - opening
1. Collect ID and proof of address          Role: Paralegal   Due: +2 days
2. Run conflict check                       Role: Fee earner  Due: +1 day
3. Send engagement letter                   Role: Fee earner  Due: +2 days
4. Request title documents                  Role: Paralegal   Due: +3 days
5. Order searches                           Role: Paralegal   Due: +5 days
6. Diary 14-day chase on seller's replies   Role: Paralegal   Due: +14 days

Note the last task: a chase built into the list means the matter reminds you, which is the quiet value of this automation. Clio's conflict-check tool is separate from automations, so keep step 2 as a human action: the automation reminds someone to run the check; it does not run it.

Intake to matter: where the work starts

For firms using Clio Grow, the point where an enquiry becomes a matter is the most valuable handover to tidy. The matter-template automation applies a chosen matter template when you convert a lead, so the new matter arrives with practice area, stage and defaults set. Build one matter template per practice area, and keep the list short: a template nobody can choose between will not be used. If you have no Grow, the same job is done by choosing the practice area and stage when you open the matter by hand, so the first automation, the new-matter task list, does the equivalent work.

The enquiry side, including out-of-hours answering and qualification, is a separate topic: Lawmatics against Clio Grow compares the two legal CRMs. Do not build intake automations around a product you may change in six months.

Client update emails: what to automate and what to leave

The three classic automated workflows do not send email: they assign tasks, generate documents and apply matter templates. Two newer features in Clio's help centre cover client updates instead. First, Clio's AI watches matter activity, such as completed tasks, uploaded documents and stage changes, and drafts a client update when one seems due. The draft appears under Suggested actions on the matter dashboard, only the matter's responsible attorney or responsible staff member can review and send it, and it stays available for one day. Second, Clio's AI-built Workflows can start from a Clio event and include a step that sends a message or document to a client, such as a client portal message; any such step pauses until an administrator approves it.

I could not find a plain "matter changed stage, email the client" rule documented, so test any workflow on a test matter before you promise regular updates to clients. With the classic features alone, generate a client update letter at a stage from a template with the matter details merged in, and let the task list prompt a person to send it. Either way a human stays in the loop, which for client communication is usually what a firm wants.

A short template for the "Draft sent" stage might read: "Dear [first name], we have sent the draft contract to the other side and expect a reply by [date]. We will update you when we hear. Please let us know if anything has changed on your side." Use merge fields for the name, date and matter. Keep these letters under 100 words. If you want help writing templates that sound like your firm, how small law firms draft letters with AI covers the drafting.

Where Manage AI fits beside the automations

Clio sells its assistant as Manage AI, and its help centre now mostly calls it Clio's AI features. Per those help pages, you open the Clio panel from the icon at the top right, or use the prompt box on the Today page, and ask in plain language. It can create time entries and expenses, single calendar events, tasks and notes linked to a matter or contact, and it asks for your approval before it acts: once for a single request, for the rest of that conversation, or you can reject it. There is a separate AI Scheduling feature that extracts multiple deadlines and events from a court document. The help article also notes that unified Clio is rolling out to firms in stages, so your account may still show the older experience. An administrator can switch every AI feature off for the whole firm with the Firm-level AI access setting, and actions the AI takes are recorded in the firm's audit log.

There is also a newer layer between the two. Under Automations, then Workflows, Clio lets you describe a firm process in plain language and builds it as a workflow with a trigger (a schedule, a Clio event or a manual start), tool steps such as Create Task or Create Note, conditions and human approval steps. Clio's help centre says these Workflows are separate from the older Automated Workflows and are available with a new Clio plan, a Clio Work licence or the Manage AI add-on, and that creating, running and approving them needs administrator permission. Testing one runs it on real data, so always pick a test matter. For a small firm, build the classic task-list automations first; reach for Workflows when a process needs a judgement step, a schedule or an approval in the middle.

The split with automations is simple. Automations are rules: same trigger, same result, no judgement, built once by an administrator. Manage AI is for the one-off: "Create a high-priority task to review the settlement draft for [client] due Friday." Use automations for what happens every time and Manage AI for what happens once.

Plans and prices change, so check them on Clio's pricing page. The live page blocked automated reading in this session; the most recent archived copy (20 October 2026) lists four plans, Starter, Core, Signature and Elite, from $49 a user a month, with AI features included from Core upwards and automated workflows and matter stages from Signature. Confirm on the live page before you decide. What Manage AI costs and how to switch it on goes into that in detail.

Prompts that work for Manage AI

Clio's own examples are concrete: "Create a time entry for 45 minutes on the [client] matter with the description 'Drafting correspondence'" and "Create an expense entry for $50 for filing fees on the [client] matter today." Follow the same shape: action, amount, matter, description. If you leave out a detail, Clio may assign a logical default, such as your billing rate, or ask a follow-up question. Check the entry before you approve it, as you would a trainee's timesheet. Never approve "for the whole conversation" until you have watched it handle three or four requests correctly.

A second practice area: wills and estates, with a stage-change list

Different matter types need different lists, and a firm with two practice areas should resist one shared list. Take a wills and estates practice that handles about eight probate matters a month. The stage "Grant applied for" triggers a set of tasks that are easy to forget because they follow a long wait: chase the grant, notify asset holders, open the estate account, diary the claims period. Build a task list called "Estate: grant received" and an automation that adds it when a matter in that practice area moves from "Grant applied for" to "Administration".

Task list: Estate - grant received
1. Send certified copies of grant to asset holders   Role: Paralegal   Due: +3 days
2. Confirm estate account is open                    Role: Fee earner  Due: +5 days
3. Diary the claims period end                       Role: Paralegal   Due: +7 days
4. Draft interim update letter to executors          Role: Fee earner  Due: +10 days
5. Review asset schedule against grant figures       Role: Fee earner  Due: +14 days

Eight matters at about eight minutes of manual list-building is just over an hour a month, a smaller saving than the residential example. It still ranks high because the stage change comes weeks or months after the matter opened, exactly when memory fails. This is the clearest case for building a stage-change list before a new-matter list: forgotten work after a long pause costs more than a few minutes of typing at the start.

Pair it with a generated document at the same stage: the interim update letter in task 4 can come from a template with merge fields, so the fee earner edits a draft instead of starting a blank page.

Before and after: what a matter looks like with and without the list

Before: a fee earner opens a purchase, remembers the engagement letter, forgets the search order until the client asks after ten days, and adds the title request on day four. Three tasks exist; nine do not; the file's first fortnight depends on memory. After: the matter opens with all six tasks above, dated, assigned and visible on each person's list. The fee earner's job changes from remembering to ticking and adding exceptions. What changes for the client is small but noticeable: the title request goes out on day three rather than day four, the searches are ordered when promised and the update letter arrives when the matter reaches its stage.

A mistake and how it showed up

A firm built a new-matter automation but chose the practice area "Conveyancing" while the matters were filed under "Residential property". The automation never fired. For two weeks the team assumed it was working because nobody looked for the tasks; the gap showed up when a paralegal asked why a new file had no title request. The cure was a dummy-matter test using the exact practice area and a look at Automation history, which shows when each automation fired and on which matters. The lesson: trigger conditions are matched exactly, so test with the same values your real matters carry, and look for the output rather than assuming it appeared.

Permissions, ownership and who maintains it

Because only firm administrators and primary subscribers can create and manage automations, name one person as the owner and write down what each automation does. A single page with the trigger, the task list or template used, the date built and the person who asked for it is enough. When a fee earner leaves, check that tasks assigned to their name still go to someone: assigning to a role rather than a named person avoids most breakages. Review the page each quarter, alongside any change to matter stages, so the rules the firm runs on are the rules the firm thinks it runs on.

Checking that an automation worked

• Test on a dummy matter with the right practice area and a stage move, before touching a live file.
• Check who received the tasks. If nobody did, look at roles inside the task list and at whether the assigned user has access to the matter.
• Check the document. Open a generated document and read the merge fields: a blank name or a wrong date in a template is repeated on every matter.
• Review the My Automations tab monthly to see what is active, and switch off any automation you no longer need.
• Count the misses. After a month, how many matters needed a task added by hand? If more than one in twenty, the list is incomplete.

A common failure is a stage rename. If you rename or restructure stages, the automations keyed to the old ones may stop firing without warning, so after any change to stages, retest each automation on a dummy matter.

Keep the first month small

Build three automations, not twelve. A firm that turns on everything at once cannot tell which automation produced which task, and the team stops trusting the list. Start with the new-matter task list and the engagement letter, watch them for four weeks, then add one more. If you want a second view on the order for your firm's matter types, my AI implementation consultation covers exactly that; the sequence above works without it.

Questions small firms ask before setting up Clio automations

Do Clio automations need Manage AI?

No. Automated workflows use task lists, document templates and matter stages, and work without AI. Manage AI is a separate assistant for prompts such as creating tasks, time entries and notes, and for drafting client updates. In Clio's October 2026 plan comparison, automated workflows start at Signature and AI features at Core; confirm on the pricing page.

Who can create an automated workflow?

Clio's help centre says firm administrators and primary subscribers can create, delete and manage automated workflows in Clio Manage. A firm account can hold up to 1,000 automations, which is far more than a small firm needs.

What should I set up before the automations?

Practice areas on every matter, matter stages for each practice area, task lists written out as individual tasks and document templates. The automation only connects pieces you have already built, so the preparation is most of the work.

Will an automation email my client?

Not the classic ones: they assign task lists, generate documents and apply matter templates. Clio's AI can draft a client update from matter activity for the responsible lawyer to review and send, and its newer Workflows can send a client portal message after an administrator approves it. Test on a dummy matter first.

Further reads

• Best AI Agents for Law Firms: What Clio and Spellbook Mean by Agent — What Clio and Spellbook mean by agent
• AI for Small Law Firms: What to Automate First — Which tasks to hand over first beyond Clio
• AI Client Intake for Law Firms: Qualify Enquiries Out of Hours — Qualifying enquiries out of hours
• How Small Law Firms Use AI to Answer Client Status Questions — Answering client status questions with AI
• Best AI Platform for Law Firms: Clio, Smokeball and Lawmatics Compared — Clio, Smokeball and Lawmatics compared
• Client Money Checklist for Sole Practitioners: Monthly Controls With AI — A monthly client money routine for one-person practices, with exception lists and reminders AI can prepare and the checks only you can do.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Clio help centre articles on Clio Manage automated workflows, Workflows (getting started, creating, triggers, approvals), AI features and AI-drafted client communications (checked 4 November 2026); Clio's pricing page as archived on 20 October 2026, because the live page could not be loaded.