What machine translation, MTPE, and human translation mean for engineering documentation
Three approaches sit behind most quotes for technical content, and the labels are often used loosely.
Machine translation is translation generated by software — engines like DeepL, Google Translate, or a custom model trained on your own data. It produces a draft fast, but for engineering content that draft is a starting point, not a deliverable.
Machine translation post-editing (MTPE) is what happens next: a human editor works through the raw output and corrects it. ISO 18587:2017, a 15-page standard published in April 2017, frames post-editing exactly this way — a human process applied to content that has already been processed by a machine translation system, with requirements aimed at providers, clients, and post-editors alike.
Human translation means a qualified translator writes the target text directly, without an engine draft underneath it.
The documents at stake here are engineering manuals, installation guides, service bulletins, and anything governed by controlled terminology — parts names, safety warnings, units, and interface strings that must match across versions.
Choosing between the approaches comes down to five practical factors: accuracy, terminology control, turnaround speed, cost, and how much review effort lands on your team afterwards.
One 2026 caveat: ISO/DIS 18587, a 23-page draft replacement, is in the enquiry phase. Confirm current workflow expectations with your provider rather than assuming the 2017 text is settled.
When machine translation is not enough for manuals and engineering content
Raw machine translation fails in engineering documentation at exactly the points where errors are most expensive. A warning that shifts from "do not energise before lockout" to a permissive phrasing, a torque figure carried over with a decimal separator swapped, a numbered installation sequence reordered because the source sentence used a subordinate clause, or a component that appears as three different names across the assembly manual, the label artwork, and the service bulletin — each of these is a defect a reader will act on before anyone notices.
Controlled terminology is the first thing to break. Engines translate sentence by sentence, so the same part can be rendered differently in section 4 than in section 9, and neither version may match the wording etched on the machine. Formatting suffers too: symbols, units of measure, cross-references, and callout numbers keyed to exploded diagrams often survive the translation step but stop pointing at the right thing.
This is where quality becomes a compliance question rather than a stylistic one. ManufacturingTomorrow’s argument that technical translation must be accurate for manufacturers also notes that translation on its own may not be enough — market-specific units, regulatory phrasing, and audience-appropriate instructions need localisation, not just language transfer. Documentation that supports a declaration of conformity or a liability defence has to read as if it were written for that market.
A reasonable line: raw output can serve low-risk internal reference material — engineering notes, ticket threads, draft specifications read by colleagues who can spot nonsense. Anything that guides assembly, maintenance, or operator safety needs human-led work from the first pass.
MTPE vs human translation: accuracy, terminology, speed, cost, and review effort
Neither approach wins across the board. The right answer depends on what your source content looks like and what happens if a sentence is wrong.
Accuracy. Post-editing works best when the source is clean, consistent, and repetitive — parts lists, maintenance steps, UI strings, revised sections of an existing manual. When meaning is dense, ambiguous, or safety-critical (warnings, residual-risk statements, procedures where sequence matters), full human translation holds up better, because the translator resolves ambiguity in the source rather than reproducing it. ManufacturingTomorrow makes the same point from the manufacturer’s side: accurate technical translation is a requirement, not a nice-to-have, and translation without localisation can still leave a document unusable.
Terminology control. Human translation generally gives tighter control over preferred terms, especially where a part name, a hazard word, or a regulated phrase must match your approved glossary exactly. Machine translation output can be brought to a similar standard, but only if the glossary, termbase, and style guide are enforced in the engine and re-checked during post-editing — not assumed.
Speed. For high volumes of repetitive content, post-editing is usually faster and scales better under release deadlines. Human translation takes longer per thousand words, but often reduces the correction cycles that follow, so the calendar difference narrows once review is counted.
Cost. Post-editing lowers the first-pass price. Total cost is the first pass plus subject-matter expert review, quality assurance, terminology fixes, and rework. On complex or poorly structured source text, that tail can erase the saving — which is why the per-word rate alone is a weak basis for a decision.
Review effort. Both need technical validation by someone who knows the product. The difference is linguistic: post-edited content requires a defined post-editing step under a documented process, which ISO 18587:2017 specifies for content processed by machine translation systems. Human translation typically needs less linguistic cleanup, but the engineering review does not go away.
The process is built around quality, compliance, and controlled terminology, so it is a stronger fit for regulated documentation than for buyers whose main constraint is the lowest possible first-pass cost.
How to choose MTPE, human translation, or a hybrid workflow for engineering documentation
The decision rarely comes down to language pairs. It comes down to what happens if a sentence is wrong.
Choose MTPE when the content is repetitive, the terminology is already controlled in a termbase or glossary, and the schedule allows a structured post-editing and quality assurance pass. Parts catalogues, UI strings pulled into help topics, revision histories, and reference tables usually fit. ISO 18587:2017 is the anchor here: it defines post-editing of machine translation output as a human process and sets requirements for providers, clients, and post-editors, which is why a post-editing brief should be written down rather than assumed. A draft replacement, ISO/DIS 18587, is in the enquiry phase, so buyers signing multi-year contracts in 2026 should ask which version their provider works to.
Choose full human translation when the passage is safety-critical, legally sensitive, genuinely ambiguous in the source, or written to be acted on — warnings, lockout and tagout steps, commissioning procedures, torque and tolerance instructions, declarations of conformity. ManufacturingTomorrow has argued that accuracy in manufacturing documentation is non-negotiable and that translation without localisation can still fall short; that risk profile does not suit raw engine output plus a light edit.
Choose a hybrid workflow when a single document set mixes both, which most manuals do. Route low-risk reference sections through MTPE and send hazard statements, procedures, and regulated passages to human translation, with the split defined at the section or content-type level in your authoring system so it survives the next release.
Subject-matter expert review sits on top of all three paths. A linguistic review catches grammar and terminology drift; it does not confirm that a described sequence matches the machine. For engineering content, plan an engineer or field service reviewer on the safety-critical passages regardless of which method produced the draft.
A short selection checklist keeps the choice defensible:
| Factor | Question to answer before routing |
|---|---|
| Content risk | Could an error cause injury, damage, or non-compliance? |
| Audience impact | Is the reader acting on this, or just consulting it? |
| Terminology maturity | Is the termbase current and approved? |
| Turnaround time | Does the release date allow a real review cycle? |
| Review resources | Is an SME actually available, with hours booked? |
Tie the result to your release plan. Corrections after publication cost more than the review you skipped — reprints, service bulletins, and re-approval cycles included.
What regulated and safety-critical manuals need from translation workflows
Safety and compliance content raises the bar on three things at once: terminology control, traceability, and depth of review. A marketing page can tolerate a synonym drift; a lockout procedure, a torque specification, or a residual-risk warning cannot. For these documents you need a locked glossary, a record of who changed what and why, and a named person accountable for the final technical read.
Post-editing of machine translation output can meet that bar, but only when four conditions hold together: a clean, unambiguous source text; enforced terminology and a maintained glossary; post-editors qualified in the subject matter, not just the language pair; and a technical validation step by someone who understands the equipment. Remove any one of those and the workflow stops being controlled.
Mixed treatment is normal and defensible. Installation steps, parts lists, and maintenance tables often run well through post-edited machine translation while warnings, safety instructions, and declaration text are translated and reviewed fully by humans within the same document set.
When evaluating a provider, ask for the written workflow, reviewer qualifications and credentials, how glossaries and translation memories are maintained between releases, and the specific quality assurance checks applied before delivery. ISO 18587 defines post-editing as a formal process for machine translation output — useful as a baseline, but it describes the process, not whether your content suits it. That judgement stays with you.
Is post-editing acceptable for regulated or safety-critical manuals? Yes, for lower-risk sections under a documented process with qualified reviewers and terminology control. For passages where a mistranslation causes injury or non-compliance, keep full human translation.
FAQ: MTPE, human translation, and engineering documentation in 2026
Is post-editing acceptable for regulated or safety-critical manuals?
Partly. For descriptive content — component lists, routine maintenance steps, UI strings already covered by an approved glossary — post-edited output can meet the same quality bar as a fully human pass. For warnings, residual-risk statements, lockout procedures, and anything a notified body or auditor will read line by line, treat human translation as the default and post-editing as the exception. ISO 18587:2017, published in April 2017 and currently being replaced by a draft update in its enquiry phase, sets requirements for the post-editing process itself; it applies only to content processed by machine translation systems and does not certify that any given passage is safe to automate. That judgement stays with you.
Should raw output ever ship without review?
Not for engineering documentation. Even where the source is clean and the terminology base is mature, unreviewed output carries no accountability trail, and a mistranslated torque value or negation is indistinguishable from a correct one to a reader who does not speak the source language.
How much review is normally needed afterwards?
It varies with three things: the risk class of the passage, how mature your termbase and translation memory are, and the document type. A service bulletin built from reused, previously approved segments needs far less intervention than a first-release installation guide in a new language pair.
Is human translation always more expensive?
Per word, usually yes. Per release, not necessarily. Once you count reviewer hours, terminology corrections that propagate across every future version, and the cost of reissuing a manual, the gap narrows — and on short, high-risk documents it can invert.
How do you decide quickly under release pressure?
Split the deliverable, not the standard. Route low-risk, high-reuse sections through post-editing, reserve human translation for safety and compliance content, and hold the release on the smaller human-translated portion rather than diluting review across everything.
The underlying rule is simple: match the workflow to what the content can do if it is wrong, not to how many words there are. If you want a second opinion on where your own documentation set falls, Mesa Translation can review a sample and map it against risk before you commit to a workflow.
Leave a Reply