A translation glossary gives every contributor a shared record of preferred terms, approved translations, and language-specific rules. This guide provides a practical translation glossary template, explains what to track, and shows how to review it as your products, campaigns, and multilingual content change.
Overview
A glossary is more than a list of words. It is a controlled terminology reference for recurring content: product names, interface labels, feature descriptions, industry terms, campaign language, and phrases that must be handled consistently. A well-maintained multilingual glossary helps translators, editors, reviewers, and content teams make the same decision across a website, app, help center, document, or social channel.
Use the glossary alongside a broader multilingual content style guide. The glossary answers, “Which term should we use?” The style guide answers questions such as, “How formal should the writing be?” and “How should headings, numbers, punctuation, and calls to action work in this locale?” Keeping these resources connected prevents terminology decisions from becoming scattered across chat messages and old project files.
The best format is the one your team will actually update. A spreadsheet can work for a small publishing operation. A terminology-management feature in a translation platform may be more suitable when several languages, translators, or content repositories are involved. The structure below works in either case.
What to track
Start with terms that recur often, create confusion, or affect how readers understand your offer. Do not try to record every ordinary word in the source language. A focused glossary is easier to use and review.
Core translation glossary template
| Field | What to record | Example |
|---|---|---|
| Source term | The exact word or phrase in the source language. | Workspace |
| Approved translation | The preferred term for a specific language and locale. | Approved target-language equivalent |
| Prohibited alternatives | Translations, spellings, or variants that should not be used. | Older product label or literal alternative |
| Definition | The meaning of the term within your product or subject area. | A shared area for organizing project material |
| Context | A sentence, screen, title, or content type showing how the term appears. | Navigation label; not a physical room |
| Part of speech | Whether the term is a noun, verb, adjective, or another form. | Noun; may also appear as a verb |
| Gender or grammatical form | Gender, case, number, article, or other required language information. | Record masculine, feminine, neuter, or context-dependent use where relevant |
| Region or locale | The country, market, or language variant where the term applies. | French for France; French for Canada |
| Status | Whether the entry is proposed, approved, deprecated, or under review. | Approved |
| Owner and review date | The person responsible for the decision and the date it was last checked. | Product editor; quarterly review |
| Notes | Exceptions, usage restrictions, pronunciation, or links to supporting context. | Keep product name unchanged in headings |
For product and brand terminology, record capitalization and whether the term may be translated at all. Brand names, feature names, trademarks, and plan names often need separate handling from ordinary descriptive language. For marketing terms, include the intended meaning and audience rather than approving a word based only on its dictionary equivalent.
For SEO and website translation, add optional fields for the target-language search term, page type, and keyword intent. A literal translation may not be the phrase people use when searching. Terminology decisions should still protect clarity and brand consistency; the glossary should not turn every sentence into a keyword-placement exercise. See the website translation SEO checklist for a broader localization review.
Cadence and checkpoints
Glossary maintenance works best as a recurring workflow rather than a last-minute cleanup. Set a light monthly check for active projects and a more deliberate quarterly review for the complete terminology set. Adjust the cadence to the pace of publishing, product releases, and language expansion.
At the start of a project
- Collect recurring terms from the source copy, product interface, previous translations, and customer-facing documentation.
- Separate terms that are already approved from terms that need a decision.
- Confirm the target locale, audience, tone, and any grammatical requirements before translating.
- Share the glossary with everyone who will translate, edit, review, or approve the content.
During production
- Ask contributors to flag missing terms instead of silently adding personal preferences.
- Record the proposed translation, the reason for it, and the context where the issue appeared.
- Use a clear status such as “proposed” until an accountable reviewer makes the decision.
- Check translated files against the glossary before publication, especially navigation, buttons, product names, and recurring calls to action.
At a monthly or quarterly review
- Filter for proposed, disputed, outdated, or missing entries.
- Compare current content with the approved terms using a terminology checker, translation environment, spreadsheet filter, or text comparison tool.
- Review feedback from translators, editors, support teams, and readers in each locale.
- Archive obsolete terms rather than deleting them, so older content and previous decisions remain understandable.
- Record the decision date and notify the people responsible for updating existing content.
If your workflow includes AI translation tools, provide the approved glossary as a controlled reference and still review important output in context. A machine may select a plausible synonym that conflicts with your product terminology, locale, or brand voice. The glossary should guide the tool, not replace human judgment for ambiguous or high-impact language. For a decision framework, compare the approaches in this human versus AI translation workflow.
How to interpret changes
Not every variation is an error. A language may require different forms because of grammar, formality, gender, number, or sentence position. A term can also be correct in one region and unsuitable in another. Review consistency at the level of meaning and usage, not by forcing identical word shapes everywhere.
When a term changes, first identify the cause:
- Source change: The product, feature, legal wording, or editorial concept has changed.
- Locale change: A regional audience prefers or requires a different form.
- Context change: A noun is being used as a verb, a heading, a button label, or a technical definition.
- Quality issue: A translator used an unapproved synonym, outdated term, or literal translation.
- Glossary issue: The entry lacks enough context, has conflicting instructions, or was never formally approved.
Then decide whether to correct one translation, revise the glossary, or update the source content. Avoid changing an approved term solely because another option sounds attractive. A terminology decision should consider comprehension, existing usage, search behavior where relevant, grammatical fit, brand meaning, and the cost of changing published material.
Use status labels to make uncertainty visible. “Proposed” means a decision is pending; “approved” means contributors should follow it; “deprecated” means it should not appear in new content; and “regional alternative” means it is valid only for a defined locale or context.
When to revisit
Revisit the glossary on a monthly cadence when you publish frequently or have active localization work. A quarterly review is usually a practical minimum for a stable content library. Review it immediately when you launch a product, rename a feature, enter a new market, change brand positioning, add a language, or discover repeated terminology errors.
Use this short update checklist:
- Are all new product, campaign, and interface terms represented?
- Do approved translations include the correct region, gender, grammatical form, and context?
- Are prohibited alternatives clearly explained rather than simply listed?
- Have old entries been marked deprecated or archived?
- Does the glossary match the current website, documents, and user interface?
- Do translators and reviewers know where to submit a terminology question?
- Have changes been communicated to the people maintaining existing translations?
To put the system into practice, create one shared glossary, add the ten to twenty terms that cause the most disagreement, assign an owner, and schedule the first review. Link each important entry to a real example rather than relying on isolated words. As your library grows, pair the glossary with a content style guide and a translation review checklist. For related document workflows, see how to translate documents online without losing formatting or meaning. Consistent terminology is built through small, recorded decisions that remain easy to find and revise.