Your translator sees “Charge”. Your product team sees the screen. Fix the context gap.

“Charge” is a word. The screen supplies the meaning.

A translator opens a string called “Charge”. Is it a payment action, a battery status or a fee? The product team knows. The translation task does not say. A fluent translation can still describe the wrong action.

Marco Wagner describes unclear translations tracing back through product, design and older requirements. Diego Cresceri highlights missing context and unclear approval ownership. These practitioner discussions identify questions to resolve; they do not measure how often every localization team encounters them.

Start with the ambiguous strings in the next release. Give linguists enough information to explain what each control does without opening a chat thread.

A small context record beats a long briefing

Illustrative record: billing.invoice.collect_payment; source: “Charge {amount}”; intent: collect the outstanding invoice balance now; screen: invoice detail, unpaid state. The product lead owns the payment meaning; the localization lead owns linguistic approval.

• Identity: keep the key stable while its purpose remains stable. Give unrelated uses of “Charge” separate keys, even when the English matches.
• Screenshot: mark the exact control and show nearby labels, the relevant state and build revision. Use synthetic data or an approved redacted capture.
• Variables: define {amount}, who formats it and a representative rendered value. Preserve the placeholder name; allow its position to follow target-language grammar.
• Locale constraints: list target locales, required plural variants and a meaningful length constraint. Specify whether a limit means characters or rendered space; record wrapping behavior and the smallest supported viewport.

Put the record where translation happens

Inspect your TMS before building a context service. Crowdin supports tagging source strings on screenshots so translators can see them in the editor. Crowdin Enterprise also offers a Source Text Review workflow step before translation. Availability and setup depend on the tool and edition you use.

Store intent and variable notes with the string, link the screenshot and assign unresolved source questions to the decision owner. Test access using the translator role. A design link that requires unavailable permissions fails the handoff.

Add an integration only after a real handoff shows which required field your current workflow loses. Preserve that identity through downstream review using the CAT-to-LQA handoff checklist.

A stable key can carry a changed promise

Suppose the illustrative payment button now schedules collection instead of collecting immediately. Keeping its key does not make yesterday’s translation approval valid. Change the source and intent together, then identify affected locales for fresh review.

Adopt an explicit invalidation rule: changes to meaning, placeholders, plural structure or layout constraints reopen affected review. Let the owner record why a cosmetic correction can retain approval. Crowdin’s source-review documentation describes controls for keeping translations and approvals; choose deliberately rather than preserving everything by habit.

Check the rendered target UI with representative values, required plural variants and the agreed viewport. Capture the source revision, target locale and tested build with the result.

Before the next translation handoff