ISO 17100 — Translation Services Process Conformity 📘

Defined processes, qualified linguists, terminology governance, QA/LQA, and documented change-control — so your translations/localisation meet ISO 17100 requirements across projects and certified deliveries.

👩‍🎓 Qualified Resources 🧭 Project Prep 🧠 Term Management ✅ Review & LQA 🔁 Change-Control 📦 Delivery Evidence
Process diagram and documents showing compliance steps

Scope & Process Elements

Resources

Qualified Translators & Revisers

Projects use qualified linguists with proven domain competence. We log roles (translator, reviser, reviewer) and maintain training records to satisfy ISO 17100 resource requirements.

  • CVs/records on file

  • Domain checks matched to project

  • Reviser independent of translator

Preparation

Project Setup & Baselines

We confirm purpose, audience, locale variants, file types, and reference material; we prime baselines for translation/localisation including style and terminology packs.

  • Requirements & deliverables agreed

  • Reference & style guides shared

  • Term bases seeded

Production

Translate → Revise → Review

Every job follows translation by a qualified linguist, and revision by a second qualified linguist. Review stages may include LQA sampling and stakeholder feedback with governance.

  • Two-linguist workflow

  • LQA sampling where scoped

  • Governed feedback loop

TermOps

Terminology Governance

Terminology extraction, domain packs, variant notes and concordance. Translated variants are justified and logged with sources to keep decisions reproducible.

  • Mandatory/forbidden terms

  • Domain-specific packs

  • Variant rationale

Change Control

Redlines & Acceptance

We record who changed what and why, align to LQA categories, and link decisions to an acceptance matrix. This supports sign-off for certified translations too.

  • Segment redlines

  • LQA thresholds

  • Acceptance mapping

Delivery

Evidence & Traceability

Signed PDFs, hash/QR verification for translated files, sealed ZIP manifests, courier logs for hard copies — all tied back to project records.

  • Verification blocks

  • Sealed manifests

  • Chain-of-custody

Evidence Snippets

Resource Qualification
translator: tl-284  | domain: med-devices | quals: MA (Ling), 8y exp
reviser:    rv-143  | domain: med-devices | quals: ISO17100 listed
Two-Linguist Log
workflow: translate -> revise -> (review/LQA)
rev-note: "terminology alignment to IEC 60601; TBX links attached"

FAQ

Does ISO 17100 require a reviser?

Yes. A second qualified linguist revises the work; we log this stage for every job in scope.

How do you prove qualification?

We maintain records for translators/revisers (CVs, domain evidence) and map them to projects.

Is LQA mandatory?

LQA is applied per scope; revision is mandatory, LQA sampling is common for continuous localisation.

What about MT/MTPE?

MT/MTPE can be used, but output still goes through revision and quality gates before sign-off.

What do you need next?

ISO 17100 Scope Pack

Get a scope summary and example records for audit files.

/#quick-quote
Start Certified Translation

Two-linguist workflow with delivery verification.

/#quick-order
Security & QA Call

Map ISO 17100 to your internal policy.

/#quick-contact