Is Your Jargon Costing You Certification? The ISO 17100 Terminology Trap

1. Introduction: The High Stakes of "Close Enough"

In the high-stakes world of ISO 17100 audits, "close enough" is the precursor to a Major Nonconformity. As a lead auditor, I frequently see organizations treat terminology as a matter of semantics rather than a framework for compliance. In the context of professional translation, words are not merely descriptions—they are legally and technically precise requirements. Misusing industry jargon is not just a linguistic slip; it is a signal to an auditor that your Quality Management System (QMS) lacks the structural integrity required for certification.

2. Takeaway 1: Revision is Not a Choice—It’s a Mandate

Under ISO 17100, "Revision" is a non-negotiable, mandatory step in the translation process. It is a fundamental violation of Clause 3 to rely on a "translator self-check." In my experience on the audit floor, the absence of an independent, qualified second person performing a bilingual examination is an automatic Major Nonconformity.

To satisfy the standard, the revision process must be documented and fulfill specific criteria:

Revision involves a: "Bilingual examination of the translation against the source text by a reviser, checking: Accuracy, Terminology, Style, and Completeness."

If you cannot produce annotated files, revision records, or checklists that prove this bilingual comparison took place, your process does not exist in the eyes of an auditor.

3. Takeaway 2: The "Bilingual" Distinction Between Revision and Review

A frequent point of failure during audits is the conflation of Revision and Review. The standard creates a sharp, technical divide between these two actions, yet organizations often attempt to pass off one for the other.

• Revision: Bilingual, Mandatory, and focused on Accuracy (Source vs. Target).
• Review: Monolingual, Optional, and focused on Audience Suitability (Target only).

This confusion creates a "Common Audit Risk." If your workflow replaces the mandatory bilingual revision with a monolingual "subject matter expert" review, you have failed to fulfill the core process requirements of ISO 17100.

4. Takeaway 3: Proofreading is a Finish, Not a Foundation

ISO 17100 defines "Proofreading" with surgical precision: it is a final check for typographical errors, formatting, and layout after the content has been formatted or published.

Logically and technically, proofreading is a surface-level check. It is a finishing touch, not a foundation for quality. Relying on proofreading to catch translation errors is a major nonconformity because it is physically impossible for a surface check to replace the mandatory bilingual revision stage. If your QC process only happens at the post-layout stage, you are essentially gambling with the integrity of the translation.

5. Takeaway 4: Competence is a Documented Requirement, Not an Assumption

Auditors do not deal in assumptions; we deal in evidence. Competence is not a vibe—it is a documented status based on three pillars:

• Education: Formal qualifications in translation or a related field.
• Experience: Documented years of professional practice.
• Continuous Professional Development (CPD): Verified records of ongoing skill enhancement.

Crucially, the Reviser’s competence must be just as rigorously documented as the translator’s. Furthermore, "Independence" is my primary focus when evaluating these assignments. Clause 3 requires the reviser to be a different person than the translator. If I see the same individual performing both roles, the system has failed.

6. Takeaway 5: Industry Slang vs. Audit Reality

In an audit environment, industry slang is a dangerous liability. Auditors are trained to enforce the "Lecture 5.1" definitions over any casual workplace vernacular.

• Industry Slang "Review": Often means any general checking of the text.
• ISO 17100 "Review": Specifically a monolingual quality check for style and readability.
• Industry Slang "Proofread": Often refers to a full quality check.
• ISO 17100 "Proofread": A final check for surface errors and layout after formatting.
• Industry Slang "Edit": Used loosely for any change to a file.
• ISO 17100 "Edit": Must match a specific, defined step in the documented workflow.
• Industry Slang "QA": Often implies an automated software scan.
• ISO 17100 "Translation Process": A controlled, documented process requiring specific human qualifications.

7. Conclusion: Beyond the Lexicon

Mastering this terminology is the first step toward certification and operational excellence. If your team continues to use industry slang in project instructions and records, you are inviting an auditor to find gaps in your compliance.

These definitions are the exact criteria Lead Auditors are trained to use to fail a system. Before your next audit, look at your internal workflows with an uncompromising eye: Would your documentation survive a "Lecture 5.1" style audit, or is your "Revision" just a spell-check in disguise?

Share This Article

Found this useful? Share it with your network: