Quick read · Translation & Business Travel
Technical interpreting is not business interpreting with harder words. It is a different job: the interpreter has to hold a term for a component, a process and a defect at the same time, and decide within a second whether to translate literally or explain. Most bad technical sessions fail on preparation, not on language.
What the job actually involves
Three settings, three demands. A design review needs precision and the willingness to interrupt. A factory trial needs speed and physical context — pointing at a machine beats describing it. A quality dispute needs neutrality, because both sides will read the record afterwards.
What has to happen before the meeting
- The drawing or spec sheet, in advance, not at the door
- A glossary of the ten terms that will decide the meeting
- The names of the people attending and what each one decides
- Whether the session will be recorded, and who keeps the notes
Where it breaks
Three recurring failures: the interpreter summarises a technical answer instead of translating it; the session runs without a written record so verbal commitments evaporate; and the glossary is built on site, which means the first hour is spent inventing vocabulary. All three are avoidable with one hour of preparation.
How to judge a technical interpreter
Ask for a short test on your own terminology, not a general language test. Ask which sector they have worked in most. Ask whether they are willing to say “I don’t know this term” rather than guess — the second behaviour is what protects your meeting.
The test that separates a technical interpreter from a good one
Give both candidates the same drawing fifteen minutes before a mock meeting and watch what they do with it. A good interpreter asks what the part does. A technical one asks which dimension is critical, whether the tolerance is bilateral, and what the surface callout refers to — because those three answers decide how a sentence gets translated.
The second test is silence. In a technical meeting, a competent interpreter stops the speaker when a term is ambiguous instead of guessing. Fluency without interruption is usually fluency without comprehension.
Next step
Send the drawing and the meeting date. We will tell you which terms need to be agreed before the session, and who is available.
See interpreting scope or send the drawing.
Related reading
Where this guide connects
This page is one entry in a category. The service behind it is where the work actually gets done.
Send a request →