Subpoena Translation Services

One Subpoena, Two Translations, One Terminology Base

Every subpoena that crosses a language line creates work in two directions, and most vendors only think about one of them. Direction one goes out: the command itself, the attached rider, the definitions and instructions, the date and place of compliance, all of it has to reach a recipient who reads Korean or Portuguese or Farsi and has to reach that person in a form they can act on. Direction two comes back: forty thousand pages of invoices, chat logs, board minutes and shipping manifests in that same language, landing on a review platform staffed by attorneys who read English.

Jurilingua runs both sides of that exchange on the same matter, with the same glossary and the same reviewers. The words used in the demand are the words used when the answering documents are rendered, which sounds obvious until you have watched a production come back where the custodian's term for a purchase order was translated three different ways by three different agencies and the privilege log stopped matching the document set. Consistency here is not aesthetic. It is what lets you argue that a production is deficient, or defend that yours was complete.

Forty years of legal work sit behind that discipline. We opened in 1984, and the two-reader rule has applied to every file since: one specialist translates, a second checks the rendering against the source before anything is released to a client. Litigation teams score us 4.8 out of 5, and the comment we see most often has nothing to do with prose quality. It is that we answered the phone on a Friday afternoon when a compliance date was Monday.

Compelling a Custodian Who Does Not Read English

Rule 45 gives a subpoena real teeth, but teeth only bite where the recipient understood the bite was coming. A witness who receives an English document she cannot read has an argument, and courts are not indifferent to it. That is why counsel translate a subpoena before service whenever the recipient's working language is not English: a foreign-born treating physician in a personal injury case, a warehouse operator in a supply chain dispute, a bank branch manager whose records are the entire case, a former employee who moved home three years ago and now reads only Tagalog.

What we translate is the whole instrument, not a summary of it. Command language stays imperative. The place, date and time of compliance stay unambiguous, with formats adapted so a European reader does not misread a US date and appear a month late. The rider listing categories of documents keeps its numbering, because objections will be made category by category and the numbering is how everyone stays aligned. The notice of rights and the text setting out protections against undue burden are translated in full, since stripping them is the fastest way to hand the other side a motion.

Deposition subpoenas get particular attention. A witness needs to know that she is being ordered to appear and answer questions under oath, that she may bring counsel, and what happens if she does not show. Third-party subpoena work is where that clarity matters most: the recipient has no lawyer in the case, no stake in the outcome, and no reason to guess at what an English legal form wants from them. Our witness statement desk often picks up the same matter later, when that person's account has to be reduced to writing.

Across a Border: Hague Evidence Convention, Letters Rogatory, Section 1782

A US subpoena does not travel well. Serving one on a person or company abroad usually means abandoning the subpoena as a self-executing instrument and moving into a mechanism the destination country recognizes. The Hague Evidence Convention route sends a Letter of Request to a foreign Central Authority. Letters rogatory go the slower diplomatic way. Applications under 28 U.S.C. 1782 run the other direction entirely, bringing a foreign proceeding's evidence needs into a US district court. Every one of these paths has a translation requirement written into it, and every one of them stalls when the translation is wrong.

Central Authorities reject filings. They reject them for missing certification, for a translation that omits an annex, for language that does not match the Convention's own vocabulary in the receiving state, and rejection costs weeks that your scheduling order does not have. We produce these packages the way the receiving authority expects them: certified translation of the request and its schedules, the underlying pleadings where required, the categories of evidence sought, and a signed attestation from the translator. Where a country requires a sworn or court-appointed translator, we route the file to one who holds that standing in the relevant jurisdiction.

Section 1782 applications carry the mirror problem. The foreign proceeding is described in a foreign language, and the district court needs to see it in English to decide whether the statutory factors are met. Foreign court orders, local counsel declarations and procedural rules all come across our desk in that posture, rendered so a judge who has never seen a Brazilian civil procedure filing can follow what stage it is at and what the applicant actually needs. The wider paperwork of a cross-border case sits with our pleading translation team, working from the same terminology file.

When the Production Comes Back in Another Language

A subpoena duces tecum served on a foreign supplier does exactly what you wanted, and then the pain starts. Twenty gigabytes arrive. The emails are in Mandarin, the attachments mix scanned purchase orders with spreadsheets, half the messages are WeChat threads full of abbreviations, and your review deadline is fourteen days out. Nobody budgeted to translate all of it, and translating all of it would be waste anyway, since most of it will never matter.

We work this the way experienced litigation teams work it, in tiers. First a fast machine-assisted pass with human calibration, enough for your reviewers to sort responsive from irrelevant and flag the hot material. Then full human translation of what survives triage: the documents going into deposition binders, the ones cited in a motion, the ones an expert will rely on. Then certified versions of the handful that will actually be shown to a court. Costs fall by an order of magnitude compared to translating a production wholesale, and nothing that matters gets missed on the way through.

Foreign language ESI brings its own traps. Character encoding that mangles Cyrillic on export. Date formats that reorder a chronology. Vertical Japanese text in scanned faxes. Chat platforms whose slang and internal shorthand carry the meaning a formal translation would flatten. Redactions applied in the source language that have to be preserved exactly in the target. We handle load files, Bates ranges and metadata fields so the translated set drops back into Relativity or Everlaw beside its originals rather than living in a separate folder nobody links to. The broader mechanics of that exchange sit with our discovery translation desk.

Objections, Motions to Quash and the Clock Behind Them

The fourteen day window for written objections under Rule 45 does not pause because a recipient needed the document translated first. Neither does the meet and confer that follows, the motion to compel, the motion to quash on grounds of undue burden, or the show cause hearing where a non-party explains why nothing was produced. Contempt is available at the end of that road, and judges have used it against foreign entities that treated an American subpoena as advisory.

Our scheduling assumes those dates. Upload the instrument and two things land in your inbox within thirty minutes: what it costs, and the hour it will be finished. No range, no promise to check capacity and call you back. Rush lanes exist for compliance dates already in motion, and they compress the calendar without dropping the second reviewer, because a subpoena that is served with an error in the compliance date is worse than one served two days later.

Objection and quash practice runs both ways too. When a foreign recipient files objections in its own language, or a foreign court issues a blocking order or a data protection ruling standing between the custodian and compliance, that material has to reach your judge in English and reach it credibly. Blocking statutes, GDPR-based refusals and state secrecy provisions are argued from their actual text, and we translate that text with the source preserved alongside so opposing counsel cannot claim you paraphrased in your favor. Certified renderings are available for anything filed, following the standards described on our certified translation page.

Who Sends Us Subpoenas and What They Get Back

Litigation boutiques send single subpoenas with a compliance date circled in red. Large firms send matter-length streams, dozens of third-party subpoenas across a multidistrict case, and want one point of contact who already knows the glossary. In-house legal departments send the ones landing on their own company as a non-party, which is a distinct and unloved position: you are not in the fight, you are paying to answer questions about it, and you want the cost controlled. Government contractors, banks, hospitals and logistics companies live in that category permanently. The support we build around those teams is described on our page for firms and legal departments.

What comes back is built to be used, not admired. Formatting mirrors the original so a court, a witness or opposing counsel can lay the two side by side and match line to line. Certification statements are signed and attached where certification is needed, with translator credentials available if anyone challenges them. Transfer is encrypted, storage is encrypted, and the list of people who can open the folder stops at the ones staffed on the matter. Non-disclosure runs on your paper, not on a form of ours. Pricing is per word and quoted by pair, with the memory built on your first job cutting what the next one costs.

The people doing the work are lawyers by background as often as they are linguists by training. That is the point of the bench described on our translator profiles page: someone who has drafted a document request knows why the definitions section of a rider is the load bearing part, and knows that instructions telling a custodian how to search are procedurally different from the categories telling him what to hand over. A subpoena translation company that misses that distinction produces something readable and useless.

The Languages Non-Party Records Arrive In

Custodians and their files show up in the languages of trade and migration: Spanish, the most common by a wide margin, Chinese for supply chain productions, Korean and Japanese in manufacturing disputes, Portuguese across the Brazil corridor, Russian in sanctions and asset tracing, Arabic for Gulf commercial matters. Past eighty pairs in total, all on the same review standard.

Where the Compliance Dates Are Set

Subpoenas reach this desk from courts and firms nationwide: New York City and its financial dockets, Washington DC for regulatory and congressional demands, Chicago, Houston where energy witnesses sit abroad, Miami and its Latin American record custodians, Los Angeles, San Francisco, Dallas, Newark, Boston, Atlanta and Seattle. The compliance date is what we schedule against.