Why certifications matter when you buy technical translation for software and manufacturing
The real question a buyer faces is not whether a provider can write a readable sentence in German or Japanese. It is whether that provider can move multilingual technical content through a controlled process — traceable revisions, stable terminology, documented reviewer qualifications, and confidentiality that holds up when someone asks for records months later. Certification is the shorthand most buyers reach for, and it is a reasonable starting signal, provided you know what it proves.
What it proves is process, not domain knowledge. A certificate says a provider has documented procedures and review controls that an auditor has checked; it does not say the translator understands your PLC error codes or your API reference. Both matter, and they fail in different places. Software releases break on terminology drift and version control between builds. Manufacturing documentation breaks on inconsistency across manual revisions and gaps in the audit trail.
The standards worth understanding are ISO 17100 for translation services, which the ISO 17100 agency-selection guidance describes as requiring qualified translators, independent revision by a second person, and documented project management; ISO 18587 for post-editing machine translation output; ISO 9001 quality management; and ASTM F2575-25, a standard practice for language translation.
What follows is how to verify those claims — the evidence to request, and where quality and compliance signals stop being useful.
The core certifications and standards to look for
Start with ISO 17100. It is the main translation-services standard, and it is the one worth naming explicitly in a request for proposal. Certification does not grade individual sentences; it attests that a provider runs a documented process. Guidance published at iso17100.com describes what a certified agency should be able to show: translators with verified qualifications, independent revision by a second linguist, documented project management, appropriate technical resources, and a defined procedure for handling client comments and corrections.
The workflow behind that certificate is where the value sits for technical content. It runs from analysis of the source files and quotation through agreement, assignment to named resources, translation, the translator’s own check, revision by a different person, final verification against the brief, delivery, and post-delivery handling of feedback. Ask a prospective provider to walk you through each stage against a real project of yours. If revision and final verification collapse into the same person, the certificate is describing a process the team no longer runs.
Is ISO 17100 sufficient on its own? Not once machine translation enters the pipeline — and for software strings and manufacturing documentation, it usually does. ISO 18587 is the companion standard covering post-editing of machine translation output, and TÜV SÜD lists both together in its certification services. If a provider proposes machine translation for your release notes or parts catalogues, ask which post-editing level they apply, who performs it, and how the edited output is reviewed before sign-off.
ASTM F2575-25, the standard practice for language translation available from ASTM International, is a useful second reference for buyers who want a broader benchmark for specifying a translation project, particularly around agreeing requirements up front.
One distinction worth holding firmly: ISO 9001 is a quality-management system standard. Many providers hold it, and it signals disciplined internal governance, but it says nothing specific about bilingual revision or translator competence. Treat it as supporting evidence of quality and compliance maturity, not as a substitute for translation-specific certification.
How to verify a provider’s claims before you sign
A certification logo on a website is a claim, not proof. Ask for the certificate as a document, and check four things on it: the issuing body (an accredited certification body, not a self-declared membership), the exact scope of the certification, the sites or entities it covers, and the validity period. Scope matters more than most buyers realise — a certificate can cover a head office but not the subsidiary that will handle your product manuals. Ask when the last surveillance audit took place and when recertification is due; certification bodies such as TÜV SÜD run ISO 17100 and ISO 18587 assessments on a recurring audit cycle, so a provider should be able to name dates without hesitation.
Audit trail checklist. Ask to see, on a real (anonymised) project:
- Version history for source and target files, including which source version each translation was built from
- Revision records showing who revised what, and what changed
- Documented approval steps before delivery
- Evidence of post-delivery handling — how a reported error was logged, corrected, and fed back into the terminology base
That last item is the one buyers skip. The ISO 17100 guidance for choosing a certified agency describes a defined sequence from analysis and quotation through translation, the translator’s own check, revision by a second person, final verification, delivery, and post-delivery handling — ask the provider to walk you through their version of it with artefacts, not slides.
Translator qualification evidence. Request anonymised profiles for the linguists who would actually work on your account: years in the specific language pair, subject-matter background in software or manufacturing, and how competence is documented and reassessed. Ask who performs independent revision and how terminology disputes are escalated and resolved.
Document control and confidentiality. For unreleased software builds and manufacturing instructions, confirm where files are stored, who has access, how long they are retained, and what the non-disclosure terms cover. ASTM F2575-25 is a useful reference point when specifying these requirements in writing.
Finally, ask directly how machine translation is used, on which content types, and where human post-editing enters the workflow — a provider serious about quality and compliance will answer with a process, not a disclaimer.
When certification matters most, and when process maturity and domain expertise matter more
Certification earns its weight when you need formal controls you can hand to someone else. If procurement requires evidence of supplier vetting, if an auditor will ask how a translation was reviewed, or if your release process depends on repeatable steps rather than individual goodwill, a certified provider gives you a documented answer. ISO 17100 is built around exactly that structure: qualified translators, independent revision by a second person, documented project management, and a defined route for handling comments and corrections. Where post-edited machine translation is part of the workflow, ISO 18587 covers that output specifically. For regulated documentation — safety instructions, labelling, anything tied to a conformity file — that paper trail is not optional.
Domain expertise outweighs a certificate alone when the risk sits in the terminology rather than the paperwork. A certified vendor with no experience in PLC programming, CNC tooling, or your product’s UI string conventions can still produce a compliant-looking translation that a field engineer will not recognise. Ask for translator qualification evidence in your subject area, sample revisions, and the glossary they would inherit or build.
Process maturity is often the more honest signal. A provider who can show stable workflows, revision records, and named ownership of terminology is demonstrating the same discipline a certificate attests to — just directly.
The tradeoffs cut both ways. A certified provider may still need to prove subject-matter depth; a specialist engineering translator may have deep product knowledge and a thinner certification footprint. In practice, buyers get the best result by combining both: certification for structure and auditability, domain expertise for technical accuracy, which is how quality and compliance hold together over repeated releases rather than one project.
How quality management systems support consistency in technical translation
Certification to a translation-specific standard tells you a provider has defined roles and revision steps. A general quality management system tells you whether those steps hold up across hundreds of jobs and several years. ISO 9001 is the common example: it covers process documentation, internal monitoring, corrective action, and management review for an organization as a whole. It says nothing about translator qualifications or bilingual revision, so it is not a substitute for ISO 17100 — but it does signal that the provider treats its own workflow as something to measure and fix.
Longevity is the useful signal here. The German technical documentation firm DOCTEC, for instance, states it has held ISO 9001 certification since 2004 and undergoes annual monitoring plus recertification audits — a claim a buyer can ask any provider to match with certificate dates and audit reports.
That cadence matters because software and manufacturing content is never finished. A machine manual gets a new safety notice; a user interface adds forty strings. Repeatable handling of updates depends on documented procedures for terminology approval, translation memory maintenance, version control against the source, and re-review of changed segments only. When a mistranslated warning surfaces, a corrective action record shows whether the provider traced the cause or simply patched the file.
Ask for three things: the procedure documents that govern these steps, the date of the last external audit, and a completed corrective action from the past year. Documented quality and compliance practices are only worth what the evidence behind them shows.
FAQ: common questions about certified translation providers
Does a technical translation agency have to hold ISO 17100?
It is the clearest single signal, but not the only one. ISO 17100 requires qualified translators, independent revision by a second person, documented project management, appropriate technical resources, and a procedure for handling comments and corrections. An uncertified provider can run the same controls — the difference is that nobody outside the company has audited them. If a provider isn’t certified, ask for the equivalent evidence: translator qualification records, revision records showing who checked what, and a written process covering analysis, quotation, assignment, translation, the translator’s own check, revision by another person, final verification, delivery, and post-delivery handling.
What’s the difference between a certified provider and a certified translation?
A certified provider is a company whose processes have been audited against a standard such as ISO 17100. A certified translation is document-level: a signed statement that the translation is complete and accurate, sometimes with a sworn translator’s seal or notarisation. Requirements are jurisdiction-specific, and a certified provider does not automatically produce a translation a given court, patent office, or notified body will accept. Confirm the receiving authority’s format before ordering.
How does machine translation fit into a controlled workflow?
It fits when post-editing is defined, staffed, and recorded. ISO 18587 covers post-editing of machine translation output, and TÜV SÜD lists it alongside ISO 17100 among its certification services. Practical questions for a provider: which engine is used, whether your content is retained or used for training, whether the post-editing level is light or full, and who performs the final verification. Machine translation is a tool inside the process — the audit trail still has to exist.
Is ISO 9001 on its own enough?
ISO 9001 shows general quality management discipline, including corrective action and recurring audits — DOCTEC, for example, states it has held ISO 9001 since 2004 with annual monitoring and recertification audits. What it does not address is translator competence or mandatory two-person revision. Pair it with translation-specific controls: ISO 17100, ISO 18587 where post-editing applies, and practice standards such as ASTM F2575-25.
Read three things together before you decide: the exact scope on the certificate (which services, sites, and language pairs), how revision and final verification actually run, and whether the provider has handled your content type — software strings, machine safety instructions, service manuals. Certification narrows the field; domain evidence picks the winner. If you want a second read on a shortlist, Mesa Translation’s team can walk through scope, revision records, and the quality and compliance questions specific to your documentation set.
Leave a Reply