- What the EMA Requires from Translated Pharmaceutical Documents
- Document Types That Require Translation for EU Registration
- Quality Control Requirements in Pharmaceutical Translation
- Preparing a Pharmaceutical Translation Project for EU Submission
- Pharmaceutical Translation for EU Registration with M21Global
- Related Services
- Frequently Asked Questions
Registering a medicinal product in Europe means producing accurate, consistent documentation in up to 24 languages. The EMA and national competent authorities scrutinise every linguistic version of the SmPC, the package leaflet, and the labelling. A terminology inconsistency between the reference English version and a target-language translation is not a minor issue. It is a non-conformity that can delay approval or trigger a variation procedure after authorisation.
What the EMA Requires from Translated Pharmaceutical Documents
Under the centralised procedure, when the European Commission grants a marketing authorisation (MA), the MA holder must make the Summary of Product Characteristics (SmPC), Package Leaflet (PL), and labelling available in all 24 official EU languages. Iceland, Liechtenstein, and Norway are included in the scope of the authorisation, which may add further languages depending on the target markets.
The EMA reviews translated documents for consistency against the approved reference text. Divergences in dosage instructions, contraindications, or storage conditions between language versions constitute submission errors. National competent authorities apply the same standard within their own procedures.
For the UK, the MHRA operates its own post-Brexit framework. Translations into English still require alignment with the approved licence wording, and any variation must be reflected consistently across all product documentation.
All translated documents must follow the current QRD (Quality Review of Documents) template issued by the EMA. This template defines section headings, order, and formatting requirements for each document type. A translation that does not conform to the applicable QRD template will be rejected regardless of linguistic accuracy.
Document Types That Require Translation for EU Registration
Not every module of the Common Technical Dossier (CTD) requires translation into every language. The key documents that typically require translation for each authorised market are:
- SmPC (Summary of Product Characteristics): The regulatory reference document. Any post-authorisation change to the SmPC in one language must be reflected in all versions. Translation requires independent review by a linguist with pharmaceutical expertise and terminological validation against the relevant EPAR product information.
- Package Leaflet (PL): Written for patients, but with direct safety implications. The EMA requires readability testing with actual users for each linguistic version. The translation must be written in plain language without sacrificing accuracy, and it must be capable of supporting that testing process.
- Labelling: Space is constrained and every word carries weight. Formatting conventions, permitted abbreviations, and character limits vary by language. The specific requirements for drug labelling translation go beyond text substitution and require careful typographic and regulatory review.
- Pre-clinical and clinical study reports (CTD modules 2-5): Submitted in English under the centralised procedure, but national procedures may require translation into the local language.
- Safety Data Sheets (SDS): Regulated under the CLP Regulation and REACH. Required in the language of each market where the product is placed.
Quality Control Requirements in Pharmaceutical Translation
Pharmaceutical translation is a regulated activity in practice, even where no specific legal certification is mandated. The EMA and national authorities expect MA holders to demonstrate that their translation process is auditable and that quality is verifiable.
ISO 17100:2015 is the internationally recognised standard for translation quality management. It mandates that every translation is performed by a qualified translator and reviewed by a separate, equally qualified linguist. This two-step process is the baseline for pharmaceutical document translation submitted to European regulators.
Controlled terminology management is equally critical. Translation memories and validated glossaries specific to each INN (International Non-proprietary Name) ensure consistency across the SmPC, the PL, and the labelling, and across future variations and line extensions. Without these tools, even a careful translator can introduce minor terminological drift that accumulates into a compliance problem over time.
For organisations managing multiple submissions across markets, the same quality principles apply to clinical trial protocol translation, where regulatory authorities require equivalent standards of accuracy and audit trail.
Preparing a Pharmaceutical Translation Project for EU Submission
The information provided to the translation provider before the project starts directly affects delivery time and revision cycles. For a regulatory submission, the following should be ready at project initiation:
- The approved or latest reference version of the source document in English
- The procedure type and current MA status (centralised, national, or mutual recognition)
- The applicable QRD template version
- Any previously approved translations for the same INN, or existing product glossaries
- Target language formatting requirements and any character or space constraints for labelling
With this information available from the outset, the translation provider can configure product-specific translation memories and controlled glossaries, which reduces review cycles and ensures consistency between document updates.
Pharmaceutical Translation for EU Registration with M21Global
M21Global has provided pharmaceutical translation for European regulatory submissions for over 20 years. For SmPC, package leaflet, and labelling projects, the Estratégica workflow applies three specialist linguists per project: a translator, an independent reviewer, and a QA reviewer, in full conformance with ISO 17100:2015 as certified by Bureau Veritas. This is the only appropriate workflow for documents at this level of regulatory risk.
Projects are managed by a dedicated project manager with a three-hour response commitment, using product-specific translation memories and validated terminology. M21Global operates across Portugal, Spain, France, Germany, Angola, and Brazil, covering the principal European and Lusophone registration languages.
Request a quote for your pharmaceutical translation project at m21global.com/en/services/pharmaceutical-translation.
Related Services
Request a free medical translation quote
- Request a free medical translation quote
- Medical Device Documentation Translation Mdr Compliance
- Translating Clinical Trial Protocols Regulatory Submission
- Drug Labeling Translation
Frequently Asked Questions
Does pharmaceutical translation for the EMA need to be certified?
There is no formal requirement for sworn or notarised translation under EMA procedures, but the translation process must be auditable and conform to a recognised quality standard. ISO 17100:2015 is the accepted benchmark, requiring independent review by a qualified linguist separate from the translator.
How many languages are required under the EMA centralised procedure?
The SmPC, package leaflet, and labelling must be available in all 24 official EU languages when a centralised marketing authorisation is granted. Iceland, Liechtenstein, and Norway are also covered by the authorisation, so additional languages may be needed depending on commercial plans.
What is the QRD template and why does it matter for translation?
The QRD (Quality Review of Documents) template is the EMA's official format for the SmPC, package leaflet, and labelling. Each language version must follow the template structure, including section headings and content order, in the target language. A translation that deviates from the template will be rejected at submission regardless of linguistic quality.
What is the typical turnaround time for translating an SmPC into a single language?
Turnaround depends on document length, the availability of existing translation memories for the same INN, and quality workflow requirements. A standard-length SmPC with full ISO 17100 workflow (translation, independent review, and QA) typically requires five to ten working days. Rush timelines can be agreed on a project-by-project basis.
Can the same translation provider handle multiple EU languages in a single submission project?
Yes, and this is preferable from a consistency standpoint. A provider managing all target languages within the same project can apply shared controlled glossaries and terminology databases, reducing the risk of cross-language inconsistencies that regulators flag during review.



