Quality Assurance in Certified Translation: How ISO 17100 Guarantees Accuracy
Quality assurance for certified translation combines ISO 17100 workflow, translator-reviser separation, terminology control, and signed certification statements accepted by UK authorities.
Request a Free Quote
What we do
Our services
What does quality assurance mean for a certified translation?
Quality assurance for a certified translation is the ISO 17100 production chain — qualified translator, independent reviser, domain reviewer, and project manager sign-off — that verifies accuracy, terminology, and formatting before the agency signs, stamps, and dates the certification statement.
Which ISO 17100 clauses govern certified-translation quality assurance?
ISO 17100 governs certified-translation QA through five operative clauses: §3.1.4 translator competences, §5.3.1 translation, §5.3.3 revision by a second linguist, §5.3.4 domain review, and §5.3.5 proofreading before release, plus §5.1 project management oversight.
What are the four roles in a certified translation QA workflow?
A certified translation QA workflow uses four separated roles: the translator produces the target, the reviser compares source and target bilingually, the reviewer verifies domain accuracy, and the project manager releases the file after checking certification-statement fields and formatting.
How is terminology consistency enforced during QA?
Terminology consistency is enforced through a project-specific glossary, a translation memory locked to the client account, and an automated QA pass using tools such as Xbench or Verifika that flag inconsistent renderings, untranslated segments, number mismatches, and forbidden terms before revision.
What must appear on a certified translation certification statement in the UK?
A UK-accepted certification statement must include the translator’s or agency’s full name, the statement ‘true and accurate translation of the original document’, the source and target languages, the date, the signatory’s contact details, and the agency stamp on letterhead, per Home Office and HMCTS guidance.
How fast can a QA-compliant certified translation be delivered?
A QA-compliant certified translation is delivered same-day for civil documents under 1,000 words placed before 11:00 GMT, within 24 to 48 hours for legal and academic packs, and on agreed milestones for technical projects above 10,000 words, all under ISO 17100 quality control.
Certified translations accepted by UK authorities — the Home Office, HMCTS, universities, Ecctis, the NHS, and HMRC — are only as reliable as the quality assurance chain behind them. Under ISO 17100:2015, that chain is a four-role production workflow whose evidence trail is what makes a signed, stamped certification defensible on receipt.
What does quality assurance mean for a certified translation?
Quality assurance for a certified translation is the ISO 17100 production chain — qualified translator, independent reviser, domain reviewer, and project manager sign-off — that verifies accuracy, terminology, and formatting before the agency signs, stamps, and dates the certification statement. It is not a single proofread; it is a documented four-role workflow.
The QA chain produces five distinct artefacts on every certified job:
- Translator’s target file with source-layout markers ([stamp], [signature], [illegible]) and a query log.
- Bilingual revision diff from an independent second linguist.
- Domain review notes on legal, medical, technical, or financial content.
- Project-manager release checklist covering certification-statement fields.
- Signed, stamped, dated certification statement on agency letterhead.
How is QA different from a simple proofread?
QA is a multi-role verification workflow; proofreading is one step inside it. ISO 17100 requires an independent reviser to compare source and target bilingually, whereas a proofread only checks the target monolingually for surface errors. The distinctions matter because UK receiving authorities reject files that show only surface polishing.
| Check | Proofread | ISO 17100 QA |
|---|---|---|
| Source comparison | No | Yes, sentence by sentence |
| Second qualified linguist | Not required | Required (§5.3.3) |
| Terminology enforcement | Ad hoc | Glossary + TM + automated QA |
| Domain expert review | No | Yes on legal/medical/technical/financial |
| Auditable evidence trail | No | Yes, retained against project record |
Why does certification without QA get rejected by UK authorities?
UK authorities reject certified translations when the certification statement is unsupported by an auditable QA trail. The Home Office, HMCTS, and Ecctis require the translator’s credentials and the agency’s accountability, both produced by the ISO 17100 QA chain. Six recurring rejection triggers appear on returned files:
- Missing agency letterhead or stamp on the certification page.
- No translator credentials line or agency reference number.
- Incomplete translation (annexes, seals, or margin stamps omitted).
- Terminology inconsistency between recurring documents.
- No statement of accuracy in the exact form the receiving body accepts.
- Undated certification or mismatched source/target page counts.
Which ISO 17100 clauses govern certified-translation quality assurance?
ISO 17100 governs certified-translation QA through five operative clauses: §3.1.4 translator competences, §5.3.1 translation, §5.3.3 revision by a second linguist, §5.3.4 domain review, and §5.3.5 proofreading before release, plus §5.1 project management oversight. Each clause produces a specific QA artefact on a certified pack.
| ISO 17100 clause | Requirement | QA artefact on a certified job |
|---|---|---|
| §3.1.4 | Translator competences | Credentials line on the certification statement |
| §5.1 | Project management | Release checklist and project record |
| §5.3.1 | Translation | Target file plus source-ambiguity query log |
| §5.3.3 | Bilingual revision | Reviser diff with accept/reject decisions |
| §5.3.4 | Domain review | Subject-matter expert sign-off notes |
| §5.3.5 | Proofreading | Monolingual final read before delivery |
ISO 17100:2015 is the internationally recognised standard for translation services and specifies requirements for core processes, resources, and quality assurance in delivering translation services, per the ISO 17100 record on iso.org. It sits alongside ISO 9001, a general quality management standard that governs process consistency and continual improvement across the agency.
What translator qualifications does ISO 17100 §3.1.4 require?
ISO 17100 §3.1.4 requires translators to meet one of three thresholds: a recognised degree in translation, a degree in another field plus two years of full-time translation experience, or five years of full-time professional translation experience with documented evidence. Every translator assigned to a certified job is vetted against one of these paths before the file is opened.
- Path A: Recognised degree in translation, linguistics, or language studies.
- Path B: Degree in another field plus two years documented full-time translation experience.
- Path C: Five years documented full-time professional translation experience.
UK-market translators additionally hold membership of the Chartered Institute of Linguists (CIOL) or the Institute of Translation and Interpreting (ITI), which UK authorities recognise as professional standing on the certification statement.
What does §5.3.3 bilingual revision add on top of translation?
Clause 5.3.3 mandates a second qualified linguist to compare source and target sentence by sentence, checking meaning, terminology, register, and completeness. The reviser cannot be the translator, and the revision output is logged as a distinct QA artefact. Nine items are verified in every bilingual pass:
- Completeness against the source (no dropped segments, footnotes, or seals).
- Accuracy of meaning at sentence level.
- Terminology consistency against the project glossary.
- Register appropriate to the document type.
- Numbers, dates, and currency values.
- Proper names, addresses, and identifiers.
- Formatting, layout, and stamp/signature markers.
- Punctuation and typography per target-language convention.
- Adherence to the receiving authority’s presentation rules.
When is a §5.3.4 domain review triggered on a certified job?
A §5.3.4 domain review is triggered when the certified document is legal, medical, technical, or financial. A subject-matter expert verifies terminology and factual claims, such as drug names on an NHS report or clause numbering on a court exhibit. On Legal Translation Services destined for HMCTS, the reviewer confirms cause numbers, party names, and statute citations. On Expert Technical Translation Services in London, the reviewer checks unit conversions, part numbers, and industry-standard terminology.
How it works
What are the four roles in a certified translation QA workflow?
1
What does the translator deliver on a certified job?
The translator delivers a full target-language rendition of the source document, keeping layout, seals, and signatures marked as [stamp], [signature], and [illegible] where required for UK-accepting authorities, and flags source ambiguities in a query log. Every visible element on the source appears on the target — nothing is silently dropped, including margin notes, apostille pages, and reverse-side text.
2
What does the independent reviser check line by line?
The independent reviser checks completeness, accuracy of meaning, terminology consistency, register, numbers, dates, proper names, and formatting against the source. Any change is recorded so the translator accepts or rejects it, producing an auditable diff. The reviser also confirms that stamp and signature placeholders match the source position, that names are transliterated consistently, and that recurring terms use the client-locked glossary rendering.
3
What final checks does the project manager sign off?
The project manager verifies the certification statement fields, agency stamp, translator credentials, page count, source-to-target page mapping, and delivery format before release. Only then is the certified PDF signed and dated on agency letterhead. The release checklist covers seven items:
- Certification statement wording matches the receiving authority’s requirement.
- Translator name and credentials line are present.
- Agency stamp is applied on the certification page.
- Date matches the delivery day.
- Page count on certification equals the target page count.
- Every source page maps to a target page (annex included).
- Delivery format matches the client’s submission channel (PDF, hard copy, or both).
How is terminology consistency enforced during QA?
Terminology consistency is enforced through a project-specific glossary, a translation memory locked to the client account, and an automated QA pass using tools such as Xbench, Verifika, memoQ QA, and Trados QA Checker that flag inconsistent renderings, untranslated segments, number mismatches, and forbidden terms before revision. The client-locked translation memory enforces terminology continuity across recurring certified jobs — the same company name, product code, or clinical term renders identically on every future file, eliminating drift that can cause a document to be rejected by a receiving authority.
Terminology management is not a cosmetic step; for legal, medical, financial, and technical certified content, a single inconsistent rendering of a defined term can alter legal meaning or trigger a refusal from bodies such as the Home Office or HMCTS. That is why the glossary is built and locked at the project-setup stage, before the first segment is translated, and is shared across every role in the ISO 17100 workflow — translator, reviser, and reviewer all work from the same controlled vocabulary. The automated QA layer then independently verifies adherence to that vocabulary before any human reviser opens the file, creating a two-layer defence: machine precision followed by expert judgement.
Which automated QA checks run before the human reviser opens the file?
Automated QA runs eight checks before human revision:
- Segment completeness (no untranslated or empty target segments).
- Number and date parity between source and target.
- Punctuation and end-of-segment consistency.
- Tag and formatting integrity.
- Terminology adherence against the project glossary.
- Forbidden-term detection (deprecated renderings or client blacklists).
- Double-space and typography rules per target language.
- Translation-memory inconsistency reporting across the file.
Automated checks do not replace the human reviser; they clear the mechanical layer so the reviser focuses entirely on meaning, register, and domain accuracy. This division of responsibility is deliberate: software excels at pattern-matching across hundreds of segments simultaneously, while a qualified independent reviser — who under ISO 17100 §5.3.3 must be a separate person from the translator — brings the contextual and linguistic judgement that no algorithm can replicate. Together, both layers form the predicate foundation of a defensible, authority-ready certified translation.
What must appear on a certified translation certification statement in the UK?
A UK-accepted certification statement must include the translator’s or agency’s full name, the statement “true and accurate translation of the original document”, the source and target languages, the date, the signatory’s contact details, and the agency stamp on letterhead, per Home Office and HMCTS guidance. Missing any field is a routine rejection trigger.
| Receiving authority | Certification requirement |
|---|---|
| UK Home Office | Full translation, translator/company details, statement of accuracy, date, contact — per gov.uk guidance |
| HMCTS | Certified translation with signed statement of truth and translator credentials |
| Ecctis (formerly UK NARIC) | Certified translation from a professional translator or agency for academic recognition |
| NHS / GMC | Certified translation with translator credentials on letterhead |
| HMRC | Certified translation with agency contact and stamp |
| UK universities | Certified translation on letterhead with signatory contact |
Certified translation differs from sworn, notarised, and apostilled documents under UK acceptance rules. A sworn translation exists in civil-law systems (Germany, France, Spain) where court-authorised translators produce it — the UK does not operate a sworn-translator register. A Notarised Translation Services engagement adds a notary public confirming the translator’s identity and signature, not the accuracy of the translation itself. An apostille, issued under the 1961 Hague Convention, authenticates the signature and seal on a public document for cross-border use; it does not certify content.
How is the QA trail evidenced on the delivered pack?
The QA trail is evidenced by a signed certification page, the translator’s credentials line, an agency reference number tying the file to the ISO 17100 project record, and — when requested — a covering letter listing translator, reviser, and reviewer names for HMCTS submissions. Confidentiality is maintained throughout under UK GDPR-aligned handling of personal documents during QA.
How fast can a QA-compliant certified translation be delivered?
A QA-compliant certified translation is delivered same-day for civil documents under 1,000 words placed before 11:00 GMT, within 24 to 48 hours for legal and academic packs, and on agreed milestones for technical projects above 10,000 words, all under ISO 17100 quality control. The QA chain is not shortened for speed — it is parallelised.
| Document type | Word count | Turnaround SLA |
|---|---|---|
| Civil (birth, marriage, ID) | Under 1,000 | Same-day if placed before 11:00 GMT |
| Legal / academic | 1,000–10,000 | 24–48 hours |
| Technical / financial | Above 10,000 | Agreed milestones |
Same-day civil turnaround covers the workload behind Document Translation Services in London and the UK, including birth certificates, marriage certificates, driving licences, and academic transcripts. Same-day certified translation London runs under the same four-role QA chain as multi-week technical projects.
How much does a QA-included certified translation cost in the UK?
A certified translation with the full ISO 17100 QA chain starts from £30 per page in the UK, covering translation, bilingual revision, project-manager release, and the signed certification statement, with no separate ‘QA fee’ added at checkout. Language coverage extends to 200+ languages under the same pricing structure.
- Civil documents (single-page): from £30 per page.
- Legal, medical, technical, and financial: priced per word to reflect the §5.3.4 domain review overhead.
- Rush and out-of-hours delivery: surcharge on the standard rate.
- Recurring corporate accounts: client-locked TM reduces per-word cost on repeat terminology.
How do you request a certified translation with full QA?
Requesting a certified translation with full QA is a structured, six-step process designed so that every document enters a compliant ISO 17100 workflow from the moment it is received. The process begins with uploading the source document, specifying the receiving authority — such as the Home Office, HMCTS, Ecctis, GMC, NHS, or HMRC — and confirming the target language. A dedicated project manager then confirms scope, workflow, timeline, and price within one business hour, ensuring nothing is left ambiguous before work begins.
Naming the receiving authority at the outset is essential because acceptance criteria differ across bodies. The Home Office requires a full translation accompanied by the translator’s or agency’s details, a statement of accuracy, and a date. HMCTS requires a signed statement of truth alongside verified translator credentials. Ecctis requires confirmation that the translation has been produced by a professional translator or agency. Each of these requirements shapes the wording and format of the certification statement — so specifying the authority upfront means the statement is drafted correctly the first time, avoiding resubmission delays.
Every certified project is backed by a quality-first approach — including ISO 9001:2015 certified Quality Management System disciplines — ensuring documents are accurate, accepted, and protected before they leave our hands.
- Upload the source document (PDF, scan, or photo of every page, including reverse sides).
- Name the receiving authority so the certification statement wording precisely matches its acceptance rules.
- Confirm the target language and any transliteration preferences for proper names.
- Receive a fixed quote in GBP with a turnaround SLA within one business hour.
- Approve; the four-role ISO 17100 QA chain — translator, reviser, domain reviewer where required, and project manager — begins immediately under a unique project reference number.
- Receive the signed, stamped, and dated certified translation with a full QA evidence trail, ready for submission to the named authority.
The certification statement delivered with every completed project carries all mandatory fields: the translator’s or agency’s name, a declaration of accuracy, the source and target languages, the date, contact details, a stamp, and agency letterhead. This is not a courtesy addition — it is the documentary proof that receiving authorities examine before accepting a translated document as valid.