Clio Manage AI Review: Deadlines, Billing and the Move from Duo

JSH LAW / LEGAL AI PRODUCT RESEARCH

England and Wales perspective · Sources reviewed 23 October 2026 · Documentary assessment

What happened to Clio Duo?

Clio’s UK Manage AI article describes Manage AI as the development of the earlier Duo assistant. References to Duo in older material therefore need to be understood as part of the product’s history, not necessarily as the current commercial label.

Clio is the practice-management supplier behind the product. Its wider range includes other services for research, drafting and client intake. This review concerns the administration of matters in Manage, rather than the proposition that every Clio product is one interchangeable subscription.

The current UK feature page describes court documents becoming calendar events, matter activity becoming client updates and time or expenses becoming invoices. Those are useful workflows to investigate, but each has a different error consequence and approval requirement.

Extracting a deadline is not calculating the legal deadline

If an order says “file by 4 pm on 12 November”, extraction asks what the document says. If it says “within fourteen days of service”, the task may also require identifying the service event and applying the relevant procedural rules. Those are different tasks.

The UK feature page describes reviewing a proposed event alongside its document source. That is a useful design direction. The practice must still establish whether the source is the operative order, whether it has been varied and whether the extracted event belongs to the correct matter and person.

This table is a practical review framework, not a statement that Clio performs every listed function in every configuration. The relevant functionality needs demonstration in the proposed UK account.

Billing assistance needs a financial approval boundary

The published material describes draft invoices, approval routing and matching expenses to matters. A useful implementation should make the draft status visible and retain a clear decision about what is billed.

Check the underlying time entries, client agreement, matter, rate, tax treatment and any agreed cap or write-off. An AI-generated description should not invent work, overstate what was done or conceal a correction. The person approving the bill needs to understand the source entries.

Measure the quality of the final approved invoice. A faster draft is not a saving if it produces more disputed entries or requires a longer reconstruction. Also establish what the system may do automatically and what requires an authorised approver; do not infer that an attractive billing workflow should be allowed to send or collect money unattended.

Client updates are consequential communications

A summary based on matter activity can help a practice communicate consistently. It can also repeat an old assumption, omit an important qualification or tell the wrong person something they should not receive.

For family work, the distinction between allegation, assessment and judicial finding must survive the rewrite. A note that says a professional “raised a concern” should not become a message saying the court “found” the concern established. Nor should a draft order be presented as a sealed order.

Before any external communication, check the recipient, current procedural position, agreed scope and next step. The pilot should identify whether the proposed product configuration merely drafts or can also send, and how that boundary is controlled. Convenience is not a reason to remove an approval stage with a real protective purpose.

Three hypothetical practice-management exercises

A revised order with conflicting dates

Create a mock file containing an earlier direction, a later variation and an email discussing a proposed date that was never ordered. Ask for proposed calendar entries with document references. The correct human ledger identifies the current date and marks the unapproved proposal separately.

The test fails if the system chooses the most recent email merely because it is newest, or retains two contradictory deadlines without explaining the conflict. It should also be possible for a reviewer to reject a proposed entry without losing the source record.

Month-end billing with deliberate exceptions

Use invented time and expense entries across two fictional matters. Include a duplicated expense, an agreed fee cap and an entry requiring clarification. Ask for a draft bill and exception list.

The useful outcome is a reviewable draft with unresolved items visible. Do not count a shorter approval queue as success if the system has quietly decided the exception. These are test designs, not completed Clio results.

A sensitive client update

Build a fictional matter with a disputed allegation, a new hearing date and a protected contact route. Request a concise update for the client. Check factual status, tone, recipient and whether the wording introduces advice or promises not supported by the record.

Repeat after changing the contact preference. The workflow should respect the current approved route, rather than infer that any address stored somewhere in the matter is safe to use.

England and Wales deployment: local law still controls

A UK product page and UK billing currency are useful evidence of a domestic offering. They do not show that every generated application, procedural suggestion or deadline calculation is legally correct for England and Wales.

Distinguish an express direction in a court order from a general rule, a local practice requirement and an internal target. The practice needs a competent person to resolve legal ambiguity. A calendar entry is an operational record, not the authority for the obligation.

Similarly, imported terminology from international product material should not determine domestic procedure. If a drafting feature refers to motions or discovery, confirm what that means for the actual UK task. Do not assume a generic template is a prescribed family-court form.

Matter data, permissions and integrations

An assistant grounded in practice data is only as useful as the data it can legitimately access. Start by checking matter labels, document versions, contact roles and access restrictions. If the underlying records are incomplete or inaccurate, automation may reproduce the problem faster.

Ask which connected systems are involved, what information is copied and where the system of record remains. Establish how a revoked permission or corrected contact propagates. A safe trial includes an account that should not be able to see the sensitive matter.

Test export and recovery. Can the practice reconstruct the source of an entry, identify who approved it and correct it without losing the audit context? Can it retain usable matter and task records at the end of the subscription? We have not verified a single audit or export configuration across every Clio plan.

Confidentiality, retention and the scope of supplier assurances

Clio publishes AI principles and product-level information. The customer still needs the applicable service terms, data-processing agreement, subprocessor list and account controls for the particular deployment.

Ask about prompts, source documents, proposed actions, logs, support access and retained outputs. Identify where processing occurs and what happens after deletion or termination. Do not generalise a promise about one Clio product to every connected service without checking.

For family papers, the legal authority to transmit information and the court’s restrictions remain relevant even where a practice already uses a case-management system. Enabling a new processing function can change the data flow. Use synthetic records for the pilot until the relevant legal and governance checks have been completed.

The hub explains the common framework. It does not certify any individual practice’s configuration or assume a supplier’s public statement resolves privilege.

Pricing: a current starting price is not a complete quotation

On 23 October 2026, Clio’s UK pricing page displayed practice-management plans starting at £79 per user per month, with further tiers and configurations. That is the published starting point, not a verified total for every AI workflow, tax position or contract term.

Confirm the exact plan, AI entitlement, billing period, minimum users, additional modules, migration, training and VAT treatment before committing. Older Duo add-on prices should not be assumed to describe the current offer.

The incremental value may be strongest for a practice already using Manage effectively. If adopting the AI also requires moving the entire practice-management system, compare the full migration and operating cost, not simply the attraction of an assistant.

A pilot that measures safe completed work

Test one calendaring task, one billing task and one communication task separately. Prepare the correct answer ledger first, including exceptions and current permissions. Record what the AI proposed, what the reviewer changed and what was finally approved.

Critical failures include an incorrect operative deadline, unauthorised recipient, invented billable work or action without the required approval. Those should stop the relevant workflow. Minor drafting improvements do not compensate for a failure in one of those controls.

Re-run after a source document or contact instruction changes. The meaningful measure is the time and reliability of the final reviewed action, including correction and supervision. We make no numerical saving claim for Manage AI.

Alternatives and JSH Law’s assessment

Vincent by Clio is relevant if the main need is legal research. Wordsmith addresses in-house intake and business workflows. ChatGPT may help with general drafting, but does not by itself provide the same matter-management system or approval structure.

Our assessment: a plausible administrative improvement for practices with reliable Clio matter data and clear approval responsibilities. It should be tested as a set of consequential workflows, not treated as an all-purpose legal adviser. The strongest implementation keeps the source, proposed action and human decision visible.

Can Manage AI take responsibility for a missed deadline?

The practice remains responsible for its work. A tool’s extraction or suggestion does not replace checking the order, trigger and applicable procedure.

Is an AI-generated bill ready to send?

It should pass the practice’s normal financial and client-agreement checks. Draft generation and authorisation are separate stages.

Sources and methodology

Reviewed on 23 October 2026: the Manage AI history, UK feature page, current UK pricing and AI principles. This is a documentary review; no live matter, billing run or account permissions were tested. Final entitlements and contract terms require confirmation. Recheck after changes to pricing, action permissions, deadline handling or integration scope. See the research hub for the wider methodology.

For help understanding and organising what a family-court order requires, JSH Law’s case-navigation support may be relevant. Book a Consultation with the immediate issue and next date; do not rely on software alone where the legal requirement is uncertain.