Machine Translation Post-Editing: What It Is and Why Teams Use It
Machine translation post-editing (MTPE) is the process of having a qualified human linguist review, correct, and finish the output of an automated translation engine before it ships. The engine produces a draft; the post-editor fixes mistranslations, enforces approved terminology, repairs formatting and tags, and brings the text up to an agreed quality level. It is a translation process with a different starting point — not an automated substitute for translation judgment.
That distinction matters. Raw machine translation is unreviewed engine output: fast, cheap, and acceptable for gisting or internal triage, but unverified against your glossary, style rules, or regulatory wording. MTPE produces a deliverable someone has signed off on. The international standard for this work, ISO 18587:2017, sets requirements for the full human post-editing process and for post-editor competence, and is written for translation service providers, their clients, and post-editors alike. It was published in 2017 and is flagged for revision.
Documentation and localisation leads look at MTPE for three reasons: throughput on large or frequently updated content sets, terminology consistency across releases, and predictable cost per word.
The harder questions are when it fits, when it does not, and what quality to expect by content type — answered here for software and manufacturing content specifically, not general-purpose translation.
When Post-Editing Makes Sense and When Full Human Translation Is the Safer Choice
Two questions settle most cases: can this content tolerate an accurate but plain rendering, and is your source text clean enough that editing is faster than translating?
Post-editing is usually worth it for repetitive, tightly scoped material — UI strings, parts catalogues, maintenance procedures, release notes, support articles — where terminology is controlled by a glossary and translation memory, the source is stable between releases, and the consequence of an awkward sentence is confusion rather than injury or a failed audit. Engine quality on your own content is the pivot: a study of machine translation quality and post-editor productivity found each one-point gain in BLEU cut editing time by roughly 0.16 seconds per word (about 3–4%), while weaker output drove up effort and pushed final quality down.
Full human translation is the safer choice for safety-adjacent instructions such as warnings and lockout steps, compliance-heavy documents that support a conformity declaration or regulatory file, high-visibility customer copy where tone and brand voice carry weight, and any text that needs restructuring rather than sentence-level correction. When the editor would rewrite most segments anyway, the savings disappear.
Raw output has a narrow but real role: internal comprehension and triage — scanning a supplier email, reading a field report, deciding which documents deserve budget. It is not a publishing path.
Then check operational readiness before committing: consistent source authoring, an approved termbase, segmentable formats (XLIFF, RESX, DITA rather than flattened PDFs), and a named reviewer per language with actual capacity. ISO 18587, published in 2017 and flagged for revision, sets out requirements for the full post-editing process and post-editor competence — useful language for specifying what you expect from a provider.
The tradeoff is blunt: post-editing buys speed only when the source and the workflow are clean enough to avoid rework.
Where MTPE Fits in Software and Manufacturing Content
Post-editing works best where content is repetitive, structured, and already written with translation in mind. In software, that usually means release notes, help-center articles, UI strings, and installation guides. These share a narrow vocabulary, reuse phrasing across versions, and live in modular files, so the engine has seen the pattern before and the editor is mostly confirming terminology and fixing placeholders, plurals, and string length rather than rewriting sentences.
Manufacturing content follows similar rules. Operator manuals, product specifications, and maintenance instructions are typically written in short imperative steps with fixed component names. Where a controlled language rulebook is enforced — one meaning per term, no ambiguous pronouns, capped sentence length — machine translation output tends to arrive close to usable, and the review pass concentrates on units, part numbers, and figure callouts.
Safety-adjacent material is a different case. Warnings, lockout/tagout procedures, hazard statements, and anything feeding a declaration of conformity can still go through post-editing, but it needs a second reviewer with subject-matter knowledge and a documented sign-off. ISO 18587 describes full post-editing and post-editor competence requirements for exactly this reason.
Structure predicts effort more reliably than language pair does. Short strings, templated sections, and a stable glossary keep editing light; dense narrative, marketing-adjacent copy, and regulated text push effort toward full human translation.
The practical move is segmenting by risk rather than by file. Tag content into three buckets — light review, full post-editing, human-only — and route each accordingly. Most localisation teams find the first bucket is larger than expected.
Quality Levels, Review Effort, and the Risks That Change the Outcome
Post-editing is usually delivered at one of two levels. Light post-editing aims for accurate, understandable text: the editor fixes mistranslations, dropped content, and terms that would mislead a reader, but leaves wording that is merely clumsy. Full post-editing aims for output that reads as though it were written by a translator in the target language — consistent terminology, correct register, and syntax a technical writer would accept. ISO 18587:2017 sets requirements for the full post-editing process and for post-editor competence, and is written for providers, clients, and post-editors alike. It was published in 2017 and is flagged for revision, so treat it as a process baseline rather than a current statement of engine capability.
Review effort tracks engine quality closely. Research presented at AMTA 2016 on machine translation quality and post-editor productivity found that each one-point gain in BLEU score cut post-editing time by roughly 0.16 seconds per word — about 3–4% — and that weaker output raised effort while producing lower final quality. Poor raw output does not just cost more time; it degrades the deliverable.
That makes the workflow around the editor as important as the editor. Locked terminology lists, a subject-matter expert pass on safety and configuration content, a defined QA checkpoint, and clean file handling for structured formats all change the outcome more than the engine choice does.
The recurring failure modes in software and manufacturing content are predictable: terminology that drifts between strings and manuals, technical terms translated in their general sense, syntax that is grammatical but unnatural, and ambiguous source segments with no context for the editor to resolve.
Set the quality target by use case. A UI string, a maintenance procedure, and a regulatory declaration do not need the same standard, and no honest process promises that every post-edited segment is publication-ready.
What the Standards and Workflow Evidence Say About MTPE Effort
There is a formal reference point for this work: ISO 18587:2017, Translation services — Post-editing of machine translation output — Requirements. It sets out requirements for the full human post-editing process and for post-editor competence, rather than treating editing as an undefined cleanup step. The standard was published in 2017, and ISO’s catalogue entry lists it as under revision, so treat it as a stable baseline for process design rather than a current statement on engine capability.
Its intended audiences matter as much as its contents. ISO frames the document for translation service providers, clients, and post-editors alike — which makes it usable on the procurement side, not just inside a provider’s production team. If you are writing a statement of work, it gives you shared vocabulary for defining what "post-edited" means, who is qualified to do it, and what the deliverable should look like before it reaches your documentation set.
The productivity evidence is more specific. In a 2016 AMTA paper, Machine Translation Quality and Post-Editor Productivity, researchers found that each one-point gain in BLEU score cut post-editing time by roughly 0.16 seconds per word — about 3–4% — and that weaker raw output raised editing effort while lowering the quality of the final text.
The practical reading for localisation leads: post-editing is not a fixed-cost shortcut. Its cost curve bends with source-text quality and engine output quality, which means review planning has to be estimated per content type and per language pair. Budget editing hours against measured engine performance on your own material, not against a blanket percentage discount.
Cost, Speed, and Quality: What Buyers Should Expect from MTPE
Post-editing sits between raw machine translation and full human translation on both cost and turnaround. Vendors report meaningful gains: POEditor’s blog claims post-editing can cut delivery times by roughly half, and Crowdin reports that around half of companies now post-edit their machine translation output rather than publishing it untouched. Treat those figures as vendor benchmarks, not guarantees — your savings depend on the engine, the language pair, and the content.
Speed is a function of how much editing the text actually needs. Research presented at AMTA 2016 on quality and post-editor productivity found each one-point gain in BLEU score reduced post-editing time by about 0.16 seconds per word, roughly 3–4%, with weaker engine output driving both higher effort and lower final quality. Clean, consistent source text, a maintained termbase, and segment-level context move that number more than any pricing negotiation will.
On quality, set expectations plainly: post-edited output is publication-ready only after review. ISO 18587:2017 defines requirements for full human post-editing and post-editor competence precisely because the review step is the deliverable, not an optional extra.
For budgeting, map content to risk. Raw machine translation suits internal or throwaway text; post-editing fits high-volume documentation with stable terminology; regulated, safety-critical, or brand-facing copy still warrants full human translation.
FAQ: Common Questions About Machine Translation Post-Editing
What is post-editing, in one sentence?
It is the process of having a qualified linguist review and correct raw machine translation output until it meets an agreed quality level — light for internal or short-lived content, full for published documentation.
Is it cheaper than full human translation?
Usually, but not automatically. Savings come from the engine doing enough of the work that the editor is correcting rather than retranslating. Weak source text, unstable terminology, tagged file formats, or a low-quality engine can push editing effort close to human translation levels — at which point you are paying for two steps instead of one. Research presented at AMTA 2016 on machine translation quality and post-editor productivity found that as engine output quality improved, post-editing time per word fell measurably, while poorer output raised effort and lowered final quality.
How much faster is it?
Faster on most repeatable content, though the gain varies by language pair, domain, and how clean the source is. Treat any single percentage figure as a vendor average, not a forecast; measure your own throughput on a pilot batch before committing a release schedule to it.
What quality can you expect for software and manufacturing content?
With controlled terminology, a trained engine, and defined QA checkpoints, full post-editing targets output comparable to human translation — the outcome ISO 18587:2017 describes for full post-editing and post-editor competence. Safety notices, regulated labelling, and marketing-facing copy still warrant human translation.
If you want a second opinion on where your content falls, Mesa Translation’s team can review a sample.
Leave a Reply