A translation glossary for interviews: terms, context and approved equivalents
How to build an interview translation glossary with the source term, context, meaning, approved equivalent, forms to avoid, decision source and review status.
The same term can call for different translations in different contexts
Interviews contain feature and product names, internal processes and industry jargon. A dictionary equivalent might be valid yet differ from the terminology readers use or from previously published material. A glossary records the chosen term and when it applies.
Start from the text instead of filling hundreds of rows in advance. Focus on recurring or high-risk terms: a product name, role, metric, legally significant term or abbreviation. Give each decision an owner and a source so it can be traced later.
Build the glossary around concepts and context
Find candidate terms in the transcript
Mark recurring terms, abbreviations and words that have a special meaning for the speaker. Keep the timecode and the surrounding sentence for each candidate. Include ordinary words only when there is a reason.
Describe the concept before choosing an equivalent
Briefly explain what the term means in this interview, what it refers to and how it differs from related concepts. If the meaning is unclear, ask a subject-matter expert before deciding how to translate it.
Record the decision
Document the approved term, register, plural form and variants to avoid. Add the source, such as official product copy, a governing document or confirmation from the term owner. Include the date because terminology changes.
Review the finished translation
Search the document for the source term and all its translations. Confirm that an equivalent was only applied where the concept matches. Add any new decision and its context to the glossary so that it can be found after the comments are resolved.
The word “release” in a team discussion
This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.
We use “release” for the point when a version is available to customers. An internal build is a “candidate.”
Rendering both terms as the Russian equivalent of “release” would lose the distinction. Record the speaker’s definitions: “release” is a version available to customers, and “candidate” is an internal candidate build. Choose the final Russian terms in line with the project’s existing terminology.
This example shows what the context column is for. If “release” later refers to the preparation process, it may need a different equivalent. That is a different meaning and should have its own entry.
| Field | Example | Purpose |
|---|---|---|
| Source term | release | Find occurrences |
| Context | Available to customers | Identify the meaning |
| Translation | Approved equivalent | Keep terminology consistent |
| Status | Expert-reviewed | Show readiness |
Terminology record
For ambiguous terms, create a separate record for each meaning.
Source term: Language and part of speech: Timecode / context: Concept in this project: Approved equivalent: Permitted forms: Forms to avoid: Abbreviation: Source of the decision: Owner / approver: Status and date: Translator’s note:
Check that the glossary is useful
- Each term has real context.
- The equivalent reflects the concept in the interview.
- The source and decision owner are listed.
- The finished text has been checked for competing variants.
A closer look
Should I add common words?
Only if they are ambiguous, recur or matter for consistency. Otherwise, they make the glossary harder to use.
Who approves the translation?
Assign an owner based on subject expertise and project rules. The translator can propose an equivalent, and a qualified source confirms disputed meanings.