ISO 17100 certifiedinfo@translationservicesuk.co.uk+44 20 4569 1419
Translation Services UK
Get a fixed quote

Translation service

Regulatory Submission Translation Services UK

UK regulatory submission translation services under ISO 17100 for MHRA, EMA and FDA dossiers — CTD/eCTD, ICFs, SmPCs, IFUs, CoT included, from £30 per page.

What are regulatory submission translation services in the UK?

Regulatory submission translation services in the UK convert dossiers for the MHRA, EMA and FDA into target languages under ISO 17100, with CIOL/ITI-credentialed life-sciences linguists, a Certificate of Translation and a Trial-Master-File-ready audit trail, from £30 per page.

Which regulatory documents do UK translation services translate for life-sciences submissions?

UK regulatory translation services cover CTD/eCTD modules, clinical trial protocols, informed consent forms, SmPCs, PILs, IFUs, CMC quality content, pharmacovigilance safety reports, labelling, promotional materials and health-authority correspondence — every document the MHRA, EMA or FDA expects in the submission language.

Why is specialist translation critical for regulatory submissions in the UK and EU?

Specialist regulatory translation protects submission acceptance, patient safety and market timelines: a mistranslated SmPC heading, a non-compliant QRD annex or a missing Certificate of Translation can trigger a Day-120 EMA question, an MHRA inspection finding or outright dossier rejection, delaying launch by months.

How do UK translation providers ensure accuracy and regulatory compliance?

UK providers ensure accuracy through an ISO 17100 translate-edit-proofread (TEP) workflow, domain-credentialed subject-matter linguists, controlled terminology against MedDRA and EDQM, back-translation and reconciliation for patient-facing content, and a Certificate of Translation issued with every regulatory deliverable.

Which quality standards and certifications should a UK regulatory translation provider hold?

A UK regulatory translation provider should hold ISO 17100 for translation processes, ISO 27001 for information security, ISO 9001 for quality management and ISO 18587 for machine-translation post-editing, with linguists credentialed by CIOL (MCIL) or ITI (MITI) and documented GxP familiarity.

How do translation providers protect confidential regulatory documents?

Providers protect regulatory documents through ISO 27001-governed encrypted file transfer, UK GDPR and NHS DSPT-aligned processing, signed NDAs with every linguist, role-based access controls in the translation management system, and UK or EU data residency with no third-country processing without client authorisation.

Pricing starts from £30 per page under ISO 17100, with CIOL/ITI-credentialed life-sciences linguists, 150+ languages, a signed Certificate of Translation on every TMF-filed document, and standard turnaround of 2–3 working days. Framework agreements, retainers and TMS/API integration cover recurring regulatory content for pharmaceutical companies and CROs.

What are regulatory submission translation services in the UK?

Regulatory submission translation services in the UK are a specialist life sciences translation discipline that converts dossiers for the MHRA, EMA and FDA into target languages under ISO 17100, delivered by CIOL/ITI-credentialed linguists with a Certificate of Translation and a Trial-Master-File-ready audit trail, from £30 per page. The service covers CTD/eCTD modules, clinical, CMC, labelling, safety and promotional content.

Core deliverables on every regulatory translation project:

Which UK, EU and US regulators receive these translated dossiers?

Translated dossiers reach the MHRA in the UK, the EMA for Centralised and decentralised EU procedures, national competent authorities for Mutual Recognition and Decentralised Procedures, and the FDA for US INDs, NDAs, BLAs and 510(k) submissions. Each regulator sets specific regulatory requirements for the submission language and the Certificate of Accuracy or Certificate of Translation evidence that accompanies the file.

RegulatorJurisdictionSubmission languageTranslation evidence required
MHRAUKEnglishCoT on translated source documents filed in TMF
EMA (Centralised Procedure)EU/EEAEnglish dossier; product information in 24 EU/EEA languages at Day 215CoT per language; QRD-conformant files
National CA / MRP / DCPEU member statesRMS and CMS languagesCoT per language
FDAUSAEnglishCertificate of Accuracy on all non-English source documents in IND/NDA/BLA/510(k)

How does regulatory translation differ from general medical translation?

Regulatory translation is governed by submission templates, controlled vocabularies and a Certificate of Translation, whereas medical translation covers clinical content without the submission-template or CoT obligation. Regulatory work binds the linguist to EMA QRD segments, eCTD module 1 regional specifications, MedDRA Preferred Terms and EDQM Standard Terms. For the distinction between technical, certified, sworn and notarised services, see What Is a Technical Translation Service?

Which regulatory documents do UK translation services translate for life-sciences submissions?

UK regulatory translation services cover CTD/eCTD modules, clinical trial protocols, informed consent forms, SmPCs, PILs, IFUs, CMC quality content, pharmacovigilance safety reports, labelling, promotional materials and health-authority correspondence — every category of documents requiring translation for MHRA, EMA or FDA review.

Document categoryExample documentsTypical translation scope
CTD / eCTD Module 1Cover letter, application form, product information, labellingTranslated per target market language
CTD / eCTD Modules 2–5Quality, nonclinical, clinical summariesEnglish; target-language summaries for national procedures
Clinical trial documentsProtocols, IBs, ICFs, PIS, CRFs, patient diariesFull translation + back-translation on patient-facing items
Product informationSmPC, PIL, IFU, labellingLocalised against EMA QRD templates; MedDRA and EDQM applied
PharmacovigilancePSUR, DSUR, RMP, SUSAR, DHCP lettersTranslated for multilingual market distribution
CorrespondenceDay-120/180 responses, variation applicationsRush TEP with pre-cleared linguist pool

Which CTD and eCTD modules require translation?

Module 1 regional administrative content requires translation into each target market language, while Modules 2–5 quality, nonclinical and clinical summaries remain in English, with target-language summaries where national procedures demand them. CTD eCTD translation scope is agreed at project scoping against the submission plan.

How are clinical trial documents translated for MHRA and HRA submissions?

Clinical trial protocols, investigator brochures, informed consent forms, participant information sheets, case report forms and patient diaries are translated into the trial participant's native language with back-translation, reconciliation and REC-accepted certification. Workflow for consent documents is covered in detail on Informed Consent Form Translation Services UK, including HRA Research Ethics Committee acceptance.

How are SmPCs, PILs and IFUs localised against EMA QRD templates?

Summaries of Product Characteristics, Patient Information Leaflets and medical device Instructions for Use are localised against EMA QRD templates and MedDRA terminology, with layout preserved for leaflet print and back-translation supplied for MHRA and notified-body audits. The QRD mechanics for pharmaceutical product information are already explained on Medical Translation Services London. For device labelling that overlaps with engineering content, see Technical Translation Services London. Medical device IFU translation under EU MDR and IVDR covers every EU/EEA market language, aligned to EDQM Standard Terms.

Which safety and pharmacovigilance documents need translation?

Pharmacovigilance translation covers Periodic Safety Update Reports (PSURs), Development Safety Update Reports (DSURs), Risk Management Plans, suspected unexpected serious adverse reaction (SUSAR) reports and Dear Healthcare Professional Letters when distributed across multilingual markets. Sequential transcription-plus-translation workflows handle clinician interview content for regulatory submissions; see Medical transcription services London.

Why is specialist translation critical for regulatory submissions in the UK and EU?

Specialist regulatory translation protects submission acceptance, patient safety and market timelines: a mistranslated SmPC heading, a non-compliant QRD annex or a missing Certificate of Translation can trigger a Day-120 EMA question, an MHRA inspection finding or outright dossier rejection, delaying launch by months. The cost of translation errors in a regulatory context runs well beyond re-translation fees.

The patient-safety and compliance consequences are set out further on Why Accurate Document Translation Is Important.

What happens when a regulatory submission is rejected due to translation errors?

Rejected submissions trigger a resubmission cycle that costs 6–12 weeks on the EMA clock, plus legal fees for Day-120/180 responses, re-translation and re-certification charges, and lost first-mover revenue in the target market. Regulatory agencies log the deficiency against the sponsor's file, affecting future review.

How do translation errors affect patient safety in product information?

Dosing errors, mistranslated contraindications and ambiguous warnings in Patient Information Leaflets have caused hospitalisations and product recalls, which is why MHRA and EMA require back-translation and linguistic validation on patient-facing content. Patient safety is the direct test applied by the EMA QRD review process.

How do UK translation providers ensure accuracy and regulatory compliance?

UK providers ensure accuracy through an ISO 17100 translate-edit-proofread (TEP) workflow, domain-credentialed subject matter experts, controlled terminology against MedDRA and EDQM, back-translation and reconciliation for patient-facing content, and a Certificate of Translation issued with every regulatory deliverable. Quality assurance runs at every stage of the translation process.

What does the ISO 17100 TEP workflow include step by step?

The TEP translation workflow runs in four stages:

  1. A native-target translator with life-sciences credentials drafts the target text at 1,500–2,000 finished words per day.
  2. An independent reviser performs a bilingual check against the source and the termbase.
  3. A project manager runs QA against the brief, QRD templates and client style guide.
  4. A certified linguist signs the Certificate of Translation before delivery and TMF filing.

When is back-translation and linguistic validation required?

Back-translation and linguistic validation are required for informed consent forms, patient-reported outcome measures, Clinical Outcome Assessments and PILs, following ISPOR Principles of Good Practice. The linguistic validation sequence is forward translation, reconciliation, back-translation and cognitive debriefing, proving conceptual equivalence to the English source.

What is a Certificate of Translation (CoT) and when is it mandatory?

A Certificate of Translation is a signed statement from the language service provider affirming the translation is a complete and accurate rendering of the source. For regulatory documents filed in a Trial Master File, 100% of translated content carries a CoT, with narrow exceptions for large documents where only a defined section is relevant to the submission. Certificate of Translation TMF rules are the baseline for inspection readiness.

What are the exceptions to the 100% CoT rule for TMF documents?

Exceptions apply when only a defined section of a large source document is relevant to the submission — for example an extract from a published study or a labelled page of a manufacturing SOP. The translated extract still carries a CoT scoped to that section, with the untranslated remainder clearly identified.

How are 'untranslatables' in English Product Information handled?

'Untranslatables' are flagged against an EMA-aligned untranslatables register and either retained in English, transliterated or handled per the QRD annex, with every decision logged for the regulator. The categories covered:

CategoryExampleHandling
Invented product nameBrand nameRetained in English, transliterated for non-Latin scripts
QRD-locked legal phrasesStandard SmPC boilerplateTranslated using QRD annex equivalent
EDQM Standard TermsDosage form, route of administrationMapped to EDQM target-language term
Specific indication wordingApproved indication statementTranslated per CHMP opinion wording
MedDRA Preferred TermsAdverse event termVersion-locked MedDRA target-language term

Which quality standards and certifications should a UK regulatory translation provider hold?

A UK regulatory translation provider should hold ISO 17100 for translation processes, ISO 27001 for information security, ISO 9001 for quality management and ISO 4043 for interpreting booths, with linguists credentialed by CIOL (MCIL) or ITI (MITI) and documented GxP familiarity. ISO 18587 governs machine translation post-editing where that service applies.

StandardScopeRelevance to regulatory submissions
ISO 17100Translation processes, TEP, linguist qualificationsBaseline for ISO 17100 certified translation on all dossiers
ISO 27001Information security management systemProtects pre-submission data and clinical records
ISO 9001Quality management systemCorrective-action procedures and audit trail
ISO 4043Interpreting booth standardApplies to on-site inspection interpreting

What does ISO 17100 certification actually require?

ISO 17100 requires documented translator qualifications, a mandatory bilingual revision step by a second linguist, project management traceability, client-brief handling, terminology management and corrective-action procedures — all auditable by the certification body. Linguist credentials verified under this standard include CIOL (MCIL) or ITI (MITI) registration plus a life-sciences degree or equivalent working experience. More on translator qualifications: What Qualifications Should a Technical Translator Have?

Why is ISO 27001 relevant to regulatory submission translation?

ISO 27001 governs the information-security management system that protects pre-submission dossiers, clinical trial data and patient-identifiable content from leak or loss during the translation workflow. EMA and MHRA inspectors expect this alongside UK GDPR compliance.

How do translation providers protect confidential regulatory documents and preserve confidentiality?

Providers protect regulatory documents through ISO 27001-governed encrypted file transfer, UK GDPR and NHS DSPT-aligned processing, signed NDAs with every linguist, role-based access controls in the translation management system, and UK or EU data residency with no third-country processing without client authorisation. Caldicott Principles and UK GDPR Article 9 obligations apply across the chain. The confidentiality controls:

How can terminology and document versions stay consistent across languages?

Consistency is maintained by a central translation memory, a client-specific termbase aligned to MedDRA and EDQM, controlled QRD segments, and a translation management system that version-locks every segment to the eCTD baseline. Translation memory systems reuse approved translations across lifecycle variations and renewals, protecting translation accuracy and regulatory consistency. Computer-assisted translation tools support but never replace the human linguist on submission-grade content.

How are MedDRA and EDQM Standard Terms applied in the termbase?

MedDRA Preferred Terms are applied for adverse-event coding, EDQM Standard Terms for pharmaceutical dosage forms and routes of administration, and both are version-locked in the termbase so the linguist cannot deviate without project-manager approval. Termbase governance sits with the regulatory translation team.

How are lifecycle variations and renewals kept aligned with the original submission?

Lifecycle variations and renewals are translated against the original approved TM so every change is diffed, tracked and traceable to the baseline submission, satisfying EMA Type IA/IB variation requirements. Translation memory diffs are archived with the TMF filing.

How long does regulatory submission translation take, and what affects the cost in the UK?

A standard regulatory submission translation takes 2–10 working days per 10,000 words depending on language pair and QA depth, priced from £30 per page under ISO 17100 with a 15–40% subject-matter uplift for pharmaceutical, clinical and medical-device content. Standard turnaround is 2–3 working days, with a 30–50% rush surcharge for same-day or weekend delivery. The 24-language EMA product-information pack runs 15–20 working days.

Document typeTypical volumeTurnaroundPrice indication (GBP)
Short regulatory correspondence<1,000 wordsSame-day in London before 11:00 GMT£0.10–£0.20 per word + rush
Clinical trial protocol10,000–30,000 words5–10 working daysFrom £0.12 per word, uplift applied
SmPC + PIL pack (per language)5,000–8,000 words3–5 working daysFrom £30 per page
Medical device IFU5,000–15,000 words5–8 working days per languageFrom £0.14 per word
24-language CP product informationPer language ×2415–20 working daysFramework agreement pricing

The 15–40% uplift for specialised domains is explained further on How Much Does It Cost to Translate a Document in the UK?

What drives per-word and per-project pricing for regulatory content?

Pricing is driven by language pair, document type, subject-matter specialisation, back-translation requirement, format complexity, turnaround and total volume. Framework agreements and retainers lower unit cost for recurring regulatory content.

How are rush and Day-120 response translations handled?

Rush translations for Day-120 or Day-180 EMA responses are handled through a dedicated project manager, pre-cleared linguist pool and parallel TEP tracks. Same-day turnaround is available on urgent updates under 1,000 words placed in London before 11:00 GMT, with the 30–50% rush surcharge applied.

What commercial terms suit framework agreements and retainers?

Framework agreements and retainers suit sponsors with recurring submission volume:

Do regulatory submissions need human translation, or can machine translation be used?

Regulatory submissions to the MHRA, EMA and FDA require human translation under ISO 17100. Machine translation with full post-editing to ISO 18587 is accepted only for internal reference, bulk literature triage or non-submission reading copies — never for SmPCs, PILs, ICFs or any patient-facing content that enters the dossier.

Where does MT with full post-editing fit in a life-sciences workflow?

MT with full post-editing fits literature review for horizon scanning, internal regulatory intelligence, large-volume CMC source documents destined for reference only, and first-pass drafts that still enter the full TEP workflow before certification. Submission-grade content always runs the human TEP workflow.

Which languages do UK regulatory translation services support for Centralised Procedure and national dossiers?

UK regulatory translation services support 150+ languages, including all 24 official EU/EEA languages required for Centralised Procedure product information at Day 215, plus Russian, Arabic, Mandarin, Japanese and Korean for FDA, PMDA, NMPA and GCC market extensions. Life sciences localization covers each target language with native linguists.

How do Centralised Procedure translation obligations differ from national procedures?

Centralised Procedure marketing authorisations require product information in all 24 EU/EEA languages (plus Icelandic and Norwegian) at Day 215 of the procedure, while national procedures and Mutual Recognition/Decentralised Procedures require only the Reference Member State and Concerned Member State languages.

ProcedureLanguage scopeTiming
Centralised Procedure (EMA)24 EU/EEA languages + Icelandic + NorwegianDay 215 following CHMP opinion
Mutual Recognition / DecentralisedRMS + CMS languages onlyPer procedure timetable
National (single member state)Single national languagePer national CA requirement
MHRA (UK)EnglishSubmission date
FDA (USA)English with CoA on non-English sourcesSubmission date

How should a UK sponsor or CRO choose a regulatory translation provider and translation partner?

Choose a UK regulatory translation partner by verifying ISO 17100, ISO 27001 and ISO 9001 certification, auditing linguist CVs for life-sciences credentials, requesting a sample Certificate of Translation, confirming TMF-ready file handling, testing termbase governance on a pilot ICF, and benchmarking per-word GBP pricing against framework-agreement discounts. Procurement steps:

  1. Confirm ISO 17100, ISO 27001 and ISO 9001 certificates with scope statements.
  2. Review linguist CVs for CIOL/ITI credentials and regulatory experience.
  3. Request a sample CoT and anonymised TMF-filed document.
  4. Run a paid pilot on an ICF or SmPC segment to test terminology governance.
  5. Benchmark per-word GBP pricing across three providers.
  6. Negotiate framework agreement, SLAs, data residency and NDA terms.

In-house CRO linguist versus ISO 17100 agency responsibility matrix:

ResponsibilityIn-house CRO linguistISO 17100 agency
Four-eyes TEPNot guaranteedMandatory second-linguist revision
Certificate of TranslationInternal sign-off onlySigned CoT per document for TMF
Linguist CV traceabilityHR fileAudited CV pack per project
Termbase governanceAd hocVersion-locked, PM-controlled
Audit outcome riskFinding risk at MHRA GCP inspectionInspection-ready evidence pack

What should an RFQ for regulatory submission translation include?

An RFQ should include document inventory with word counts, source and target languages, regulator and procedure, required certifications, file formats, deadline per Day milestone, and security requirements. Specify CoT, back-translation, linguistic validation, UK data residency and NDA scope on each line.

What questions reveal a provider's real regulatory experience and regulatory expertise?

Ask for anonymised examples of submitted dossiers, the ratio of in-house to freelance linguists per language pair, how 'untranslatables' are logged, how MedDRA versions are updated in the termbase, and how a Day-120 clock-stop response was handled on a prior project. The answers evidence genuine regulatory process maturity.

How are translated regulatory documents handled in the Trial Master File for inspection readiness?

Translated documents enter the Trial Master File alongside the source, each with a Certificate of Translation, linguist CV reference, version number and TM revision ID, filed under TMF Reference Model zones so MHRA GCP inspectors and sponsor QA can reconstruct every translation decision. Inspection-readiness checklist:

Which TMF zones hold translated regulatory and clinical documents?

Translated ICFs and PIS sit under TMF Reference Model Zone 5 (site management), translated protocols and investigator brochures under Zone 2 (central trial documents), and translated regulatory correspondence under Zone 4 (regulatory). Each filing pairs the English source with the translation and the CoT.

What inspection findings are triggered by non-compliant translations?

Common inspection findings:

Each is raised as a critical or major finding in the inspection report.

How our regulatory submission translation process works end to end

Intake and scoping. Document inventory, word counts, target languages, procedure (MHRA, EMA CP, national, FDA), deadlines per Day milestone.

Confidentiality setup. NDA signature, secure portal credentials, UK/EU data residency confirmed.

Linguist assignment. CIOL/ITI-credentialed subject matter experts matched to therapeutic area and target language.

Termbase and TM preparation. MedDRA and EDQM alignment, QRD segments pre-loaded, client style guide applied.

Translation. Native-target linguist drafts at 1,500–2,000 finished words per day.

Revision. Independent second linguist performs the bilingual TEP check.

Back-translation and reconciliation. Applied to ICFs, PILs, PROs and COAs per ISPOR Principles of Good Practice.

Quality assurance. Project manager runs QA against brief, QRD and termbase; final proofread.

Certification. Signed Certificate of Translation issued per document.

Delivery and TMF handover. Files delivered via secure portal with linguist CV pack, TM diff and version log for TMF filing.

Pricing starts from £30 per page under ISO 17100, or £0.10–£0.20 per word, with a 15–40% uplift for pharmaceutical, clinical and medical-device content. Standard documents fall in the £80–£150 range; framework agreements lower per-word rates on recurring volume.

Frequently asked questions

Which translation services are accredited in the UK?

In the UK, accredited translation services are those operating under recognised quality standards such as ISO 17100 (translation services) and ISO 9001 (quality management). Providers may also hold membership of the Association of Translation Companies (ATC) or employ translators who are members of the Chartered Institute of Linguists (CIOL) or the Institute of Translation and Interpreting (ITI). For regulated sectors — life sciences, legal, financial services — procurement teams should also look for GDPR-compliant data handling, NDA/DPA frameworks, and demonstrable sector-specific experience rather than accreditation alone.

How much do translation services cost in the UK?

Professional translation in the UK is typically quoted per source word, with rates commonly ranging from £0.10 to £0.25 per word depending on language pair, subject matter and service level. Highly technical or regulated content — pharmaceutical, legal, financial — commands the higher end of that range. Volume pricing, framework agreements and retainers reduce the per-word rate for organisations with recurring needs. Project-based pricing is also available for complex deliverables such as regulatory submission packages, where word count is only one variable alongside formatting, review rounds and certification requirements.

What translation services are available for clinical trials?

For clinical trials, specialist translation services cover Investigator Brochures (IBs), Clinical Study Reports (CSRs), Informed Consent Forms (ICFs), Patient-Reported Outcomes (PROs), Case Report Forms (CRFs), protocol documents and regulatory correspondence. Providers working to ISO 17100 apply a translate-edit-proofread (TEP) workflow with subject-matter-expert translators, controlled termbases and translation memory to ensure consistency across document versions and sites. Integration with eTMF systems and issuance of a Certificate of Translation (CoT) are standard requirements for GCP-compliant trial documentation.

What is the difference between an official translation and a certified translation?

A certified translation is one accompanied by a signed statement — a Certificate of Translation (CoT) — in which the translation provider attests that the translation is accurate and complete to the best of their knowledge. An 'official translation' is a broader, context-dependent term: in some jurisdictions it refers to translations produced by a court-sworn or government-authorised translator, while in the UK it most often simply means a certified translation accepted by a regulatory body, court or public authority. For regulatory submissions (MHRA, EMA), a provider's CoT on headed paper is typically sufficient; sworn translation requirements apply mainly for certain foreign-jurisdiction documents.

When is translation actually required for a regulatory submission in the UK/EU?

Translation requirements for regulatory submissions depend on the territory, procedure and document type. Under the EMA centralised procedure, the Product Information (SmPC, labelling, PIL) must be translated into all 24 official EU languages. For MHRA submissions post-Brexit, English is the working language, but supporting documents originating in another language must be accompanied by a certified English translation. In decentralised and mutual-recognition procedures, each member state requires its own language version of the Product Information. Clinical documents within a CTD dossier are generally acceptable in English, but patient-facing and label content must meet local language requirements.

What counts as an officially translated document for a TMF, and when is a Certificate of Translation (CoT) needed?

For Trial Master File (TMF) purposes, a translated document is considered 'official' when it is accompanied by a Certificate of Translation (CoT) on the provider's headed paper, signed by a qualified translator or authorised representative, attesting accuracy and completeness. A CoT is required whenever a source document is not in the language of the competent authority or ethics committee reviewing it — for example, a foreign-language ethics approval, an IB originating in a non-English language, or ICFs translated for local sites. The ICH E6(R2) GCP guideline and EU CTR (536/2014) both reinforce the principle that essential documents must be legible and verified for accuracy.

What are 'untranslatables' in regulatory translation and how do you handle them?

In regulatory translation, 'untranslatables' are terms, abbreviations or proprietary names that have no direct equivalent in the target language and must be carried over unchanged — examples include INN (International Nonproprietary Names), CAS numbers, instrument trade names and established acronyms such as GCP or ICH. Handling them correctly requires a managed termbase that flags each term as 'do not translate', ensuring translators and the TMS apply the source-language form consistently across all documents. A regulatory translation provider will also annotate these terms in the CoT or translator's notes where a competent authority may need explicit explanation of why a term remains untranslated.

How do you handle translated documents in a Trial Master File (TMF)?

Translated documents in a TMF should be stored alongside their source originals, with the Certificate of Translation (CoT) filed as a companion document in the same TMF zone and artifact. The DIA TMF Reference Model (v3.x) provides guidance on artifact placement; translated ICFs, ethics approvals and regulatory correspondence each have defined zones. Version control is critical: if the source document is amended, the translation must be updated and a new CoT issued, with both superseded and current versions retained. Many sponsors use eTMF platforms — Veeva Vault, Oracle, etc. — that support document relationships and version linking to maintain a clean audit trail.

Are there exceptions to the 100% official translation rule for regulatory documents?

Yes, competent authorities and sponsors sometimes accept partial translation or translation summaries for lower-risk or supporting documents. For example, literature references cited in a CTD dossier may be acceptable with an abstract translation or a certified summary rather than a full translation. Internal working documents and sponsor-to-CRO correspondence are generally exempt. Some ethics committees accept bilingual documents for site-level materials. However, patient-facing content (ICFs, PILs, patient diaries), labelling and any document that forms part of the formal regulatory dossier reviewed by the authority must be fully translated with a CoT — exceptions do not apply to these categories.

What does 'certified translation' mean?

A certified translation is a translation accompanied by a written statement — the Certificate of Translation — in which the translator or translation company declares that the translation is a true and accurate rendering of the source document. In the UK, there is no statutory requirement for a government-licensed translator to certify; the provider's signed declaration on headed paper is the accepted standard for courts, the Home Office, HMRC, regulatory bodies and most public authorities. The certificate typically includes the translator's name and qualifications, the language pair, the date, and a description of the source document.

What is an ISO 17100 certificate?

ISO 17100 is the international standard that specifies requirements for the processes, resources and other aspects necessary for the delivery of a quality translation service. Certification means an accredited third-party body (such as BSI or SGS) has audited the provider and confirmed it meets requirements covering translator qualifications, the translate-edit-proofread (TEP) workflow, project management, revision processes and data handling. For procurement teams in regulated industries, ISO 17100 certification provides an auditable baseline of quality assurance — it is increasingly a minimum requirement in framework agreements and public-sector tenders for translation services.

Who can certify a translation in the UK?

In the UK, any professional translation company or qualified translator can certify a translation by providing a signed Certificate of Translation on headed paper — there is no statutory requirement for a court-sworn or government-authorised translator as exists in some civil-law countries. Members of the Chartered Institute of Linguists (CIOL) or the Institute of Translation and Interpreting (ITI) are widely recognised as qualified certifiers. For most regulatory, legal and public-authority purposes, a certification from a reputable language service provider operating under ISO 17100 is fully acceptable. Notarisation is only required when the receiving authority or jurisdiction explicitly demands it.

Can I certify my own translation?

Generally, no — self-certification of your own translation is not accepted by UK courts, the Home Office, HMRC, regulatory bodies or most public authorities. The certifier must be independent of the requester, and must be a qualified translator or professional translation company able to attest to accuracy and completeness. A bilingual individual who is not a professional translator cannot certify their own work for official purposes. For organisations submitting regulatory dossiers or legal documents, a translation provider issuing a formal Certificate of Translation on headed paper — ideally operating under ISO 17100 — is the required route.

Related