Legal translation: why changing the word changes the obligation

In any transaction that crosses a language, both sides sign two texts. Each party reads its own version and assumes it says precisely what the other one says. Most of the time that assumption holds. When it does not, the problem rarely surfaces on signing day — it surfaces months later, at the first disagreement, when it is hardest and most expensive to fix.

The idea we come back to on every file is a simple one: a translated document is not an accompanying paper. It is the document itself, in another tongue — and the body receiving it will read it exactly as seriously as it reads the original.

One: a term is not a synonym

Many legal terms have no single counterpart in the other language. They have several, each with a different scope. Choosing between them is not a stylistic decision — it defines the extent of the obligation.

Take a clause setting compensation for delay. One rendering can make it a ceiling, beyond which nothing further may be claimed. Another can make it a floor, leaving the door open to claim the difference. To a quick reader the two look equivalent. In application they are not remotely the same.

A translator who picks on linguistic frequency alone can produce a text that is impeccable as language and broken as an instrument. Choosing correctly requires knowing what the clause does, not how it reads.

Two: structure carries meaning

Clause numbering and ordering are not decoration. Contracts refer to themselves constantly: “subject to clause 7.2”, “save as set out in Schedule B”. When a translator reorders paragraphs or merges two clauses because it flows better in the target language, those internal references break silently. The result looks elegant and cannot be reconciled with the original clause by clause.

So numbering, tables, and the position of signatures and seals are preserved, even where the original ordering is the clumsier of the two. Function before elegance.

Three: the receiving body sets the form

We always ask, before starting: who will receive this document? The answer is not procedural curiosity. It settles three things at once:

• The terminology that body accepts, which is not always the terminology common in the market.
• The form of delivery: a stamped hard copy, a digital file, or both.
• What must accompany it — a translator’s declaration, credentials, or neither.

A linguistically flawless document can still be refused for arriving in the wrong form. That is an avoidable failure, and one question at the outset avoids it.

Four: numbers, dates and names

The costliest mistakes are rarely in the difficult terminology. They are in the simplest elements:

• Dates — day/month order differs between conventions, and confusing them moves an entire due date.
• Numbers — the decimal point and the thousands separator swap places between languages.
• Names — they must match the party’s official documents, not how they are pronounced.
• Currencies and units — stated explicitly, never left to context.

These are checked a second time after the translation is complete, separately from the reading of the text, because the eye passes over them without seeing them.

Five: confidentiality is not an add-on

A document sent for a quote is not published, not used as a sample, and is deleted on request. Papers do not travel beyond the team assigned to the file. That is the default position, not a service to be asked for.

What actually reduces the risk

• Send the complete file with its schedules, not just the disputed pages — a clause is understood in its context.
• Name the receiving body and the purpose of the document.
• Supply your company’s agreed glossary if you have one, or a previously accepted translation.
• Keep both versions side by side under the same numbering; that is what makes later reconciliation possible.
• Check the names and figures yourself before signing off — you know them better than any translator can.

In closing

Legal translation is precise linguistic work whose purpose is that the other party — and the body that will examine the file — reads the meaning you intended. It offers no opinion on a document’s validity, its effect, or what should be done on the strength of it; that is a separate scope, agreed separately. But its accuracy is what makes that conversation possible in the first place.