Document Translation Services at Scale: How to Scope, Format and Review Large Programs

Updated · 7 min read
On this pageScoping: what to send before you ask for a priceFile formats: where the hidden work isTerminology and translation memory: who keeps whatPlanning the timelineTranslation, revision and review are different stepsVersion control: the source will changeConfidentiality and personal dataA one-page checklist for your next program

A legal team sends a 300-page policy pack for translation into four languages. The quote is approved, the delivery arrives on time, and two weeks later someone notices that the annexes are still in English. They were scanned images inside the PDF, the word count tool could not read them, and nobody looked. The translation was fine. The scope was wrong.

That is the typical shape of a failed document translation project. The translators rarely cause the trouble. It comes from the quote, the files, the review plan and the version of the source that was used. This guide covers those parts, in the order you meet them, for teams that buy document translation services in volume: legal, compliance, HR, product and regulatory.

Scoping: what to send before you ask for a price

A vendor can only price what it can see. The more of the following you send with the request, the fewer surprises later:

  1. The editable source files. Word, PowerPoint, Excel, InDesign packages, XML exports. A PDF export of a Word file hides tracked changes, comments and text boxes that may also need translating.
  2. A list of scanned or image-only pages. Signed annexes, stamped certificates, screenshots and drawings with callouts. They need text extraction or retyping and are often missing from automatic word counts.
  3. The purpose of each document. "Internal reference", "published on our website", "signed by both parties" and "filed with an authority" justify different workflows and prices. Say which is which.
  4. Existing language assets. Glossaries, previous translations, style guides, translation memories from earlier vendors. They lower cost and keep wording consistent with what you already use.
  5. Real deadlines per batch. Most programs do not need everything on one date. Phased delivery is usually cheaper and safer than one rush.
  6. Who answers questions. A named contact for terminology and meaning queries. Queries without an owner stall the work and push the delivery date.

File formats: where the hidden work is

The file type decides how text gets in and out of the translation tool, and how much layout work follows. The same 10,000 words can be a clean job or a week of desktop publishing.

Source formatWhat tends to go wrongWhat to send or ask for
Word (.docx)Tracked changes and comments translated by accident, or left in EnglishAccept or reject changes first, or state that comments are out of scope
PowerPoint / ExcelText in images, hidden sheets, speaker notes and formulas built on textList what is in scope (notes? hidden sheets?) and mark cells that must not change
InDesignExpansion breaks the layout; missing fonts in the target scriptPackaged IDML files with fonts and links; budget a layout check per language
Native PDFConverted to Word, translated, then rebuilt with layout driftFind the original source file; use PDF only as the visual reference
Scanned PDF or imagesNot counted, not translated, or retyped with errorsFlag these pages; agree text extraction and a check against the image
XML, JSON, CMS exportsTags or keys translated; broken files on importExport to a localization format such as XLIFF and test one file round-trip first

XLIFF, the OASIS exchange standard, exists for exactly this: it stores localizable content and carries it from one step of the localization process to the next, so the vendor translates text without touching the structure around it. If your content system can export XLIFF, ask for it.

Terminology and translation memory: who keeps what

A large program produces two assets besides the translations: a translation memory (every source sentence paired with its approved translation) and a termbase (the approved equivalent for each key term). They are what makes the next batch cheaper and the wording consistent across hundreds of documents and several translators.

Two points to settle in the contract. First, ownership: the memory and termbase built from your documents should be delivered to you at the end of each project. Second, format: ask for the translation memory in TMX, the exchange format designed to move translation memory data between tools and vendors, and the termbase in an export your tools can import, even a plain spreadsheet. Without that clause, switching vendors means paying again for sentences you already own. For building the termbase itself, see our guide to terminology management for consistent global messaging, and for how memory matching works inside the tools, how CAT tools improve translation quality.

Split work carefully. Giving one large document to five translators shortens the schedule but multiplies terminology drift. If you must split, the shared termbase and a single reviser across all parts matter more than any other step.

Planning the timeline

Turnaround depends on how many linguists can work in parallel without losing consistency, plus revision, query handling and layout. Use your vendor's committed daily throughput, not a figure from a website. The calculator below shows how the pieces add up; the defaults are placeholders, so replace them with your own numbers.

Translation–
Total working days–
Words per translator–

Assumes revision starts after translation ends. In practice revision can overlap batch by batch, which shortens the total but needs a reviser available from the start.

Translation, revision and review are different steps

Quotes often say "translation and proofreading" without saying who does what. ISO 17100, the international standard for translation services, separates the steps and makes one of them non-negotiable: revision by a second person, a linguist other than the translator who compares the target against the source. Review by a subject specialist, reading the target on its own, is an optional step in the standard, and it is the one your own team often fills.

Translation

Translator

Source to target, with termbase and memoryOutput: complete target, queries raisedSelf-checks spelling, numbers and completeness before handing over.
Revision

Second linguist

Bilingual check against the sourceOutput: corrected target, error notesCatches omissions, misread sentences and inconsistent terms.
Review

Domain or in-market specialist

Reads the target for its purposeOutput: change requests with reasonsYour legal, product or regulatory owner. Ask for reasons, not rewrites by taste.

Not every document needs the full chain. Internal reference material can carry lighter checks; contracts, policies employees sign and anything filed with an authority should not. Our piece on risk-based translation QA shows how to tier content so review effort goes where errors cost most. Note too that the standard does not cover raw machine translation output plus post-editing; if a vendor proposes machine translation for part of the program, agree in writing which document types qualify. Hybrid human and AI translation works when those roles are explicit.

Version control: the source will change

In long programs the source documents keep moving. Legal updates a clause, HR renames a benefit, a product spec gets a new revision. If the change reaches the vendor by email as "small edits, please update", the result is often two translated versions of the same clause in different documents.

  • Freeze the source for each batch and give it a version number that appears in the file name.
  • Send changes as a new version, never as instructions in an email. Translation memory will match the unchanged sentences, so you only pay for what actually changed.
  • Keep one delivery log: document, source version, target language, delivery date, reviser. When someone asks "which version is current?", the log answers.

Confidentiality and personal data

Document programs often contain personal data: employee handbooks with names, HR letters, customer correspondence, clinical or claims files. If you are subject to the GDPR, a translation vendor handling that data is a processor working for you, and Article 28 sets out what the contract must contain. Three requirements matter most in practice:

Under GDPR Article 28: the vendor may not engage another processor, such as a freelance translator or another agency, without your prior specific or general written authorisation; people processing the data must be committed to confidentiality; and at the end of the services the data must be deleted or returned, at your choice, unless law requires storage.

Ask your vendor how files move (portal or email), who can see them, which freelancers or subcontractors are used and where they are, and whether any machine translation engine stores your text. If your security team requires a certified information security management system, ask whether the vendor is certified to ISO/IEC 27001. Price comparisons that ignore these questions compare different services; our article on choosing an affordable translation service without losing quality covers what a low quote usually leaves out.

If you are still choosing the vendor for the program, shortlist questions, pilot design and SLA terms for selecting a translation partner come first.

A one-page checklist for your next program

  1. Editable files collected; scanned and image pages listed separately.
  2. Purpose and required workflow set per document type.
  3. Glossary, style guide and previous translations shared.
  4. Translation memory and termbase ownership and export format in the contract.
  5. Second-linguist revision confirmed for everything published, signed or filed.
  6. Machine translation policy agreed in writing.
  7. Source frozen and versioned per batch; one delivery log.
  8. Data processing terms, subcontractor list and file transfer method agreed.

Planning a large document program?

We help global companies scope document sets, set up terminology and translation memory, and run translation with second-linguist revision, with specialist depth in English-to-Korean legal, technical and corporate documents. See our services or tell us about your project →

Work with us

Clear scope, clear price, Korean you can rely on.

Translation and localization into Korean with specialist review and a quote before work starts.

Get a free quote