Technical Manual Translation: Where the Cost Really Comes From, and How to Cut It Without Losing Accuracy
The cost of technical manual translation depends less on the per-word rate than on how much of each manual you pay for twice: repeated content translated again, late source changes, PDFs rebuilt by hand and terms argued over in review. Manufacturers cut it by reusing their own memory and glossary on every release. DEMA Solutions builds that reuse into every manual project.
Why does the translation line of a machine project never seem to shrink?
This guide is written for the people who carry manuals from the technical office to export markets: technical documentation managers and technical writers who prepare the source, procurement managers who compare quotes, and operations directors who want to know why the translation line of a machine project never seems to shrink. Most of them work at manufacturers of equipment that ships with a thick set of documents, such as operating and installation manuals, maintenance manuals, spare parts catalogues, HMI strings, safety warnings and CE technical files.
Their questions are practical. Why do two quotes for the same manual differ so much? Why does a slightly changed manual cost almost as much as the first edition? Where can we save without putting a safety instruction at risk? We do not quote prices here, because a fair price depends on your files and your history, but we explain how a quote is built so you can judge any offer yourself.
How a technical manual translation quote is built
A quote for technical documentation translation starts with an analysis of the source files against your existing translation memory. The analysis splits the text into segments, usually sentences, and sorts every segment into a category. That breakdown, not the headline word count, is what decides the cost.
New words are segments that have never been translated for you before. They need full translation and full revision, and they make up the core of the price.
Fuzzy matches are segments similar to something already translated: a sentence where only a value, a component name or a word order changed. The linguist starts from the earlier translation and edits it, so these are normally charged at a reduced rate that depends on how close the match is.
Exact matches and context matches are segments already translated and approved in the same or a very similar context. They still need checking in place, because a correct sentence can sit in the wrong context, but the effort is much lower.
Repetitions are segments that occur more than once within the files being quoted. A warning repeated on forty pages is translated once and checked where it appears.
On top of the linguistic work, a quote may include project management, file preparation, desktop publishing, terminology work and extra review rounds.
A simple example from maintenance manual translation shows why this matters. Imagine a new maintenance manual of 40,000 words for a machine that shares its platform with an existing model. If the analysis shows that half the text is an exact or near match from the earlier manual and a further quarter consists of internal repetitions, the genuinely new part is about 10,000 words. A quote built on that analysis looks very different from one that charges all 40,000 words at the full rate, even if both use the same per-word figure. When you compare offers, this is the first thing to look at.
Why the per-word rate is the wrong number to compare
Procurement teams are often asked to compare suppliers on rate per word, because it is the number that fits in a spreadsheet. For technical manual translation services, it tells you very little on its own. Two suppliers with the same rate can produce totals far apart if one applies your memory fully and the other treats the manual as new text. A lower rate can also hide costs that appear later: layout work quoted separately, review rounds charged per hour, or a PDF conversion added to every language.
The more useful questions are about the total cost of a release. How much of this manual will be charged as new? How are fuzzy matches and repetitions priced? Who rebuilds the layout, and is that in the price? What happens when the source changes halfway through? Who owns the translation memory at the end, and can you take it with you? The answers turn a rate into a forecast, and they are worth asking every supplier in the same form. Our article on how to choose a technical translation company sets out these questions in more detail.
How the source format drives the cost
Most manuals arrive for translation as PDFs, because a PDF is what the technical office has to hand. But the format you send has a direct effect on cost and on the risk of errors. Beyond the format, a complete request also needs memories, glossaries and reference material, all listed in our guide to what to send a translation supplier.
Word and other editable formats are the easiest case. The text can be extracted cleanly, translated against your memory and put back into the same structure. Styles, numbering and cross-references survive, and the translated file comes back ready to check.
InDesign and FrameMaker files are equally good sources when the original package is complete, with fonts and linked images. Translation works directly on the text layer, and desktop publishing handles the adjustments needed in each language. FrameMaker books with many chapters and conditional text need someone who understands how the book is built, but the reuse they allow is excellent.
DITA, XML and CCMS output give the best leverage of all when they are well structured, because topics are reused across manuals by design and only changed topics need translation. The condition is that the structure is respected: tags, attributes and conditional content must come back exactly as they were sent.
PDF is the expensive case. The text has to be extracted, the document rebuilt into an editable layout, and only then translated and laid out again in each language. Extraction can split sentences at line breaks, which lowers memory matches and confuses the analysis. Scanned PDFs need OCR before anything else can happen.
A PDF is not a dead end. Our DTP team regularly turns PDFs into editable files before translation starts, and the DTP file preparation service explains how that step works. The point is that it is a cost you pay on every project if the editable source never comes back into your hands. When the rebuilt file is delivered to you and becomes your new master, the next edition can start from an editable file and the conversion cost does not recur.
Desktop publishing and text expansion
Layout is the most underestimated part of the budget for technical documentation translation. Translated text is rarely the same length as the source: German and Italian versions of an English manual often run longer, and labels, tables, callouts and HMI screenshots have fixed space. When translated text is delivered loose, someone in your company has to paste it into the layout, fix broken pages, shorten callouts and check that every figure reference still points to the right place. That work is invisible in a translation quote, but it shows up in your team’s hours and in delays.
Keeping multilingual desktop publishing inside the same workflow as translation means that the person adjusting the layout can ask the linguist about a shortened label, that page breaks are checked in every language, and that the manuals come back ready to print or publish. Problems such as untranslated text inside images are then found before delivery, not by a service technician on site.
Terminology and review: the hidden cost of inconsistency
A large share of avoidable cost in technical manual translation comes from review rounds. Your engineers, subsidiaries or distributors send back changes, many of which are preferences rather than errors: a different word for the same component, or a name that changed in the source two editions ago. Every round costs time and delays the release.
The cure is to decide terminology once. An approved multilingual glossary of component names, safety terms, HMI labels and process terms, agreed with your experts and your markets, means that the translator applies the agreed term and the reviewer checks against it rather than against personal preference. Our guide to glossary management and translation consistency explains how to build one and keep it alive. The same glossary should serve the manual, the spare parts catalogue and the interface texts, because a technician who reads one name in the manual and sees another on the screen will hesitate at exactly the wrong moment.
The cost of late source changes
Machine projects rarely freeze the documentation early. Design changes arrive late, a component supplier changes, a safety review adds a warning, and the manual is updated while translation is already under way. How this is handled makes a large difference to cost.
The expensive pattern is to send a complete new manual each time something changes, so that every resubmission risks being treated as a new job. The efficient pattern is to work at segment level: the new version is analysed against the memory that already contains the work done so far, unchanged segments are confirmed automatically, and only changed and new segments are translated. For that to work, it helps to tell your supplier at the start that changes are expected, to send changes as updated source files rather than as comments in a PDF, and to agree on a cut-off after which only critical changes go in before release.
Fix it upstream: single-sourcing and controlled language
Some of the largest savings are made before translation starts, in the way the source is written. When several authors describe the same procedure in slightly different words, the memory cannot recognise the second version, and you pay for it again in every language. This kind of authoring drift is common in companies where manuals have grown over many years and many product families.
Two practices help. Single-sourcing means writing content once and reusing it wherever it applies, through DITA or simply through disciplined reuse of chapters, warnings and procedures in Word or FrameMaker. Controlled language means one term per concept, one action per step and consistent phrasing for warnings. Both make the source clearer for the end user and raise the share of each new manual already in your memory. Starting with safety warnings and recurring maintenance procedures already pays back on the next release.
What changes over several revisions
The first translation of a manual into a new language is the most expensive one, because there is little or nothing to reuse. What matters for budgeting is what happens afterwards. When each release is translated against a memory that contains every approved sentence from the previous ones, the share of new content in each update usually falls, and the cost of an update follows the amount of real change rather than the size of the manual.
That only works under three conditions. The memory must be maintained, with approved corrections fed back into it rather than made only in the final layout. It must be yours, in a portable format, so that the reuse does not depend on staying with one supplier; who owns your translation memory is worth settling in writing before the first project. And the reuse must be visible: a leverage report for every job, showing how much came from the memory and how much was new, lets operations and procurement see whether the trend is going the right way.
When machine translation with post-editing fits
Machine translation can reduce time and cost for some kinds of technical content, provided it is controlled by your own glossary and memory and a qualified linguist post-edits the result fully. It fits best with large volumes of recurring, well-structured text with stable terminology, such as service procedures, internal documentation and some spare parts descriptions. It fits less well with content where a mistranslation has safety or legal consequences, with new products whose terminology is not yet agreed, and with marketing-style passages inside a manual.
Raw machine output is not suitable for manuals that customers, service technicians or authorities will read. Our article on machine translation post-editing looks at where that line falls today.
Where you should not cut
Some savings cost more later. Safety warnings and instructions must be correct and consistent in every language, and the Machinery Regulation (EU) 2023/1230, which applies from 20 January 2027, keeps instructions in a language the user understands a legal requirement; our guide to the Machinery Regulation and translated documentation explains what changes. Numbers, units and tolerances deserve the same care: a fluent sentence with a wrong torque value is worse than an awkward sentence with the right one. And revision by a second qualified linguist is not the place to save, because the errors it catches are the ones that are most expensive to fix after the manual has shipped. Our article on checking translation quality before you hire a supplier covers what a reliable revision step looks like.
An error in a manual rarely costs just a retranslated sentence. It costs a reprint, a corrected PDF for every distributor, a delayed acceptance at the customer’s site or, at worst, an incident.
How to reduce technical manual translation cost, step by step
Pulling the sections above together, this is the sequence we recommend to manufacturers who want to bring the cost of each release down without risking accuracy:
- Collect what you already own. Gather previous translations, existing memories and any glossaries from past suppliers, and have them aligned into a memory that belongs to you.
- Agree terminology once. Build an approved glossary with your engineers and markets, starting with components, safety terms and HMI labels.
- Send editable sources. Send Word, InDesign, FrameMaker or XML files instead of PDFs, and if only a PDF exists, have it converted once and keep the editable result as your new master.
- Ask for an analysis-based quote. Compare offers on the breakdown of new words, fuzzy matches and repetitions, and on what is included for layout and review.
- Plan for change. Agree how late source changes will be handled, and send updates as files analysed against the memory rather than as complete new jobs.
- Keep layout in the same workflow. Have translated manuals delivered laid out and checked for text expansion in every language.
- Write for reuse. Introduce single-sourcing and controlled language for warnings and recurring procedures, so each new manual reuses more.
- Track leverage over time. Ask for a leverage report on every job and review the trend with procurement and operations once or twice a year.
How DEMA Solutions handles technical manuals
Manufacturers that translate documentation continuously send us Word, InDesign, FrameMaker, DITA and XML files, and often PDFs that our in-house DTP team first turns back into editable sources so nothing is retyped or paid for twice. Our technical translation services run on an ISO 17100 certified process, audited every year, in which a second qualified linguist revises each translation; our quality page covers the details. Each client has a dedicated translation memory and approved glossary that remain the client’s property in portable formats, so the savings from reuse travel with you. After more than 20 years in technical documentation, our teams in Italy, Serbia and Spain handle translation and layout together and deliver each manual laid out in every language.
Example: from shipment risk to routine
One of our clients, an Italian manufacturer of industrial equipment, exports most of what it builds. Every machine ships with operating and maintenance manuals, safety information and interface texts in the language of the destination market. New machines are often configurations of an existing platform, and the technical content can still change close to shipment.
Before, every order meant coordinating language and layout suppliers again and paying for content already translated for a previous variant. Today the documentation runs through one managed process: a dedicated project manager, a memory that recognises content repeated across variants, an approved glossary, the same linguists on the same product families, in-house layout and a defined route for urgent jobs. The office no longer coordinates suppliers for each shipment, and each new manual gets more efficient because more of it has already been approved. You can read the full story in the industrial manufacturer case study.
Where TUBE fits
For manufacturers with a continuous documentation programme, TUBE keeps the effort of each release focused on what is genuinely new. Sentences already approved in earlier manuals are reused automatically from a memory you own, your glossary guides machine translation for the rest, and a transparent leverage report on every update shows exactly how much of the release came from reuse.
Frequently asked questions
It depends on the length of the manual, the number of languages, the source format, the amount of layout work and, above all, how much of the text is already in your translation memory. For an update, new and changed content is the main cost. Ask for a quote based on an analysis of your files against your memory, not only a per-word rate.
Usually because the previous translations were not reused: the memory was not available, the source was sent as a PDF that extracted differently, or the text was rewritten in different words even where the meaning did not change. An analysis against the right memory and a consistent source normally shows a much smaller new part.
The editable source whenever possible: Word, the original InDesign or FrameMaker package with fonts and images, or DITA and XML files. Add previous translations, any glossary and reference material. A PDF can be converted into an editable file, but that adds a step and is best done once, with the result kept as your new master.
The company that paid for the translations. A memory you own, in a standard exchange format, lets you reuse approved work with any supplier and protects the savings you have built up over several releases.
For recurring, well-structured content with stable terminology, machine translation fully post-edited by a qualified linguist can work. Raw machine output is not suitable for manuals that customers or technicians rely on, and safety warnings need full human attention.
Yes. In the EU, instructions for machinery must be supplied in a language accepted by the country where the machine is used, and the Machinery Regulation (EU) 2023/1230 applies from 20 January 2027. Other product legislation sets similar rules for instructions and safety information.
Pay for what is new, not for what you already own
If your manual translations cost about the same every release, a large part of that cost is probably repeated work. Send us a recent manual and tell us how often it changes, and we will show you how much of it your existing translations could already cover.
How can we help?
Tell us what you need and we’ll get back to you with the solutions.