Why Your Translation Project Fails Before It Starts: The ISO 17100 Secret to Pre-Production

In the language services industry, the most dangerous operational fallacy is the belief that quality is a byproduct of the translation phase alone. Stakeholders often assume that hiring a qualified linguist guarantees a successful outcome. However, I have seen multimillion-dollar technical manuals face full-print recalls because a single high-stakes term—unverified during pre-production—was applied inconsistently. This is not a linguistic error; it is a systemic failure of the process.

ISO 17100 dictates that quality is not a reactive fix applied during the linguistic process; it is a state that must be prepared in advance. Under this standard, a project is not judged solely by its final text, but by the rigor of the infrastructure that supported it.

Quality is an Upstream Process: The Efficiency Multiplier

ISO 17100 shifts the focus of quality control from the final review to Clause 6: Pre-Production. As a Strategic Operations Lead, I view this stage as a defensive moat. Every hour invested here in subject-matter analysis, cultural considerations, and defining the language register typically saves three hours in the Linguistic Quality Assurance (LQA) and revision phases.

By treating preparation as a formal quality control stage, Translation Service Providers (TSPs) move from "fixing" errors to "preventing" them. This reduces the revision workload and mitigates the risk of misinterpreting the client’s strategic intent.

"ISO 17100 recognizes that quality is not created during translation alone — it is prepared in advance."

Terminology is a Mandatory Asset, Not an Option

Under ISO 17100, terminology management is a non-negotiable requirement for brand accuracy and technical precision. It is the difference between a cohesive user experience and a fragmented, unprofessional brand voice. The standard requires more than just a list of words; it demands rigorous approval workflows and controlled updates via change logs.

Operational risks often stem from common failures such as utilizing outdated glossaries or lacking a structured terminology approval process. To remain compliant, a TSP must ensure:

• Approved terminology is integrated into the workflow from the start.
• Terminology databases are accessible to all members of the production chain.
• Linguistic resources are tailored to the specific content type and subject matter.

Technical Readiness: The Silent Hero of Margin Protection

Linguistic talent requires a stable technical environment to be effective. Technical preparation serves as the "smooth runway" for a project, ensuring that files, tools, and systems are configured for success before the first word is translated. Neglecting this stage leads to the nightmare of broken files, data loss, or "corrupt" Translation Memories (TMs) midway through a tight deadline.

Strategic technical preparation involves rigorous pre-flighting, evidenced by:

• QA Profile Configuration: Ensuring automated checks are calibrated to the specific project requirements.
• Backup Preparation: Establishing data redundancy to protect the production assets.
• CAT Tool and TM Setup: Optimizing the environment for consistency and speed.
• File Format Testing: Verifying that the round-trip from source to target format is seamless.

The Audit Trail: If It Isn't Documented, It Didn't Happen

Perhaps the most jarring reality for many TSPs is that a project can be linguistically perfect yet fail an ISO 17100 audit. If there is no traceable evidence of a project brief, a style guide, or a resource package, the project is a failure of process.

In an audit scenario, a project with zero linguistic errors will still receive a finding of "Major Nonconformity" if the auditor finds no evidence of pre-production preparation. While minor issues like "incomplete resource packages" might result in a minor nonconformity, the complete absence of linguistic instructions or technical prep for complex files is a critical breach of the standard.

"Major Nonconformity: No terminology provided for technical projects, no linguistic instructions, or no technical preparation for complex files."

Auditors look for "traceable evidence"—the logs, resource packages, and email instructions that prove the TSP did the work of preparing the project before production commenced.

Conclusion: The Future of Frictionless Projects

Adhering to Clause 6 transforms translation from a reactive, firefighting task into a proactive strategic operation. This is the "hidden ROI" of ISO 17100: by front-loading the effort into linguistic and technical readiness, you protect your margins from being eaten by endless re-works and LQA cycles.

A project that is "prepared" is a project that is profitable, scalable, and audit-proof. Is your current workflow built on the solid ground of professional preparation, or are you just waiting for the next preventable systemic failure to appear?

Share This Article

Found this useful? Share it with your network: