Building a Translation Glossary Your Team Will Use.

23 June, 2026· Article by Maria Jones

Building a Translation Glossary Your Team Will Use

Every company has words that matter more than others. Product names, legal phrases and slogans need to stay the same across every page and every language. A glossary makes that possible, but only if people actually use it. Many glossaries die in a spreadsheet nobody opens, and this guide shows how to avoid that.

Why consistency matters

Customers notice when a product has three different names. It looks careless, and it makes support harder because people search for different words. A clear glossary removes that confusion.

Consistency also saves time. Translators stop debating the same choices again and again, and reviewers spend their effort on meaning instead of vocabulary.

Start with the terms that matter

Do not try to list every word. Begin with product names, features, menu labels, legal terms and anything your brand owns. Fifty good entries beat five hundred rushed ones.

Ask support and sales teams as well. They know which words customers actually use, and those are the terms most worth protecting.

What each entry needs

A useful entry has the source term, the approved translation, a short definition and a note on usage. Add a flag for terms that must never be translated, such as brand names.

Context prevents mistakes. A word like "case" can mean a legal matter or a box, and a one line note tells the translator which meaning applies.

Where the glossary lives

A glossary kept in a spreadsheet is easy to ignore. Inside your memory translation software, terms are highlighted as translators work and warnings appear when a different word is chosen.

That placement turns a reference list into a daily helper. Nobody needs to remember to check it, because the tool does the checking.

Choosing owners

Every glossary needs an owner. Someone has to approve new terms, retire old ones and answer questions from translators. Without a name attached, the list slowly goes stale.

Keep the approval path short. If a translator has to wait a week for an answer, they will guess instead, and the glossary loses its purpose.

Learning from established practice

Our article on terminology management and glossaries explains how to structure entries, handle synonyms and deal with terms that change over time. It is a good companion to this guide.

Reading it before you start prevents common design mistakes, such as mixing approved and forbidden terms in a single column.

Handling several languages

Each target language needs its own approved terms, and they should be reviewed by native speakers. A term that works in Spain may sound odd in Mexico.

Where regions differ, create separate entries or notes. It is much easier to maintain two clear variants than to argue about one compromise.

Forbidden and preferred terms

Sometimes you need to tell translators what not to use. A legal department may ban certain words, or a brand may avoid a competitor term. Mark these clearly.

Alerts help here. When a translator types a forbidden word, the tool can warn them at once, which prevents problems before review.

Keeping up with industry data

Research and community resources show how other teams manage terminology. Material from TAUS covers data sharing, quality practices and the role of language assets in modern workflows.

Use these sources to benchmark your own process, and to find ideas for areas where your glossary is still thin.

Linking terms to translation memory

A glossary and a translation memory work best together. The memory handles whole sentences, while the glossary guards individual words inside them.

When both sit in the same system, a change to a term can be traced across all earlier projects, which makes cleanup far easier.

Training the team

Show translators and reviewers where the glossary is and how to suggest changes. A short walkthrough of ten minutes is enough for most people.

Feedback improves the list. Translators see real problems every day, and their suggestions often reveal missing terms or unclear entries.

Reviewing and cleaning up

Set a regular review, for example once a quarter. Remove outdated products, merge duplicates and fix entries that cause confusion.

Check how often each term is used. Entries that never appear may be unnecessary, while terms that cause many warnings may need clearer notes.

Common mistakes to avoid

Teams often build a huge list with no context, or forget to tell translators it exists. Others let several people edit freely, which creates conflicts and duplicates.

Keep it small, clear and owned. A short glossary that people trust is worth far more than a long one that nobody believes.

A quick start plan

Export the terms you already use, remove duplicates and add a note to each one. Load the list into your tools and ask two translators to test it on a real project.

Collect their comments after one week, fix the unclear entries and then share the glossary with the wider team.

Measuring the effect

Track the number of terminology corrections in review. If the count falls over time, the glossary is doing its job and your reviewers are spending time on better things.

Share the results with the team. People keep using tools that visibly make their work easier.