eCTD 4.0 Is No Longer a Future Problem for Global Sponsors

The eCTD 4.0 implementation timeline is now materially different across Japan, the EU and the US, forcing global sponsors to manage overlapping submission standards and regional transition dates

Japan set the first mandatory date for eCTD v4.0, and it has passed. Under MHLW notification 0218-4 of Feb. 18, 2022, the transitional period allowing the former eCTD format ran to March 31, 2026. PMDA’s own briefing materials state the consequence directly: from applications filed in April 2026, only eCTD v4.0 is accepted.

Two qualifiers belong with that, because secondary sources routinely drop them. The mandate applies to applications filed on or after that date. An application that began in v3.2.2 continues in v3.2.2 for its entire lifecycle. And the scope is pharmaceutical applications. The cited PMDA implementation materials do not state that the April 2026 cutover extends to medical devices or IVDs.

Everyone Else Is Somewhere Else on the eCTD 4.0 Implementation Timeline

The rest of the eCTD 4.0 implementation timeline is a spread rather than a wave, and the differences are operationally significant.

FDA has accepted new regulatory applications in eCTD v4.0 in CDER and CBER since Sept. 16, 2024, announced by Federal Register notice. That is a voluntary window for new applications only. FDA’s current v4.0 standards page was updated again on Aug. 28, 2026, while the agency still describes forward compatibility for existing v3.2.2 applications and two-way communication as future phases. FDA’s own v4.0 standards table does not list a Date Requirement Begins for the standard. The current ICH regional implementation table lists 2029 as the US mandatory date, but FDA has not yet published a corresponding requirement date on its eCTD v4.0 pages.

The EU is further along than FDA on optional use and behind Japan on mandate. From Dec. 22, 2025, applicants may optionally submit new marketing authorization applications for centrally authorized products in eCTD v4.0. Version 3.2.2 remains accepted throughout the optional period. EMA launched a third pilot phase on forward compatibility for CAPs in March 2026. It finalized EU eCTD v4.0 validation criteria version 1.1, applicable from July 15, 2026. EMA now states that strongly recommended use for new CAP MAAs begins in Q1 2027 and mandatory eCTD v4.0 use for new CAP MAAs begins in Q1 2028. The timeline for forward compatibility for CAPs with existing eCTD v3.2.2 lifecycles remains dependent on testing and further readiness assessments.

An older EMA planning document showing mandatory CAP use in 2026 is stale, and the document itself carries a disclaimer that timelines are subject to revision. The current EMA roadmap and the ICH regional implementation table now both place mandatory use for new CAP MAAs at Q1 2028.

Sponsors filing in Japan, the US, and Europe are therefore running two submission standards at once. Region, application age, and the transition date an application started under all determine which standard applies.

eCTD 4.0 implementation timeline comparing PMDA, EMA and FDA transition dates

The Part That Is Not a Format Change

It is tempting to treat this as a publishing problem that a vendor solves. That reading misses what eCTD v4.0 changes.

Version 4.0 is built on HL7 Regulated Product Submission. Content is identified by controlled vocabulary and metadata rather than by position in a folder hierarchy. In ICH terminology, a Context of Use gives the referenced document its CTD context, while keywords provide additional information about that context. A document is described by what it is and what it relates to. The same content can be referenced in more than one context without being duplicated, using eCTD v4.0’s document reuse capability and persistent document identifiers.

That is a content model change wearing the clothes of a format change. Under v3.2.2, an organization could maintain documents and let the publishing step impose structure at the end. Under v4.0, the structure is the submission, and metadata quality determines whether it is coherent.

Which means the work moves upstream. Decisions about how content is identified, classified, and related have to be made while the content is authored. The people who understand what it is should make them, rather than a publishing team inferring later from filenames.

Why the Dual Standard Is the Hard Part of eCTD 4.0 Readiness

Running two standards at once is harder than either standard alone, and the difficulty is not technical.

The same source content has to serve both targets. Suppose the organization maintains two parallel content estates, one shaped for v3.2.2 and one for v4.0. It has doubled its maintenance burden and created a reconciliation problem between them. Any change now has to be applied twice and verified twice.

The alternative is to hold content once, in a governed structure rich enough to satisfy the more demanding target. Publishing then serves whichever standard a region requires. Under that arrangement the dual period is a publishing configuration rather than a fork in the content estate.

That option is only available to organizations whose content is already structured and governed. It cannot be adopted at publishing time, because the metadata it depends on has to have been captured at authoring time.

Governance First, Then Structure,Then Intelligence

Governance is the prerequisite. Controlled vocabulary is a governance artifact before it is a technical one. Someone has to own each term, authorize changes to it, and enforce its consistent use. An organization without that ownership will produce v4.0 submissions that validate and still misrepresent the relationships between their own content.

Structure is the mechanism. Docuvera holds regulatory content as governed components carrying their own metadata and relationships. One governed source can be published to multiple submission targets without maintaining parallel estates.

Intelligence follows and stays bounded. Under the Hierarchy of Intelligence, Retrieval Augmented Reuse comes first, because it works from approved, governed content and carries provenance forward. Retrieval Augmented Transformation adapts governed content to a required target structure, which is precisely the operation a multi-standard period demands. Retrieval Augmented Generation sits last, because generated text is the least traceable of the three. AI assists provability here, and it does not substitute for the regulatory review that authorizes what is filed.

One practical instruction outweighs the rest. Confirm dates against the regulators directly rather than against secondary summaries, because the summaries conflict with each other and with the primary sources.

Japan’s mandate is in force for new pharmaceutical applications. FDA’s v4.0 window remains voluntary; ICH lists 2029 as the US mandatory date, while FDA has not yet published its own corresponding requirement date. The EU’s optional period is open, with strongly recommended use for new CAP MAAs from Q1 2027 and mandatory use from Q1 2028. Any plan built on a different set of facts is built on commentary.

Regulatory source note: Implementation dates and status statements in this article were checked against current PMDA, FDA, EMA and ICH materials. Regulatory implementation timelines can change; sponsors should confirm applicable requirements with the relevant health authority before filing.

Frequently Asked Questions

Sources

Note for editorial: the topic brief asked for verification because secondary sources disagree, and they do. The current ICH regional implementation table lists 2029 as the US mandatory date, while FDA’s own current eCTD v4.0 standards material does not publish a corresponding Date Requirement Begins. The EU position has changed since the earlier draft: EMA now states strongly recommended use for new CAP MAAs from Q1 2027 and mandatory use from Q1 2028. The cited PMDA materials frame the April 2026 cutover around pharmaceutical applications and do not state that it extends to medical devices or IVDs. PMDA’s November 2025 briefing remains the clearest explicit cutover wording cited here. The Japanese notification number is rendered here in romanized form because the canvas title field handles the original characters inconsistently.

See what structured component authoring can do for you.

Contact Us
Scroll to Top