Does AI Document Review Work on Foreign-Language ESI?

A scanned page with no text layer is invisible to search, in any language.

The Sedona Conference's April 2026 Working Group 1 agenda said it plainly: "Additional guidance is necessary for the industry to reasonably adopt Generative AI tools in discovery practice," which is to say the process you run is still yours to defend. Skip that and nothing breaks loudly. Even machine translation ships without promises: Gartner's software review site notes that Google disclaims all warranties for the Google translations the site may show, including accuracy and reliability. (No one gets an alert about a document that was never there.)

Courts have mostly stopped asking whether the model is allowed. In Schulte v. LinkedIn, the court let LinkedIn run Relativity aiR for final responsiveness calls after a search-term pre-cull, and found that pre-culling "reasonable and proportional" largely because the plaintiffs had not shown the terms were defective. Fine. Which is to say the scrutiny now sits upstream, with whatever the keywords and the extracted text let through.

A Portuguese email the search terms never matched is gone. So is a scanned contract with no text layer. The competence duty already reaches the risks of the technology a lawyer picks, and these tools are still just tools, with a human expected to check what the machine skipped.

When the tools can't sort a set, everyone goes back to reading: a lawyer in an April 2025 r/LawFirm thread tried search terms and predictive algorithms on 40,000+ documents for production and concluded a full manual review "may be warranted."

Does AI document review actually find foreign-language documents?

Yes, for files whose text was extracted, OCR'd and language-tagged first. AI-assisted review runs cents per document instead of dollars, but only on documents the index can actually read.

Before trusting an AI-coded result on a mixed-language matter, check three things, in this order:

1. Every image-only file went through OCR, optical character recognition, the step that turns a picture of words into searchable text.
2. Every document carries a language tag applied before indexing, so the system knows a German email is German and treats it that way.
3. Someone has read the exception report, the list of files that failed either step, and decided what happens to each one.

The money explains why everyone is asking. Our own pricing case is blunt: manual review costs dollars per document and roughly $19K/GB, while AI-assisted review costs cents. That gap is real. It is also conditional, and the condition rarely makes the slide deck (it applies only to documents the system could see in the first place).

The thing is, a missed foreign file is not just a budget leak. In an April 2025 Daily Journal column, JAMS neutral Daniel B. Garrie and Baker & McKenzie partner Bradford K. Newman argued that Comment 8 to ABA Model Rule 1.1 makes eDiscovery and AI competence part of a licensed attorney's duty of competence. That comment asks lawyers to keep up with "the benefits and risks associated with relevant technology." The same authors warn that AI review can expose a party to arguments of "under-inclusivity" in the data sets searched.

An untagged Japanese contract is under-inclusivity in its purest form. Nobody decided to exclude it. It simply never existed as far as search was concerned.

The common assumption is that a file the AI cannot read throws an error. It does not have to. Keyword and concept search return what matches, an empty text layer matches nothing, and the document sits in the database marked as processed while staying invisible to every query you run (which is honestly worse than a crash, since a crash at least gets someone's attention). The reviewer-side version of this mess is covered in how foreign-language documents get buried in review; this piece is about the step before anyone reviews anything.

So I care more about the processing record than the model. Relevant keeps immutable originals with content hashing, an append-only audit trail and documented chain of custody, so what happened to each file can be shown if opposing counsel pushes. Pairing that defensible spine with cited answers is the whole design; a fast answer you cannot trace is just a confident guess.

Homemade setups skip the processing step entirely: a lawyer in a February 2026 r/legaltech thread described pasting document chunks into ChatGPT ("Death by a thousand Ctrl+C / Ctrl+V cuts") and losing context with every new chunk, so the model only ever judged what it was handed. To be fair, there is a trade-off. Tools that hide processing behind one upload button feel wonderful on day one and much less wonderful when you have to explain a single missing file to a judge.

And most published advice on multilingual review never reaches that step, because it starts with the translation bill.

Why is translation cost the wrong first question?

Translation only helps documents the system already found. Linking every AI answer to its exact exhibit shows what was found, not what processing quietly dropped.

Most published advice on multilingual discovery opens with the translation budget and never really leaves it. A May 2023 piece by Jeffrey Patanindagat for the Association of Certified E-Discovery Specialists (ACEDS) defines multilingual e-discovery as "the use of technology and specialized techniques to collect, process, review, and produce electronic data in multiple languages," then spends its energy on language barriers, cultural nuance and the expense of traditional translation. It says the tools "can provide accurate translations." It also says accurate translations "can be difficult to obtain, unless done through professional translators."

Both claims assume the document is already on someone's screen. Neither asks how it got there.

Conventional wisdom treats foreign-language ESI as a cost line: so many pages, so many cents per word, a bilingual reviewer at a premium. Fine, as far as it goes. The trouble is that it skips the question deciding whether any of those costs matter at all.

Before: What will it cost to translate the Portuguese emails?

After: How many of the Portuguese emails can our search actually see, and how would we know if the answer were zero?

The second question is less fun at a budget meeting. It is also the one that decides whether the first question matters. Translation is downstream of retrieval.

Even the ACEDS piece closes on a caution worth keeping: tools are "just that, tools," and a full investigation needs a balance of expert human and machine work. Human balance only helps if the human sees the file.

Here is where I have to be straight about our own design, too. Our outputs link back to the exact exhibit they came from, so an attorney can verify any AI answer in one click before filing. That is a genuine guard against invented citations. It verifies what the system returned; it depends on the document having been indexed in the first place (which is, annoyingly, the whole subject of this article).

That is also why our demo asks you to bring a messy collection and a hard question, then watch the system read, code and cite your own evidence instead of reading a case study about someone else's. Bring the mixed-language collection. Bring the scanned one too.

Cross-border sets add a layer before language even enters the picture, because where the data sits can be restricted on its own. Deployment inside your own AWS account under your own keys handles part of that; the transfer rules themselves are worked through in moving EU employee data to a U.S. review platform.

None of this makes the translation bill disappear. Somebody still has to read the documents that matter, and people who read fluently in two languages do not come cheap.

When does AI review beat paying bilingual reviewers?

When every foreign file has readable, tagged text and is processed somewhere you control, single-tenant or inside your own AWS account, with no vendor retention and no model training.

Start with the labor price, because that is the number driving the decision. An American Bar Association career guide for young lawyers puts average document review pay in Michigan at $20 per hour, and says plainly that a reviewer who can read a foreign language will earn "about double the usual rate."

That premium lands on the exact documents that are hardest to retrieve. Which is to say, the savings case is strongest precisely where the processing risk is worst. I find that genuinely funny, in the way a tax audit is funny.

Translation vendors tend to propose a middle path: machine translation for gisting, meaning a fast rough read of high-volume foreign email to flag what is obviously irrelevant or privileged. The same vendors concede that raw machine translation is generally not admissible in court, so anything you rely on still needs a human. Gisting is triage. It is not review.

Here is how I would route a mixed-language set before anyone books a bilingual reviewer:

1. Files with clean, language-tagged text go to AI coding first, with source-linked results an attorney can spot-check.
2. Image-only or failed-OCR files go back through OCR and language identification, then join the first group.
3. Whatever the AI flags as hot, privileged or ambiguous goes to a bilingual human, who now reads a short list instead of the whole pile.

The second condition is control, and it matters more for foreign data than people expect. Our processing runs single-tenant or inside the client's own AWS account, with no vendor retention and no model training, so nothing fed into it trains anyone's model or waives privilege. Privileged foreign-language files are still privileged files. Sending them to an outside party for a quick translation does not make them any less so.

I also think the economics only matter if a small firm can actually run the thing. We built for a solo or small firm on a single messy matter, the segment the big enterprise platforms price out and cannot serve without an administrator. If you are weighing how to pay for that, the trade-offs between per-matter and annual platform pricing for small firms are laid out separately.

None of the routing works if the second step never happens, and the second step is the one budgets tend to forget.

What decides whether foreign-language AI review works next year?

Processing, not translation. Ask for the OCR failures, the language tags and the exception list before any review savings get counted toward the budget.

The money is already moving upstream. ComplexDiscovery's 2025 review update put review at 64% of eDiscovery spending in 2024, projected to fall to 52% by 2029 as investment shifted toward collection and processing. In its Winter 2025 pricing survey with EDRM, about 50% of respondents were unsure how special processing or exception handling was priced in GenAI-assisted review.

Sit with that one. Exception handling is where a scanned Arabic invoice or an untagged German email ends up. If one of those files was a key document, a commenter in an April 2025 r/LawFirm thread spelled out the bill: opposing counsel "will start questioning why," and that "could result in a judge ordering a re-review costing more." (The Sedona Conference previewed a forthcoming Commentary on Rule 26(f) conferences at its April 2026 meeting; that conference is where to put language handling on the table with opposing counsel, before production.)

The figure I would want next is one this evidence does not contain: recall on tagged non-English files measured against recall on untagged ones, in the same collection. Once someone runs that comparison, it will show whether the savings were real or simply never checked. Start with the exception report. Then ask who reads it.