The Invisible Audit Trap: Why Flawless Translations Can Still Result in a Major Nonconformity

Imagine an ISO 17100 audit where the project files look pristine. The translation is linguistically brilliant, the technical formatting is flawless, and the client’s feedback is glowing. You expect a commendation; instead, I issue a Major Nonconformity against Clause 6.1.

How is this possible? Because as a Lead Auditor, I am not just auditing your prose—I am auditing your system. In this scenario, the Translation Service Provider (TSP) failed to produce Objective Evidence of a feasibility review or a documented contract review. Under the ISO 17100 standard, a high-quality result that occurs by accident is just as much a failure as a poor translation.

Clause 6 (Pre-Production Processes) is the silent engine of quality. It is the most critical stage of the translation lifecycle, yet it is where most TSPs unknowingly sow the seeds of their own audit failure.

1. Quality is a Pre-Production Problem

In my experience auditing TSPs, the most frequent point of failure isn't a translator's typo; it is a systemic lack of documentation. Most quality errors are decided before the first word is even translated. When you skip the administrative rigor of Clause 6, you aren't just being "agile"—you are inviting a cascade of failure.

Without a controlled pre-production process, you face four distinct systemic risks:

• Wrong resources assigned: Deploying a linguist without verified subject-matter expertise.
• Missed deadlines: Committing to volumes that are mathematically impossible within the timeline.
• Compromised quality: Forcing a "rush job" to compensate for poor initial planning.
• Client dissatisfaction: Failing to meet expectations that were never formally captured in the Project Brief.

2. Feasibility: The "Technical Yes" vs. The "Sales Yes"

There is a dangerous gap between a "Sales Yes" (we want the revenue) and a "Technical Feasibility Yes" (we have the capacity and tools to execute). Under ISO 17100, feasibility is a mandatory audit requirement, not a business suggestion.

Before you commit, you must perform a technical audit of the request, accounting for:

• Resource Availability: Can we secure qualified linguists for these specific dates?
• Technical Infrastructure: Do our tools support the specific file formats and volume?
• Complexity & Confidentiality: Can we meet the subject matter requirements and confidentiality constraints?

"ISO 17100 requires TSPs to confirm feasibility and clarity upfront."

If your project files do not contain Feasibility Checklists or PM approval logs, you are operating outside of the standard’s requirements.

3. The Danger of Informal "Handshake" Agreements

Informal "special instructions" shared over a phone call or a quick Slack message are audit landmines. They are frequently lost between the enquiry stage and the project brief, leading to a direct violation of Clause 6.1.

ISO 17100 demands a rigid distinction between Client Enquiry Management and Contract Review. You must maintain a paper trail of Audit Evidence—such as CRM records, enquiry forms, and request logs—that document:

• Precise source/target languages and volume.
• Specific Style Guides and Terminology Lists.
• Deadlines, formatting, and quality levels.

Without these artifacts, there is no proof you understood the scope. If it isn't documented, it didn't happen.

4. The "Scope Creep" Trap and the Reset Button

A major point of failure I see during audits is the handling of mid-project changes. When a client adds 500 words or moves a deadline up by two days, most PMs simply update the calendar. This is a mistake.

Any change in scope requires you to hit the "Reset Button" and reassess feasibility. This Change Control process is an auditable step. To remain compliant, I expect to see:

• Revised Quotes reflecting the new scope.
• Updated Project Plans shared with the production team.
• Documentation of the reassessment of resource availability.

5. The "Perfect Translation" that Fails the Audit

The most surprising reality for many TSPs is that the process is as important as the product. I have sat in rooms where a TSP produced an excellent translation, but because they lacked a documented contract review and feasibility check, I was forced to record a Major Nonconformity.

ISO 17100 is built on the philosophy of a controlled, repeatable process. An auditor doesn't care if you got it right this time through individual heroics; we care if your system guarantees you get it right every time. If your pre-production controls are missing, your certification is at risk—regardless of the quality of the final prose.

Conclusion: Looking Beyond the Text

Professionalizing your pre-production stage moves the relationship with your client from a vendor-client transaction to a technical partnership. By strictly adhering to documented requirements, feasibility checks, and formal change controls, you protect your reputation and your ISO status.

As you evaluate your current workflow, ask yourself: Is your next project failure already happening right now, before your translators have even opened the file?

Share This Article

Found this useful? Share it with your network: