Regulatory professionals are entering a major transition in how they submit drug applications and product information to the U.S. Food and Drug Administration (US FDA). The electronic Common Technical Document (eCTD) format, the global standard for structuring and transmitting regulatory dossiers, has begun its long-awaited transition from eCTD v3 to eCTD v4. This next format promises greater flexibility, improved data management, and more efficient communication between industry and regulators. After years of planning, eCTD v4 is finally becoming a reality: as of 16 September 2024, the US FDA’s CDER and CBER are accepting new applications in eCTD v4 format. In this blog, we will explore what eCTD v4 is, why it matters, key features and benefits, implementation timelines, and how companies can prepare for this new chapter in regulatory submissions.
Why update to eCTD v4?
While eCTD v3 greatly improved paper-based submissions, it has limitations that increasingly obstruct regulators and industry. The current eCTD standard is built around a fixed table of contents (ToC) structure that cannot easily accommodate new document types or adapt to innovative submission needs. Moreover, eCTD v3 supports a one-way flow of information: industry submits sequences to regulators, but agencies cannot send back official correspondence through the same channel. Also, over the years, other pain points have emerged, like the difficulty of reusing the same document in multiple applications, challenges in managing the lifecycle for complex submissions, and inconsistencies across regions in how submissions are structured. These challenges set the stage for eCTD v4, developed through the ICH (International Council for Harmonisation) M8 expert working group in collaboration with Health Level Seven (HL7) standards development, to create a more robust, flexible, and long-term solution.
For a detailed comparison of eCTD v3 and v4, please read our blog post: What are the Differences between eCTD v3 and eCTD v4? - A Comprehensive Guide
Implementation timeline & US FDA’s current status (USA)
Center for Drug Evaluation and Research (CDER) and Center for Biologics Evaluation and Research (CBER) have accepted new regulatory applications in eCTD v4 since 16 September 2024. The US FDA’s own status page states that future phases will address forward compatibility (linking v3 history) and two-way communication. The US FDA is also accepting sample v4 packages (currently for new applications).
-
Submission types currently supported
Per the US FDA guidance and the Data Standard Catalog, eCTD v4 support (beginning on 16.09.2024) specifically covers new NDAs, BLAs, ANDAs, INDs, and Master Files (MFs). The US FDA currently supports new marketing and investigational application types in v4; lifecycle submissions that belong to an existing v3 application are not yet migrated automatically.
The US FDA’s M1/submission-type materials and legacy eCTD guidance continue to define the broader list of submission types/subtypes (original application, amendment, supplement, report, safety report, promotional submissions, etc.). The practical effect today is that you can create new regulatory activities in eCTD v4 (where applicable), but many submission-type combinations and lifecycle behaviors remain constrained until forward-compatibility phases are deployed.
The US FDA maintains an “eCTD Submission Standards” catalog for v4, including the Module 1 Implementation Guide v1.7 (18 Feb 2025), Validation Specifications v1.4 (Feb 2025), and the Comprehensive Table of Contents (CTD Headings) v2.2 (18 Feb 2025). These define code lists, message structure, forward-compatibility concepts, grouped submission constraints, and validation rules.
-
Forward compatibility & conversions
The US FDA has not yet enabled forward compatibility for existing v3 dossiers; this is planned for future phases. Until then, new applications may start in v4, but ongoing v3 dossiers stay in v3.
-
Two-way communication & ESG NextGen
The US FDA’s ESG NextGen is live with a new Unified Submission Portal and APIs, but bi-directional messaging is not in scope for current releases, so official correspondence still arrives via traditional channels.
The US FDA ran an eCTD v4 technical pilot (completed in 2023) involving a small set of companies; a limited number of test submissions were performed to confirm technical behavior for features such as document reuse and lifecycle scenarios (one-to-many/many-to-one). The pilot summary in the US FDA program materials reports that 11 companies participated and six companies submitted test submissions during the pilot. The US FDA now accepts optional v4 packages for technical feedback. Industry can submit samples through the sample-submission process to get the US FDA technical feedback.
As of today, the US FDA has not announced a mandatory date for eCTD v4. Industry commentary often projects a late-decade mandate (e.g., ~2029), but that is not an official US FDA commitment. Track the US FDA’s eCTD v4 page and Submission Standards for updates.
Preparing for eCTDv4:
1. Update SOPs & train teams
Ensure publishing/QC staff understand Context of Use, sender-defined keywords, and lifecycle behaviors (replace one-to-many). Use the US FDA Module 1 IG and Validation Specs as your operational backbone.
2. Engage your tech stack early
Confirm your tools build submissionunit.xml, load ICH/US FDA CVs, and pass the US FDA v4 validations. Dry-run internal builds against the US FDA validation rules before your first live sequence.
3. Pilot on low-risk filings
Consider starting with a new IND or master file to build muscle memory, then scale. (The US FDA currently evaluates sample packages for new apps.)
4. Run dual-track operations (for now)
Most portfolios will run v3.2.2 (legacy apps) and v4 (new apps) in parallel until forward compatibility is enabled. Keep clear labeling and tracking to avoid cross-version confusion.
5. Monitor US FDA updates
Watch the eCTDv4 and Submission Standards pages for new CVs, validation updates, Q&As, and any forward-compatibility/two-way communication announcements.
eCTD v4 is a significant, format-first modernization that makes submissions more flexible, reusable, and easier to manage over a product’s lifecycle, without changing the fundamental CTD Modules 1–5 model. The biggest wins come from data-driven organizations, UUID-based reuse, richer lifecycle, and updatable code lists with two-way communication as a future milestone once the US FDA turns it on. For the US industry, the immediate move is optional for new applications, but the direction is clear. Teams that prepare their process, tooling, and training now will be positioned to transition smoothly when the US FDA expands capabilities and, eventually, sets a mandate.
.png)