Download Translation Quality Review Checklist (PDF)
How to review translated documentation effectively
Most translation quality problems are not caused by bad translation. They are caused by bad review.
A reviewer who rewrites accurate translations because they would have phrased things differently adds cost, introduces inconsistency, and delays the project without improving the result. A reviewer who cannot distinguish between an error and a preference generates feedback that confuses translators and undermines the terminology consistency that professional translation is designed to deliver.
This guide helps reviewers focus on what matters and avoid the common mistakes that erode translation quality rather than improving it.
Getting the Right Reviewer
The wrong reviewer is worse than no reviewer at all. Before assigning someone to review a translation, confirm:
- Native speaker of the target language — not someone who learned it at school or spent a year abroad. Bilingual competence, not functional familiarity
- Understands the subject matter — a linguist who doesn’t know the product cannot assess whether technical terms are correct. A bilingual engineer with no linguistic training may introduce grammatical errors. The ideal is someone with both
- One reviewer per language — multiple reviewers with different preferences produce conflicting feedback. Designate one person with authority to make final decisions
If you don’t have a qualified reviewer for a particular language, it is better to rely on the translation provider’s quality process than to assign someone who will guess.
What to Check
Accuracy
- Does the translation convey the same meaning as the source?
- Is anything omitted — sentences, bullet points, table entries, footnotes, captions?
- Is anything added that isn’t in the source?
- Are numbers correct — measurements, quantities, dates, part numbers, tolerances, voltages, temperatures?
- Are units of measurement appropriate for the target market?
- Are names and proper nouns correct — company names, product names, brand names?
Terminology
- Are glossary terms used correctly and consistently?
- Do technical terms match industry usage in the target language?
- Are terms flagged as “do not translate” still in English — brand names, product codes, standards references?
- Is the same source term translated the same way throughout?
Readability
- Does it read naturally — as though written in the target language, not translated from English?
- Does the tone match the brief — formal, technical, conversational, as specified?
- Is grammar correct, including gender agreement, case endings, and diacritical marks?
Formatting
- Is formatting preserved — bold, italic, bullet points, headings, table structures?
- Is any text missing from tables, diagrams, headers, footers, or captions?
- Are cross-references and page references correct in the translated version?
Safety-Critical Content
- Are warnings and cautions factually correct? (“Do not exceed 240V” must not become “Do not exceed 240W”)
- Are hazard symbols paired with the correct text?
- Are regulatory statements and compliance declarations complete and accurate?
How to Give Feedback
This is where most review processes break down. Good feedback improves future translations. Bad feedback makes them worse.
Track your changes. Don’t silently overwrite the translation. Use tracked changes or a feedback form so the translation team can see what was changed and why. Unexplained changes cannot be learned from.
Distinguish errors from preferences. An error is something factually wrong — a mistranslation, an omission, a number that doesn’t match the source. A preference is an alternative phrasing that is equally correct. Flag them differently. Errors must be fixed. Preferences should be discussed, not imposed. This distinction is critical and most reviewers do not make it clearly enough.
Explain your reasoning. “I changed X to Y because Z” is feedback the translator can act on across the entire document and on future projects. “Changed” with no explanation is not. The five seconds it takes to add a reason saves hours of misalignment later.
Consolidate before sending. One set of feedback per language, from one reviewer. Not three separate people’s contradictory notes in the margins.
Return feedback on time. Delayed review delays the entire project. Build review time into the schedule and hold to it.
Common Review Mistakes
Rewriting for style preference. If the translation is accurate, uses correct terminology, and reads naturally, it does not need rewriting because the reviewer would have phrased it differently. Every unnecessary change costs money, delays delivery, and creates inconsistency with the translation memory.
Overriding agreed glossary terms. If a term was agreed in the glossary and approved for use, changing it in review breaks consistency with every other document that uses the same term. If you believe the glossary term is wrong, raise it as a glossary change — don’t silently swap it in one document.
Introducing “variety” into consistent terminology. Using the same term for the same concept is a feature of technical translation, not a flaw. Reviewers who change terms “for variety” introduce ambiguity. In technical documentation, where a reader may need to cross-reference between the manual and the parts catalogue, consistent terminology is a safety and usability requirement.
Reviewing in a language you’re not fluent in. Well-intentioned review by someone with intermediate-level language skills causes more problems than it solves. They catch obvious issues but introduce subtle ones — incorrect register, unnatural phrasing, grammar errors that a native speaker would never make.
The Bigger Picture
The most valuable outcome of a review is not a list of corrections. It is a set of confirmed preferences.
When a reviewer confirms that specific terminology choices, tone, and style are correct, those confirmations feed into the glossary and translation memory. Every subsequent project benefits. Over time, translations arrive closer to what the reviewer wants because the translator is working from an increasingly refined set of approved decisions.
This is how review effort decreases over time. Not because standards drop, but because the foundation gets stronger with each project. The goal is a translation partnership where review becomes a formality rather than a gatekeeping exercise.
Download more resources: bubblestranslation.com
Questions? info@bubblestranslation.com | 0870 777 7750
Bubbles Translation Services — Quality you can verify, since 2003
