The EAEU Dossier Alignment Deadline Just Moved to 2027. Here Is What Changes for Leaflet Translation.
Postponing a regulatory deadline rarely reduces risk. More often, it just redistributes it. The deadline for bringing national registration dossiers into compliance with Eurasian Economic Union (EAEU) law shifted from the end of 2024 to 31 December 2027, and a number of pharmaceutical companies read this as a signal to deprioritize translation work on product leaflets. While that internal timeline was moving, documentation quality requirements and liability for errors in it kept evolving.
Over the past twelve months, the Council of the Eurasian Economic Commission (EEC) updated the Good Clinical Practice (GCP) rules and submitted a draft decision on unified liability principles for violations of mandatory product requirements to the Supreme Eurasian Economic Council (SEEC) for approval. For a regulatory affairs manager, this means one thing: translating the Patient Information Leaflet (PIL) or the Summary of Product Characteristics (SmPC) into the language of a recognizing state is no longer a technical layout task. It is part of the quality system, checked as carefully as the manufacturing process.
How a Leaflet Translation Moves Through the Registration Dossier
An EAEU registration dossier is structured according to the Common Technical Document (CTD) format, made up of five modules. Translation work primarily affects Module 1 («Administrative Information»), specifically Section 1.3, which holds the information intended for patients and physicians. Section 1.3.1 contains the SmPC, Section 1.3.2 is for the PIL (patient information leaflet / package insert), and Section 1.3.3 covers packaging mock-ups. The content and structure of these documents are set out by EEC Council Decision No. 88 of 3 November 2016, «On Approval of the Requirements for the Instructions for Medical Use of Medicinal Products and the Summary of Product Characteristics for Medicinal Products for Human Use» (hereinafter, Decision No. 88).
The SmPC and PIL texts are submitted for review in the Reference Member State (RMS) in Russian. To register in a Concerned Member State (CMS), such as Armenia or Kazakhstan, an applicant needs a translation that matches the approved Russian version in meaning. A discrepancy between the RMS-approved text and the national translation remains one of the main causes of delays at the recognition stage.
The applicant chooses one of two registration pathways, and the choice determines how translation work is organized.
Under the Mutual Recognition Procedure (MRP), the stages run sequentially. Review and registration in the RMS take up to 210 calendar days, during which the master version of the SmPC and PIL is approved in Russian. Once the registration certificate (RC) is issued in the RMS, the applicant submits the application and translations to the concerned member states. The CMS expert bodies then have 100 calendar days to assess the RMS review report and check the national translation linguistically. The main risk is that a CMS may require edits to the translation as a result of its own review, and the national version then starts to diverge from the text approved in the RMS.
Under the Decentralized Procedure (DCP), all participating states review the dossier in parallel, and the whole process fits into 210 calendar days. All language versions need to be ready at the same time, before submission, and this lowers the risk of divergence between countries compared with the sequential procedure.
| Parameter | MRP | DCP |
|---|---|---|
| Order of stages | RMS first, then CMS | RMS and CMS at the same time |
| Timeline in RMS | up to 210 calendar days | included in the overall timeline |
| Timeline in CMS | 100 calendar days after submission | included in the overall timeline |
| Total procedure length | 210 + 100 days, sequential | up to 210 calendar days |
| Risk of divergence between versions | higher, edits come in stages | lower, text is aligned for all markets at once |
| Translation preparation | can start after the RC is issued in the RMS | must be finished before submission |
A separate logic applies to medical devices (MD). Their registration and review are governed by EEC Council Decision No. 46 of 12 February 2016, «On the Rules for Registration and Examination of Safety, Quality, and Efficacy of Medical Devices.» An assessor checks the translation of the instructions for use, the software user interface, and the warning labels on the device itself against the technical specifications in the MD technical file and against the labeling on the device. A mistranslated technical parameter can hold up registration just as badly as an incorrect dosage for a medicinal product.
Regulatory Shifts in Timelines, GCP, and Documentation Liability
Three events from 2025 are reshaping priorities for anyone responsible for the language versions in a dossier.
First, the EEC extended the deadline for bringing national registration dossiers into compliance with Union law from 31 December 2024 to 31 December 2027. The amendment was made in 2025 to EEC Council Decision No. 96 of 10 June 2022, «On Temporary Measures Establishing Specifics for the Circulation of Medicinal Products for Human Use.» The extra three years increase the volume of documentation that needs translation and validation: applicants keep registering new products and filing amendments to existing dossiers.
Second, by Decision No. 63 of 1 August 2025, the EEC Council approved a new edition of the EAEU Good Clinical Practice rules (GCP; originally EEC Council Decision No. 79 of 3 November 2016). The new rules take effect on 10 March 2026 and introduce the concepts of «validation of computerized systems» and «certified copy» for electronic trial data. These provisions concern clinical data, and the requirement to confirm that a computerized system is fit for its intended purpose extends, by the same logic, to translation management systems (TMS) and computer-assisted translation tools (CAT tools): data that ends up in the registration dossier passes through them. Companies without documented validation of these systems will be exposed at inspection.
Third, on 26 September 2025, the EEC Council submitted a draft decision to the SEEC on common principles and approaches for member states’ legislation on liability for violations of mandatory product requirements and conformity assessment procedures (EEC Council Decision No. 81 of 26 September 2025). The document has not yet been adopted by the SEEC and does not name leaflet translation as an object of regulation directly. The principles it sets out, proportionality, inevitability, and presumption of innocence, still set the direction for future national rules on liability for defects in documentation that accompanies a product. Having a documented translation-review process already counts as evidence of good faith if a dispute comes up later.
Decision No. 88 spells out the consequences directly. If the SmPC or PIL does not meet the content requirements, the registration dossier or the amendments to it are declared incomplete, and the competent authority of the member state is entitled to suspend the registration until the deficiencies are fixed. This applies to the translated version too: a CMS expert body treats a mismatch between the translation and the approved RMS text as grounds for the same requirement.
| Parameter | Before | Now |
|---|---|---|
| Deadline for dossier alignment with EAEU law | until 31.12.2024 | until 31.12.2027 |
| GCP rules | Decision No. 79, 2016 edition | Decision No. 79 as amended by Decision No. 63 of 01.08.2025, in force from 10.03.2026 |
| Validation of translation systems and data | not specifically regulated | falls under the general requirement to validate computerized systems |
| Liability for defects in documentation | national rules in each country, no common principles | draft common principles submitted to the SEEC (Decision No. 81 of 26.09.2025) |
The EEC is also discussing a move to electronic product information (ePI), following a similar initiative from the European Medicines Agency. The ePI format is built on structured data rather than a finished page layout, so translation validation shifts from checking a printed page to checking a database: every structural element has to link correctly to the matching section of the SmPC once it is converted into the language of the recognizing state. This is a direction the rules are heading in, not a requirement in force today. The glossaries and processes built for paper leaflets now will become the basis for the future ePI structure.
International practice for linguistic validation, used by many RC holders, includes forward translation by two independent native-speaking linguists with a medical background, reconciliation of the two versions by a third specialist, back-translation into the source language, and comparison with the original. Some companies add cognitive debriefing: testing the text with a small group of patients or physicians in the target country, which helps surface cultural or linguistic issues in how dosage or frequency instructions are understood. Union law does not establish this methodology as a mandatory procedure. In practice, it reduces the likelihood of the substantive discrepancies that CMS assessors find during linguistic review.
What to Do
Audit the language versions for every product. Compare the current Russian version of the SmPC and PIL, as approved in the reference member state, against the translations submitted to each concerned member state. Flag any product where the versions diverge on even one point.
Document the translation process as part of the quality system. Set out in a standard operating procedure (SOP) who does the translation, who reviews it, what tools are used, and how the change history is kept. This document becomes evidence of good faith if Decision No. 81 is adopted.
Check translation tools against the computerized systems validation requirements. If the dossier is prepared using a TMS or CAT tools, make sure the system has a documented assessment of fitness for its intended purpose and of the risk to data reliability, before the new GCP rules take effect on 10 March 2026.
Centralize the terminology glossary for each product. A single glossary across all Union languages lowers the risk of divergence between the SmPC, the PIL, and the packaging mock-ups during later changes to the registration certificate.
Track the status of draft Decision No. 81 on the EEC portal. Once the SEEC adopts it, companies will have a specific deadline to bring their internal procedures in line with national liability legislation.
Companies that formalize their translation process now will enter 2027 with a ready set of evidence of good faith. Those relying only on the extended harmonization deadline risk building their translation validation procedure in the middle of their first inspection, when there will be no one left to explain the missing documentation.
Regulatory Framework:
1. EEC Council Decision No. 78 of 3 November 2016, «On the Rules for Registration and Examination of Medicinal Products for Human Use» (as amended)
2. EEC Council Decision No. 88 of 3 November 2016, «On Approval of the Requirements for the Instructions for Medical Use of Medicinal Products and the Summary of Product Characteristics for Medicinal Products for Human Use» (as amended)
3. EEC Council Decision No. 79 of 3 November 2016, «On Approval of the Rules of Good Clinical Practice of the Eurasian Economic Union» (as amended by EEC Council Decision No. 63 of 1 August 2025)
4. EEC Council Decision No. 46 of 12 February 2016, «On the Rules for Registration and Examination of Safety, Quality, and Efficacy of Medical Devices» (as amended)
5. EEC Council Decision No. 96 of 10 June 2022, «On Temporary Measures Establishing Specifics for the Circulation of Medicinal Products for Human Use» (2025 edition)
6. EEC Council Decision No. 81 of 26 September 2025, «On the Draft Decision of the Supreme Eurasian Economic Council ‘On Defining Common Principles and Approaches Regarding the Establishment of Liability in the Legislation of EAEU Member States for Violation of Mandatory Product Requirements…’»