Translate only what changed.
Compare previous and new content, identify reusable text, and estimate the cost advantage of translating only changed content.
How the work is framed
Translate only what changed. is most useful when it is treated as a document fidelity and usability problem rather than a generic request to “translate this”. The practical work begins by understanding the source, the people who will use the result, the market in which it will appear, and the consequences of a mistake. Document translation begins with structure. Before translating, the team should know what is body text, a caption, a table heading, a footnote, a form field or an image label.
What deserves professional attention
For this type of work, the working scope typically includes source quality and extractability, headings, tables, footnotes and references, names, numbers and repeated labels, layout reconstruction and reading order, and final visual comparison against the source. The exact combination should be agreed before production instead of being discovered after delivery.
Typical control points
- source quality and extractability
- headings, tables, footnotes and references
- names, numbers and repeated labels
- layout reconstruction and reading order
- final visual comparison against the source
Questions worth resolving early
- Who owns the final decision on source quality and extractability?
- Which source elements must remain unchanged?
- What evidence of review is required at delivery?
- What happens if the source changes after work begins?
A practical production path
The recurring failure modes are concrete: translating text in the wrong reading order; missing content embedded in images or headers; changing identifiers or references; and recreating layout so aggressively that the translation becomes harder to use. A serious workflow turns those risks into explicit checks rather than relying on a final proofread to catch everything. Scanned or poorly generated PDFs need a source-quality decision early; OCR can accelerate extraction but its output must not be treated as authoritative text.
What to prepare before kickoff
Before kickoff, provide the latest source version, intended audience, destination market, reference terminology, any previous approved translations, and the required delivery format. If the content will be filed, published, built into software, printed, subtitled or presented live, say so at intake because that changes the review path. The final check should be visual as well as linguistic, especially where page references, signatures, stamps, tables or bilingual layouts matter.
What a senior reviewer actually checks
A senior review does not reread every sentence with the same intensity. It samples for meaning and register, then deliberately inspects the elements most likely to cause operational harm: layout reconstruction and reading order, final visual comparison against the source, numbers, names, references and repeated terminology. It also looks for the less obvious problem of internal inconsistency—two individually plausible translations that cannot both be correct in the same document, product or program.
Source preparation that saves time later
Good source preparation is part of quality control. Before translate only what changed. starts, remove obsolete drafts, identify the authoritative version, separate instructions from translatable content, and supply reference material that is genuinely approved. If previous translations exist, they should be treated as evidence to review rather than blindly copied. This is especially important where translating text in the wrong reading order or missing content embedded in images or headers has already occurred in earlier projects.
Acceptance is about use, not appearance
Acceptance criteria should describe how the result will be used. A file that is destined for publication, filing, software release, printing or live delivery needs a different final check from material used only for internal understanding. For translate only what changed., the practical test is whether a qualified reader can use the target content without reconstructing the source, while every protected fact, instruction, identifier and constraint remains intact.
Questions a project manager should ask
A useful kickoff conversation for translate only what changed. should answer four things plainly: What can never change? What may be adapted for the target reader? Who resolves terminology or factual questions? What evidence is required before release? Those questions make the workflow proportionate. They prevent both under-review of consequential content and unnecessary layers of checking on low-risk material.
The strongest outcome for translate only what changed. is therefore not “more content” or “more automation”. It is controlled clarity: the reader receives natural target-language material, the project team can explain the important decisions, and the delivered version can be traced back to the correct source and review path.
