ISO 17100 translator competence is where many certification journeys stall. Tools and templates are easy to buy; proving that every translator and reviser on in-scope work meets defined qualification routes—and that revisers are independent—is harder.
ISO 17100:2015 expects Translation Service Providers to treat competence as an operational control. That means documented criteria, current records, domain fit, and job assignments that show the reviser is not the translator.
This guide covers:
- The three qualification paths for translators under ISO 17100
- Reviser rules, including domain expertise and independence
- HR evidence auditors commonly expect
- Assignment workflows and a decision table for go/no-go staffing
GIF via GIPHY
Related guides:
- What is ISO 17100:2015? Everything you need to know
- ISO 17100 requirements: a complete breakdown
- Who needs ISO 17100 certification?
- ISO 17100 audit: what auditors look for
- ISO 17100 collection
Key takeaways
- ISO 17100 translator competence typically requires meeting at least one of three qualification paths (translation/linguistics degree; other graduate degree + 2 years; or 5 years full-time professional experience).
- Revisers need translator-level competences plus domain experience, and must be a different person from the translator on that job.
- Competence is proven with records, not hallway reputation—HR and vendor management own the evidence lifecycle.
- Project managers and technical resources also need defined competence expectations inside the TSP system.
- SecureSlate can help organize ownership and evidence for audits; it does not replace linguistic certification or professional judgment.
Why competence is a control — not a CV pile
Buyers and auditors do not only ask “Do you hire good people?” They ask:
- Which criterion qualifies this translator for this language pair and domain?
- Who revised the job, and why are they qualified in this subject area?
- How do you onboard freelancers and retire access when contracts end?
- What happens when a complaint traces back to a competence gap?
If answers live in a project manager’s memory, your ISO 17100 system is fragile. Competence should connect to production requirements: no qualified reviser available means the job should not be accepted under an ISO 17100 production claim.
Translator qualification paths
Under ISO 17100:2015, a translator typically must meet at least one of the following:
| Path | Requirement (summary) | Evidence examples |
|---|---|---|
| (a) Translation / language degree | Graduate degree in translation, linguistics, or language studies | Diploma/transcript; credential verification notes |
| (b) Other graduate degree + experience | Graduate degree in another field plus 2 years professional translation experience | Degree proof + employer/client attestations, work history |
| (c) Experience-only route | 5 years full-time professional translation experience | Detailed CV, references, sample projects, attestations |
Operational tips:
- Define what “professional translation experience” means in your procedures (paid work, language pairs, full-time equivalence).
- Re-verify freelancers on a cadence—not only at first onboarding.
- Map language pairs and domains separately from the base qualification path.
- Keep exceptions rare, written, and approved by a named quality owner.
Do not invent a fourth informal path like “native speaker with good vibes.” If someone cannot meet (a), (b), or (c), they should not be assigned as the ISO 17100 translator of record.
Reviser rules and domain expertise
Revision is mandatory in ISO 17100 translation production, and reviser competence is stricter in practice because domain fit matters.
Reviser expectations commonly include:
- Meeting translator competence requirements (paths above)
- Demonstrable domain experience relevant to the content
- Independence: reviser ≠ translator on the same translation task
- Ability to compare source and target and judge suitability for purpose per your process
| Reviser scenario | Acceptable? | Why |
|---|---|---|
| Translator A translates; Translator B revises (qualified + domain fit) | Yes | Independence + competence |
| Same person translates and “self-revises” | No for ISO 17100 production | Violates second-person revision |
| Reviser qualified in language but no domain experience for clinical IFU | Risky / typically no | Domain experience required |
| Junior proofreader labeled as “reviser” without translator competence | No | Role inflation |
Domain expertise can be shown through prior projects, subject-matter employment, specialized training, or vetted sample evaluations—documented in the competence file.
Project managers and related competences
ISO 17100 is not only a linguist standard. Project managers need competence to:
- Analyze requirements and feasibility
- Select appropriate linguistic resources
- Enforce process steps (especially revision)
- Communicate with clients on specifications and changes
- Protect confidentiality throughout the job lifecycle
Technical resources (tools, IT support) should be competent to maintain environments that protect linguistic assets and support production. Define training and access rules so freelancers do not become unmanaged shadow IT.
For who should pursue organizational certification around these roles, see Who needs ISO 17100 certification?.
HR evidence records to keep
Auditors typically sample people and jobs. HR (or vendor management for freelancers) should keep a living competence file.
Core records
- Legal name / working name and contact
- Language pairs and directions
- Qualification path used (a, b, or c) with supporting documents
- Domain competencies and evidence
- Signed confidentiality / NDA acknowledgements
- Onboarding checklist completion dates
- Performance or complaint-related notes tied to CAPA when relevant
- Last review / re-qualification date
Assignment-linked records
- Job ID with translator ID and reviser ID (must differ)
- Spec version used
- Dates of translate and revise completion
- Any review/proof/verify participants
| Record | Owner | Refresh cadence (typical) |
|---|---|---|
| Qualification path dossier | HR / vendor mgmt | On hire + when credentials change |
| Domain matrix | Linguistic lead | Quarterly or per major vertical expansion |
| NDA / confidentiality | Ops / security | Onboarding + contract renewal |
| Job role separation log | PM system | Every job (system-enforced) |
| CAPA from quality escapes | Quality manager | As events occur; trend in management review |
Store records so they survive staff turnover. Shared inboxes and personal drives fail audits.
Assignment workflows that prove independence
Competence on paper fails if the PMS lets one user complete both translate and revise. Design the workflow so:
- Translator and reviser fields cannot be the same user
- Domain tags gate eligible revisers
- Status cannot move to “ready for delivery” without revise complete (unless a documented, approved exception path exists—and exceptions should be rare)
- Freelancer access expires after project windows
Sample operational workflow:
- PM confirms specification and risk level
- System proposes translator candidates meeting path + pair + domain
- System proposes reviser candidates excluding the chosen translator
- Both accept NDA/task terms
- Production completes with timestamps
- Verification checks role separation before delivery
This is exactly the kind of evidence trail discussed in ISO 17100 audit: what auditors look for.
Decision table — qualify, upskill, or do not assign
| Candidate situation | Decision | Next action |
|---|---|---|
| Meets path (a)/(b)/(c), domain fit strong, NDA current | Assign | Log path + domain tags on job |
| Meets base path, weak domain for this job | Do not assign as reviser; maybe translate with strong reviser | Upskill domain or find specialist |
| Near experience threshold but documentation incomplete | Do not assign yet | Collect attestations; freeze until file complete |
| Strong linguist, refuses independent revision model | Do not use on ISO 17100-scoped work | Limit to out-of-scope services or exit |
| Only available person for both translate and revise | Do not claim ISO 17100 production for that job | Reschedule, subcontract reviser, or decline |
| Complaint closed with competence root cause | Restrict domains until CAPA done | Retrain, shadow revise, re-approve |
Use the table in weekly resourcing meetings so commercial pressure does not silently override the standard.
Streamline competence evidence with SecureSlate
Competence programs fail when HR files, NDAs, and job logs disagree. SecureSlate helps TSPs keep policies, ownership, confidentiality workflows, and audit-ready evidence connected—so translator and reviser controls stay reviewable.
With SecureSlate you can:
- Assign owners for competence dossiers, re-qualification, and CAPA follow-ups
- Centralize confidentiality acknowledgements alongside quality process records
- Prepare audit packs that sample people and jobs without a week of folder archaeology
- Support ongoing readiness after certification, not only during Stage 2
- Align security-adjacent access workflows when freelancers handle sensitive source content
SecureSlate does not replace linguistic certification, degree evaluation, or reviser professional judgment.
FAQ: ISO 17100 translator competence
What is required for ISO 17100 translator competence?
Typically at least one of: a graduate translation/linguistics/language degree; another graduate degree plus two years’ professional translation experience; or five years’ full-time professional translation experience.
Do revisers need extra qualifications?
Yes—revisers need translator competences plus domain experience, and must be a different person from the translator on that job.
Can a native speaker without the three paths translate under ISO 17100?
Not as the qualified translator of record unless they meet one of the defined paths (or your certification body agrees a documented equivalent under your approved system—do not assume). Stick to the published routes.
What HR documents should we keep for freelancers?
The same competence logic as staff: path evidence, domain proof, NDAs, onboarding, and job assignment history showing reviser independence.
Does SecureSlate certify translators?
No. SecureSlate helps with policies, ownership, and evidence workflows. Linguistic qualification remains a TSP and professional responsibility.
How does this connect to certification cost and audits?
Incomplete competence files are a common delay and nonconformity source. Plan evidence early using the certification checklist and cost guide.
Disclaimer (legal note)
SecureSlate is not a law firm, and this article does not constitute legal advice, certification advice, or an attorney-client relationship. Translator and reviser competence criteria summarized here are for operational education. Confirm exact requirements against ISO 17100:2015, your documented procedures, and guidance from your accredited certification body or qualified counsel before making hiring, assignment, 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.
No credit card required
