ISO 18841 vs ISO 17100 is one of the most common comparison questions from language service companies preparing RFPs, certification roadmaps, or board updates. Both are ISO standards for language services—and both can appear on the same buyer checklist—but they answer different questions about different delivery models.
ISO 18841 asks whether your interpreting services follow general requirements and recommendations for Interpreting Service Providers. ISO 17100 asks whether your translation services follow competence and process requirements for Translation Service Providers. Treating them as interchangeable creates false confidence in sales decks and gaps in audits.
This guide covers:
- A clear side-by-side comparison of ISO 18841 and ISO 17100
- Where confidentiality and ethics overlap—and where controls diverge
- When to pursue one or both, and which to sequence first
- A practical decision table for dual-service language providers
GIF via GIPHY
Related guides:
- What is ISO 18841:2018? Everything you need to know
- What is ISO 17100:2015? Everything you need to know
- Who needs ISO 18841 certification?
- ISO 18841 requirements: a complete breakdown
- ISO 18841 collection
Key takeaways
- ISO 18841 is interpreting-service specific (spoken and signed); ISO 17100 is translation-service specific (written).
- Holding ISO 17100 alone does not prove interpreting competence matching, assignment prep, or interpreting ethics controls.
- Holding ISO 18841 alone does not prove mandatory translation revision, translator qualification routes, or other ISO 17100 production controls.
- Many mature LSPs pursue both when they sell interpreting and translation into enterprise, healthcare, legal, or public buyers.
- Shared foundations—confidentiality policies, document control mindset, corrective action, vendor onboarding—reduce dual-standard overhead when ownership is clear.
Quick comparison table
| Dimension | ISO 18841:2018 | ISO 17100:2015 |
|---|---|---|
| Primary focus | Interpreting services — general requirements and recommendations | Translation services — requirements for translation services |
| Typical audience | Interpreting Service Providers (ISPs) | Translation Service Providers (TSPs) |
| Core proof point | Competent interpreters + ethics + prepared assignments | Competent translators/revisers + controlled translation process |
| Signature control | Mode/setting matching, assignment prep, impartiality/confidentiality | Mandatory revision by a second qualified person |
| Modality | Spoken and signed interpreting | Written translation |
| Out of scope notes | Written translation | Interpreting; raw MT + post-editing addressed elsewhere (e.g., ISO 18587) |
| Buyer question it answers | “Do you run ISO-aligned interpreting services?” | “Do you run ISO-aligned translation production?” |
| Substitutes for the other? | No | No |
Use this table in internal planning docs and sales enablement so account teams stop saying “we’re ISO language-quality certified” without naming which standard covers which service line.
What ISO 18841 covers
ISO 18841:2018 frames interpreting as real-time communication facilitation. It typically emphasizes:
- Organizational responsibilities of the ISP
- Interpreter competence across linguistic, cognitive, interpersonal, and technical dimensions
- Ethics, commonly including confidentiality and impartiality
- Modes such as consecutive and simultaneous interpreting
- Settings/specializations such as community, legal, healthcare, and conference
- Assignment preparation and suitable working conditions
- Quality feedback and continual improvement habits
Specialized interpreting standards (for example ISO 20228 for legal interpreting) may sit beside ISO 18841. For operational detail, see ISO 18841 requirements: a complete breakdown and interpreter competence requirements.
ISO 18841 does not turn your translation desk into a certified TSP. If you deliver written translation under controlled processes, that is an ISO 17100 conversation—see What is ISO 17100:2015?.
What ISO 17100 covers
ISO 17100:2015 frames translation as a managed document production service. It typically emphasizes:
- Organizational responsibilities of the TSP
- Human and technical resources
- Pre-production, production, and post-production stages
- Translator qualification paths and mandatory revision by a second qualified person
- Client agreements, confidentiality for source/target content, and feedback handling
ISO 17100 does not certify your interpreting line. Interpreting is typically out of ISO 17100 scope. Forcing interpreting jobs into a “translate then revise” metaphor usually fails both auditor conversations and operational reality.
| Process idea | Interpreting (18841 world) | Translation (17100 world) |
|---|---|---|
| Core unit of work | Assignment / encounter / event | Project / document job |
| Quality gate | Competence match + prep + ethics + feedback | Translate + mandatory revise (+ optional review) |
| Time pressure | Real-time / near real-time | Asynchronous production |
| Typical artifact | Performance and briefing records | Bilingual files + revision evidence |
Overlapping confidentiality and ethics
This is where dual-service LSPs can reuse work—carefully.
Common overlap
- Confidentiality obligations toward client content and participant information
- NDAs / confidentiality acknowledgements for linguists and vendors
- Secure handling of briefing materials, source files, recordings, and glossaries
- Clear escalation when a confidentiality incident occurs
Where controls diverge
| Topic | Interpreting (ISO 18841 lens) | Translation (ISO 17100 lens) |
|---|---|---|
| Confidentiality object | Spoken/signed encounter content; often highly personal | Source and target documents; terminology assets |
| Impartiality | Central professional ethic in many settings | Less central as a named production control |
| Recording / remote platforms | VRI/OPI platforms, booth audio, session logs | CAT tools, TMS, file transfer |
| Role boundaries | Interpreter ≠ advocate / advisor (commonly) | Translator/reviser role separation on the job |
Build one organization-wide confidentiality policy, then attach interpreting-specific and translation-specific procedures. Do not pretend a translation file-handling SOP covers clinical interpreting encounters—or that an interpreting code of ethics replaces translation revision records.
When you need both standards
You typically need both when:
- Your company sells interpreting and translation as distinct service lines
- Buyers issue RFPs that list ISO 18841 and ISO 17100 separately
- Healthcare, legal, or government clients buy language access and document translation from the same vendor
- Sales currently blurs “ISO certified language services” without scope clarity—and you need to fix that before the next diligence cycle
You may need only ISO 18841 when interpreting is your core offering and written translation is rare, fully outsourced under a certified TSP, or out of commercial scope.
You may need only ISO 17100 when translation is your core offering and interpreting is occasional, subcontracted, or not sold under your brand’s quality claims.
For who should pursue interpreting certification specifically, see Who needs ISO 18841 certification?. For translation-side buyer triggers, see Who needs ISO 17100 certification?.
Which should you do first?
Sequence based on revenue risk and RFP pressure, not alphabetical order.
Practical sequencing guidance:
- Follow the next lost deal. If interpreting RFPs are blocking revenue, prioritize ISO 18841 readiness. If translation RFPs are, prioritize ISO 17100.
- Reuse shared foundations early. Confidentiality, vendor onboarding, corrective action, and document control benefit both programs.
- Separate scopes in writing. Publish clear service-line scope statements so sales and auditors do not mix interpreting and translation claims.
- Staff evidence differently. Interpreter competence files ≠ translator/reviser competence files. Keep both current if you pursue both.
- Confirm scheme maturity. ISO 17100 certification markets are often more mature; ISO 18841 scheme availability can vary—validate before promising dates.
A dual-service LSP that implements shared policies first, then service-specific procedures, usually spends less than two disconnected projects inventing parallel binders.
Decision table — one, the other, or both?
| Situation | Recommendation |
|---|---|
| Dual-service LSP selling into enterprise/healthcare/legal | Both — separate scopes; shared confidentiality foundation |
| Interpreting-only agency | ISO 18841 — do not force ISO 17100 |
| Translation-only TSP | ISO 17100 — keep interpreting out of scope claims |
| Mostly translation; small interpreting desk | 17100 first; align 18841 when interpreting revenue/RFPs grow |
| Mostly interpreting; occasional document work | 18841 first; use certified TSP partners or add 17100 later |
| Buyers ask only for “ISO quality” without naming a standard | Clarify — map questions to interpreting vs translation evidence |
| Same linguists do both interpreting and translation | Dual competence files — prove fit per service type and job |
Streamline dual-standard readiness with SecureSlate
Dual-standard programs fail when interpreting and translation evidence live in separate tribal knowledge. SecureSlate helps language providers operationalize shared policies and service-specific ownership—without claiming to replace linguistic certification, interpreter licensing, or reviser judgment.
With SecureSlate you can:
- Separate scopes for interpreting (ISO 18841) and translation (ISO 17100) while sharing confidentiality controls
- Assign owners per service line for competence, prep/production, and feedback
- Track evidence for interpreter matching and translator ≠ reviser job records
- Prepare diligence packs that answer the right standard for each buyer question
- Maintain readiness across surveillance cycles and RFP seasons
FAQ: ISO 18841 vs ISO 17100
Are ISO 18841 and ISO 17100 the same thing?
No. ISO 18841 covers interpreting services; ISO 17100 covers translation services. They are complementary for dual-service providers, not substitutes.
If we have ISO 17100, do we automatically cover interpreting?
Typically no. Interpreting is generally out of ISO 17100 scope. Keep interpreting claims under ISO 18841 (or other interpreting-specific frameworks).
If we have ISO 18841, does that include translation revision?
No. Mandatory translation revision and TSP production stages belong to ISO 17100, not ISO 18841.
Can one certificate cover both?
Usually not as a single blended claim. Organizations commonly maintain separate scopes (and often separate certificates or statements of applicability) for interpreting and translation service lines. Confirm with your certification body.
Where do confidentiality requirements overlap?
Both standards expect disciplined handling of confidential information. Build a shared policy with service-specific procedures for encounters (interpreting) versus documents (translation).
What about specialized interpreting standards like ISO 20228?
They may sit beside ISO 18841 for specific settings (for example legal). They do not replace ISO 17100 for written translation.
Disclaimer (legal note)
SecureSlate is not a law firm, and this article does not constitute legal advice, certification advice, or an attorney-client relationship. ISO 18841:2018 and ISO 17100:2015 interpretation, certification scope, scheme availability, and contractual obligations vary by organization, market, and certification body. Confirm requirements with qualified counsel and your auditor or certification body before making compliance or certification decisions.
Need compliance without the complexity?
SecureSlate automates ISO 27001, SOC 2, GDPR, HIPAA, and more. Built for growing teams. See it in action.
Find compliance gaps in 30 seconds
