How Foreign-Language Documents Get Buried in Review

The foreign-language page is usually already in the pile. The question is whether anything flagged it.

Before a lawyer opens a single file, processing has already stamped each one with a language code, and the question worth asking is what happens when the stamp is wrong. Everything downstream inherits the mistake. Search reads the wrong words. Reviewers get the wrong batch.

A 2024 issue of Kiran Nasir Gore's newsletter Law & Global (Dis)Order drew the line plainly. Keyword search relies on exact word matches. Conceptual search uses natural language processing to surface relevant documents even when the specific keywords were never used. The same issue reported that a Texas federal judge had ordered litigants in that courtroom to certify their use of generative AI, so courts had already started asking what the machine actually did.

Conceptual search sounds like the cure. It isn't, quite. It can only weigh the text the index gave it, and an index that tokenized (chopped into searchable words) a German contract as broken English is handing it gibberish with excellent formatting.

Most review platforms already offer machine translation, which I appreciate the way I appreciate a fire extinguisher kept in a locked closet. The button works. Agencies and clients once trained reviewers on review platforms, but a 2025 r/ediscovery commenter said "generally, they don't do that anymore," so the reviewer may never have been shown where the language tag lives. Has anyone looked at yours?

What actually buries a foreign-language document in review?

Foreign-language documents get buried before anyone translates them, and with manual review at roughly $19K/GB against cents per document for AI-assisted review, a mislabeled language tag gets expensive fast.

When a document that should have turned up does not, I would check three things before blaming anyone's Spanish:

1. Whether the file has a text layer at all, or is a scanned image that search cannot read.
2. What language processing stamped on it, and whether that matches what a human sees on the page.
3. Whether its text was broken into search terms using rules built for its own language or for English.

The common assumption is that foreign-language evidence gets lost in translation. That assumption is wrong about where to look. A document has to clear text extraction, language detection and indexing before a search can return it. Translation only happens to documents a search returns.

Two terms carry the rest of this article. Language detection is the processing step that reads a document and assigns it a language code. Tokenization comes next: it splits the text into the individual terms an index stores and a search later matches.

Picture a Portuguese email thread with an English confidentiality notice at the bottom. The notice is long. It is, I should mention, longer than the email. Processing reads the whole thing, decides it is English, and indexes it with English rules. Nobody did anything wrong, exactly. The email now sits in a pile for a language it barely speaks, waiting for an English search term that will never match a Portuguese word. It is a dinner guest seated at the wrong wedding, too polite to mention it.

Translation vendors themselves say the machine translation built into review platforms may be enough to judge relevance during discovery. Fair enough. It is also beside the point for a document nobody opens. The expensive mistake is rarely a bad translation. It is a good translation of the wrong documents.

Fixing a misrouted file means reprocessing it, which makes careful litigators nervous. In our platform, originals are immutable and content-hashed, the audit trail is append-only, chain of custody is documented, and production sits behind a fail-closed privilege gate. A file re-indexed under the right language is provably the same file that arrived at intake. Relevant e-Discovery keeps the defensible spine (Bates numbering, privilege, chain of custody) and the cited question-and-answer layer in one tool, so the routing fix and the record of that fix live in the same place.

Combining 4 sources points to one practical question for whoever processed the collection: which language was each custodian's mail tagged with, and did anyone check? It is the same trap behind why searching Outlook isn't a defensible document review, since a search can only vouch for what it was able to see. And what it can see depends on a small, confident machine guessing which language you speak.

How does a wrong language tag hide a document from search?

A wrong language tag hides a document because search, and any AI answer built on search, can only cite text indexed correctly. Source-linked answers make that gap visible.

Language detection reads character patterns and picks the single most likely language for a file. That works well enough on a clean French contract. It works less well on the documents litigation actually produces:

• Email threads that switch languages halfway down, with an English disclaimer underneath.
• Chat messages too short to carry much signal, full of slang and shorthand.
• Scanned pages whose text came out of OCR as a scramble of characters.

Once the tag is set, tokenization follows it. An English analyzer splits text on spaces and trims English word endings. Apply that to a language written without spaces between words, and a whole phrase can collapse into one long term nobody will ever type. Apply it to a heavily inflected language, and the different forms of one word never meet. The text is in the index. The words a lawyer would search for are not.

One legal translation vendor argues that keyword lists must be dialect-precise so regional variations are not missed, and that standard AI often mangles the slang in WhatsApp conversations. Both points are fair. Both also assume the document was indexed under the right language in the first place, which is the part nobody checks.

Another translation provider makes a quieter point: foreign-language material turns up even when every client speaks English, because clients write to people who do not. So no matter is safely monolingual. Assume a tag is wrong somewhere until you have looked.

This is where source-linking earns its keep, and also where it runs out. In our review platform, every answer links back to the exact exhibit it came from, so an attorney can verify it in one click before filing. That protects you from an answer that cites nothing. It cannot protect you from an exhibit that never made it into the index to be cited. A citation is a receipt, not an inventory.

I have some sympathy for the detector, I should say. Tune it to doubt itself and more files go to the slower, pricier foreign-language queue; tune it to be confident and more files quietly dissolve into English. Neither setting is free. I would rather pay for the doubt.

Reprocessing those files also raises a custody question. Our platform can run inside your own AWS account under your own keys, so re-detecting, re-indexing and machine-translating a privileged foreign-language memo happens where the memo already lives. The alternative, pasting it into a free browser translator to find out what it says, feels efficient right up until someone asks where the memo went.

The honest test is your own collection. Our demo asks you to bring a messy collection and a hard question, then watch the tool read, code and cite your own evidence, mixed languages included. It is the same instinct behind checking what one-click cloud collection tools miss before trusting them: look for the gap on your data, not on someone else's. Then look at who was assigned to read whatever came out the other end.

Who ends up reading a misrouted document, and how do you stop it?

A misrouted document lands with an English reviewer who cannot read it. The fix is a routing check before batching, run where privileged evidence never leaves your control.

Review labor is sorted and priced by language, so the tag decides who reads a file. A 2024 thread on the r/ediscovery forum put the national average for English-language review projects at twenty-something an hour, with wages that had stayed flat instead of rising with inflation. The same poster, a self-described believer in technology, argued that AI could not yet handle QC, privilege logging or spotting hot documents, and that the best approach paired AI with review attorneys.

Notice the qualifier. English-language. A German email tagged English goes into that batch, at that rate, on that clock. The reviewer then has three options: guess, skip, or flag it. The batch clock rewards the first two.

So the tag is not a technical detail. It is a staffing decision made by software.

Scanned files make it worse. One practice-management vendor notes that image-based PDFs are effectively invisible to AI assistants until OCR adds a text layer, and it lists foreign-language records among the files that tend to arrive that way. A document with no text has no language. It simply gets whatever default the system assigns, and then it waits.

Before any batch goes to people, I would run three checks:

1. Confirm every file has extracted text, and send image-only files through OCR before language detection runs.
2. Pull a sample of documents tagged English from custodians and sources known to write in other languages, and have a human read the first few lines of each.
3. Re-index anything re-tagged with rules for its actual language, machine-translate it for gisting, and only then batch it to reviewers who can read it.

Before: a supplier's Japanese emails sit in an English batch, coded quickly and forgotten. After: the same emails are flagged at intake, indexed with Japanese rules, gisted by machine, and handed to someone who reads Japanese. Same documents. Different case.

Where those checks run matters as much as whether they run. Our processing keeps no vendor copy and trains no model on what you feed it, so a re-detected, re-translated privileged memo does not train anyone's model or waive privilege along the way.

Relevant e-Discovery was built for the matter where this bites hardest: a solo or small firm with one messy collection, the segment Relativity and Everlaw price out and cannot serve without an administrator. Those firms have no administrator to notice a bad tag. The check has to live in the tool.

Taken together, these 4 sources point one way: language routing is a review decision, and it belongs before the first batch. It is the same lesson behind why AI semantic search still misses the documents that matter, which is that no search, however clever, finds what processing has already filed in the wrong drawer. And once a buried document does climb out of that drawer, a court will want to know exactly how its English version was made.

Where should a small firm spend first on a mixed-language collection?

Spend first on checking which language each document was tagged as, then on translation. In Texas, a translation offered at trial needs a translator's affidavit or declaration, provided forty-five days ahead.

In 2025, a translation-industry founder put human-quality translation at roughly $1 a sentence. Nobody translates everything at that price. Over the next year or two, I expect translation to become a late and selective purchase, saved for the documents headed to a deposition or an exhibit list, which means the language tag quietly decides what gets bought.

Gore's newsletter made a point about clustering that deserves a second reading. Clustering groups documents by content or theme so that privilege, confidentiality and non-responsiveness calls get applied uniformly across the set. Uniformly is the catch. A cluster built on misread text spreads one wrong call across every document in it, with perfect consistency, which is the worst possible way to be consistent.

So before the next batch goes out, open a few documents tagged English from the custodian most likely to write in another language. If one of them turns out to be Portuguese, you have your answer, and possibly your weekend.