Why the Annexes of ISO 17100 Deserve Serious Attention
When people study ISO 17100, they tend to focus on the main body of the standard. The production workflow, the competence requirements for translators and revisers, the post-production obligations. The annexes, by contrast, often get a quick skim or are skipped entirely on the basis that they are informative rather than normative.
On this page
That is a mistake, and a fairly common one.
The annexes of ISO 17100 contain practical guidance that shapes how compliant translation service providers actually operate day to day. If you are auditing a translation company, implementing the standard, or advising a client who is preparing for certification, understanding what the annexes say and why they exist will sharpen your work considerably.
This article walks through each annex in plain terms, explains what it is asking for, and draws out the audit and implementation implications that matter most in practice.
A Quick Orientation: Normative vs Informative in ISO 17100
Before getting into the content, it is worth being clear about what normative and informative mean in ISO terms, because it affects how you treat each annex.
Normative content contains requirements. When a clause says the organisation shall do something, that is a normative requirement and it must be met for conformity. Informative content provides guidance, context, or examples. It does not create requirements, but it does clarify how the standard expects things to work in practice.
All three annexes in ISO 17100 are informative. That means none of them create additional shall statements. However, auditors who dismiss informative annexes as irrelevant are missing the point. Informative guidance in an ISO standard reflects the intent of the technical committee. When you are assessing whether a normative requirement has been met in substance, the informative annexes often tell you what good looks like.
With that framing in place, here is what each annex covers.
Exemplar Global Recognised Training ProviderRTP No. 310970
Annex A: Agreements Between TSPs and Clients
What the Annex Contains
Annex A provides detailed guidance on the content of agreements between translation service providers (TSPs) and their clients. It builds on the pre-production requirements in Clause 4 of the standard, which requires that the TSP and client reach agreement on the scope and nature of the services before production begins.
The annex sets out a comprehensive list of items that a well-formed agreement should address. These include:
- The source and target languages involved
- The subject field and any domain-specific requirements
- The intended purpose and readership of the translation
- The deliverable format and any file type requirements
- Reference materials to be used, including glossaries and style guides
- Confidentiality expectations
- Intellectual property arrangements
- Applicable standards or specifications
- Deadlines and delivery arrangements
- Pricing and invoicing terms
- Complaint handling and revision procedures
- What happens if the client provides incomplete or ambiguous source material
Why This Matters for Auditors
When you audit Clause 4 pre-production conformity, you are looking for evidence that agreements exist and that they are fit for purpose. Annex A gives you a reference framework for evaluating whether an agreement is substantive or superficial.
A TSP that issues a one-line email confirming a word count and a deadline has technically communicated with the client, but it has not established the kind of agreement that ISO 17100 envisages. An auditor who only checks that some form of communication occurred before production started will miss this gap.
In practice, look for agreements that address the items in Annex A, even if they do so through a combination of documents. A standing master service agreement supplemented by a project-specific purchase order or work order is a perfectly legitimate approach, as long as the combination covers the relevant ground.
Common weaknesses you will find in this area include agreements that say nothing about reference materials, agreements that do not address what happens when source content is unclear or incomplete, and agreements that contain no revision or complaint procedure. These are not automatic nonconformities against a normative clause, but they signal that the TSP may not have a robust pre-production process, which is a normative requirement.
The Practical Implementation Angle
If you are helping a translation company implement ISO 17100, Annex A is a useful checklist for reviewing their client agreement templates. Walk through each item and ask whether it is addressed somewhere in the agreement documentation. Where items are missing, consider whether they need to be added to the standard template or whether they are addressed in another document that forms part of the contractual relationship.
Pay particular attention to the items around intellectual property and confidentiality. These are areas where translation companies frequently have informal arrangements rather than documented ones, and they become significant when a client discovers that their source material has been handled in a way they did not expect.
Annex B: Project Registration Information
What the Annex Contains
Annex B addresses project registration, which is the process of recording the key details of a translation project before and during production. It provides guidance on the information that should be captured in the TSP's project management or workflow system.
The recommended information includes:
- A unique project identifier or reference number
- Client name and contact details
- Source and target language pair or pairs
- Subject field
- Brief description of the content being translated
- Word count or volume metric
- Agreed deadline
- Names of the translator, reviser, and any other personnel assigned to the project
- Reference materials provided or used
- Special instructions relevant to the project
- The status of each production stage
- Any issues encountered during the project and how they were resolved
Why This Matters for Auditors
Project registration is the backbone of traceability in a translation management system. When you audit a TSP, you need to be able to trace a project from the initial client enquiry through to delivery and post-production archiving. If the project registration records are incomplete or inconsistent, that traceability breaks down.
Annex B tells you what a complete project record looks like. Use it as a reference when you are sampling project files during an audit. Pull a sample of completed projects and check whether the records contain the information the annex recommends. Where information is systematically absent, for example where no reviser is ever recorded, that is a signal worth investigating further.
One of the most important items in Annex B is the recording of personnel assigned to each production stage. This connects directly to the normative competence requirements in Clause 3 and the production workflow requirements in Clause 5. If you cannot determine from the project records who performed the translation and who performed the revision, you cannot verify that the mandatory two-person workflow was followed. That is a significant conformity issue.
The Practical Implementation Angle
For TSPs implementing ISO 17100, Annex B provides a practical template for what their project management system needs to capture. Whether the TSP uses a dedicated translation management system, a generic project management tool, or a structured spreadsheet, the fields recommended in Annex B should be present and consistently populated.
One area where implementation often falls short is the recording of issues and how they were resolved. Many TSPs record the basic project parameters but do not systematically document problems encountered during production. This matters because it affects the TSP's ability to learn from experience and improve over time, which connects to the continual improvement intent of the standard.
If you are advising a TSP on implementation, encourage them to build issue logging into their project workflow rather than treating it as an optional extra. Even a simple free-text notes field that is consistently used is better than no record at all.
Annex C: Translation Technology
What the Annex Contains
Annex C is the most forward-looking of the three annexes. It addresses the use of translation technology tools, including translation memory systems, terminology management tools, machine translation, and other computer-assisted translation technologies.
The annex does not prohibit or restrict the use of any particular technology. Instead, it sets out considerations that TSPs and clients should address when technology is used as part of the translation process. These include:
- Whether the use of specific tools has been agreed with the client
- How translation memory matches are handled and what quality checks apply to leveraged or fuzzy-matched segments
- How machine translation output is treated, particularly whether it undergoes post-editing and at what level
- Ownership and confidentiality of translation memory data
- The impact of technology use on pricing and turnaround
- How technology-assisted output is reviewed to ensure it meets the same quality standards as human translation
Why This Matters for Auditors
Translation technology is now central to how most professional TSPs operate. Translation memory systems, machine translation with post-editing, and AI-assisted tools are not fringe practices. They are standard. An auditor who approaches a TSP audit without understanding how these tools fit into the ISO 17100 framework will struggle to assess conformity accurately.
The key audit question that Annex C raises is whether the use of technology has been disclosed to and agreed with the client, and whether the quality requirements of the standard still apply regardless of how the translation was produced.
This second point is critical. ISO 17100 does not create a lower standard for machine-translated content. The normative requirements for quality, revision, and verification apply to the final output regardless of how it was generated. A TSP that uses machine translation and then skips revision because the output looks clean is not compliant, even if the final translation happens to be accurate.
When auditing, look for evidence that the TSP's quality process treats technology-assisted segments with the same rigour as human-translated segments. Check whether revisers are instructed to review all segments, including those drawn from translation memory, rather than assuming that high-match segments are automatically correct. Translation memory errors propagate systematically, and a reviser who skips high-match segments will miss them every time.
Also check whether the TSP's agreements with clients address technology use explicitly. This connects back to Annex A. If a client has not been told that machine translation is being used, and the TSP's agreement is silent on the point, that is a pre-production gap worth noting.
The Practical Implementation Angle
For TSPs implementing ISO 17100, Annex C is a prompt to review how technology use is documented and governed. Specifically, consider the following areas:
- Client agreements: Do they address which tools may be used, whether machine translation is permitted, and who owns the translation memory data?
- Reviser instructions: Are revisers explicitly instructed to check all segments, including high-match translation memory segments?
- Machine translation post-editing: Is there a defined process for post-editing that specifies the level of editing required (full post-editing vs light post-editing) and how quality is verified?
- Terminology management: Is the terminology database reviewed and updated regularly, and is its use by translators monitored?
As machine translation quality continues to improve and AI-assisted tools become more sophisticated, Annex C will become increasingly important. TSPs that have clear, documented policies on technology use will be better positioned for audit and better able to demonstrate that their quality standards are consistent regardless of the tools used.
How the Annexes Connect to the Main Body of the Standard
It is worth stepping back and seeing how the three annexes relate to each other and to the normative clauses.
Annex A supports Clause 4, which covers pre-production. The agreement is the foundation on which the entire project rests. If the agreement is vague or incomplete, the production process starts on unstable ground.
Annex B supports Clauses 4, 5, and 6 collectively. Project registration is the thread that connects pre-production, production, and post-production. Without complete and consistent records, you cannot demonstrate that the required workflow was followed or that the right people were involved at each stage.
Annex C cuts across the entire standard. Technology use affects pre-production agreements, production workflows, quality checking processes, and post-production archiving. It is not confined to a single clause.
Understanding these connections helps auditors think about the standard as a system rather than a checklist of isolated requirements. When you find a weakness in one area, consider what it implies for related areas. A TSP with poor project registration records is likely to have difficulty demonstrating compliance with the production workflow requirements. A TSP whose agreements say nothing about technology use is likely to have gaps in how technology-assisted content is quality-checked.
Common Audit Findings Related to the Annexes
Based on what typically emerges when auditing against ISO 17100, here are the findings that most commonly connect to the annex content:
- Client agreements that do not address reference materials, revision procedures, or intellectual property, leaving the TSP exposed to disputes and unable to demonstrate pre-production conformity
- Project records that identify the translator but not the reviser, making it impossible to verify that the mandatory two-person workflow was completed
- No documented process for handling machine translation output, with revisers left to make individual judgements about how thoroughly to check technology-assisted segments
- Translation memory ownership and confidentiality not addressed in client agreements, creating potential legal and reputational risk
- Issue logs that are either absent or so sparse that they provide no useful information about problems encountered and resolved during production
None of these findings necessarily constitute a major nonconformity on their own. But taken together, they paint a picture of a quality management system that is not operating with the rigour that ISO 17100 requires. An auditor who connects these dots and presents them as a pattern will produce a more useful audit report than one who notes each gap in isolation.
If you want to sharpen your ability to connect findings into coherent audit conclusions, the articles on writing audit reports people actually read and how to write audit findings that stand up to challenge are worth your time.
Exemplar Global Recognised Training ProviderRTP No. 310970Preparing for an ISO 17100 Audit: What to Have Ready
If you are a TSP preparing for certification or a surveillance audit, the annexes give you a useful self-assessment framework. Before your audit, review the following:
- Pull three to five recent client agreements and check them against the Annex A list. Are all the key items addressed, either in the agreement itself or in a referenced document?
- Pull three to five completed project files and check them against the Annex B list. Is all the required information present? Are the personnel assigned to each production stage clearly identified?
- Review your internal guidance on technology use. Is there a documented policy on how translation memory matches are handled? Is there a process for machine translation post-editing? Are revisers instructed to check all segments?
- Check your client agreements for technology-related provisions. Do they address which tools may be used, who owns the translation memory data, and how technology use affects pricing?
This preparation will not only help you perform well in the audit. It will also identify genuine gaps in your quality management system that, once addressed, will improve the consistency and reliability of your translation services.
For a broader understanding of how ISO 17100 certification works and what the two-stage audit process involves, see the article on how to get ISO 17100 certified. And if you are still building your understanding of the standard from the ground up, the overview at what is ISO 17100 is a good starting point.
Building Auditor Competence Across Specialised Standards
ISO 17100 is one of a growing number of sector-specific ISO standards that auditors are being asked to work with. The skills required to audit it effectively are the same skills that underpin good auditing across any ISO standard: the ability to follow an audit trail, to connect evidence across different parts of a system, to distinguish between superficial conformity and genuine effectiveness, and to write findings that are clear, specific, and useful.
If you are developing your auditing skills and want a structured pathway from foundation level through to lead auditor, the training courses at Audit Workshop are designed by practitioners who have conducted hundreds of real certification audits. The focus is on practical skill, not just passing an exam. Whether you are new to auditing or looking to extend your scope into additional standards, the courses provide the grounding you need to audit with confidence.
