How to Manage a Glossary for Consistent Translations

Terminology drift is one of the quietest ways a localized product starts to feel unpolished. It's rarely a single glaring error — it's five different translators making five reasonable but different choices for the same recurring word, and a user noticing that your product calls the same feature by two different names depending on which screen they're on.

What belongs in a glossary

• Product and feature names that should stay consistent, or that you've deliberately decided to translate a specific way.
• Recurring nouns that show up across many strings — "workspace," "project," "member," anything central to how your product is described.
• Terms you deliberately don't translate — brand names, or technical terms your audience already knows in the source language.
• Anything that's been corrected before. If a reviewer ever had to fix the same word twice across different translators, that's a signal it belongs in the glossary so the correction doesn't need to happen a third time.

Keep entries short and per-language

A glossary entry doesn't need a paragraph of explanation — a term, its approved translation for a given language, and an optional one-line note ("keep lowercase," "do not translate") is usually enough. Long explanations tend not to get read in the middle of a translation session; short, scannable entries do.

Make it visible where translators actually work

A glossary that lives in a separate document nobody opens is a glossary that doesn't get used. The most effective version sits next to the translation editor itself, scoped to the project, so a translator can check a term without leaving the screen they're working on. If your platform can highlight glossary terms directly inside the source text being translated, that removes the step of remembering to check at all.

Review glossary changes like you review translations

Because a glossary term affects every future translation of that word, a bad glossary entry propagates further than a single bad string. Treat glossary edits with at least the same scrutiny as a translation review — ideally from whoever has the most context on how the term is actually used across the product.

A glossary is a small amount of upfront structure that saves a much larger amount of downstream cleanup. Most teams don't build one until after they've already noticed the inconsistency — it's worth setting up as soon as you bring on a second translator, not after the third one asks why the word for "project" keeps changing.