The Compliance Trap: 5 Surprising Ways Translation Teams Fail ISO 17100 Certification

Achieving ISO 17100 certification is a rigorous milestone that often reveals a jarring gap between established internal workflows and international compliance standards. I frequently see even the most seasoned Language Service Providers (LSPs) stumble during audits, not because of bad intent, but because of terminology confusion. To a lead auditor, industry slang and "the way we’ve always done it" hold no weight; only strict adherence to the standard’s definitions can prevent a major nonconformity.

This post reveals the most common, counter-intuitive ways organizations accidentally trigger audit failures by misinterpreting the core pillars of the standard.

1. "Revision" is Mandatory, "Review" and "Proofreading" are Optional

The most frequent source of major nonconformity I encounter is the conflation of Clause 3 terms. Many teams believe they are compliant because they perform a final check, but they often mistake "Review" or "Proofreading" for the mandatory "Revision" step.

• Revision (Mandatory): A bilingual check. It requires a qualified reviser to compare the source and target texts to ensure accuracy, terminology consistency, and completeness.
• Review (Optional): A monolingual check of the target language only, focusing on style and readability.
• Proofreading (Optional): A final check before publication. In an audit, "Proofreader comments" are frequently rejected as evidence because they lack the bilingual comparison required by the standard.

"Revision is always required, regardless of project size, client budget, or urgency."

From a compliance perspective, the absence of a bilingual revision record—documented objective evidence that the target was verified against the source—is an automatic major nonconformity. A spell-check report or a monolingual "skim" will not satisfy a lead auditor.

2. The Myth of the Self-Checking Translator

A dangerous misconception persists that a senior translator’s self-revision is sufficient for certification. ISO 17100 explicitly requires independence; the reviser must be someone other than the translator.

I always look for these Red Flags that signal a breakdown in the audit trail:

• "Our translators revise themselves": This directly violates the requirement for an independent bilingual check.
• "The software ensures quality": While QA tools are excellent assistants, they are not a replacement for the human-led revision process.

Auditors view software as a tool to assist the reviser, not a substitute for the professional judgment of a second, qualified linguist.

3. Machine Translation is Not "Translation" Under ISO 17100

There is a pervasive "MT Myth" that machine output alone can be delivered as an ISO 17100-compliant product. It cannot. The standard is unequivocal: only human-controlled processes qualify for conformity.

For a workflow involving Machine Translation (MT) to be compliant, it must be treated as a highly documented human-led process. This requires a robust audit trail including:

• Explicit Client Agreement: Documented consent to use MT in the workflow.
• Human Post-Editing: Every segment must be handled by a qualified professional.
• Independent Revision: Post-edited MT must still undergo a full, independent bilingual revision.

Organizations often wrongly assume MT reduces the need for documentation; in reality, it requires more evidence to prove that quality controls remain intact.

4. Post-Editors Must Meet the Same High Bar as Translators

A frequent trap for LSPs is the attempt to reduce costs by using less qualified resources for "light post-editing." However, ISO 17100 dictates that post-editors must meet the exact same professional competence requirements as standard translators.

I flag the following statement as a sign of imminent nonconformity: "We only do light checking." This indicates a failure to treat post-editing as a professional translation task. To maintain conformity, your records must show:

• Verified post-editor qualifications (matching translator standards).
• A clearly defined Post-Editing Machine Translation (PEMT) process.
• Objective evidence of a full bilingual revision following the post-editing phase.

5. The "Client Request" is Not a Get-Out-of-Jail-Free Card

Perhaps the most frustrating reality for business owners is that client instructions cannot override the standard. If a client requests a "translation-only" service to save money or asks to waive the revision step for a rush project, that specific project cannot be claimed as ISO 17100 compliant.

The Auditor Rule is absolute: ISO does not allow waiver.

This creates a sharp tension between business flexibility and certification. You can certainly accommodate the client's budget by skipping steps, but you must exclude that project from your conformity declarations. Using the ISO 17100 mark on a project where the bilingual revision was skipped—even at the client’s request—is a breach of compliance.

Conclusion: Beyond the Certificate

Surviving an audit requires shifting your mindset from "company labels" to the strict definitions of Clause 3. As a lead auditor, I don't trust the software or the reputation of the firm; I trace project workflows and verify the competence of every human in the chain.

Compliance is about creating a transparent audit trail of objective evidence. By adopting ISO's definitions over industry slang, you protect your certification and ensure your quality controls are as robust as the standard demands. Is your team following the spirit of quality, or are you accidentally skipping the very steps that define professional translation standards?

Share This Article

Found this useful? Share it with your network: