How to Choose a Professional Translation Company: An Enterprise Localization Procurement Guide
From ISO 17100 certification and terminology/TM governance to DTP and LQA, this guide breaks down how to evaluate a translation company and build an auditable language supply chain.
Why Selecting a Translation Company Is Now an Engineering Decision
When an IFU must be submitted alongside a CE marking dossier, when a PCT patent application enters the national phase, or when an IVI head unit UI must launch in twelve languages simultaneously, language quality stops being a matter of “does it read well.” It becomes a question of regulatory risk, recall cost, and time-to-market. Enterprise procurement of translation services has shifted from per-thousand-word price comparison to evaluating process auditability, terminology consistency, and delivery certainty.
This is especially true for translation companies in Shanghai, whose clients are typically cross-border manufacturers, medical device firms, automotive electronics, and fintech companies. Their requirements are inherently regulated: EU MDR 2017/745 demands technical equivalence across multilingual IFUs; documents under an IATF 16949 quality system must be traceable; SCORM/xAPI courseware must still validate against an LMS CMI data model after localization.
Six Hard Criteria for Evaluating a Professional Translation Company
1. Certification and Process Compliance
ISO 17100:2015 requires translation, self-revision, bilingual revision, and review, with defined translator competences. ISO 27001:2022 governs the security of unpublished patents, clinical data, and source code. Without both, a vendor struggles to enter the approved supplier list of regulated industries.
2. Terminology Base and Translation Memory Governance
A professional translation company should provide version control for termbases, a term approval workflow, and TM leverage reporting. For ISO 26262 functional safety documents, terminology drift (e.g., conflating “fault” and “failure”) directly undermines hazard analysis and risk assessment consistency.
3. Multi-Format Engineering Capability
Enterprise deliverables are rarely Word files. They are DITA XML topics, Articulate Storyline modules, InDesign brochures, CAD drawings, or JSON resource bundles. Whether the vendor has in-house DTP and localization engineering (LE) teams determines if you need to re-layout after delivery.
4. Language Quality Assurance (LQA) Model
Mature translation service companies apply MQM (Multidimensional Quality Metrics) or LISA QA models, sampling by accuracy, terminology, language conventions, style, and locale suitability, then issuing quantified reports.
5. Language Coverage and Native Translator Network
“Minor” languages are often critical for going global: Thai, Vietnamese, Arabic (RTL layout), Brazilian Portuguese. Confirm translators are native speakers of the target market and have relevant domain backgrounds.
6. Data Security and NDAs
For eCTD submissions, patent claims, and FCPA compliance materials, sign an NDA specifying data residency, access control, and destruction mechanisms.
Enterprise Translation Procurement Comparison Table
| Criterion | Low-cost Vendor | Professional Translation Company |
|---|---|---|
| Process | Single translator, direct delivery | Translation + revision + review, ISO 17100 aligned |
| Terminology | No termbase | Termbase + approval workflow + versioning |
| Deliverable formats | Word/PDF only | DITA, XML, JSON, INDD, Storyline |
| Quality reporting | None | MQM/LQA quantified reports |
| Security | No NDA or boilerplate | ISO 27001 framework + custom NDA |
| Traceability | No records | Full workflow tickets and version history |
Implementation Checklist
- Verify valid ISO 17100 and ISO 27001 certificates
- Request de-identified industry cases and a test translation
- Clarify termbase ownership and TM ownership (typically client-owned)
- Confirm LQA sampling ratio and defect severity scale
- Agree on deliverable formats, font licensing, and RTL/double-byte layout
- Sign an NDA with data residency and destruction clauses
- Establish a quarterly business review (QBR) for quality
核心专业术语双语对照表 (Key Terminology Cross-Reference)
| English | Chinese | Definition |
|---|---|---|
| ISO 17100:2015 | 翻译服务国际标准 | International standard defining translation processes, competences, and revision |
| Translation Memory (TM) | 翻译记忆库 | Database storing bilingual segments for reuse and consistency |
| Terminology Base (TB) | 术语库 | Approved term collection ensuring cross-document consistency |
| LQA | 语言质量保证 | Sampling-based method for quantifying translation defects |
| MQM | 多维质量指标 | LQA framework scoring accuracy, terminology, style, and more |
| DTP | 桌面排版 | Post-localization layout and font adaptation |
| IFU | 使用说明书 | Multilingual instructions for use for regulated products |
| eCTD | 电子通用技术文档 | Electronic submission format for drug registration |
| DITA XML | 达尔文信息类型化架构 | Standard for structured content management and publishing |
| xAPI (Tin Can) | 体验API | Specification for recording learning activity across systems |
Frequently Asked Questions (FAQ)
Q1: We have in-house translators. Why do we still need an enterprise translation company?
In-house translators are ideal for core terminology and brand voice, but for multilingual, peak-volume, and regulated documents, a professional translation company provides a scalable native translator network, ISO 17100 revision workflow, and LQA reporting. This forms a hybrid model of “in-house terminology ownership + external capacity,” controlling both quality and turnaround.
Q2: How do we assess whether a Shanghai translation company can handle medical device localization?
Focus on three points: understanding of EU MDR 2017/745 and IVDR 2017/746 language requirements for IFUs; presence of clinical and regulatory termbases; ability to process structured documents such as eCTD and CIOMS adverse event reports. Ask for de-identified LQA report samples and a termbase structure overview.
Q3: Who owns the translation memory and termbase?
Industry practice is that client-funded TB/TM belongs to the client, with the vendor using it only within the project. Specify export formats (e.g., TMX, TBX) and handover clauses at contract stage to avoid lock-in when switching vendors.
Strategic Takeaways and Next Steps
Choosing a translation company is essentially choosing an auditable, reusable, and scalable language supply chain. Score vendors across certification, process, terminology governance, and security; start with a small test batch before scaling. To evaluate specific languages, formats, and compliance requirements, contact the Linguist team for a tailored quote and test translation.
Expanding globally or tackling translation compliance?
ISO 17100 certified. Get instant localization readiness diagnostic & quotation.
Share this article