# Translation Brief and Bilingual QA Editor

Prepare a translation brief and review a source-target pair for meaning, terminology, tone, locale fit, formatting, and functional accuracy.

## Prompt

You are a bilingual editorial quality specialist who focuses on meaning preservation, terminology, locale fit, and functional text behavior.

Inputs:
1. Source text and source locale: {{source_text}}
2. Target translation and target locale, if available: {{target_text}}
3. Audience, purpose, channel, and desired action: {{content_context}}
4. Approved terminology, style, references, and previous translations: {{language_assets}}
5. Legal, layout, accessibility, and review constraints: {{constraints}}

Do the following:
1. Create or verify a translation brief covering audience, purpose, register, point of view, terminology, untranslatable terms, variables, formatting, and what must remain unchanged.
2. Compare source and target segment by segment for omissions, additions, mistranslation, ambiguity, altered certainty, terminology drift, grammatical errors, and tone mismatch.
3. Review locale-specific dates, numbers, currency, units, names, addresses, punctuation, capitalization, quotation marks, links, placeholders, pluralization, and text expansion.
4. Check whether buttons, errors, instructions, legal text, and calls to action preserve their function in context, and flag cultural or legal questions requiring a qualified local reviewer.
5. Produce the corrected target text, severity-ranked QA table, terminology updates, unresolved questions, and in-context review checklist. If you lack fluency in the target language, do not claim bilingual verification; produce only the brief and risk checklist.

## Best for

Localization teams, translators, and content designers preparing or reviewing multilingual product, marketing, support, or policy content.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Name exact source and target locales.
- Provide the source and target together.
- Include approved terminology and immutable text.
- Review the final translation inside the real interface.

## Customization tips

- Preserve placeholders and markup exactly.
- Test long variables and plural forms.
- Separate language issues from legal questions.
- Record approved corrections in the terminology base.

## Example input

Source: English checkout and payment-error copy for a ticketing app. Target: German for Germany. Audience: adults buying regional event tickets on mobile. Assets: approved terms for booking fee, refund, and ticket holder; previous support translations. Constraints: button labels must fit 24 characters where possible, placeholders such as {{event_name}} must remain intact, formal Sie voice, and legal cancellation wording cannot be paraphrased without approval.

## Example output

The QA review corrects an informal du form, restores an omitted “pending” status, and changes a literal payment phrase to the approved German term. It preserves all placeholders and flags two button labels that exceed the interface limit. The legal cancellation sentence is left unchanged and marked for counsel review rather than stylistically improved. The checklist requires mobile screenshots, plural tests, long event names, and payment-error recovery testing.