Litera brings legal document comparison and firm search into Claude
The November addition connects Claude to Litera’s comparison engine and Foundation products. Existing licenses, administrator approval and user permissions determine what is available.
Litera’s connector gives eligible firms a way to invoke Litera document comparison, firm-knowledge search and selected business-record queries from Claude. The key distinction is that Litera’s rules-based engine—not Claude—is described as producing document redlines; Claude provides the conversational route to those tools. The practical reach depends on each firm’s Litera licenses, administrator settings and users’ existing permissions, so connecting Claude does not open all firm records to everyone.
01
Litera says its comparison engine draws on more than 30 years of development and detects changes in text, tables, headers and footnotes; those claims have not been independently tested.
02
The comparison workflow returns a redline and a link to Litera’s viewer, with a separate tool available to summarize the redline.
03
Foundation tools cover client and matter searches, relationships, collections and billing data, plus budgets and spending against budget.
Lawyers at eligible Litera customers can ask Claude to compare document versions and search their firm’s knowledge through a connector added in November 2026. The integration brings document review, client and matter searches, and financial queries into one chat interface. Access still depends on the firm’s Litera products, administrator approval and individual permissions.
A comparison engine behind the conversation
The document workflow begins with two or more versions uploaded for comparison. A user asks Claude to compare them, and Litera’s rules-based engine performs the comparison. The connector therefore links the request in Claude to Litera’s comparison system; the listing does not describe Claude itself as the engine that identifies the document changes.
Litera says that engine draws on more than 30 years of legal comparison development and detects changes in text, tables, headers and footnotes, among other elements. Those details put the stated scope beyond a comparison of the main paragraphs alone. The coverage and accuracy description comes from Litera’s marketplace listing, rather than an independent test.
The output is a redline—a document showing the differences—with a link to open it in the Litera viewer. Redline summarization is also among the listed tools. That gives the workflow two distinct outputs: a marked comparison available for inspection and a tool for summarizing the redline, rather than only a conversational description of what changed.
Search reaches firm knowledge and business records
The other major workflow starts with a question rather than uploaded versions. Firm AI Search, powered by Litera Foundation, accepts plain-language questions about clients, matters, people, packets and content across the firm. It returns results in a table that the user can review. This part of the connector is aimed at retrieving the firm’s own knowledge, not comparing documents.
Alongside that search function, the connector exposes three groups of Foundation tools. Each covers a different set of records or questions, from locating a client to checking financial information or examining a budget:
Foundation 365 supports listing clients, searching matters and understanding relationships. Its listed tools include client and matter lookups, giving users a route to specific firm records as well as broader searches.
Foundation Finance supports questions about collections, billing and other financial data. That places financial queries alongside the connector’s legal-document and firm-knowledge functions, within the same Claude interface.
Foundation Scoping supports finding budgets and reviewing summaries, details, categories and spending against budget. It also provides lookups for clients, matters and scoping codes, connecting budget questions with the records used to identify the work.
Availability follows the firm’s existing setup
The connector is for current Litera customers. Getting started requires a Litera Platform account, completed onboarding and a tenant administrator who has enabled the connector and granted the necessary entitlements. Finding it in Claude’s marketplace is therefore not, by itself, enough to make the listed functions available to a user.
Product licenses impose another boundary. Document comparison requires a Practice of Law Pro or Advanced license. Firm AI Search and the Foundation tools require the corresponding Litera Foundation products. A firm’s available workflow thus depends on which underlying Litera products it has, not simply whether it connects Claude.
Administrators decide both who can use the connector and which capabilities are enabled. Once connected, results remain limited to information the signed-in user is authorized to see. The new conversational route does not, according to the listing, give every user access to every firm record.
Reader comments
Newest comments first. Replies stay oldest first.