How to Build a Translation Glossary That Sticks

Quick answer — A translation glossary should hold only terms that must never vary — product names, statutory phrasing, charge descriptions — pinned so a general match cannot overwrite them. Long glossaries get ignored; short enforced ones change output.

Vitra.ai Universe keeps one memory and one quality gate across every format.

Short and enforced beats long and advisory

The failure mode is always the same. Someone builds a four-hundred-term glossary, circulates it, and translators use the parts they remember. A glossary that is advice does nothing. A glossary the system enforces changes every output, and that only works if it is short enough to be right.

Start at forty terms. If a term does not have a consequence when it varies, it does not belong.

What earns a place

What does not earn a place: ordinary vocabulary, anything a competent translator resolves correctly, and preferences with no consequence. Those belong in a style guide, which is a different document doing a different job.

Pinning, not suggesting

The mechanism matters more than the content.

A pinned term resolves identically regardless of surrounding context, and a general memory match cannot overwrite it.

That is what makes the glossary binding rather than advisory — the term is applied at translation time instead of checked afterwards by someone who may not check.

Applying at translation time also removes the most common review finding, which frees reviewers for the judgement work only they can do.

Ownership and drift

One owner per language. Not a committee, because a committee produces a glossary nobody has decided on.

Review quarterly, and treat every reviewer correction as a candidate entry — if a reviewer fixed the same term twice, it should have been pinned. The quality control record is where that pattern shows up, since it logs what was flagged and why.

Version it alongside the content it governs. When someone asks a year from now why a claim was worded a particular way, the answer is a glossary version, and it needs to still exist.

Industrial products make the strongest case for doing this first, since one component name runs through every document — manufacturing glossary.

FAQ

How long should a translation glossary be? Short enough to be correct, which usually means starting near forty terms rather than four hundred. If a term has no consequence when it varies, it belongs in a style guide instead.

What belongs in a glossary rather than a style guide? Terms that must never vary: product and feature names, statutory phrasing, charge descriptions, legal entity names, and UI strings referenced in documentation. Preferences without consequence belong in the style guide.

How do you stop a glossary term being overridden? Pin it, so it resolves identically regardless of context and a general memory match cannot replace it. Applying terminology at translation time rather than checking afterwards is what makes it binding.

Who should own a translation glossary? One named owner per language, reviewed quarterly. Committees produce glossaries nobody has decided on. Reviewer corrections are the best source of new entries — a term fixed twice should have been pinned.