A translation can be grammatically correct and still be unsuitable for publication. Use this translation quality assurance checklist to review meaning, omissions, tone, terminology, formatting, links, and usability before a localized page, document, or campaign goes live.
Overview
Translation quality assurance is the final control stage between a completed translation and a published asset. It is broader than proofreading: proofreading catches language problems, while quality assurance checks whether the translated version works as intended in its real context.
A reliable review compares the source and target versions, confirms that the message has not changed, and tests the translated content as a reader will encounter it. That may include opening links, viewing a web page on a mobile screen, checking a form, listening to text with assistive technology, or reviewing a document after it has been exported.
Use this process for website translation, document translation, product interfaces, email campaigns, subtitles, help content, and marketing copy. The depth of review should match the risk. A private draft may need a focused language check; legal, financial, medical, safety-related, or high-visibility content usually deserves a second qualified reviewer and a more structured sign-off.
Keep a record of findings rather than relying on memory. A simple table with the source phrase, translated phrase, issue type, severity, proposed correction, owner, and status makes recurring problems easier to identify. For terminology work, a translation glossary template can help reviewers distinguish a genuine error from an approved variation.
What to track
1. Meaning and completeness
Start with the source-to-target comparison. Read in short sections, then review the whole page or document for context. Check whether the translation preserves:
- the main claim, instruction, or call to action;
- qualifiers such as “may,” “only,” “before,” and “unless”;
- relationships between cause, condition, sequence, and consequence;
- examples, captions, footnotes, warnings, and supporting labels;
- every sentence, heading, list item, table cell, and repeated interface string.
Look specifically for omissions, additions, mistranslated negatives, unexplained abbreviations, and sentences that appear fluent but do not express the source meaning. A translation comparison tool or text-difference utility can help locate missing and duplicated segments, but it cannot decide whether a sentence is appropriate in context.
2. Terminology and consistency
Record important product names, feature labels, industry terms, recurring verbs, and approved translations. Search the target text for each term and check that it is used consistently unless the language or context requires a deliberate variation. Inconsistent terminology can make one feature appear to have several names or cause users to misunderstand an instruction.
Do not change an approved term simply because another synonym sounds more natural. Instead, confirm the glossary, client instructions, product interface, and previous localized content. If no terminology decision exists, flag the choice for review and document the final decision for future batches.
A style guide should also define preferences such as formality, punctuation, capitalization, numbers, dates, units, and treatment of brand names. See the multilingual content style guide template for a practical structure.
3. Tone, audience, and cultural fit
Assess whether the translation sounds appropriate for its audience and purpose. A support article, product warning, social post, and executive letter should not all use the same level of formality. Check whether humor, idioms, metaphors, politeness, and calls to action carry the intended effect without sounding forced or confusing.
Read the target version without looking at the source. This reveals awkward phrasing, excessive literalness, unnatural sentence order, and wording that a fluent reader would not normally use. For clarity-focused reviews, apply the checks in this multilingual readability guide.
4. Names, numbers, dates, and sensitive details
Verify every detail that can change the practical meaning of the content:
- names of people, companies, products, places, and files;
- prices, percentages, quantities, version numbers, and reference codes;
- dates, times, time zones, currencies, decimal separators, and measurement units;
- email addresses, phone numbers, URLs, QR codes, and tracking parameters;
- placeholders, variables, tags, and text that must remain unchanged in a content system.
Check local conventions deliberately rather than assuming that a familiar-looking format transfers safely between languages. Confirm that translated text has not altered a placeholder or broken a variable used by the publishing system.
5. Formatting and functionality
Review the rendered asset, not only the translation file. Look for clipped buttons, overflowing text, broken line breaks, incorrect bullets, missing accents, damaged tables, inconsistent heading levels, and captions that no longer match images or video.
Test internal and external links, downloads, forms, navigation labels, search fields, and calls to action. On a website, inspect at least the main desktop and mobile layouts when available. On a document, review the exported format because fonts, page breaks, headers, and footers can change during conversion. This guide on translating documents without losing formatting addresses common document checks.
Include accessibility in the review. Confirm that headings follow a logical order, alternative text is translated where needed, language metadata is correct, and text-to-speech output is understandable when the platform supports it. A visually polished page can still be difficult to use if its structure or labels are inaccessible.
6. Native-speaker and specialist review
Use a qualified native or near-native reviewer who understands the target audience and subject matter. Give that reviewer the source, target, context, glossary, style guide, and a clear brief. Asking someone to “check the translation” without context often produces personal preferences rather than useful QA.
Human review is especially valuable for regulated, technical, culturally sensitive, and persuasive content. AI translation tools can assist with drafts, comparisons, terminology searches, and issue detection, but output should be checked against the source and the intended audience. The human versus AI translation decision guide can help frame that choice.
Cadence and checkpoints
Use checkpoints throughout the workflow instead of waiting until publication day. A practical sequence is:
- Before translation: identify the audience, purpose, market, content type, prohibited wording, terminology, placeholders, and review owner.
- During translation: resolve ambiguous source text, record terminology decisions, and flag cultural or technical questions.
- After translation: compare meaning and completeness, then review tone, terminology, grammar, and spelling.
- After layout or upload: inspect the rendered asset, links, forms, responsive layout, metadata, and accessibility details.
- Before release: complete a final focused pass on changed sections and obtain documented approval.
- After release: monitor corrections, reader feedback, search behavior, support questions, and recurring defects.
For recurring content, review high-risk pages monthly or whenever they change. A broader quarterly review can examine terminology drift, repeated error types, outdated links, and consistency across channels. Use a translation management system or shared tracker if several people need to assign, resolve, and approve issues.
How to interpret changes
Not every issue deserves the same response. Classify findings by impact:
- Critical: changes safety instructions, legal meaning, payment details, privacy information, eligibility, or a core user action. Stop publication or remove the affected content until corrected.
- Major: creates a material misunderstanding, omits important information, breaks a link or function, uses a wrong product term, or makes the content unsuitable for its audience. Correct before release.
- Minor: includes a spelling mistake, punctuation issue, formatting inconsistency, or wording that is less natural but still clear. Fix before release when practical, and always correct repeated patterns.
- Preference: reflects an acceptable stylistic alternative rather than an error. Record it only if it supports a documented style or terminology decision.
Track patterns, not just totals. A rising number of omissions may point to unclear source files or a segmentation problem. Repeated terminology changes may indicate an incomplete glossary. Layout defects may originate in templates rather than translation. When the same issue appears across languages, fix the source content or workflow; when it appears in one language, review the target-language guidance and reviewer briefing.
For multilingual SEO, separate language quality from search performance. Check translated titles, descriptions, headings, image text, internal links, and localized search terms, but do not force keywords into unnatural sentences. The website translation SEO checklist provides a separate review path for international pages.
When to revisit
Revisit this translation review checklist whenever content changes, a new market is added, a product feature is renamed, a glossary is updated, or a translation workflow introduces a new tool. Schedule a monthly or quarterly audit for important recurring content, even when no major release is planned. Also reopen the review after customer complaints, support tickets, legal feedback, accessibility findings, or a pattern of search and conversion changes that suggests the localized experience needs investigation.
At the end of each review cycle, save the approved terminology, resolved questions, and known exceptions. Then begin the next batch with those decisions available to translators and reviewers. For an immediate final pass, confirm five things: the meaning is complete, terminology is approved, tone fits the audience, the rendered asset functions correctly, and every critical issue has a named owner and resolution.
This repeatable process turns translation quality assurance from a last-minute proofread into a manageable publishing control. It also creates a record that helps each new document, page, and campaign become faster and more consistent to review.