EMA eCTD Guidance

Why eCTD matters for EU submissions

The electronic common technical document is more than a folder tree. It is a structured electronic submission standard that allows reviewers to navigate documents through an xml backbone, assess lifecycle management changes across an eCTD sequence history, and confirm that files integrity guaranteed checks such as checksum validation are in place. In practice, the eCTD structure supports a more efficient review model because documents are linked, searchable, and organized into the 5 modules used across ICH regions.

For applicants, the benefits are practical. eCTD format submissions provide a predictable file structure, support lifecycle management for amendments and responses, and align with global standards used by FDA, other agencies, and the international council framework.

Which submissions must use eCTD in the EU

In the EU, eCTD format submissions are mandatory for all submission types related to marketing authorisation within the main EU procedures. That includes the centralized route, decentralized route, and mutual recognition procedures, and the wider EU regulatory roadmap has also made eCTD mandatory in human national procedures. In practice, teams should assume that eCTD submissions are the default standard whenever they prepare marketing authorization applications, renewals, or major lifecycle updates in Europe.

Once a product is in eCTD, future changes should be managed through new sequences rather than parallel document collections. That is one reason disciplined submission types related planning matters so much.

Centralized, decentralized, MRP, and national procedures

For centralized products, the European Medicines Agency acts as the hub for receiving and routing eCTD submissions. For decentralized and mutual recognition procedures, teams also need to account for national procedures expectations and authority-specific handling. In those multi-country workflows, the common European submission portal is often relevant for MRP, DCP, and national submissions, while the EMA uses its own esubmission gateway and web channels for agency-facing submissions.

The dossier logic may be harmonized, but the operational route for submission can still vary by procedure, destination, and specific requirements.

Current EMA technical requirements in 2026

For EU eCTD submissions in 2026, teams must align publishing systems, templates, and validation tools with the current EU Module 1 and regional validation package.

eCTD 3.2.2, EU M1 v3.1.1, and validation criteria v8.2

The current version of the common technical document eCTD specification for CTD Modules 2 to 5 is eCTD v3.2.2. From 1 December 2025, submissions are expected to comply with EU Module 1 v3.1.1 and validation criteria v8.2. In operational terms, publishers need to verify their technical validation setup, update rulebooks in validation tools, and confirm that teams are not still preparing packages against outdated validation criteria.

Validation criteria drive what will be accepted, flagged, or rejected. If a dossier is built on older assumptions, the result may be a failed submission, even when the scientific documents are complete.

ZIP package, XML delivery file, and working documents folder

For EMA-facing electronic submission, the package is prepared as a ZIP archive with no password or internal encryption. The XML delivery file is mandatory for use through the esubmission gateway and the web client because it carries routing and regulatory information used in technical validation and downstream handling.

Teams also need to pay attention to the working documents folder. When working documents are included with an eCTD package, they should be placed in a separate folder called xxxx-workingdocuments, where the number reflects the relevant sequence number. Any deviation from this file structure can create validation problems and may trigger rejection or resubmission.

PDF documents, hyperlinks, and file integrity

In the EU, the generally accepted file format remains PDF, although some exceptions exist for specific content. That makes pdf documents a core quality focus. Files must be readable, appropriately bookmarked, and linked correctly. Broken hyperlinks, malformed PDFs, corrupted files, or checksum mismatches can all interrupt validation.

A dossier can look complete to a human reviewer and still fail technical validation because the underlying file structure, xml backbone, or files integrity rules do not meet current technical guidance.

Lifecycle management: where strong teams outperform

Lifecycle management is one of the biggest reasons companies adopt disciplined eCTD publishing. Every eCTD submission is part of a cumulative record. Over time, that record includes initial applications, responses, amendments, variations, renewals, safety updates, and other post-approval documents.

In EU practice, lifecycle operators such as new, replace, and delete determine how a document behaves within the dossier. Publishers also need to know when not to resubmit documents already present in prior sequences. Good version control matters here. Without it, teams create duplicate content, inconsistent references, and confusing review histories.

For products transitioning from older electronic submission approaches, a baseline strategy may also be considered to support a cleaner eCTD lifecycle. In some EU guidance contexts, a baseline helps bring previously submitted content into the electronic common technical document structure so future variations and responses can be managed more efficiently.

Sequence planning and cover letters

Each eCTD sequence should be planned before publishing begins. That means agreeing the submission type, related sequence logic, affected modules, and expected lifecycle actions. Cover letters must align with the content of the sequence, and tracking information should accurately reflect what has been submitted, to whom, and in what order.

This is especially important in national procedures and multi-country workflows, where teams may be coordinating the same regulatory activity across several agencies.

EMA vs FDA: what global teams should know

Global teams often ask whether a single process can cover Europe and the United States. The answer is yes at a high level, but not without local adaptation. Both the European Medicines Agency and FDA rely on the electronic common technical document and both expect structured, technically compliant electronic submission. But the regional implementation details still differ.

For example, FDA requires electronic submissions through defined digital channels, and the FDA Electronic Submissions Gateway remains the central transmission point for many regulated submission types. FDA also supports eCTD v4.0 for certain new applications, including new drug applications and biologics license applications, while the EU is rolling out eCTD v4.0 more gradually for specific use cases. That means organizations need harmonized core publishing standards plus region-specific requirements, not a one-size-fits-all SOP.

The smartest organizations therefore build one governance model around global standards, but maintain separate regional rule sets for eCTD modules, validation criteria, cover letters, and technical requirements. That reduces rework while still respecting what regional regulatory agencies and other agencies have accepted.

A practical checklist before you submit

Before any submission, confirm

• the submission type
• the elated sequence logic
• and the target procedure.

Verify that the dossier uses the correct eCTD format, the right sequence number, and the expected module placement. Check that all pdf documents open correctly, hyperlinks work, and filenames follow correct naming rules.

Then confirm that the XML delivery metadata is complete, the ZIP package is unencrypted, and the working documents folder is named correctly if applicable. Run validation tools against the latest validation criteria, review all high-risk warnings, and make sure the cover letter and tracking table match the actual submission documents. Finally, confirm that the transmission route is correct, whether that is the EMA gateway, the esubmission gateway, the esubmission web client, or CESP.

Most technical validation issues are not caused by obscure edge cases. They come from routine process gaps, inconsistent version control, or weak coordination between regulatory, publishing, and vendor teams.

Final thoughts

The current EU environment leaves little room for avoidable technical mistakes. eCTD submissions must be accurate at both document level and package level. Teams need to understand the eCTD structure, current validation criteria, sequence planning, and submission channels, while keeping sight of the broader common technical document logic that underpins global regulatory work.

For regulatory teams, that means treating eCTD as a governed process with clear ownership, validated tools, and procedure-specific controls. For leadership, it means recognizing that the quality of an electronic submission can affect approval timelines just as much as the quality of the scientific content. And for organizations working across Europe, the US, and other agencies, it means building a model that can satisfy both today’s operational rules and tomorrow’s evolving technical guidance.