The Documentation Trap: Why Your Translation Workflow Might Fail an ISO 17100 Audit

1. Introduction: The Chaos of the "Informal" Project

In many translation agencies, the daily grind is managed through a flurry of emails, frantic chat messages, and "as-per-usual" verbal agreements. While this might keep the wheels turning on a Tuesday afternoon, it is a recipe for disaster during a certification audit. This style of "managing by email" is the primary reason many firms struggle to achieve or maintain ISO 17100 compliance.

Clause 6 of the ISO 17100 standard serves as the critical divider between professional translation service providers (TSPs) and those who are simply winging it. It mandates that pre-production processes—everything that happens before a translator touches a file—must be controlled and documented. The core premise is simple but demanding: compliance isn't about doing the work; it’s about proving the work was meticulously planned before it began.

2. Your Inbox is Not a Project Plan

A common red flag for ISO auditors is the phrase, "We handle everything by email." While email is a communication tool, it is never a substitute for documented workflow charts or formal PM checklists. Relying on disorganized email chains and verbal agreements is the primary reason for audit failure, as it lacks the rigor required for professional execution.

Auditors look for a definitive shift from "handling things" to "documenting processes." When planning is informal, critical details like quality levels or technical setups are often lost or assumed rather than verified. Transitioning to a compliant workflow requires moving beyond the inbox and into structured records where task assignments and instructions are clearly visible and retrievable.

"Most ISO 17100 failures occur because planning was informal or undocumented."

3. Feasibility is a Pre-Requirement, Not an Afterthought

One of the most surprising insights for many TSPs is that auditors are not just looking for the final delivered file; they are looking for proof that you were capable of doing the job before you accepted it. ISO 17100 requires documented evidence of a "Quotation & Contract Review" that must occur before a project is officially taken on. The timing of this documentation is just as critical as the content itself.

During this review, the TSP must verify specific items: language pairs, deadlines, total volume, and the definition of the scope. The auditor is searching for a formal feasibility assessment—a record showing that the TSP confirmed they had the resources, technical capacity, and confidentiality protocols to meet the client's needs. If these reviews aren't documented prior to acceptance, the TSP has already failed the audit.

4. Risk Management is a Practical Tool, Not a Theoretical Exercise

For a Senior QA Consultant, risk management is a defensive strategy documented in real-time, not a retrospective justification for project issues. Auditors expect TSPs to identify specific risks such as tight deadlines, highly technical content, or the usage of Machine Translation (MT). Identifying these factors is only half the battle; the standard requires a documented response to each identified threat.

In a real audit, "mitigation" must be recorded as a concrete action. For example, if a project involves high-volume technical content, the auditor will look for a documented risk response, such as the assignment of a "Senior Translator" or the implementation of extra QA checks. This turns risk management into a controlled, recorded workflow rather than a vague preference or a lucky outcome.

"Projects are planned — not improvised; risks are controlled — not discovered late."

5. The "Audit Trail" as a Story of Quality

A compliant project tells a story through its "audit trail," providing the traceability required to prove that Clause 6 was followed from start to finish. Imagine an auditor pulls a sample for "Project X." They shouldn't just see a finished file; they should see the chronological fingerprint of quality—starting with the feasibility check and ending with the strategic assignment of resources.

For "Project X," the trail would show an approved quotation, documented requirements, and a project plan detailing linguistic preparation and technical setup. If a risk log notes a "tight deadline," the auditor should see a corresponding action, such as the assignment of an additional reviser to maintain quality standards. Traceability is the ultimate goal, ensuring every decision was intentional and documented.

6. The High Cost of "Weak" Findings

Auditors distinguish between "bad work" and a "lack of proof," often categorizing failures as either Major or Minor nonconformities. A Major nonconformity occurs when there is a complete absence of documented project planning or feasibility checks across multiple samples. These findings signal to the auditor that the TSP's quality management system is fundamentally broken.

However, even Minor nonconformities, such as inconsistent risk notes or poor traceability between files, can undermine your certification. A "strong" audit finding specifically highlights these gaps: "No documented evidence of feasibility review was available for 3 of 5 sampled projects." Without proof, from an auditor's perspective, the process simply did not happen, regardless of how good the final translation was.

7. Conclusion: Moving Toward Professional Maturity

Rigorous pre-production controls are the hallmark of a mature translation service provider. By documenting feasibility, planning resources with workflow charts, and mitigating risks before a project begins, TSPs protect themselves from the chaos of informal management. These protocols are not just administrative hurdles; they are the foundation of a reliable, scalable business model.

As you evaluate your internal processes, ask yourself: Is your current "informal success" simply an audit failure waiting to be discovered? True professional maturity in the translation industry begins with the realization that the documented plan is just as important as the final product. Moving toward ISO 17100 compliance means ensuring that your workflow is defined by control, not by the contents of an overstuffed inbox.

Share This Article

Found this useful? Share it with your network: