A translation glossary gives translators, reviewers, and subject experts a shared record of preferred terminology. This guide explains how to build one, what fields to track, how to manage questions and approvals, and when to review the glossary so terminology remains consistent across documents, products, and languages.
Overview
A translation glossary is a controlled list of important source-language terms and their approved equivalents in one or more target languages. It may also record definitions, context, grammatical information, forbidden variants, and approval history. Unlike a simple word list, a useful multilingual glossary explains how a term should be used and what to do when a similar expression appears.
Glossaries are especially valuable for recurring content such as product interfaces, user manuals, legal documents, training materials, support articles, and marketing campaigns. They reduce avoidable variation, help translators resolve questions more quickly, and give reviewers a clear basis for checking terminology. A glossary does not replace human judgment: terms may change meaning according to audience, region, subject field, or document type.
Store the glossary in a format that the project team can maintain and search. A spreadsheet can work for a small project, while a terminology-management system may be more suitable for large content libraries or multiple language pairs. Before sharing files, check who can access them and whether they contain confidential product, customer, legal, or personal information.
What to track
Use the following fields as a practical translation glossary template. Not every project needs every field, but the same structure should be used consistently.
| Field | What to record |
|---|---|
| Source term | The approved term in the source language, including the exact spelling and capitalization where relevant. |
| Approved translation | The preferred equivalent for each target language. Record separate entries when regional variants are intentionally different. |
| Context | A sentence, screen label, document location, or short explanation showing how the term is used. |
| Part of speech | For example, noun, verb, adjective, or phrase. This can prevent an approved noun from being used incorrectly as a verb. |
| Subject field | The relevant area, such as finance, software, medicine, education, manufacturing, or customer support. |
| Definition or note | A plain-language explanation of the concept, particularly when a direct translation could be ambiguous. |
| Forbidden variants | Words or phrases that should not be used, along with a short reason when the choice may be unclear. |
| Review status | Use clear labels such as proposed, under review, approved, deprecated, or blocked. |
| Owner and review date | Identify the person or team responsible for a decision and record when it should next be checked. |
For example, a software team might list the source term “workspace,” approve one target-language equivalent, identify it as a noun, add a user-interface sentence, and forbid a commonly confused alternative. The context matters: a term used as a button label may need a different grammatical form from the same concept in a technical explanation.
Step-by-step glossary workflow
- Collect candidate terms. Extract repeated product names, feature labels, technical expressions, legal phrases, measurement units, abbreviations, and terms that reviewers have previously corrected. Do not add every word in a document; prioritize terms whose variation could affect meaning, usability, or brand consistency.
- Confirm the source meaning. Ask a subject expert to define ambiguous terms and identify differences between similar concepts. Include a sentence or screenshot when a term depends on context.
- Draft target-language options. A translator or linguist can propose equivalents, regional forms, grammatical information, and notes about tone. Mark proposals as unapproved until the responsible reviewer decides.
- Resolve translator questions. Keep questions in a central log rather than scattering decisions across email or chat. Record the question, options considered, decision, reasoning, owner, and date. Convert recurring answers into glossary entries.
- Approve changes. Set an approval rule appropriate to the subject. A technical, regulated, or legally sensitive term may require review by both a linguist and a subject expert. Preserve the previous value when possible so the team can understand what changed.
- Apply and check the glossary. Use the approved terms during translation, then search the delivered files for forbidden variants, inconsistent capitalization, untranslated terms, and incorrect grammatical forms.
Cadence and checkpoints
Terminology management works best as a recurring process rather than a final proofreading task. Use checkpoints that match the project’s pace:
- Before translation: review existing entries, identify new high-risk terms, confirm language and regional requirements, and agree on who can approve changes.
- During translation: add genuine terminology questions to the decision log, avoid silently changing approved terms, and flag entries that lack enough context.
- At linguistic review: compare the files with the glossary, check forbidden variants, verify product names and labels, and confirm that terminology works in its actual sentence or interface.
- After delivery: record accepted corrections, rejected suggestions, and terms that caused repeated confusion. Update the glossary only after the decision is confirmed.
- Monthly or quarterly: review recently added terms, unresolved questions, deprecated entries, and terms used across new content. A faster cadence may be appropriate during a product launch or major revision.
- Every 12 months: review the structure, permissions, file compatibility, privacy handling, language coverage, and quality-control rules. Terminology-management practices and translation technology can change, so confirm that the workflow still suits the team.
Common working formats include spreadsheets, tabular exports, and terminology files supported by translation tools. Confirm the exact import and export requirements before converting a glossary. Preserve character encoding, language codes, field names, and special characters, and test a small file before migrating the full record.
How to interpret changes
A growing number of entries is not automatically a sign of better terminology management. Look at the reason for each change. New product features, markets, or legal requirements may legitimately create new terms. By contrast, frequent reversals between two translations may indicate that the source definition is unclear or that approval responsibilities are missing.
Track practical signals such as the number of unresolved questions, repeated reviewer corrections, forbidden-variant matches, and terms awaiting subject-expert approval. If the same term generates questions in several projects, improve its context or definition rather than adding multiple loosely defined alternatives. If a term is no longer used, mark it deprecated instead of deleting it immediately; this helps reviewers understand older documents.
Review language-specific issues separately. A source term may have one approved equivalent in one language and several context-dependent equivalents in another. Grammatical gender, formality, regional vocabulary, compound formation, and character limits can all affect the final choice. Record these constraints in notes instead of forcing every language into one identical rule.
When to revisit
Revisit the glossary whenever a new translation project begins, a product or service changes, a source document is revised, or reviewers identify recurring terminology errors. Schedule a monthly or quarterly review for active content programs, and complete a broader annual review even if the glossary appears stable.
Before each review, export or back up the current version, confirm the review period, and assign owners for unresolved entries. Then work through this short checklist:
- Remove duplicates and merge entries that describe the same concept.
- Check that every approved translation has enough context and a clear status.
- Review forbidden variants and confirm that they are still genuinely unsuitable.
- Identify entries that have not been reviewed since a major content or product change.
- Search recent translated files for inconsistent terminology and update decisions where necessary.
- Check access permissions and remove sensitive information that is not needed for translation.
- Publish a dated version and tell translators, reviewers, and subject experts what changed.
A glossary becomes more useful when it records decisions, not just words. Start with the terms most likely to cause confusion, assign clear ownership, and make review part of every translation project workflow. For related planning, compare the translation service request checklist and the certified document translation checklist when your content has formal submission requirements.