What to use it for
This reference is relevant when discussing how a translation service is organized and what an applicable service claim covers. A service description, an individual translated text and a provider's marketing statement are different pieces of evidence.
Our practical recommendation is to ask which service, edition and scope a claim refers to. If a certificate is supplied, examine its coverage and validity rather than assuming that a logo covers every language, product or production route.
An illustrative procurement conversation
A team receives two proposals for the same manual. One describes a human translation service; the other proposes machine translation followed by human post-editing. Both mention quality, but that does not make their processes equivalent.
The buyer can ask each provider to identify the intended production stages, responsible roles and acceptance evidence. It can then compare the proposals against the brief. A useful question is “Which reference governs this particular workflow?” rather than “Do you use standards?”
This example is editorial guidance. It is not a list of mandatory ISO 17100 clauses.
Relationship to the LISA legacy
LISA's exchange formats concern how language resources travel. ISO 17100 addresses the service surrounding the work. A project can need both a defined service process and dependable exchange of translation memories or terminology. Neither proves the other has been handled correctly.
AI and the published scope
An AI-assisted workflow needs a precise description before any conformity claim can be assessed. Do not treat the announced revision as permission to rewrite the scope of the published edition. Equally, do not infer from a tool's presence alone that a particular service claim is valid or invalid; the actual workflow and applicable text must be examined.
For the published requirements concerning full human post-editing, see ISO 18587. For project planning and output evaluation, see ISO 11669 and ISO 5060.
Source record
ISO 17100:2015 and amendment record. This article relies on public metadata and scope. Detailed implementation requires the applicable full documents; this website does not certify services.