A translation glossary needs a change process

A company approves a product term and adds it to its translation system. Months later, the product meaning changes while the term continues to be applied automatically.

Record meaning and scope

Google’s Cloud Translation glossary guidance describes using glossary resources for domain terminology. The organisation still needs to decide which terms are appropriate and where they apply.

Keep the source meaning, approved translation, relevant product version and reviewer. Distinguish a general term from wording approved only for one customer or context.

An illustrative logistics product might use “release” for several different actions. One translation entry may not fit all of them.

Review changes with the affected teams

Include language specialists and people responsible for the business workflow. Sales preference alone should not determine a term that changes the meaning of a customer instruction.

Test revised entries on representative sentences rather than isolated word pairs. Negation, word order and surrounding context can affect whether the approved term remains appropriate.

Version the glossary and retain a way to identify which outputs used it, where feasible.

Monitor corrections after deployment

Collect errors with context and route them to a named owner. Do not permit unreviewed local edits to fragment the terminology across teams.

When a glossary change affects material documents, determine whether earlier outputs need review. A correction to future translation does not automatically repair existing content.

Retain representative sentences beside each important glossary entry. They help future reviewers see why a translation was approved and where it should not be applied. A term list without context can encourage increasingly broad substitutions that preserve vocabulary while weakening the meaning of the surrounding instruction.

A glossary is part of a translation operating system, not a completed localisation project. Its value comes from maintained meaning and controlled use rather than the number of entries stored.