How to Save on Translation Updates
Originally published December 10, 2014. Updated October 16, 2026, with guidance on translation memory, managing revisions, and evaluating AI-assisted workflows.
Estimated Read Time: 8 minutes
Summary
Keep the previous and current source files, approved translations, and terminology together. Ask how translation memory affects the quote, combine routine changes when practical, and give translators enough context to check the revised text. AI may help with suitable content, but compare the total cost of review and delivery. A small edit does not always mean a small amount of work.
You updated a few paragraphs in your employee handbook. Now the Spanish version needs to match. Should you pay to translate the entire document again?
Not necessarily. To save on translation updates, preserve your editable files, identify what changed, and make approved translations available for reuse. Then agree on the review and production work needed to deliver an accurate, usable update.
The biggest opportunity is often reducing the work that has to be repeated. That starts well before you request the next quote.
In This Article:
Keep the Files You Will Need Again
Make the Changes Easy to Identify
Use Translation Memory With Clear Terms
Understand Why Small Edits Need Context
Build Templates That Work Across Languages
Batch Updates and Consolidate Feedback
Evaluate AI by Total Cost and Risk
Keep the Files You Will Need Again
Imagine that your marketing coordinator leaves and the next person inherits only a folder of PDFs. The translations may still be useful, but someone now has to locate the originals or rebuild the layouts before making changes.
Avoid that problem by keeping a shared project archive with:
- The approved source document and its translated versions in editable formats.
- Final PDFs or screenshots showing what readers actually received.
- Linked graphics, licensed fonts where sharing is permitted, and production instructions.
- The language, intended market, version date, and approval status for each file.
- The provider’s contact information and relevant delivery agreements.
For example, retain the Word document behind a PDF or the InDesign package behind a brochure. For a website, preserve the approved text and page identifiers in a format your website team and provider can exchange.
A PDF is useful as a visual reference. It may also be editable, but it is not always an efficient substitute for the original production file. Ask which source format will reduce preparation work for your project.
Include editable translated files in your requested deliverables from the beginning. Our multilingual desktop publishing overview explains the layout work that may accompany a translation.
Make the Changes Easy to Identify
Send three things together: the previous approved source, the new approved source, and a marked comparison. Also include the translation that belongs to the previous source version.
If you work in Word, Microsoft’s document comparison instructions explain how to display differences between two versions in a third document. Check the comparison before sending it; it needs to reflect the versions you actually intend to update.
Identify additions, deletions, moved sections, and changes inside tables or images. A note saying “we changed page 12” may become unhelpful after text moves onto another page. Section names, document IDs, and a brief change log are more dependable references.
Send the full document for context even when you want only selected changes translated. Ask the provider to confirm the boundary of the work and whether unchanged sections need broader review. This helps avoid both unnecessary retranslation and gaps in the finished material.
A complete update package helps the provider connect the right source version, translation, and changes.
Use Translation Memory With Clear Terms
A translation memory, or TM, stores source text alongside its translations. Translation software can suggest previously translated segments when the same or similar wording appears again. It is different from machine translation, which generates a translation.
Matching text still needs judgment. An identical sentence may have a different meaning in a new location. The software provider memoQ explains how translation memory uses surrounding text as context.
Ask your provider:
- Which match categories affect the price, and what review does each include?
- How are approved corrections added to the memory?
- Who can access, use, and export the resource?
- What fees or restrictions apply when you change providers?
Do not assume ownership or free access simply because you paid for a translation. Put those arrangements in the agreement. Ask about an export format such as TMX; memoQ’s translation memory documentation describes exchanging memories with other tools. Have the receiving provider confirm compatibility and whether useful context or formatting information will transfer.
No translation memory available? Ask whether the previous source and approved translation can be aligned, meaning paired into corresponding segments. That preparation has a cost, so compare it with the expected value of future reuse.
What an Update Quote Might Include
Suppose a 12,000-word manual contains 900 new or revised words. This is an illustrative scenario, not a quote or a promised discount.
| Work Category | What to Confirm |
|---|---|
| 900 new or revised words | Translation and the agreed linguistic review |
| 11,100 unchanged words | Whether reuse is appropriate and what checking is included |
| File preparation and layout | How changes will be inserted and checked in the final files |
| Project coordination | Minimum charges, delivery requirements, and revision allowances |
Changing 7.5% of the words does not guarantee paying 7.5% of the original price. The quote should explain the work that remains. For a broader explanation of billing methods, see our guide to translation pricing.
The share of words changed is not the same as the share of project work required.
Understand Why Small Edits Need Context
“It’s only one word” describes the change in your source file. It does not necessarily describe the work in each translation.
Changing a singular noun to a plural can affect a verb, an article, or nearby references. Replacing a department name can also require updates to navigation, forms, and linked documents. A translator needs to see how the changed wording functions in the complete message.
Consider this simple illustrative example:
| Version | English | Spanish |
|---|---|---|
| Before | The document is ready. | El documento está listo. |
| After | The documents are ready. | Los documentos están listos. |
The Spanish revision changes every word. Other edits may affect word order or wording elsewhere in the paragraph. That is why replacing individual translated words without language review can create new errors.
For buyers, the useful takeaway is straightforward: identify the change precisely, but allow the linguist to check its full effect.
Build Templates That Work Across Languages
Reusable notices, forms, and instructions can reduce repeated writing and translation. Keep approved wording stable when the meaning, audience, and use have not changed. If a revision improves accuracy or clarity, make it; preserving a match should never become the reason to retain confusing text.
Templates need language-specific rules. A blank for a date is different from a blank that can hold any noun or phrase. Word order, grammatical agreement, and plural forms may change around the inserted information.
The W3C’s guidance on working with composite messages explains why assembling sentences from reusable fragments can cause translation problems.
Have a linguist review the complete template and representative filled-in examples. Specify which fields staff can change and which changes require another review. Keep a short glossary of approved product names and recurring terms alongside the templates.
Batch Updates and Consolidate Feedback
Where timing allows, collect routine changes into a planned release. Several small requests may trigger repeated setup or minimum charges. Ask whether related updates can share a project minimum; the answer may differ by language or service.
Do not hold back an urgent correction to save on a fee. Separate time-sensitive changes from routine wording improvements, and agree on a process for each.
Before translation begins, designate one person to approve the source and consolidate feedback. Give internal reviewers the glossary, intended audience, and a deadline. Ask them to distinguish an accuracy correction from a preference or a new source change.
For recurring work, track actual spending on translation, formatting, rush requests, and extra revision rounds. That shows whether the next improvement should be better files, earlier approvals, or a different release schedule.
Evaluate AI by Total Cost and Risk
Machine translation and generative AI can be useful options for some content. They do not eliminate the need to decide what quality the finished material requires.
A low-risk, nonconfidential text used only for a preliminary understanding has different needs from published instructions people rely on. For higher-consequence material, consider a human-led process or qualified bilingual review with subject-matter expertise, based on the intended use and applicable requirements.
NIST’s Generative AI Profile identifies risks including confidently presented false content and data privacy. The practical implication for translation buyers is to evaluate accuracy and data handling, even when a draft reads smoothly.
Ask the provider to test representative material before committing to a large recurring workflow. Compare the complete cost of generation, correction, review, formatting, and coordination with a human-led option. If correcting the draft takes longer than translating it, the proposed saving may disappear.
Confirm which tools will receive the files, what retention or training terms apply, and whether your organization permits that use. Keep unreviewed machine output separate from approved translation resources. Our AI-assisted language services overview explains how human review can fit into the process.
Compare workflows using the same quality expectations and finished deliverables.
Send a Complete Update Request
Before requesting a quote, gather:
- The old and new approved source files, plus a marked comparison.
- The matching approved translations and available translation memory.
- Languages, regional preferences, intended readers, and purpose.
- A change log covering text, images, tables, links, and deleted content.
- Final file formats, layout needs, and accessibility requirements.
- The deadline, review contact, and any AI or confidentiality restrictions.
Ask the provider to describe what it will reuse, what it will translate or review, and what could change the price. Confirm whether final client corrections will be reflected in the editable files and translation memory.
Make the Next Update Easier
The next translation update becomes easier when today’s project ends with organized files, documented approvals, and clear reuse arrangements.
Start with one recurring document or content series. Gather its files, identify the steps that repeatedly create extra work, and ask your provider to explain the available options. You can then make a practical decision about where to spend and where to save.
If you have questions or are ready to update your translated materials, contact NWI Global. Share your current files, previous translations, and intended changes so we can discuss the work your project needs.



