Why Good Translation Isn't Enough: 5 Surprising Truths About ISO Quality Standards

In the high-stakes world of global communication, there is a persistent and dangerous misconception: that a high-quality result is solely the product of a talented translator. As a Senior ISO Standards Auditor, I have seen this "talented individual" myth lead to catastrophic certification failures. Under ISO 17100 Clause 7 – Production Processes, linguistic talent is merely the baseline. For a service to be truly professional, it must be supported by a rigorous, repeatable, and auditable production process.

ISO 17100 is the international "gold standard" for translation services, but its requirements are often misunderstood. Here are five findings from the audit floor that reveal why your current process might be one "finding" away from a Major Nonconformity.

1. Revision is Not an "Optional Extra"

Under the auditable requirements of Clause 7, revision is not a premium service or a line-item luxury; it is a mandatory, non-negotiable production process. The standard treats revision as the primary quality safeguard for every project, regardless of size or subject matter.

"Revision is mandatory for every translation project."

From an auditor’s perspective, the data is clear: skipping this step is a leading cause of certification failure. When a Translation Service Provider (TSP) bypasses this phase, they aren't just cutting costs—they are operating an incomplete production process. In an audit, the absence of this step is categorized as a failure of the core quality control system.

2. The Myth of the "Self-Check"

Many providers believe a thorough "check" by the original translator satisfies the standard. This is a critical misunderstanding of the "Independence Requirement." ISO 17100 generally mandates that the reviser must be a different person from the translator to ensure an objective control step.

"No self-revision as the main control."

Independence is vital because it addresses the cognitive blind spots that occur when an author reviews their own work. While the standard allows an exception for small organizations where full independence may be difficult, this is not a "free pass." Small TSPs must provide objective evidence of risk control. Simply "trusting the translator" is not a risk control; an auditor looks for a documented mitigation strategy that proves quality is not compromised by the lack of a second pair of eyes.

3. A Spellcheck is Not a Revision

In the language industry, terms like "proofreading" and "revision" are often used interchangeably, but in an ISO 17100 environment, "Revision" has a very specific, technical definition: it is a Bilingual Comparison.

A common Real Audit Scenario involves a project folder containing a translation file and a spell-check report. When an auditor asks for evidence of revision and is presented with only a spell-check or a target-only review, the finding is immediate: Major Nonconformity.

A compliant bilingual revision must involve a side-by-side comparison of source and target text to verify:

• Accuracy: Ensuring the source meaning is fully preserved.
• Completeness: Verifying no segments or information were omitted.
• Terminology Consistency: Confirming adherence to client-specific or industry glossaries.
• Style Adherence: Ensuring the tone and register meet the intended purpose.
• Client Requirements: Validating that all project-specific instructions were followed.

4. Error Categorization is a Growth Tool, Not a Punishment

ISO 17100 requires a systematic approach to identifying and evaluating errors. Crucially, the standard does not prescribe a specific error model (such as MQM or DQF), but it does require that the TSP has a consistent method for evaluating quality.

The goal of this data is to "close the quality loop." By categorizing errors, a TSP can identify recurring patterns, which should then trigger Corrective Actions and Process Updates. A professional error-tracking system typically includes:

• Accuracy: Mistranslations or meaning errors.
• Terminology: Usage of incorrect or non-approved terms.
• Omission: Missing text or segments.
• Grammar: Syntax and grammatical failures.
• Formatting: Layout and visual issues.
• Style: Inappropriate tone or register.

Failure to systematically identify these errors is often cited as a Minor Nonconformity, as it prevents the TSP from learning from recurring issues and improving procedures.

5. Documentation is the "Evidence of Quality"

The auditor’s axiom is simple: if it isn't documented, it didn't happen. You may have the best linguists in the world, but without Objective Evidence, your process is non-compliant. A Major Nonconformity is often triggered not by a bad translation, but by a total lack of revision records.

To satisfy an audit, a TSP must produce "Audit Evidence" such as:

• Annotated translation files: Showing the reviser’s actual marks and corrections.
• QA Checklists and Revision Reports: Documenting that each required check was performed.
• Reviser Competence Records: Proving the person performing the revision met the same professional requirements as the translator.
• Error Logs and Approval Forms: Showing that issues were addressed before final acceptance.

While "incomplete checklists" may only result in a Minor Nonconformity, the total absence of these records suggests that mandatory quality controls are missing entirely.

Conclusion: Moving Toward "Zero-Failure" Quality

Achieving ISO 17100 compliance requires a shift from viewing translation as a craft to viewing it as a managed, auditable process. Quality is not a happy accident; it is the result of a system where bilingual revision is mandatory, independence is the rule, and every check leaves a paper trail.

By strictly adhering to these production standards, a TSP moves away from "hoping for the best" and toward a "zero-failure" reliability model. This transformation not only satisfies auditors but also provides clients with the ultimate assurance of consistency.

Is your current quality process a documented safeguard, or are you just hoping for the best?

Share This Article

Found this useful? Share it with your network: