The Quality Illusion: Why Even the Best Translators Can’t Guarantee ISO 17100 Compliance

In my years of auditing Translation Service Providers (TSPs), I frequently encounter a persistent, dangerous myth: the belief that high-quality translation is simply the result of hiring a talented linguist. Many TSPs operate under the assumption that if their "people" are good, the output will naturally meet international standards.

As a Lead Auditor, I am here to tell you that talent is a single point of failure. Relying on individual brilliance without a framework for consistency leads to unpredictability and systemic risk. To move from "lucky" outcomes to guaranteed quality, the industry relies on the hidden architecture of ISO 17100.

This standard represents a fundamental shift in perspective. It moves the focus away from the "talented individual" and places it squarely on "controlled processes." It is the difference between a craft and a professional industrial service.

Systemic Safeguards: Why Process Dominates the Person

ISO 17100 is built on the principle that quality is a byproduct of a managed environment. While the competence of the translator is a prerequisite, it is insufficient on its own. When I conduct an audit, I am not just looking for a roster of impressive CVs; I am looking for objective evidence that the organization executed a controlled, consistent, and traceable process from start to finish.

A talented person can have an "off" day, but a controlled process acts as a systemic safeguard. By standardizing every step—from how requirements are analyzed to how files are prepared—the TSP ensures that the final product is a result of intentional design rather than individual luck.

"ISO 17100 is not just about qualified people — it is about controlled, consistent, traceable processes."

The "Four-Eyes" Principle: The Mandatory Core Control

One of the most critical components I verify is Stage 4: Revision. In many non-certified environments, a second check is treated as an optional "add-on." Under ISO 17100, this "four-eyes" principle is a mandatory core control.

The standard requires an independent, qualified reviser to perform a bilingual check of the target language content against the source. I often see TSPs fail here by having a Project Manager perform a "quick look-over." As an auditor, I look for proof that the reviser possesses competent resource qualifications equal to the translator. If the person who translated the text is the same person who checked it, the process is non-compliant. The reviser must focus on:

• Accuracy: Preservation of meaning across languages.
• Completeness: Verifying no content was omitted.
• Terminology: Adherence to client-specific or industry-standard glossaries.
• Style: Ensuring tone and register meet project specifications.

The Forensic Audit: Tracing the End-to-End Trail

I do not walk into an audit to "check boxes" on a manual sitting on a shelf. I operate as a detective using the Process Tracing Technique. I select a completed project at random and trace its lifecycle from the initial client enquiry through to final delivery.

This creates an "end-to-end audit trail" where I look for the "smoking guns" of compliance. If a step wasn't recorded, then in the eyes of an auditor, it never happened. To pass this forensic scrutiny, a TSP must produce objective evidence such as:

• Resource Competence Records: Proving the selected linguists and revisers met specific ISO 17100 requirements.
• Annotated Files: Providing physical proof that the bilingual revision actually took place.
• Quotation and Requirement Records: Confirming the feasibility, technical capability, and scope were reviewed before the work began.

The Final Gatekeeper: The Check of the Checks

Before any project is delivered, it must pass through Stage 7: Final Verification. This is a mandatory gatekeeping step, typically performed by a Project Manager, but it is often misunderstood.

This is not a final proofreading. Rather, it is a meta-check. The verifier must confirm that the entire defined process was followed: Was the revision completed? Are the files in the correct format? Were the client’s technical specifications met? This stage is the TSP’s last line of defense and a critical moment of risk management. It ensures that the files leaving the TSP aren't just "good," but are the result of a fully executed quality workflow.

Closing the Loop: Continuous Improvement as a Requirement

A truly robust quality system is never static. ISO 17100 mandates Stage 9: Feedback and Improvement. Collecting client feedback and formally addressing complaints is not just "good customer service"—it is a formal requirement for compliance.

By documenting corrective actions and identifying process gaps, the organization is forced into a feedback loop. This ensures the TSP evolves, identifying systemic issues so they are resolved rather than repeated. It transforms the organization from a reactive entity into a proactive, maturing system.

The Future of Quality

The value of ISO 17100 lies in its ability to transform translation from a subjective, individual craft into a controlled, industrial process. By emphasizing the "four-eyes" principle, forensic traceability, and mandatory final verification, the standard provides a roadmap for reliability that talent alone cannot sustain.

As you evaluate your own workflows, I invite you to look at them through the lens of an auditor: Is your current success the result of a truly controlled process, or are you simply lucky enough to have good people?

Share This Article

Found this useful? Share it with your network: