Regulatory Submission Translation

What does regulatory submission translation mean?

Regulatory submission translation is the certified conversion of a pharmaceutical, medical device or clinical trial dossier — including CTD/eCTD modules, IFUs, SmPCs, informed consent forms and labelling — into target languages under an ISO 17100 workflow, with a signed certificate of accuracy accepted by MHRA, EMA and FDA.

Why is accurate translation crucial for regulatory submissions?

Accurate translation protects patient safety, prevents regulatory queries and rejection, and preserves the submission timeline: a single mistranslated dosage, indication or contraindication in an SmPC or informed consent form can trigger a clock-stop, an authority query, or refusal to approve the product.

What are the different types of regulatory submission translations?

There are six regulatory submission translation types the UK market commissions most often: CTD/eCTD modules, clinical trial documents, medical device technical files under EU MDR/IVDR, product information (SmPC, PIL, labelling), safety and pharmacovigilance content, and regulatory correspondence including query responses.

What regulatory bodies and regions require translated submissions?

MHRA, EMA, FDA and national agencies across the EU, Switzerland, the Gulf and Asia each set their own translation requirements: EMA centralised submissions require all EU official languages for product information, MHRA requires English for the UK, and FDA requires English with translated reference documents.

What are the key challenges in regulatory submission translation?

The key challenges in regulatory submission translation are five: dense regulatory terminology, evolving authority requirements, tight submission timelines, high dossier volumes with strict consistency demands, and the audit-trail obligations that GCP and pharmacovigilance inspectors expect.

How do we deliver regulatory submission translation in the UK?

We deliver regulatory submission translation across 150+ languages at £0.10–£0.20 per word, in a 2–3 working day baseline turnaround, under an ISO 17100 workflow with subject-matter-expert linguists, second-linguist review and a signed certificate of accuracy on company letterhead.

Regulatory submission translation converts pharmaceutical, medical device and clinical trial dossiers into target languages under a controlled ISO 17100 workflow, priced £0.10–£0.20 per word and delivered in 2–3 working days across 150+ languages from our London office.

What does regulatory submission translation mean?

Regulatory submission translation is the certified conversion of a pharmaceutical, medical device or clinical trial dossier — including CTD/eCTD modules, IFUs, SmPCs, informed consent forms and labelling — into target languages under an ISO 17100 workflow, with a signed certificate of accuracy accepted by MHRA, EMA and FDA.

The service sits at the intersection of regulatory affairs, life sciences and linguistic quality management. It combines subject-matter expertise, terminology governance and a documented audit trail. Our Technical Translation page defines the ISO 17100 baseline we apply here.

What is a regulatory submission in pharmaceutical and medical device contexts?

A regulatory submission is the structured dossier a company files with a regulatory authority — MHRA, EMA, FDA or a national agency — to obtain, maintain or vary market authorisation for a drug, biologic or medical device. Common submission package formats include:

How does translation fit into the regulatory submission process?

Translation sits inside the submission timeline at three points: source-content preparation, target-language authoring under terminology governance, and post-submission regulatory queries requiring translated responses within tight deadlines. Each point maps to a distinct QA depth and a distinct project management milestone in the submission project plan.

Why is accurate translation crucial for regulatory submissions?

Accurate translation protects patient safety, prevents regulatory queries and preserves the submission timeline. A single mistranslated dosage, indication or contraindication in an SmPC or informed consent form can trigger a clock-stop, an authority query, or refusal to approve the product. Regulatory compliance depends on linguistic precision at every module boundary. Every authority — whether the MHRA requiring certified English translations of all foreign-language source documents, the EMA mandating product information in all EU official languages plus Icelandic and Norwegian, or the FDA requiring a certified English translation and translator statement — applies a zero-tolerance standard to linguistic error. The translation layer of a dossier is therefore as inspection-critical as the clinical or chemistry data it accompanies.

What happens when a regulatory submission translation contains errors?

Errors in regulatory content produce three cascading outcomes:

1. Regulatory queries that stop the review clock — authorities issue formal questions that suspend the assessment timeline until a corrected translation is submitted.
2. Rejection of the submission package — where mistranslations affect safety-critical sections such as dosing, contraindications or device instructions for use, the receiving authority may refuse the dossier outright.
3. Post-approval patient safety risk — labelling or IFU wording that reaches the market in an inaccurate form is directly traceable to the translation step and creates both regulatory and product-liability exposure.

Terminology governance is the primary defence against all three outcomes. Establishing controlled product, compound, clinical, CMC, safety and regulatory terminology before multilingual production begins ensures that the same precise language is applied consistently across every document and every target language in a programme — whether that programme covers five markets or twenty.

Does regulatory submission translation guarantee authority acceptance or product approval?

Regulatory submission translation does not guarantee product approval; it guarantees the linguistic layer of the dossier is compliant, accurate and inspection-ready. A complete, ISO 17100-aligned workflow with second-linguist review and a signed certificate of accuracy removes translation defects as a grounds for query or rejection, so the regulatory review can focus on scientific merit. Approval remains the receiving authority's decision on clinical, non-clinical and quality data — but a precisely translated dossier eliminates one of the most avoidable causes of delay.

Get a quote

What are the different types of regulatory submission translations?

There are six regulatory submission translation types the UK market commissions most often: CTD/eCTD modules, clinical trial documents, medical device technical files under EU MDR/IVDR, product information (SmPC, PIL, labelling), safety and pharmacovigilance content, and regulatory correspondence including query responses.

Document type	QA workflow depth	Typical authority
SmPC, PIL, outer/inner labelling	Linguistic validation + regulatory review	EMA, MHRA, national agencies
Informed consent forms and PIS	Forward + back translation + reconciliation	Ethics committees, sponsors
CTD/eCTD Module 1	ISO 17100 + terminology lock	EMA, MHRA, national
CTD/eCTD Modules 2–5	ISO 17100 second-linguist review	Where authority mandates
Medical device IFUs and labelling	Linguistic validation + regulatory review	EU Notified Bodies, MHRA
DSURs, PSURs, RMPs	Second-linguist review, expedited	EMA, MHRA, FDA
Investigator brochures, CSRs	ISO 17100 SME translation	EMA, MHRA, FDA
Regulatory query responses	Expedited SME translation	Receiving regulatory bodies

How are CTD and eCTD modules translated for EMA and national submissions?

CTD and eCTD modules are translated module-by-module. Module 1 — administrative and product information — requires national-language versions of SmPC, PIL and labelling. Modules 2–5 are translated only where the receiving authority mandates it. A translation memory is locked at kickoff to keep terminology identical across every module.

What clinical trial documents require certified translation?

Clinical trial translation covers seven core document types: informed consent forms, patient information leaflets, investigator brochures, clinical study reports, protocol synopses, ethics committee correspondence and site-facing materials. Each carries linguistic validation requirements set by the sponsor or regulatory body. See our Clinical Trial Translation Services page for study-specific workflows.

How are medical device IFUs, technical files and IVDR documents handled?

Medical device translation under EU MDR and IVDR covers five document families: instructions for use, labelling, declarations of conformity, technical files and post-market surveillance reports. These are required in every official language of every EU member state where the device is placed on the market. UK Notified Bodies apply the same evidentiary standard for UKCA-marked devices.

How are product information, SmPCs and labelling translated?

SmPC, PIL and labelling translation follows EMA QRD templates and national terminology. Each target-language version is reviewed against the English source and against the receiving authority's linguistic review requirements before submission. Product information carries the highest QA depth because it is patient-facing and legally binding.

How are safety, pharmacovigilance and regulatory query responses translated?

Safety and pharmacovigilance content — DSURs, PSURs, risk management plans and expedited safety reports — is translated under tight deadlines with expedited second-linguist review. Regulatory query responses are turned around inside the authority's clock, often within days rather than weeks. For adjacent study-level materials, see our Scientific Translation Services.

What regulatory bodies and regions require translated submissions?

MHRA, EMA, FDA and national regulatory bodies across the EU, Switzerland, the Gulf and Asia each set their own translation requirements. EMA centralised submissions require all EU official languages for product information, MHRA requires English for the UK, and FDA requires English with translated reference documents.

Authority	Filing language	Certified translation requirement
MHRA (UK)	English	Signed certificate of accuracy for any foreign-language source document
UK Notified Bodies	English	Certified translation of foreign technical files and clinical evaluations
HM Courts	English	Signed certificate of accuracy; raw AI output rejected
HM Passport Office	English	Signed certificate of accuracy on company letterhead
EMA (EU centralised)	English source	Product information in all EU official languages + Icelandic and Norwegian
FDA (US)	English only	Certified English translation + translator's statement
Swissmedic, Health Canada, TGA, PMDA, NMPA, SFDA, MOH UAE	National	National translation rules for product information and labelling

How do MHRA submissions handle translation post-Brexit?

MHRA submissions are filed in English. Source documents in other languages — foreign clinical study reports, non-UK manufacturing records, overseas GMP certificates — must be accompanied by a certified English translation with a signed certificate of accuracy. Raw machine translation is rejected because no named human translator stands behind the output.

How does the EMA centralised procedure manage linguistic review?

The EMA centralised procedure includes a linguistic review window in which product information is checked in all EU official languages plus Icelandic and Norwegian. Missed deadlines in this window delay the Commission Decision, not just the CHMP opinion. The European Medicines Agency treats missed linguistic milestones as a procedural risk to the whole EU submission.

How does the FDA treat non-English source documents?

The Food and Drug Administration accepts submissions in English and requires certified English translations of any foreign-language source document, together with a translator's statement of qualifications and accuracy. FDA submission translation therefore focuses on foreign clinical, manufacturing and reference material rather than the primary filing text.

Which other regulatory authorities require translated dossiers?

Global regulatory filings extend beyond MHRA, EMA and FDA. Swissmedic, Health Canada, TGA Australia, PMDA Japan, NMPA China and Gulf regulatory bodies including SFDA Saudi Arabia and MOH UAE each publish national translation requirements covering product information, labelling and clinical documentation. A single global regulatory strategy typically involves 10–25 target languages.

What are the key challenges in regulatory submission translation?

The key challenges in regulatory submission translation are five:

1. Dense regulatory terminology across therapy areas.
2. Evolving regulatory requirements and authority template changes.
3. Tight submission timelines against the authority's clock.
4. High dossier volumes with strict consistency demands.
5. Audit-trail obligations that GCP and pharmacovigilance inspectors expect.

How is regulatory terminology managed across a multilingual submission?

Regulatory terminology is managed through a controlled glossary, a translation memory locked at project kickoff, and terminology management inside a translation management system. Every module of the dossier uses the same target-language term for the same regulatory concept, so reviewers see one consistent lexicon from Module 1 to Module 5.

How do evolving regulations affect translation workflows?

Evolving regulations force translation workflows to version-control templates and refresh terminology at each regulatory revision. Four current drivers are:

How are tight submission timelines and large dossier volumes handled?

Tight timelines and large volumes are handled through parallel linguist teams working under a single lead reviewer, translation memory leverage across modules, and a submission project plan that maps translation milestones to the authority's clock. Project management sits at the centre of every multilingual regulatory dossier.

How do we deliver regulatory submission translation services in the UK?

We deliver regulatory submission translation across 150+ languages at £0.10–£0.20 per word, in a 2–3 working day baseline turnaround, under an ISO 17100 workflow with subject-matter-expert linguists, second-linguist review and a signed certificate of accuracy on company letterhead.

How do we ensure the quality of regulatory submission translations under ISO 17100 compliance?

Quality is ensured through a four-stage ISO 17100 workflow:

1. SME linguist assignment by therapy area.
2. Translation memory and terminology governance.
3. Mandatory second-linguist review.
4. Signed certificate of accuracy issued on company letterhead at delivery.

What is the ISO 17100 workflow for regulatory content?

ISO 17100 mandates translation by a qualified linguist, revision by a second independent linguist, and a documented project management record. This is the minimum standard we apply to every regulatory submission translation, regardless of length. The standard is published by the International Organization for Standardization and sits alongside the ISO 9000 quality management family.

How does linguistic validation work for clinical trial documents?

Linguistic validation for clinical trial documents adds four steps to standard translation: forward translation, back translation, reconciliation and cognitive debriefing. Patient-facing content such as informed consent forms and PRO measures the same construct across languages. Sponsors use this workflow to validate translated content before ethics committee submission.

How is terminology managed across a multilingual regulatory submission?

Terminology is managed through a project glossary, a translation memory locked at kickoff, and a translation management system that surfaces the approved target-language term to every linguist on the project. Terminology management protects consistency across parallel workstreams and across dossier lifecycle updates.

What audit trail do we provide for GCP and pharmacovigilance inspectors?

Every project ships with four evidence sets:

This is the exact evidence a GCP or pharmacovigilance inspector expects to see on file.

What are the best practices for streamlining multilingual regulatory submissions?

The five best practices for streamlining multilingual regulatory submissions are: engage a translation partner at submission planning, build terminology before translation begins, lock templates to authority QRD standards, run QA depth matched to document risk tier, and integrate translation milestones into the submission timeline.

How should translation be planned inside the submission timeline?

Translation is planned backwards from the authority filing date. Linguistic validation windows for clinical documents, EMA linguistic review for product information, and buffer for regulatory queries are all sequenced against the submission clock. Skipping this planning step is the most common cause of missed EMA linguistic review deadlines.

When should terminology and reference materials be assembled?

Terminology and reference materials are assembled before the first word is translated. Sources include prior approved dossiers, EMA QRD templates, MedDRA and the sponsor's controlled glossary. A locked glossary at kickoff prevents rework at the second-linguist review stage.

How should QA depth be matched to document risk?

QA depth is matched to document risk: labelling, SmPC and informed consent forms receive linguistic validation and regulatory review, while internal reference documents receive standard ISO 17100 translation plus revision. Matching QA depth to risk tier controls cost without weakening the submission package.

Where is machine translation acceptable in a regulatory workflow?

Machine translation with human post-editing is acceptable for internal reference documents, prior-art scanning and translation of foreign-language source materials cited in a dossier, provided the final submission text is produced or validated by a qualified human linguist. Human review is the non-negotiable step.

Where is AI translation not acceptable for regulatory content?

Raw machine and AI output is not acceptable for submission-ready SmPCs, PILs, labelling, informed consent forms or any content filed with MHRA, EMA or FDA. None of these regulatory bodies recognise an unsigned automated declaration of accuracy. HM Courts and HM Passport Office apply the same rule to any translated evidence they receive.

How do translation memory and TMS reduce regulatory translation cost?

Translation memory and a translation management system reduce cost by locking approved sentences across modules and repeat versions. Lifecycle updates to an existing dossier are priced against the delta rather than the full document. This matters most for annual PSUR cycles and variation submissions.

Can anyone do a certified translation for regulatory submissions?

No — regulatory submission translation must be produced by a qualified translator working under an ISO 17100 workflow, with a signed certificate of accuracy. The UK has no sworn translator system; CIOL and ITI members and ISO 17100 agencies issue the accepted certification. See our Certified Translation pillar for the UK's certification model, and Medical Translation for the distinction between certified, notarised, sworn and apostilled translation.

Who is qualified to translate regulatory submissions in the UK?

Qualified regulatory linguists in the UK combine subject-matter expertise, professional body membership and evidence of prior regulatory work:

How do I qualify a pharmaceutical translation provider for regulatory submissions?

Qualify a translation partner on four factors:

1. ISO 17100 certification evidence.
2. Named-linguist SME assignment.
3. Documented terminology and translation memory process.
4. Inspector-ready audit trail covering translator qualifications, review stages and version control.

Generic pharmaceutical translation credentials are not enough for regulatory dossier translation. Where courts and evidence submissions are involved, see our Legal Translation page for HM Courts requirements.

What does a regulatory submission translation project look like end-to-end?

An end-to-end regulatory submission translation project runs through six structured stages, each logged, versioned and inspection-ready so the audit trail follows the dossier into any subsequent variation or renewal cycle.

1. Submission readiness review — the project team aligns submission type, target markets, languages, source document status, authority milestones and delivery specifications before any multilingual production begins. This stage identifies whether Module 1 alone requires translation to national languages or whether Modules 2–5 also fall within the receiving authority's scope.
2. Content and reference alignment — approved terminology, previous submissions, existing translations, current labelling, translation memory and other authoritative language assets are identified and consolidated so that nothing is created from scratch that already exists in a validated form.
3. Terminology governance — controlled product, compound, clinical, CMC, safety and regulatory terminology is established and locked before translation begins, ensuring consistent language across all documents and all target languages throughout the programme.
4. Specialised linguist assignment — qualified life sciences linguists are assigned according to language pair, document type and subject matter. Where timelines require it, parallel workstreams run simultaneously across document sets, compressing overall delivery without sacrificing accuracy.
5. Regulatory and linguistic review — a second qualified linguist reviews meaning, terminology, consistency, completeness and target-language quality. Client, affiliate, medical, scientific or in-country reviewers are integrated into this stage where the authority or the submission protocol requires it.
6. Formatting, technical preparation and submission-ready delivery — multilingual content is prepared for the required document environment, preserving tables, headings, references, numbering and all content relationships. Delivery is accompanied by a signed certificate of accuracy, ready for inclusion in the dossier.

Each of these stages is documented in an ISO 17100-aligned workflow, providing the process records that authorities and auditors expect to see when they examine how a multilingual dossier was produced. In a programme spanning fifteen or twenty languages, that coordination infrastructure is what keeps every language version consistent and on schedule.

How do we start a regulatory submission translation project with our London team?

Starting a regulatory submission translation project takes a single initial exchange. Send the source dossier, target languages, receiving authority and submission deadline to our London office and we return a fixed quote at £0.10–£0.20 per word, a project timeline against the 2–3 working day baseline, and a named project manager — all within one working day. For large dossiers or multi-market programmes, pricing and timelines are quoted individually to reflect the full scope. Urgent same-day or weekend delivery carries a 30–50% surcharge, which is always stated in writing before work begins.

Before multilingual production starts, we confirm in writing the languages required — drawn from our coverage of 150+ languages including all EU official languages — the certificate of accuracy wording, the document delivery format and any authority-specific requirements such as QRD template compliance for EMA product information or the translator statement required for FDA submissions. Nothing proceeds until every specification is agreed, so there are no surprises at the submission stage.

Our ISO 17100-aligned workflow applies from the first document to the last, with second-linguist review and full process documentation included as standard on every project, regardless of size. The signed certificate of accuracy is included at no extra cost and is worded to satisfy MHRA, EMA, FDA and other major authority requirements.

How do we contact Certified Translation Services UK?

Call +44 20 4569 1419 or visit Suite 544, Unit B, 63-66 Hatton Garden, London EC1N 8LE, Monday to Saturday 9:00–18:00, to commission a regulatory submission translation with a signed certificate of accuracy included at no extra cost. Our team is available to discuss submission scope, turnaround requirements and authority-specific formatting before you commit to a project.