1 · What the standard is, and why it matters
ISO 18587:2017 "Translation services — Requirements for post-editing of machine translation output" sets the requirements for the full human post-editing of machine-translated (MT) text and the competences a post-editor must have. MT — including our AI engine — is fast but never reliably correct. Post-editing is what turns raw MT into a deliverable of the same quality as a human translation. Working to the standard gives us a consistent, defensible process and real credibility with clients.
2 · Key definitions
- MT — automated translation produced by software/AI.
- Post-editing (MTPE) — the human editing of MT output to reach the required quality.
- Full post-editing — output comparable to a human translation: accurate, fluent, correct, stylistically appropriate.
- Light post-editing — merely comprehensible and accurate; minimal edits. Never for client-facing legal / tax / accounting documents.
- At CLA: all client-facing documents are FULL post-editing.
3 · Competences a post-editor must have (ISO 18587 §3)
Translation competence · linguistic & textual competence in source and target · research and information competence · cultural competence · technical competence · domain competence (legal / tax / accounting) · and knowledge of MT — how it works and the errors it typically makes.
4 · The MTPE process
- Pre-production — confirm the content is suitable for MT; the language pair, domain, glossary, client specs, and confidentiality.
- Production — post-edit against the full-PE requirements below. Re-use as much usable MT as possible — efficiency is part of the standard, not a shortcut.
- Post-production — self-QA (terminology, completeness, formatting), proofread, sign off, deliver; flag systematic engine errors so we improve the glossary/engine.
5 · Full post-editing — what "done" means
- Accuracy — no additions, omissions or mistranslations; meaning fully preserved.
- Terminology — correct, consistent, glossary-compliant (CLA Glossary).
- Grammar, syntax, spelling, punctuation — correct for the target locale.
- Register & style — formal, client-appropriate; correct legal/financial idiom (e.g. "IN WITNESS WHEREOF" → "DREPT PENTRU CARE").
- Locale conventions — dates, numbers, currency, names, capitalization, quotation marks (RO «…», FR spacing before : ; ? !).
- Formatting & tags — structure, headings, tables, placeholders preserved.
- No over-editing — keep correct MT; change only what quality requires, not personal preference.
6 · Common MT errors to catch (especially neural/AI MT)
Dropped or invented clauses ("hallucinations") · terminology drift · mistranslated party / company names · altered numbers, dates, currencies, units · gender / agreement errors · false friends · ambiguous pronouns · legal formulas translated literally instead of idiomatically · register too casual.
Never paste confidential or client data into public / free MT engines. Use only CLA-approved engines (this Translation Workbench). Treat every source as privileged.
8 · Records (the evidence for certification)
Each job records the language pair, engine, post-editor, full/light PE, and QA sign-off. This audit trail is exactly what an ISO 18587 certification assessment looks for — the Workbench captures it automatically.