Machine translation post-editing

Also known as: MTPE

On this page 8

Machine translation post-editing (MTPE) is the process in which a qualified human linguist reviews and corrects text produced by a machine translation engine so that it meets a defined quality target. Among AI applications in artificial intelligence, it is one of the most mature examples of human-in-the-loop production: the neural engine drafts at high speed, and the post-editor supplies the judgment on meaning, terminology and tone that the model cannot guarantee.

MTPE is not proofreading a finished translation and not translating from scratch. It sits between the two, and its economics depend on how good the raw output is, how much quality the client actually needs and how carefully the effort is measured.

How the post-editing workflow operates

A post-editing workflow passes source text through an engine, then routes the raw machine output to a linguist who edits it inside a computer-assisted translation (CAT) tool. The tool shows source and target segments side by side, together with translation memory matches and approved terminology, so the editor can compare each machine suggestion against trusted references.

Modern engines are almost always neural machine translation (NMT) systems or general large language models prompted to translate. Their output is usually fluent, which is precisely the danger: fluent errors such as a dropped negation, a wrong number or an invented term read naturally and are easy to miss. The post-editor therefore checks meaning against the source first and style second.

The typical stages are shown below, from preparation to delivery.

StageWhat happensWho or what does it
Pre-processingCleaning source files, protecting tags and placeholdersProject manager, scripts
Engine selectionChoosing a generic or domain-adapted engine per language pairLocalization engineer
Raw translationEngine translates segments not covered by memoryNMT engine or language model
Post-editingLinguist corrects meaning, terminology and styleProfessional post-editor
Quality assuranceAutomated checks for numbers, tags, terminology and consistencyQA tool plus reviewer
Feedback loopEdited segments feed memories and engine retrainingLocalization team
Stages of a typical MTPE workflow

Light and full post-editing levels

Post-editing is defined by its target quality level, agreed before work starts. The international standard ISO 18587 sets requirements for full post-editing, and industry guidelines distinguish it from light post-editing, which aims only at understandable and accurate text.

The distinction matters because the two levels differ in effort, price and suitable content. Mixing them up is a frequent cause of disputes between buyers and vendors.

LevelQuality goalTypical contentWhat the editor ignores
Light post-editingAccurate and understandable meaningInternal documents, knowledge base triage, gistingAwkward but correct style, minor repetition
Full post-editingQuality comparable to human translationProduct interfaces, contracts, published documentationNothing that affects meaning, style or terminology
Transcreation reviewAdapted message for a target marketMarketing slogans, campaignsLiteral fidelity, when creativity requires it
Comparison of post-editing levels

For regulated or high-risk text, such as medical labeling, legal agreements or safety instructions, full post-editing is normally followed by an independent second review. A single pass over machine output is rarely sufficient where an error can cause harm or liability.

Measuring post-editing effort and productivity

Post-editing effort is measured with time-based and edit-based metrics, because the number of words alone says nothing about how much work the machine output required. Pricing, engine evaluation and vendor comparison all depend on these measurements.

MetricWhat it measuresHow it is used
Edit distanceShare of characters or words changed by the editorComparing engines and adjusting rates
HTERHuman-targeted translation edit rate against the final editResearch and engine benchmarking
ThroughputWords edited per hour or per dayPlanning capacity and deadlines
Keystroke and pause dataTyping activity and hesitation in the CAT toolDetecting cognitively difficult segments
Error annotationErrors classified by type and severityFinal quality acceptance
Common metrics for post-editing effort

Productivity gains vary widely. For well-supported language pairs and repetitive technical content, editors often process roughly one and a half to three times the volume of translation from scratch. For low-resource languages, creative text or poor source quality, the gain can shrink to nothing, and editing may even be slower than translating.

MTPE is one of several ways to combine machines and people in translation, and each assigns responsibility differently. The table separates it from neighboring approaches that are often confused with it.

ApproachStarting pointHuman roleMain risk
Raw machine translationEngine output onlyNone or spot checksUndetected meaning errors
Machine translation post-editingEngine outputSystematic correction to a target levelAnchoring to the machine wording
Interactive translationEngine suggestions while typingTranslator writes, engine predictsOver-acceptance of suggestions
Human translation with memoryPreviously approved segmentsTranslator writes new textHigher cost and longer turnaround
Pre-editingSimplified source textWriter adapts source for the engineUnnatural source style
MTPE compared with related translation approaches

Related AI applications such as AI dubbing and AI writing assistants reuse the same pattern: a model drafts, and a human edits to an agreed standard. MTPE is distinctive because translation quality can be judged against an explicit source text.

Choosing content and engines for post-editing

MTPE pays off when the content is repetitive, structured and terminologically stable, and when the engine has been tested on representative samples. A short pilot with measured edit distance is the most reliable way to decide whether a language pair and content type are suitable.

SituationRecommended approachReason
Technical manuals in a major language pairFull post-editingHigh engine quality and stable terminology
Customer support tickets for internal triageLight post-editing or raw outputSpeed matters more than polish
Marketing campaign copyHuman translation or transcreationTone and cultural fit dominate
Clinical trial documentsFull post-editing plus second reviewRegulatory exposure and patient safety
Low-resource language pairPilot first, then decideEngine quality is unpredictable
Decision guide for applying MTPE

Domain adaptation usually improves results more than switching vendors. Training or prompting an engine with the client’s translation memories and glossaries reduces terminology errors, which are among the most time-consuming corrections for editors.

Limitations and common mistakes

The main weaknesses of MTPE come from human factors and from the nature of neural output rather than from the editing method itself. Experienced teams watch for the following problems.

  • Priming and anchoring: editors tend to keep machine wording that is acceptable but unidiomatic, which flattens style across large projects.
  • Hidden omissions: neural engines sometimes skip a clause entirely, and a fluent target sentence hides the gap.
  • Unfair pay models: flat discounts per word ignore segments that need complete retranslation, which damages editor motivation.
  • Confidentiality: sending client text to a public engine can breach data protection obligations and contracts.
  • Cognitive fatigue: correcting many near-correct sentences is tiring, and attention drops in long sessions.

A sound program addresses these risks with secure engine deployment, effort-based compensation and automated QA checks for numbers, negations and terminology.

Stripped to the essentials

A computer can translate a page in seconds, but it does not truly understand what it reads. It may get a number wrong, drop a word like “not” or use the wrong technical term while still sounding confident. Post-editing means a trained translator reads the computer’s version next to the original and fixes these mistakes.

Think of it like a first draft written by a fast assistant. The machine saves typing; the human guarantees meaning. How much the human polishes depends on what the text is for: a quick internal note needs only correct meaning, while a published manual needs to read as if a professional wrote it.

Where it is applied

A manufacturer of industrial pumps needs its 300-page maintenance manual in German, Polish and Spanish within three weeks. The localization team runs a pilot on 2,000 words per language with an engine adapted using its existing translation memories, and measures an edit distance of about 20 to 25 percent for German and Spanish, but over 40 percent for Polish.

The team assigns full post-editing for German and Spanish, where editors deliver roughly twice their usual daily volume, and chooses conventional translation with memory support for most of the Polish content. Every language then goes through automated checks for torque values, part numbers and warnings. The manuals ship on schedule, and the corrected segments are fed back into the memories to improve the next update.