Inconsistent terminology is one of the quickest ways to lose a client. When the same product is called three different names across one document, readers lose trust. Every serious cat tool includes a place to store approved terms, and learning to use it properly will lift the quality of your work. This article shows how glossaries and termbases fit into daily translation.
Glossary or termbase
A glossary is usually a simple list of source terms and translations. A termbase is more structured and can include definitions, usage notes, grammar details, status and links between concepts. Small projects can start with a glossary, while large programs benefit from a full termbase.
How the editor uses your terms
While you translate, the tool scans each source segment for known terms. When it finds one, it highlights the word and shows the approved translation. You can insert it with a keystroke, which saves typing and prevents accidental variation in wording.
Building your first termbase
Start with the terms that matter most: product names, interface labels and industry expressions. Ask the client for existing lists and review them before importing. Our guide to the termbase TBX file explains how such data is stored and exchanged.
Adding terms while you work
The best termbases grow during projects. When you meet a new expression, add it immediately with a short note about context. Waiting until the end usually means the term is forgotten, and the next translator will face the same question again.
Forbidden and preferred terms
Many clients have words they do not want to see. Mark these as forbidden and show the preferred alternative. Good tools warn you in real time when a forbidden term appears, which helps maintain brand voice without a long manual review.
Standards for terminology data
Terminology work follows recognized conventions. The ISO 30042 standard, described on the ISO website, defines the TBX format for exchanging termbases. Using an open standard means your data remains usable if you change software.
Sharing with the team
A shared termbase ensures that every translator and reviewer follows the same decisions. Assign an owner who approves new entries and resolves conflicts. Without this role, a shared resource can quickly become a messy collection of competing suggestions.
Checking terminology before delivery
Run a terminology check before sending files. The tool compares the translation against the termbase and lists segments where an approved term is missing. Reviewing this list takes minutes and catches mistakes that are easy to overlook by eye.
Handling plurals and inflection
Languages with rich grammar change the form of a term depending on the sentence. Good tools recognize common variants, but not always. Add the main forms to entries, or use fuzzy term matching so that useful suggestions still appear for inflected words.
Multiple meanings
The same word can mean different things in different fields. Record the subject domain for each entry and filter by project. This prevents a financial expression from appearing as a suggestion inside a medical document.
Collecting terms from source files
Many tools can extract candidate terms from a document automatically. Review the list carefully, discard common words and keep only real terminology. This approach gives you a strong head start before translation begins on large technical projects.
Working with subject experts
Experts at the client company can confirm difficult terms quickly. Send them a clean table with context sentences rather than a raw list. Their approval gives the termbase authority and reduces disputes later in the review stage.
Multilingual termbases
If you translate into many languages, keep one concept per entry with all translations attached. This structure shows gaps clearly and makes it easier to add a new language later without rebuilding the entire resource from nothing.
Maintaining quality over time
Review the termbase every few months. Delete outdated terms, merge duplicates and update statuses. A tidy resource is trusted by the team, while a neglected one is ignored, which defeats the purpose of building it.
Combining with translation memory
Memories remember sentences, while termbases protect individual words. When the two work together, suggestions stay consistent and corrections are rarely needed. Update both resources after each project so that the next job starts from the best wording.
Training new translators
Show beginners how to look up and add terms in the first week. Pair them with an experienced colleague for the first project. Early habits determine whether the termbase becomes a daily helper or a forgotten file.
Avoiding overlong entries
A termbase should help, not slow you down. Keep entries short and focused on what a translator needs at the moment of decision. Too many fields discourage contributors and lead to incomplete data.
Measuring the benefits
Track the number of terminology related corrections per project. A steady decline shows that your resource is working. Share the numbers with clients, because consistent language is a visible improvement that supports long term relationships.
Final thoughts
Glossaries and termbases turn individual knowledge into a shared asset. Build them gradually, keep them clean, store them in open formats and use the checks your editor provides. Consistent terminology will quickly become one of the strongest marks of your professional work.