What you can and cannot judge without the language
The translation and transcreation guide is blunt about the limit: a reviewer who cannot read the output is checking formatting, not quality. That is why it puts language sign-off with a named in-country reviewerThe check of translated or adapted content by a native speaker who knows the market and category, who signs off the language before publication. who is a native speaker, commercial sign-off with the market owner and compliance sign-off with whoever owns compliance in that market. This tutorial does not replace any of them.
What it adds is the job of the person in the middle: the central marketer who briefed the work, owns the asset and has to put their name to the launch. That person can verify a great deal without reading a word. They can see whether the page, email or ad looks right in its real context, whether the formats, links and tracking work, whether text is cut off, whether termbaseA record of the approved translation of each product, feature and brand term per language, with terms not to translate, definitions and rejected alternatives. terms appear where they should and whether any source-language strings were left behind. Through a back-translation they can also check what the claims, prices, offers and legal lines say.
What they cannot judge is whether the copy sounds natural, whether the register suits the market, whether a transcreatedRewriting marketing copy for another language or market from the original brief, so the intended effect survives even when the words change. line lands, or whether a word carries an unwanted association. Those belong to the reviewer, and a machine translation of the copy back into English is no substitute: it shows roughly what the text means, but nothing about how it reads to a native speaker. The accuracy and review workflows guide makes the general point that fluent output hides its errors; a fluent back-translation can hide them just as well.
Before you start
- Have the brief. The localisation brief for the job, with the label on each asset, the audience, the objective and the named reviewers.
- Have the reference files. The termbase and style guide for the language; the tutorial on building a termbase and translation memory sets out what the termbase holds.
- Get the assets in context. A staging page, an email test send to a real inbox, ad previews in each placement, not a spreadsheet of strings.
- Agree who does the back-translation. A translator who has not seen the source, so they translate what the copy says rather than what they know it should say.
- Know the sign-off owners. Who signs language, commercial and compliance for this market, written down in a RACI matrix or the brief.
The steps
Read the brief and the label on each asset
Start from what was asked for. Each asset in the brief carries a label on the spectrum: translation, localisation or transcreation. A translated help article should say exactly what the source says; a transcreated headline is expected to say something different with the same effect. Knowing the label tells you what a good result looks like before you look at it, and stops you flagging a transcreated line for not matching the source.
Check the asset in context, not in a spreadsheet
Open the page on staging, send the email to real inboxes on desktop and phone, and preview each ad in its placements. Many localisation errors are invisible in a string list and obvious in context: a headline that wraps badly because the language runs longer, a button label cut off, a subject line truncated before the point, an image with source-language text burned in, a layout that breaks with a longer word. You can see all of these without reading the language.
Check formats, links and tracking yourself
Prices in the local currency and format, dates, numbers and units as the style guide sets them, phone numbers and addresses for the market. Click every link and confirm it reaches the same-market edition, not the home site. Check that campaign links carry the market in their UTMURL tags identifying traffic source. parameters and that conversion events fire on the edition's thank-you pages. The new market launch checklist and the localisation hub's pre-publication checklist list these checks; they need no language at all.
Search the copy for termbase terms and untranslated strings
Use the browser's find function or a text search. Search for each do-not-translate name: it should appear exactly as recorded. Search for the approved term for each key product and feature: if a term is missing where the source used it, ask why. Search for common source-language words, such as button labels and navigation words, to find strings that were never translated. These are mechanical checks a non-speaker can do quickly and reliably.
Ask for a back-translation of claims, prices, offers and legal lines
Do not back-translate everything. Pick the lines that carry risk: every claim about performance, safety, durability or the environment, every price and discount, every offer condition, every guarantee or warranty line, and every piece of legal text. Send them to a translator who has not seen the source, and ask for a literal rendering of what each line says, not a polished one.
Compare the back-translation with the source meaning
Put each back-translated line beside the source line and ask one question: does it promise the same thing? Look for a claim that has become stronger or more absolute, a condition that has dropped out, a price or percentage that changed, a guarantee that now covers more than the source did. The translation guide, drawing on the Advertising Standards Authority's role in setting the UK's advertising rules, notes that a claim acceptable at home may need evidence, qualification or removal in another market, so route every claim difference to whoever owns compliance there, and check claims against the claims library. This tutorial gives no country's rule, and none of it is legal advice.
Read the reviewer's notes and ask why, never what
The in-country reviewer's notes are the richest information you will get about the edition. Read them for patterns: are corrections mostly about terms, register, formats or meaning? When a note is unclear, ask the reviewer why they changed something, not what the new wording says. The reason tells you whether the issue is a one-off or a missing rule in the termbase or style guide, and that is the part you can act on.
Settle disagreements by the brief, not by preference
When translator and reviewer disagree, ask both for their reasons and decide by the brief: the audience, the objective, the label, the termbase and the style guide. Never decide by which version reads better in a back-translation, because that judges the English, not the target language. Where a disagreement is about a term or a rule, settle it once and record it in the termbase or style guide. The approvals and compliance reviews guide covers how an unresolved disagreement is escalated without stalling the launch.
Record the three sign-offs
Record language sign-off from the reviewer, commercial sign-off from the market owner and compliance sign-off from the compliance owner, each with a name and a date, as the translation guide sets out. Add your own record of the non-language checks you ran. An asset with your checks and no language sign-off is not approved.
Watch the edition's results against home
After launch, compare the edition with the home edition on the same page type and channel. The translation guide uses conversion rate (CVRShare of visits or clicks that convert.) as the test of the whole workflow, and the conversion rate calculator is enough for a first comparison. A gap is a prompt to look at the copy, the offer and the trust content together; the localising websites and campaigns guide covers the non-language causes, and the message match guide covers an ad and landing page that say different things. Read small numbers with caution before concluding anything.
Checks a non-speaker can and cannot make: a table
| Check | Non-speaker can do it | How | Who else |
|---|---|---|---|
| Layout, length and truncation in context | Yes | Staging page, test sends, ad previews | Reviewer for the fix |
| Formats, currency, dates, units | Yes | Compare with the style guide | Reviewer confirms local form |
| Links reach the same-market edition | Yes | Click every link | None |
| Tracking and conversion events | Yes | UTM parameters, test conversions | Analytics owner |
| Do-not-translate names and termbase terms | Yes | Text search against the termbase | Reviewer for context |
| Untranslated source-language strings | Yes | Text search for source words | Translator to fix |
| Meaning of claims, prices, offers, legal lines | Partly | Back-translation by an unbriefed translator | Compliance owner and market owner |
| Natural, correct, on-voice language | No | None | In-country reviewer |
| Whether a transcreated line lands | No | None | Reviewer and market owner |
| Cultural meaning of images and words | No | None | Reviewer and market team |
| Whether the edition performs | Yes | Results against home on the same page type | Market owner |
The rows marked "No" are the reason the in-country reviewer exists. The rows marked "Yes" are the reason the central owner should not simply wait for the reviewer: most of them catch errors the reviewer is not looking for, because they are not language errors.
A cookware maker checks a Market B edition (illustrative)
Ambriquo Cookware checks its Market B launch
Ambriquo Cookware, an invented maker of cast-iron cookware, prepares 24 product pages and 3 launch emails for Market B. Its e-commerce manager does not speak the language. Working through the steps on staging, she finds a link in the care guide pointing to the home edition, a "compare" button left in the source language on every product page, and a launch email subject line that is cut off on phones before the offer. She fixes the link and sends the other two to the translator.
She asks for a back-translation of 19 lines: prices, the launch discount, the delivery offer, the guarantee and the care claims. The back-translation shows that the source line "guaranteed against cracking for life with normal use" has become, in effect, "guaranteed for life", without the condition. She routes it to Market B's compliance owner, who asks for the condition to be restored. The reviewer, who keeps language sign-off, writes the corrected line.
The reviewer's notes show 8 changes, 5 of them the same term for "pre-seasoned", which becomes a termbase entry. Six weeks after launch, the product pages convert at 1.6% against 2.0% at home on the same page type, a gap she logs and reviews with the market owner rather than reading as a verdict on the copy.
Common mistakes
- Judging the language through a machine back-translation. It shows meaning, not quality. Language sign-off stays with the native-speaking reviewer.
- Reviewing a spreadsheet instead of the asset. Truncation, wrapping and broken layouts only show in context.
- Back-translating everything. It costs time and buries the risky lines. Back-translate claims, prices, offers and legal text.
- Using the source writer for the back-translation. Someone who knows the source reads what the copy should say. Use a translator who has not seen it.
- Overruling the reviewer on preference. Decide disagreements by the brief, the termbase and the style guide, not by which English rendering sounds better.
- Translating a claim instead of checking it. A claim acceptable at home may not be acceptable elsewhere. Route every claim difference to the compliance owner.
- Treating launch as the end of review. The edition's results against home are the last check.
The marketing localisation hub sets out in-country review and the pre-publication checklist this tutorial works alongside, and the glossary entry on transcreation explains why some lines are meant not to match their source.
