One term, several contexts

The same word might describe a machine part, a software function or a process step. The choice of term should reflect the product and its use, as well as dictionary definitions.

Start with a short terminology list

List brand and product names, parts, recurring operations and expressions that should stay in the source language. A simple table with the source term, approved translation and context note gives everyone a shared reference.

  • Source term and target equivalent
  • The product or system where the term appears
  • Wordings to avoid
  • Approval and version information

Include numbers and formatting in the scope

Units, decimal separators, table headings and figure references deserve the same care as the text. If units need converting for a target market, agree that separately before translation begins.

Make future versions easier to manage

Mark changes in updated manuals and keep the previous approved translation. Mention in your quote request whether this is a first translation or a version update.

Translation standards

Standards for technical translation and user manuals

Technical manuals need clear instructions as well as accurate terms, numbers and units. Explore our guide to ISO translation processes and the approach to information for use in IEC/IEEE 82079-1.

Read the guide

These pages describe an approach to quality informed by publicly available standard scopes and official guidance. They do not claim ISO certification, full conformity or institutional acceptance for Metis Global. The work and responsibilities that apply to your project must be confirmed separately in the quote.

This guide offers general preparation information. Check current requirements, deadlines and document acceptance conditions with the relevant institution.

Let’s start with your document.

Share the language pair, document type and target date.

Request a quote