EMA Day +5: Audit Ready Multilingual Regulatory Filing for Regulatory Teams
The most reliable way to produce agency-ready multilingual regulatory filings is an auditable, ISO-aligned AI+HUMAN hybrid workflow that integrates your existing translation memories and term bases, routes every document through certified subject-matter expert review, and outputs eCTD or SPL-compliant files with a signed translator statement attached where required. Skip any of those elements, and you’re gambling on a deficiency letter.
Table of Contents
What Counts as a Multilingual Regulatory Filing?
A multilingual regulatory filing is any submission to a health authority, financial regulator, or notified body where the source content exists in one language and the target authority requires review in another, whether that means a full translation, a certified summary, or a bilingual side-by-side package. The scope is broader than most teams assume, and narrower in specific spots where agencies explicitly accept English-only or summary-only content.
Documents that typically require full, regulated translation include:
Summary of Product Characteristics (SmPC), labeling text, and Patient Information Leaflets (PIL) for EU centralized and national procedures
Clinical study reports and Good Laboratory Practice (GLP) study reports originating in a non-English language
eCTD modules 1 through 5, including quality, nonclinical, and clinical summaries, when submitted to a non-English-speaking jurisdiction
Certificates of analysis, master files, and manufacturing documentation referenced in a dossier
Foreign-language exhibits attached to SEC filings, which require an English translation or an English summary under Regulation S-T
Translations aren’t always mandatory in full. Some agencies accept a certified English summary of a longer foreign-language source document rather than a line-by-line rendering, and the EMA’s harmonised eCTD guidance lists which document types require translation into every EU member state’s language versus which can stay in English at the applicant’s discretion. The FDA’s own export guidance adds another layer: when unapproved products move across borders, documentation and labeling obligations can shift depending on the destination country, which changes what needs translating and when.
The standards that govern this space are not interchangeable. The FDA regulates content and format for U.S. submissions. The EMA governs linguistic review for centralized EU procedures. eCTD is the technical envelope both regions rely on, in different versions. ISO 17100 and ISO 18587 define what a competent translation and post-editing process actually looks like on paper, which matters when an inspector asks how your vendor selected reviewers.
How Do You Build an Auditable Translation Workflow?
Regulatory translation isn’t a single handoff from source document to target file. It’s a sequence of checkpoints, each of which needs to leave a paper trail an inspector can follow months or years later.
1. Scope the languages and artifacts before you touch a single file. Confirm exactly which modules, labeling components, and appendices require translation for the target jurisdiction, and which can remain in English or use a summary format. This step alone catches a surprising number of over-translations, where teams pay to translate content the agency never asked for.
2. Integrate existing linguistic assets. Pull in the client’s translation memory ™ and term base (TB) before any draft generation starts. Reusing previously approved label language and dossier terminology isn’t optional in a regulated environment. It’s how you avoid a reviewer flagging that “adverse reaction” appears three different ways across two modules.
3. Generate a controlled first draft. Whether the draft comes from a neural machine translation engine or a purpose-built AI system, the draft-generation step must be logged separately from the human review step in the audit trail. Auditors increasingly ask where AI stopped and human judgment started, and a workflow that can’t answer that question in writing has a real problem.
4. Route the draft to a certified subject-matter expert. A medical translator with pharmacovigilance experience reviews clinical content; a regulatory-trained linguist reviews labeling. This isn’t a proofread. It’s a technical accuracy check against source meaning, regulatory phrasing conventions, and, where relevant, prior approved label text.
5. Run completeness and terminology checks. Two-person verification, comparing the translated document section by section against the source, catches dropped sentences, omitted tables, and truncated appendices before they become a deficiency letter.
6. Insert the translator statement. For GLP study report translations submitted to the FDA, a signed and dated translation statement must sit immediately before the translated report’s cover page, attesting to the translation’s accuracy and completeness. This single document has sunk otherwise-solid submissions when it went missing.
7. Handle desktop publishing (DTP) with format fidelity as the priority. Tables, figures, and cross-references need to survive translation without shifting column headers or losing footnote numbering. This is where a translator who doesn’t touch layout software creates downstream problems for whoever does.
8. Validate and package for eCTD. Run the file set through eCTD validation tools before submission, check file naming against the agency’s expected conventions, confirm cross-references resolve, and archive the full package, including intermediate drafts and sign-off records, per your document retention policy.
Pro Tip: Keep a running log that timestamps every handoff, from TM ingestion through final DTP sign-off. When an inspector asks “who reviewed this and when,” a workflow log answers in seconds instead of triggering a scramble through email threads.
Teams that treat this as a linear checklist tend to skip step six under deadline pressure. Teams that treat it as a compliance system build the translator statement into the template from day one, so it’s never a last-minute addition.
What Do Regulators Actually Require for Translated Filings?
Agency expectations vary by jurisdiction, but a few requirements show up repeatedly across FDA, EMA, and SEC guidance, and missing any one of them is a common cause of avoidable rework.
The FDA’s Q&A on translation of GLP study reports sets a clear bar: English translations of non-English GLP reports must be accurate and complete, and every translation needs a signed, dated translator statement placed directly before the translated cover page. The guidance also addresses translator qualifications, expecting sponsors to be able to demonstrate that the person doing the translation had the subject-matter competence to do it correctly, not just language fluency.
One detail catches sponsors off guard during inspections: a signed translator statement is commonly treated as a distinct, separately checkable document. A technically flawless translation missing that statement can still trigger a finding.
For labeling and structured content, the FDA’s guidance on electronic submissions and content of labeling recommends Structured Product Labeling (SPL) in XML format for NDAs, ANDAs, and BLAs, with PDF acceptable in specific circumstances the guidance outlines. Getting this wrong means reformatting an entire labeling package after the fact.
The EMA’s linguistic review process imposes some of the tightest timing in the field: applicants for centrally authorized products face a Day +5 deadline for submitting translated product information after the CHMP opinion, feeding into the broader Day 215 and Day 235 procedural checkpoints. Waiting until the opinion lands to start translation work is the single most common planning failure regulatory teams make.
ISO 17100 defines the process requirements for translation services, covering translator qualifications, project workflow, and revision steps. ISO 18587 does the same for post-editing of machine-translated output, which matters directly for any team using AI or NMT drafts followed by human review, since it specifies what qualifies as adequate post-editing rather than a rushed skim.
On the finance side, Regulation S-T requires most SEC electronic filings to be in English, with foreign-language exhibits needing either a full English translation or an accepted English summary attached.
Formatting Rules That Make or Break Submission Acceptance
Technical formatting failures cause rejections that have nothing to do with translation quality. The linguistic work can be flawless and the submission still bounces because of a file-naming error or a broken cross-reference.
Key formatting points to lock down before you submit:
SPL versus PDF for labeling: the FDA’s guidance on content of labeling favors SPL XML for structured labeling data in marketing applications, with PDF reserved for cases the guidance specifically permits. Defaulting to PDF because it’s familiar is a common, avoidable error.
eCTD package structure: the eCTD technical conformance guide details how sequences, modules, and cross-references need to be organized, and running the package through validation software before submission catches structural errors an agency reviewer would otherwise flag.
File naming conventions: inconsistent or non-compliant file names are one of the most frequent, entirely preventable causes of eCTD validation failures.
Table and figure fidelity: translated tables need the same column structure, units, and footnote references as the source. A side-by-side comparison between source and target PDF, not just a text-level proofread, is the only reliable way to catch a shifted decimal or a dropped unit label.
Foreign-language exhibits for SEC filings: under Regulation S-T, a foreign-language document attached to an electronic filing needs either a complete English translation or an English summary meeting the rule’s conditions, not a partial or paraphrased substitute.
DTP teams working on regulatory content need to direct visibility into the source formatting, not just a translated text file dropped into a template. Losing table structure during translation is a completeness problem, not a cosmetic one, and reviewers treat it that way.
Quality Controls and the Audit Trail Auditors Expect
The paperwork behind a translated regulatory document matters as much as the translation itself when an inspector shows up. Here’s what a defensible audit trail actually contains:
Documented SOPs mapped to ISO 17100 and ISO 18587 checkpoints, showing who does what at each stage of the workflow, from intake through final sign-off.
Reviewer credentials on file for every subject-matter expert who touched the document, including subject-matter background, not just language pairs.
The translator statement itself, signed and dated, filed immediately before the translated GLP report cover page, exactly as FDA guidance specifies.
Two-person completeness verification records, showing that someone other than the original translator checked the target document against the source for dropped content.
TM and TB governance logs, documenting when terminology was locked, who approved changes, and how version conflicts were resolved.
Version control and tracked-change history, so amendments during a review cycle are visible rather than silently overwritten.
Archived packaging records for every submission, including intermediate drafts, so a reviewer years later can reconstruct exactly how the final document came to be.
Pro Tip: Lock your term base before translation starts on a dossier, not during it. Mid-project terminology changes are the single most common source of inconsistency between modules translated by different reviewers on the same project.
A 7-step translation quality checklist for regulated sectors built around these checkpoints gives regulatory teams a template they can hand directly to a vendor or an internal review board.
When Should You Start Translation for Tight Deadlines?
Compressed regulatory timelines punish teams that treat translation as the last step before submission instead of a parallel track that starts early.
The clearest example is the EMA’s Day +5 requirement: centrally authorized product applicants must submit translated product information just five days after receiving the CHMP opinion, a window that makes last-minute translation effectively impossible. Practitioners who consistently hit this deadline start translation preparation well before the final opinion, often around the mid-procedure timepoint, so that post-opinion work is limited to incorporating tracked changes rather than translating from scratch.
Practical scheduling patterns that hold up under deadline pressure:
Begin language scoping and asset integration as soon as the source dossier reaches a stable draft, not after final approval.
Run SME reviews for different modules in parallel rather than sequentially, so a bottleneck in one section doesn’t stall the whole package.
Stagger DTP work so tables and figures get format-checked as sections are finalized, not all at once at the end.
Build in a contingency buffer for at least one additional review round, since post-opinion changes are common even in a well-managed procedure.
Reserve extra QA time specifically for the final terminology and completeness pass. Hybrid AI+HUMAN workflows can compress draft-generation time significantly, but that time savings should go toward more review, not less.
Common Failure Modes and How to Prevent Them
Most regulatory translation rework traces back to a small set of recurring mistakes, each with a specific fix.
Missing translator statement: the single most cited GLP translation deficiency. Build the signed statement into your document template from the start, so it’s generated automatically rather than remembered under deadline pressure.
Terminology drift across modules: happens when different reviewers work from different term lists. Lock the term base before translation begins and route every reviewer through the same governed TB.
eCTD validation failures: caused by file-naming errors, broken cross-references, or structural mismatches. Run validation software before submission, not after a rejection notice arrives.
Table or figure corruption: occurs when DTP work happens without reference to the source layout. A side-by-side check between source and translated file, done by someone other than the translator, catches this reliably.
Failure mode | Root cause | Mitigation |
Missing translator statement | Statement treated as optional add-on | Build into template; verify before filing |
Terminology drift | Uncontrolled or duplicate term lists | Lock TB pre-project; single governed source |
eCTD validation errors | File naming or structural noncompliance | Pre-submit validation software check |
Table/figure corruption | DTP disconnected from source layout | Side-by-side format check, independent reviewer |
When Does It Make Sense to Bring in an Outside Provider?
Regulatory teams tend to reach the outsourcing decision the same way: internal bandwidth is fine for routine updates, but a full dossier translation across a dozen languages under a Day +5 clock is a different order of problem. The decision conditions that actually matter are audit requirements, data sensitivity, terminology governance complexity, and how compressed the timeline is. If two or more of those are true, a certified external provider with documented QA typically outperforms an ad hoc internal effort.
A certified AI+HUMAN hybrid model, built on a proprietary system hosted on EU servers, integrates client TM and TB assets before generation, routes every draft through a subject-matter expert review, and applies QA aligned to ISO 17100 and ISO 18587. That combination addresses the exact decision conditions above: data sovereignty for sensitive dossiers, terminology governance across modules, and SME oversight for technical accuracy, backed by ISO 9001, ISO 27001, and ISO 13485 certification.
Teams evaluating an external supplier should ask for evidence of each control specifically, not a general capability claim. Request a sample workflow log, not just a quality statement.
— Eric Brown
How AD VERBUM Supports Multilingual Regulatory Filings
AD VERBUM is the alternative to assembling a patchwork of freelance translators and hoping the paperwork holds up under inspection. The AI+HUMAN hybrid workflow runs every regulatory document through the same sequence: your translation memories and term bases integrate first, a certified subject-matter expert reviews the output, and QA aligns to ISO 17100 and ISO 18587 before anything ships.
Coverage spans many languages and regional variants, backed by a network of subject-matter expert linguists with medical, engineering, and legal backgrounds, and infrastructure certified to ISO 27001 and ISO 42001 with EU-hosted data processing. That matters directly for sponsors handling GLP reports, clinical study data, or labeling packages where data sovereignty and terminology governance aren’t optional line items.
If you’re preparing a multilingual filing with a hard deadline, start by submitting a sample file set for scoping, or request a translation readiness checklist before your next submission window opens. Visit AD VERBUM’s services page to outline scope and get a quote.
Where to Verify These Requirements Directly
Before finalizing any filing, check the primary sources rather than relying on secondary summaries. The FDA’s GLP translation Q&A covers translator statements and qualifications directly. The FDA’s content of labeling guidance governs SPL and PDF format decisions. The EMA’s linguistic review process document sets the Day +5 timeline. The eCTD technical conformance guide governs package structure and validation. For finance filings, Regulation S-T governs English-language and foreign-exhibit rules.
Sources
FAQ
What Qualifies as a Multilingual Regulatory Filing?
It’s any regulatory submission where source content in one language must be translated, summarized, or presented bilingually to meet a target authority’s requirements, covering documents like SmPCs, GLP study reports, and eCTD modules. Scope varies by agency, with the EMA’s eCTD guidance specifying which documents require full translation versus which can stay in English.
Is Multilingual Translation the Same as Bilingual Translation?
No. Bilingual work involves exactly two languages, while a multilingual regulatory filing often spans a dozen or more target languages simultaneously, each with its own terminology governance and review chain. A single centralized EU procedure alone can require translation into over twenty official languages.
Do Regulatory Translators Need Specific Qualifications?
Yes. FDA guidance on GLP study report translation expects sponsors to be able to demonstrate translator competence in the relevant subject matter, not just language fluency, and requires a signed translator statement confirming accuracy and completeness. ISO 17100 sets parallel qualification and process requirements that many regulated sponsors use as a benchmark for vendor selection.
What Happens if a Translated Filing Is Missing Required Documentation?
A missing translator statement or an incomplete section can trigger a deficiency letter or rejection even when the underlying translation quality is sound. Building the statement and completeness checks into the workflow template, rather than adding them manually at the end, is the most reliable prevention.
Does AD VERBUM Handle Regulatory and Compliance Document Translation?
Yes. AD VERBUM’s AI+HUMAN hybrid workflow integrates client terminology assets, routes documents through certified subject-matter expert review, and applies QA aligned to ISO 17100 and ISO 18587 across multiple languages. Pricing is scoped per project; current details are available through AD VERBUM’s services page.
Recommended
