Marketing Campaign Translation Memory Conflict and Terminology Governance

Executive summary

Translation memory can speed up localisation, but an old approved phrase may no longer fit a product update, legal requirement, audience, or campaign context. Conflicting glossary entries can also cause different teams to translate the same feature in inconsistent ways. This guide sets out how to resolve conflicts, distinguish reusable language from context-dependent copy, and maintain terminology that supports quality without forcing every sentence into a literal match.

Separate glossary terms from reusable sentences

A glossary defines preferred terms and usage notes; translation memory stores previously translated segments and their context. A term can have one preferred translation while a sentence needs a different construction to sound natural. Keep these resources distinct and record when a term must remain unchanged, when alternatives are allowed, and which product or market the rule applies to. This reduces the risk of treating a high match percentage as proof of a good translation.

Identify the authority for conflicting entries

When two approved translations disagree, determine which one is newer, which product or campaign it applies to, who approved it, and whether the context differs. Do not automatically choose the most recently used phrase if it came from an unreviewed campaign. Assign a terminology owner and a clear escalation path for unresolved conflicts. Preserve the reason for the decision so the same disagreement does not recur in every project.

Record context and prohibited interpretations

For important terms, include the source-language meaning, preferred target term, part of speech or grammatical notes where useful, market, product area, example usage, and terms to avoid. Note false friends, ambiguous abbreviations, and words that have a different meaning in support or legal content. If a term cannot be translated safely without context, require a question to the requester rather than allowing translators to guess.

Handle product and legal changes

A product rename, feature change, pricing revision, or updated disclosure may make an older translation obsolete. Mark affected entries as deprecated and identify current replacements. Search active assets and high-traffic pages for the old term, but preserve historical records needed to understand past campaigns. Where local legal or regulated language is involved, route the proposed terminology through the appropriate regional reviewer instead of treating a general glossary approval as sufficient.

Balance consistency with natural language

Consistency matters for product names, interface labels, and technical concepts, but marketing copy also depends on tone, rhythm, and cultural context. Reviewers should be allowed to depart from a literal memory match when the target-language sentence would be awkward or misleading, provided the rationale is documented where the deviation affects a key term or claim. Avoid scoring translators solely on reuse rate or string-level match percentage.

Integrate terminology checks into production

Provide translators and reviewers with the current glossary, reference screenshots, approved product context, and a contact for questions. Run automated checks for prohibited terms, inconsistent product names, placeholders, and untranslated segments, then review the results manually. Ensure the tool uses the correct locale and glossary version. A technically clean export can still contain a context error, so linguistic review remains necessary for important campaigns.

Govern updates and measure recurring issues

Require a request, owner, evidence, approval, effective date, and affected-language list for terminology changes. Track repeated corrections, conflicts, and questions to identify gaps in product documentation or briefing. Retire stale entries from active suggestions while preserving their history. If a term repeatedly changes, investigate whether the product concept itself is unstable or whether teams lack a shared definition.

Worked example: feature renamed across regions

A software feature is renamed in the source language, but one region continues to use an older translation from memory. The localisation lead confirms the new product meaning, obtains regional approval for the replacement term, marks the old entry deprecated, and searches current campaign assets. A note explains the change so agencies do not revive the outdated phrase from archived files.

Implementation checklist and takeaways

Separate glossary and memory, establish authority for conflicts, document context, deprecate outdated terms, allow justified linguistic judgement, integrate QA, and track recurring problems. Translation memory should accelerate accurate work, not make yesterday’s wording impossible to question.