How Claira and Legora Work Together

Legora has earned real adoption in legal practice. Founded in Stockholm and rebranded from Leya in early 2025, it now sits on desks at firms like Linklaters, Cleary Gottlieb, and Goodwin. Its pitch is a collaborative AI workspace for lawyers, and it delivers on that pitch. If your firm has already invested in Legora, the question is not whether to keep using it. The question is how it should relate to the AI review you run inside Nuix Discover.

We hear this question often, and the answer is not a turf war. Legora and Claira occupy different layers of the same litigation workflow. They were built for different jobs, they excel at different jobs, and when you connect them deliberately, each one makes the other more valuable. This article explains where the line sits and how to move work across it in both directions.

What Legora Does Well

Legora is a workspace where lawyers think, research, and draft together. Its Tabular Review takes a set of documents and returns a structured grid, one row per document and one column per question, with every cell linked back to its source. Its Workflows chain agentic steps like drafting, research, translation, and tabular reviews into repeatable processes that firms describe in natural language and adapt to their own templates. Word and Outlook add-ins put all of this inside the applications where transactional lawyers already live, and Portal extends the collaboration out to in-house clients.

That is a serious product, and firms are right to value it. For due diligence sets, financing packages, lease portfolios, and research memos, a collaborative workspace is exactly the right shape. None of this is in dispute, and we do not pretend otherwise.

The Job Legora Was Not Built For

What Legora does not do is live inside your eDiscovery platform. When a matter reaches litigation scale, Nuix Discover becomes the system of record. It holds the full collection with its family relationships intact, the coding panels your review team works in, the privilege log maintained alongside the review, and the production workflow that everything must eventually flow through.

Moving two hundred thousand emails out of that environment and into a workspace is not a workflow. It is a data transfer project with chain of custody questions attached. The workspace model works brilliantly for the hundreds of documents that matter to a deal. It breaks at the volumes and the defensibility requirements of discovery.

This is the job we built Claira for. Claira sits inside Nuix Discover, reads every document a human reviewer would have read, applies your review criterion, and writes its decisions back into the coding panels your team and your QC process already trust. A bulk scan can move through the full population, not a sample, and the results land as coded fields you can search, sample, validate, and produce from. We made the same argument about CoCounsel and Harvey in our guide to getting a useful Claira prompt from those platforms, and it applies to Legora without modification. The tools are not competitors. They are neighbours on different floors of the same building.

Feeding Legora's Thinking Into Claira

Here is where the two tools start to feed each other. By the time a matter reaches first-pass review, your team has usually done substantial thinking in its workspace. In Legora, that thinking might live in a research memo, an issues list built through a Workflow, or a Tabular Review that mapped the key agreements and the people who signed them.

That work product is precisely what Claira needs to review well. Claira's Case Context feature lets you give the AI background on the matter before any scan runs: the parties and their roles, the disputed events, the vocabulary your custodians actually use, and the issues that make a document matter. A case theory developed in Legora translates almost directly into a strong case context. The names, dates, and project code words that surfaced in your workspace research become the anchors that keep a bulk review consistent across every document in the population.

The same handoff works for review criteria. Ask your workspace to summarize the allegations, the defences, and the categories of documents each side will care about. Then distill that summary into the substantive question a reviewer would ask of each document. That question, refined with exclusions for the routine traffic you do not want flagged, becomes your Claira prompt. The lawyers do the legal thinking where legal thinking is best supported. Claira applies it at scale, one document at a time.

Feeding Claira's Findings Back Into Legora

The flow runs the other way once the review is done. A completed Claira review leaves you with a coded population: the relevant set, privilege calls awaiting counsel review, objective coding fields, and document summaries written into the workspace fields your team defined. From the full collection, you now know which few hundred documents actually matter.

That curated set is the ideal input for Legora. Export the hot documents and their summaries, and your workspace becomes the place where the second phase of thinking happens. Run a Tabular Review across the key documents to extract the facts a chronology needs. Draft the witness interview outline in Word with the source documents linked beside it. Share a curated bundle with the client through Portal instead of a raw production nobody in-house will read.

The pattern is a loop, not a pipeline. Workspace thinking shapes the review. Review findings sharpen the workspace thinking. Each pass through the loop makes the next one faster, because the case context grows richer and the document set grows more focused.

Where to Start

If your firm runs both platforms, pick one live matter and connect them on purpose. Take the case memo your team already built in Legora and turn it into a Claira case context. Draft a review prompt from the issues list. Run it against a sample of one hundred documents in Nuix Discover, check the results against a senior reviewer's calls, and adjust before you scale to the full population. Then bring the top documents back into Legora and let the drafting begin from evidence rather than memory.

None of this requires replacing anything. It requires knowing which tool owns which layer, and building the handoffs between them. If you would like to see what that looks like on your own Nuix Discover environment, book a short demo with our team and bring a matter you know well. The connection between your workspace and your review is closer than you think.