For most regulated document work the honest answer is neither one nor the other: it is machine translation with a defined human post-editing step, performed against a published standard, with the division of labour written down. Pure automation is defensible for volume review, internal comprehension and discovery triage. Pure human translation is required where a named person must attest to accuracy. The expensive mistake is choosing between them at the vendor level instead of at the document level — and the second most expensive is assuming a compliance obligation exists where it doesn't.
This guide sets out which documents fall where, what the standards actually cover, and how to build a defensible file.
The Question Regulators Actually Ask
Regulators and courts rarely ask how a translation was produced. They ask who is accountable for it, and whether the process that produced it was controlled and repeatable.
That distinction matters more than the automation debate itself. A human translation with no recorded review step, no terminology control and no version trail is weaker evidence than a machine-translated document with a named post-editor, a documented term base and a retained audit log. "A person did it" is not, on its own, a compliance argument.
So the useful framing is not automated or human. It is: what standard of care does this document need, who signs, and can we reconstruct how the output was produced if asked eighteen months from now? Once those three are answered, the automation question usually answers itself.
What the Standards Actually Cover
This is where most vendor material — and a good deal of buyer assumption — goes wrong.
ISO 18587 is the standard for post-editing of machine translation output. It defines full post-editing, sets competence requirements for post-editors, and describes the process. If you are running a machine-first workflow with human review, this is the standard your process should map to.
ISO 17100 is the translation-services standard people cite more often — and it explicitly excludes machine translation post-editing from its scope. A vendor advertising "ISO 17100-certified AI translation" has either misread the standard or is hoping you will. It is a useful early filter in a procurement conversation.
ISO/IEC 42001 covers AI management systems, and is the one increasingly appearing in enterprise security questionnaires alongside ISO/IEC 27001 for information security and SOC 2 for service-organisation controls. None of these certifies translation quality. They certify that the organisation runs a managed process. Do not let a procurement team treat them as accuracy claims, and do not present them as such.
Where Automation Is Straightforwardly Defensible
Four categories, and they cover more volume than most compliance teams expect.
Comprehension and triage. Reading foreign-language material to decide what matters. In discovery, translating a document set to identify the two hundred documents worth human attention is standard practice — the machine output is a routing decision, not evidence.
Internal operating documents. Policies, training material, internal memoranda. Real consequences if wrong, but no external attestation and an internal audience who can escalate.
Volume review under time pressure. Data-room documents during diligence, regulatory correspondence backlogs, vendor contracts in a portfolio review. The alternative is not careful human translation; it is nobody reading them at all.
Reference versions alongside a controlling original. Where the agreement specifies a governing language, other versions exist to be understood, not to be enforced. Say so on the face of the document.
The common thread: no individual is attesting to the translation's accuracy, and a reader who hits something odd has a route back to the source.
Where a Human Signature Is Required
Fewer categories, but they are non-negotiable and they are where the liability sits.
Certified translations for official filings. Immigration, courts, registries. These require a signed statement of accuracy from a translator or agency — a human act, regardless of what produced the draft. In the United States, 8 CFR Part 103 governs the requirement for immigration filings; other jurisdictions have their own.
Sworn and court-appointed translation. Civil-law jurisdictions maintain registers of sworn translators whose seal carries legal weight. No software substitutes for the appointment.
Testimony and interpreted proceedings. Federal Rule of Evidence 604 requires an interpreter to be qualified and to give an oath. That is a person under oath, not a pipeline.
Documents forming the operative text of an obligation. Where the translated version is the binding instrument rather than a convenience copy, it needs the same review a drafted document would get.
Regulated product information. Pharmaceutical product information for EU marketing authorisations goes through the EMA's linguistic review process against QRD templates — a defined procedure with member-state review, not a translation task.
The Middle, Where Most Documents Live
Most regulated documents are neither triage nor sworn filings. Contracts under negotiation, financial statements for a foreign parent, board minutes, regulatory submissions that are not product information, policy documents with external readers.
For these, the workable structure is machine translation with full post-editing under ISO 18587, plus three additions that most implementations skip:
A term base agreed before the first document moves, with defined terms, party names and statutory citations locked. Enforcement is the cheap part; agreeing the entries is the work.
A risk-tiered review depth. Not every document in a set needs the same scrutiny. A schedule of definitions and an annex of historical correspondence do not warrant identical attention, and pretending otherwise means everything gets the same shallow pass.
A retained record of what was produced how. Source hash, engine and version, glossary version, post-editor, date, and what changed. This is the artefact that answers the regulator's actual question, and it costs almost nothing to keep if it is designed in from the start.
The Format Problem Nobody Budgets For
There is a failure mode specific to regulated documents that has nothing to do with linguistic accuracy.
Regulated documents are structured: numbered clauses, cross-references, defined-term tables, footnotes carrying substantive obligations, appendices referenced by number, signature blocks. A translation process that produces linguistically excellent output and renumbers the clauses has produced a defective document. Cross-references now point at the wrong provisions. Nothing errors, and a reader checking the language will not catch it.
This is why format preservation is a compliance property rather than a convenience feature, and why the check that matters is mechanical: extract every clause number, cross-reference and citation from source and target and compare the sets. They should be identical. It takes minutes and almost nobody runs it. The same discipline applies to audited financial statements translated across borders, where the note references have to tie out across the whole reporting set.
Building a Defensible File
If you take one thing from this, take the file structure. For any document where the answer might one day be challenged, retain:
The source document and a hash of it.
The translation method — engine, version, configuration.
The glossary or term base version applied.
The name and qualification of the post-editor or reviewer.
The changes made at review.
The date and the sign-off.
That record makes the automated-versus-human question much less fraught, because it answers accountability directly rather than by proxy. A process you can reconstruct is defensible. One you cannot is not — and that is true whichever side of the automation line it sits on.
Sources and Further Reading
ISO 18587 — requirements for post-editing of machine translation output
ISO 17100 — translation services requirements (excludes MTPE)
MTPE is proof that humans aren't going anywhere — post-editors in r/TranslationStudies on where the human step genuinely carries the work
Related Reading
Last reviewed 24 August 2026 by the Bluente document engineering team. This guide describes standards and regulatory requirements as published; it is not legal advice, and obligations vary by jurisdiction and document type.
Machine speed where it's defensible, human sign-off where it's required. Bluente translates regulated documents across 120+ languages with clause numbering, cross-references and footnotes intact, and an audit record for every file. Talk to our team.