Ask any reviser what they correct most often and the answer is rarely grammar. It is terminology. A product called "Smart Sync" becomes "Intelligent Synchronization" in one file and "Smart Sync" in another. A contract uses "Licensee" on page two and "Licence Holder" on page nine. A medical leaflet translates the same dosage instruction three different ways. Each inconsistency looks small, but together they confuse readers, weaken brands and in regulated content can create real legal or safety risk.
Terminology management is the discipline that prevents this. It means deciding which terms are approved, documenting them in a translation glossary or termbase, and making sure every translator uses them every time. This guide explains how it works and how to build a glossary that translators actually follow.
What Is Terminology Management?
Terminology management is the process of identifying, defining, approving and distributing the key terms of a company or subject field across all languages. The output is a structured terminology database, usually called a termbase, which stores each concept together with its approved translations, definitions, usage notes and forbidden alternatives.
It is different from translation memory. A translation memory stores whole sentences that have already been translated. A termbase stores individual concepts and the exact words that must be used for them. Memory helps you reuse past work, while terminology tells you what is correct, even in a sentence nobody has translated before.
Glossary vs Termbase, What Is the Difference?
| Feature | Simple translation glossary | Termbase in a CAT or TMS |
|---|---|---|
| Format | Spreadsheet or document | Structured database, concept based |
| Languages | Usually one language pair | All target languages linked to one concept |
| Extra data | Rarely more than term and translation | Definitions, context, part of speech, forbidden terms |
| Use while translating | Manual lookup | Terms appear automatically in the editor |
| Quality control | Reviewer must spot errors | QA flags deviations automatically |
| Exchange | Copy and paste | Standard TBX import and export |
A spreadsheet glossary is a good start for a single freelancer and a single client. Once several translators, languages or clients are involved, a proper termbase becomes essential, because nobody reliably checks a spreadsheet for every term in every segment.
How to Build a Translation Glossary That Works
- Extract candidate terms. Start with product names, UI labels, legal and technical concepts, and words that appear often in source content.
- Define each concept. A short definition prevents translators from choosing the right word for the wrong meaning.
- Agree on approved translations. Involve in country reviewers or subject experts, especially for regulated content.
- Record forbidden terms. Listing what must not be used is as valuable as listing what must.
- Add context and notes. Example sentences, gender, plural forms and capitalization rules remove guesswork.
- Keep it lean. A focused glossary of a few hundred critical terms is used. A bloated list of thousands is ignored.
- Review it regularly. Products change, laws change and terms age. Assign an owner and update the glossary on a schedule.
Why Terminology Management Matters for Quality
Consistent terminology is one of the clearest differences between professional and amateur translation. Machine translation engines and large language models are fluent, but without guidance they choose terms based on probability, not on your client's style guide. The result can be perfectly readable text that uses the competitor's product vocabulary, an outdated legal term or a word your brand team explicitly banned.
Terminology also carries expertise. When a qualified legal or medical translator decides how a term should be rendered, that decision deserves to be reused by every colleague who follows. A termbase is how that expert judgment scales across a team, a client account and years of projects.
Standards and Portability
The industry standard for exchanging terminology between tools is TermBase eXchange (TBX), an XML format published as ISO 30042, with the current version dating from 2019. If your tool can import and export TBX, or at least clean CSV, your glossaries remain yours and can move with you if you change platforms. Before committing to any terminology management system, check this first.
Features to Look for in a Terminology Management System
- In context suggestions that show the approved term directly in the editor as you translate.
- Automatic deviation checks that flag segments where an approved term was not used.
- Forbidden term warnings for words the client has explicitly rejected.
- Multilingual concept entries, so one concept links all languages together.
- Easy import and export of existing spreadsheets and TBX files.
- Integration with memory and machine translation, so MT output is corrected against the glossary.
The WordBeam term base and translation glossary surfaces approved terms in context, while the built in QA checks and AI proofreading flag any segment that drifts from them before delivery. Both run inside the same translation management system as your memory and machine translation, so terminology is enforced at every step rather than checked at the end.
Frequently Asked Questions
What is a termbase in translation?
A termbase is a structured database of approved terms, with translations, definitions and usage notes, that a CAT tool shows to translators automatically while they work.
How many terms should a translation glossary have?
Quality matters more than size. Start with the few hundred terms that cause the most errors or carry the most brand or legal weight, then grow carefully.
Who should own terminology management?
Ideally a named person on the client or project side, supported by senior translators, so decisions are consistent and updates are approved.
Good terminology management turns individual expertise into shared, enforceable knowledge. It is the quiet foundation behind every translation that reads as if one expert wrote it in every language.