The Bilingual Document Review Checklist

TABLE OF CONTENTS

A translated document can read smoothly and still contain a missing paragraph, changed number, broken table, or hidden source-language text. A bilingual review catches these problems by comparing the source and translation in separate passes before anyone approves the final file.

Review in Passes, Not Page by Page

Do not try to check meaning, grammar, numbers, and layout at the same time. Each task needs a different kind of attention, so use this order:

Pass	Main question	Highest-risk items
1. Setup	Are we reviewing the correct files?	Version, language, audience, glossary
2. Completeness	Is every source element represented?	Headings, lists, text boxes, footnotes
3. Meaning	Does the translation say the same thing?	Negation, conditions, obligations, tone
4. Fluency	Does the target text work on its own?	Grammar, spelling, punctuation, readability
5. Data	Did any exact value change?	Numbers, dates, units, names, references
6. Layout	Is the translated file still usable?	Overflow, tables, fonts, page breaks
7. Delivery	Is this the file the recipient should receive?	Links, filename, metadata, final export

Keep the source, bilingual version, and translated version open together. Mark issues in the bilingual file, make corrections in the editable translated file, and record terminology decisions in a short glossary. This avoids turning the review copy into a second uncontrolled master file.

1. Confirm the Review Setup

An accurate review of the wrong source version is still a failed review. Resolve the file identity before reading sentences.

The source file is the latest approved version.
The translated file was generated from that exact source.
The source and target languages are correct.
The audience, country or locale, purpose, and required tone are documented.
A glossary, style guide, do-not-translate list, or approved reference translation is available where needed.
The required output format is known: editable file, print-ready PDF, or both.
Comments, tracked changes, hidden text, attachments, and password-protected sections have been identified.

Use clear filenames while reviewing. A pattern such as project-document-language-v03-review.docx is easier to control than final-new-2.docx. If the source changes after translation starts, pause and identify the changed sections instead of silently mixing versions.

Before uploading confidential material to any online service, remove data the translator does not need and check the service’s handling terms. The document translation privacy checklist covers that preparation step.

2. Check Completeness Before Style

The first content pass answers one question: did everything make it into the translation? Do not polish sentences yet.

Compare visible structures first:

Page counts do not need to match. Translation often changes text length, which can move content onto another page. Instead, compare stable landmarks: heading sequence, list item count, table structure, figure labels, and the first and last sentence of each section.

A search for common source-language words can reveal leftovers, but it is only a clue. Product names, quotations, and deliberate bilingual labels may need to remain unchanged.

3. Compare Meaning and Terminology

Read the source and target together for this pass. Review complete sentences and clauses, not isolated words.

Check high-impact meaning

Negatives such as not, unless, except, and without are preserved.
Conditions and exceptions have the same scope.
The person or organization responsible for each action is unchanged.
Requirements, recommendations, and permissions remain distinct.
Comparisons, ranges, and thresholds keep the same direction.
Uncertainty has not become certainty, or vice versa.
The tone fits the intended audience without weakening the message.

Small modal verbs can carry large consequences. May, should, and must are not interchangeable in a policy, instruction, or contract. Likewise, up to 30 days does not mean after 30 days, and at least 10 units does not mean no more than 10 units.

Enforce terminology

Each approved source term uses the preferred target term.
Product names, model numbers, trademarks, and personal names follow the do-not-translate rules.
Acronyms are expanded or retained consistently.
The same concept is not translated several different ways without a reason.
Deprecated or prohibited terms do not appear.
Interface labels and cross-references match the product or document they name.

Do not build a glossary for every noun. Focus on the terms that affect meaning, searchability, brand consistency, or user action. Microsoft describes localization style guides as language-specific rules covering style, usage, and market-specific data formats; that is the right level of guidance to record before a team reviews many documents in the same locale.

4. Read the Translation on Its Own

Hide the source and read the target document as its intended reader would. A sentence can mirror the source closely and still sound unnatural or become hard to follow.

Grammar and spelling follow the target locale.
Punctuation, quotation marks, capitalization, and spacing are consistent.
Sentences are clear without copying the source language’s word order.
Pronouns and references have an obvious subject.
Headings, labels, instructions, and calls to action sound natural in context.
Tone and level of formality stay consistent from beginning to end.
No editing change introduced a new meaning error.

After editing for fluency, compare every substantially rewritten sentence with the source again. This final comparison prevents a stylistic improvement from quietly changing a condition, number, or responsibility.

5. Verify Numbers and Structured Data

Numbers deserve their own pass because fluent prose can make a wrong value look trustworthy. Search the source and translation for digits, currency symbols, percent signs, and unit symbols.

Item	What to compare
Dates and times	Day, month, year, time zone, 12/24-hour format
Money	Amount, currency, decimal separator, symbol or ISO code
Percentages	Value, sign, decimal places, related base figure
Measurements	Value, unit, conversion, spacing, capitalization
Ranges	Endpoints, dash, inclusive or exclusive wording
Identifiers	Invoice, account, model, clause, ticket, and version numbers
Tables	Row labels, totals, column alignment, blank cells, footnotes
Figures	Axis labels, legends, captions, callouts, source notes

Use this checklist:

Every number represents the same value as the source unless an approved conversion was required.
Decimal and thousands separators follow the target locale without changing magnitude.
Negative signs, percent signs, and inequality symbols are present.
Units were not translated into a different unit by accident.
Table totals still add up.
Figure and table references point to the correct item.
Clause, section, page, and appendix references remain valid.
Email addresses, phone numbers, postal addresses, and codes are exact.

For financial, scientific, legal, medical, or safety documents, ask a subject-matter reviewer to approve the high-risk data. Language fluency alone does not verify a dosage, tax calculation, engineering tolerance, or legal obligation.

6. Inspect Layout and Formatting

Now review the translated version by itself, first in the editable format and then in the delivery format. The reader will not have the source file open to explain a broken page.

The W3C notes that English and Chinese are compact source languages and that translated text often becomes longer. Short labels can expand especially sharply, while some scripts require more vertical space. A correct translation therefore needs flexible containers and a real layout pass.

Text and typography

No text is clipped, hidden, overlapping, or reduced to an unreadable size.
Headings wrap cleanly and remain visually distinct.
Paragraph spacing, indentation, and alignment are consistent.
Required characters display correctly in regular, bold, italic, superscript, and subscript styles.
Arabic, Hebrew, and other right-to-left text uses the correct direction and reading order.
Manual line breaks from the source do not create unnatural target-language lines.

Document structure

Tables fit the page and keep the correct row-column relationships.
Lists retain their numbering level and sequence.
Images, captions, and callouts remain associated with the right content.
Page breaks do not strand a heading or separate a note from its subject.
The table of contents reflects the translated headings and current page numbers.
Headers and footers do not collide with body text.
Form fields, checkboxes, signature lines, and fillable areas still work.

If characters appear as boxes, letters disconnect, or fonts change unexpectedly, use the diagnostic steps in Why Fonts Break After Translation before resizing everything around the symptom.

7. Test Links and Interactive Elements

Links can look unchanged while pointing to the wrong target. Test them in the exported delivery file, not only in the editor.

Every web link opens the intended live page.
Email links keep the correct address and subject where used.
Internal bookmarks and table-of-contents links jump to the right section.
Cross-references display the correct number and label.
QR codes still scan and resolve correctly.
No production link was replaced by a staging or local address.
Link text makes sense in the target language.

Do not translate the URL itself unless a verified localized destination exists. If a source link points to content unavailable in the target language, decide whether to keep it, replace it, or add a short language note.

8. Use OpenL Doc Translator for the First Draft and Review Copy

OpenL Doc Translator accepts common document formats including PDF, DOCX, PPTX, and XLSX. Its official product page states that it preserves fonts, colors, tables, and page layout, and returns both a translated version and a bilingual version.

Use those two outputs for different jobs:

Upload the original editable file when available. A native DOCX, PPTX, or XLSX usually exposes document structure more clearly than a flattened scan.
Select the source and target languages. Confirm the target locale separately when spelling, dates, or terminology differ by market.
Review the free preview. Check a dense page, a table, and a page with images or text boxes before processing a long file.
Download both versions. Use the bilingual version for source-target comparison and the translated version for layout and delivery checks.
Correct the editable master. Apply approved changes once, then export a fresh final file.

Format preservation reduces manual rebuilding; it does not approve the translation. A human reviewer still needs to verify meaning, exact values, specialist terminology, and high-risk instructions.

Final Approval Checklist

Run this short gate after all corrections are complete:

The review is complete only when the source-target comparison and the final-file inspection both pass. One protects the meaning; the other protects the document the reader will actually use.

Sources

ISO 17100:2015, Translation services - Requirements for translation services - official standard covering the core processes, resources, and quality-related requirements of professional translation services.
W3C: Text size in translation - explains text expansion, wrapping, character width, and vertical-space differences across languages.
Microsoft Localization Style Guides - language-specific guidance on style, usage, and market-specific data formats.
OpenL Doc Translator - official product details for supported document formats, formatting preservation, previews, and bilingual review files.