HAMT (Human-Assisted Machine Translation)
A localization workflow where machine translation produces the first draft and a human handles the corrections that machines tend to get wrong.
Human-assisted machine translation (HAMT) combines automated output from MT engines or LLMs with a human pass that fixes mechanical and structural issues. The human does not retranslate from scratch. They pick the best engine output, then correct things like glossary adherence, placeholder integrity, tag handling, formatting, and consistency across repeated segments.
HAMT is sometimes described as a form of pre-editing or post-editing of machine translation, depending on whether the human cleans up the source before translation or the output after. The shared idea is the same: most of the volume is produced by a machine, and a human focuses on the parts machines reliably miss. This keeps cost and turnaround low while reducing the obvious errors that pure MT leaves behind.
🌍 HAMT in localization #️⃣
Localization workflows often deal with repetitive UI strings, technical documentation, and content where rough accuracy matters more than stylistic finesse. HAMT fits well here. It is commonly used for:
- Entering new markets where budget or timing rules out full professional translation.
- Languages that need a working version but are not a commercial priority.
- Large volumes of repetitive content where engine output is already close to acceptable.
- Continuous localization pipelines where strings arrive constantly and waiting for human translation would block releases.
The trade-off is scope. HAMT focuses on mechanical correctness, not native-level fluency. The person handling the strings may not be a native speaker of every target language, since the work is structural rather than editorial. Teams that need polished phrasing pair HAMT with a separate native-speaker review or skip it in favor of professional human translation services.
🧩 What HAMT covers in practice #️⃣
- Glossary adherence. The human checks that approved terms are used consistently and replaces engine choices that are not meaningfully correct.
- Placeholders and tags. Variables like
{username}, ICU plurals, and inline tags are preserved and positioned correctly. - Consistency across segments. Repeated or near-identical strings get the same treatment, instead of varying by engine guess.
- Formatting and punctuation. Quotation marks, spacing, capitalization, and locale-specific punctuation are normalized.
- Engine selection. When multiple engines are available, the human picks the best candidate per segment rather than locking to one source.
- Obvious errors. Clear mistranslations and broken output are caught, even when deeper stylistic issues are left alone.
⚖️ HAMT vs. professional human review #️⃣
These two are easy to confuse because both involve a human editing existing translations. The difference is what the human is checking.
- HAMT focuses on structural correctness. The reviewer ensures the output is mechanically sound and usable, without guaranteeing native-level fluency.
- Professional human review is an editorial pass by a native speaker who evaluates phrasing, tone, and cultural fit, and rewrites where needed.
Those who want hands-off mid-tier quality translations typically choose HAMT. Teams that need polished, market-ready copy add professional human review on top, or start with professional human translation instead.
📚 For how HAMT fits alongside other translation options on Localazy, see the translation services documentation.


