When different teams translate the same program or product name differently, clients may wonder whether they are reading about the same thing. A shared glossary helps by recording decisions once and making them reusable. It does not need to contain every word your organization uses. Start with terms that are important, ambiguous, frequently repeated, or regularly disputed.

Choose terms that need a decision

Collect candidates from current documents, support questions, internal reviews, and earlier translations. Prioritize official names, recurring service terms, job titles, product features, and words with a specialized meaning in your organization. Avoid filling the first version with ordinary vocabulary that nobody disagrees about.

For example, “member” might mean a paying subscriber, a professional association member, or someone in a household. The preferred translation depends on that meaning. Record the concept before choosing the equivalent, and separate entries when one source word represents different concepts.

Use a small, useful set of fields

  • Source term and source language.
  • Plain definition and an example sentence from your content.
  • Approved equivalent for each target language and intended audience.
  • Terms to avoid, with the reason when useful.
  • Status, decision owner, approval date, and reference.

A spreadsheet is often enough to begin. Keep one concept per entry and use stable identifiers if the same term appears in several systems. Mark an equivalent as proposed until the language reviewer and subject specialist have resolved it. A blank target-language cell is more honest than an unreviewed guess presented as approved.

Add context that prevents the wrong reuse

A term can be suitable in a technical manual and confusing in a public form. Record the audience or register when that distinction matters. For French, specify the intended market. For Arabic, include the approved written form and any agreed treatment of an abbreviation or product name.

An illustrative entry might define “intake appointment” as the first meeting to assess a client’s needs, then state that it is not an enrolment confirmation. That note gives a translator more useful guidance than a two-column word list. Leave the exact equivalents to the people reviewing those languages in context.

Resolve disagreements through evidence

Ask what the term denotes, where it appears, and whether an official name or established internal decision governs it. Compare the proposed wording with actual use in your organization. A general reference can help, but it does not automatically decide the name of your own program.

Give one person responsibility for recording the final decision. Keep a short explanation when the choice is likely to be questioned again. If the decision changes, mark the previous term as superseded and identify the documents that need updating rather than silently replacing the entry.

Use the glossary during delivery, not only afterward

Send the approved glossary with each brief and identify the version. Invite translators to flag missing concepts or entries that conflict with the source. Review new candidates at the end of the project and incorporate the agreed decisions before the next assignment.

  • Start with a manageable list of high-impact terms.
  • Test it on one real document before expanding it.
  • Keep proposed, approved, and superseded terms distinct.
  • Assign a review owner and a location for the current version.
  • Check recurring labels in the final publication against approved entries.

The useful measure is whether the glossary resolves recurring questions. A short, maintained list that includes definitions will usually serve a team better than a large file of unexplained equivalents.