Contractual document

Specification translation

A specification is not documentation: it is a contractual instrument. An ambiguity introduced in translation is not spotted on reading — it surfaces when the supplier delivers, by which point correcting it means an amendment.

In 30 seconds

We translate technical and functional specifications per source word, from €0.10 excl. VAT depending on the language pair. The glossary is locked and approved by your teams before the first line is translated, because one term must mean one thing in every clause. Units, tolerances and cross-references are never altered without telling you. Indicative turnaround: 1 to 2 business days up to 2,000 source words.

Why this document is translated differently

In a brochure, an approximation shows and is forgiven. In a specification it becomes a poorly defined contractual obligation. The supplier delivers what the translated text says, not what you had in mind: the version they signed is the one that binds them.

The risk almost never comes from technical vocabulary, which specialist translators handle well. It comes from obligation levels, from units, and from cross-references between clauses — three things a quick proofread does not check.

What we translate under this heading

Functional specification

Needs expressed as functions and expected outcomes, without prescribing the solution. The difficulty is not to harden into a technical requirement what was written as a need.

Technical specification

Specifications, tolerances, materials, testing and acceptance criteria. Numerical values are carried over exactly, never converted without written instruction.

Tender technical documents

Particular technical clauses and the annexes of a tender. They are translated with the instructions to bidders in view, since that document states what has to be translated.

Annexes, drawings and parts lists

Annexes are part of the document. Tell us which ones fall inside the scope: a parts list running to several thousand lines changes the quote entirely.

The four safeguards we apply

The glossary is locked before we start

Your in-house terms, component designations and test names are settled and approved by your teams before translation. Without that, the same term gets two renderings in two clauses — and that is precisely what ends up being argued over.

Obligation levels are preserved

Shall, must, should and may do not bind in the same way, and normative conventions differ between languages. We render the level of obligation, not merely the sense of the sentence.

Units and tolerances are not converted silently

No metric or imperial conversion is made on our own initiative. If your recipient needs one, it is added visibly, alongside the original value, never in its place.

Cross-references stay valid

A specification refers from one clause to another and to its annexes. Numbering, clause headings and cross-references are preserved, so that a reference still points at the right clause after translation.

How a project runs

1
Reading and scope
We read the document, identify the annexes and tell you what is worth translating and what can stay in the source language. The quote follows that discussion rather than preceding it.
2
Glossary submitted for approval
Recurring terms and designations are extracted, then sent back to your teams. This is the step that determines the quality of everything after it.
3
Translation by a subject specialist
A technical translator from the relevant sector, working from the approved glossary and a translation memory specific to your company.
4
Review targeted at the risk points
Beyond linguistic review, a separate check covers numerical values, obligation levels and cross-references between clauses.

What we do not do

We do not write your specification and we do not correct it: if the source text is ambiguous, the translation will be too, and we flag the passage rather than deciding on your behalf. We do not certify the document's technical compliance with any standard, and we are no substitute for your engineering department. Asiatis also holds no ISO certification and claims none.

Frequently asked questions

How much does it cost to translate a specification?

Per source word, from €0.10 excl. VAT depending on the language pair, with the full rate card on our rates page. The annexes often weigh more than the body of the document: the quote becomes firm once we have read the files.

Do all the annexes have to be translated?

Rarely. Drawings can often stay in the source language provided their captions are translated, and a parts list only matters if the recipient has to order from it. We make that selection with you at quotation stage, because it changes the budget considerably.

Do you convert units of measurement?

Never without written instruction. A conversion made on our own initiative inside a contractual document amounts to amending the specification. Where a dual indication helps, we add it beside the original value, not instead of it.

Can you work from a glossary we already have?

Yes, and it is the best possible starting point. Send it in whatever shape it is in, even incomplete: we fold it in, flag the missing or contradictory entries, and you decide.

Is a sworn translation required?

Not in most cases: a specification circulates between companies, with no authority to satisfy. Sworn translation only becomes relevant if the document is produced before an administration or a court, for instance as evidence in a dispute.

Technical translation Technical manuals Contract translation Sworn translation for tenders

A specification to translate?

Send us the document and its annexes, with the target language and the date you need. We will tell you what is worth translating and what can stay as it is. Reply within 60 minutes on business days.