Last Updated: October 2026
What is eCTD 4.0, who does it affect, and when does it take effect?
eCTD 4.0 is the next version of the electronic Common Technical Document, the format sponsors use to send regulatory dossiers to agencies. It affects regulatory operations teams first, and anyone who authors or tags submission content second. The FDA has accepted it for new applications since September 2024 and the EMA since December 2025, but neither has retired v3.2.2. Adoption is slow enough that real-time data exchange with regulators may overtake parts of it.
This article is the short version: what eCTD 4.0 is, why it exists, who it affects, and when it applies. For the mechanics (context of use, lifecycle operators, controlled vocabularies), see Everything You Need to Know About eCTD 4.0.
In this article
- The what: what is eCTD 4.0?
- The why: why is there a new version?
- The who: who does eCTD 4.0 affect?
- The when: when does eCTD 4.0 take effect?
- Why is eCTD 4.0 adoption so slow?
- Will real-time data exchange overtake eCTD 4.0?
- What should regulatory teams do now?
- How Kivo supports eCTD 4.0, and how the options compare
- FAQ
The what: what is eCTD 4.0?
eCTD 4.0 is the ICH M8 successor to eCTD v3.2.2, the version agencies have accepted for most of the past two decades. It is based on the Regulated Product Submission (RPS) standard from Health Level Seven (HL7), and it describes a whole submission in a single XML message rather than a folder tree with a backbone file per module.
Because it is built on RPS, eCTD 4.0 is designed to handle more data-driven submissions over time, and in principle other product types, such as veterinary products and medical devices, could use the same model.
The why: why is there a new version of the eCTD?
The goal of eCTD 4.0 is to make submissions faster to build, easier to maintain, and clearer for reviewers. After years of multi-agency use, sponsors and regulators asked for more controlled terms, simpler lifecycle management, and one harmonised message format across regions.
Version 4.0 answers that with a few core ideas:
- Context of use places each document in the CTD structure and carries its lifecycle.
- Controlled vocabularies standardise metadata so content is classified the same way everywhere.
- Document reuse lets a sponsor reference a previously submitted document instead of sending it again.
- Ordering and grouping let sponsors set priority so reviewers see the most important content first.
Version 4.0 also separates regulatory updates from software updates: agencies can change controlled vocabularies without a new DTD (document type definition), so tools don't need an upgrade every time the rules change.
The who: who does eCTD 4.0 affect?
eCTD 4.0 lands hardest on regulatory operations, the team that assembles, publishes, and submits the package. It also reaches anyone whose content ends up in the submission.
- Regulatory affairs and operations own the switch: new metadata, new lifecycle rules, and a publishing tool or vendor that supports v4.0 for each agency.
- Medical writers, statisticians, data managers, and CMC teams need a working understanding of context of use and keywords, because their content is tagged with them.
- IT and quality may need to upgrade or reconfigure the electronic document management system (EDMS), publishing tools, and eCTD viewer, and validate the changes.
- Executives mostly see the timeline question: when to fund the change, and whether to file the next new application in v4.0.
The when: when does eCTD 4.0 take effect?
eCTD 4.0 is accepted now at the FDA and EMA, and v3.2.2 is still accepted at both. Only the EMA has announced a mandatory date, and only for one application type.
| Agency | v4.0 accepted since | Scope today | Required from |
|---|---|---|---|
| FDA (CDER and CBER) | September 16, 2024 | New regulatory applications | No date announced; v3.2.2 still accepted |
| EMA | December 22, 2025 (optional) | New marketing authorisation applications for centrally authorised products | Q1 2028 for new centrally authorised MAAs, strongly recommended from Q1 2027 |
At the FDA, existing v3.2.2 applications cannot move to v4.0 yet; the agency says forward compatibility and two-way communication will come in future phases. Its eCTD v4.0 Technical Conformance Guide is at version 1.5, dated July 9, 2026. In the EU, a pilot for non-centrally authorised applications is planned for Q3/Q4 2026 and a forward-compatibility pilot for Q4 2026. Japan's PMDA runs its own transition; check PMDA's current notices for its dates.
Why is eCTD 4.0 adoption so slow?
ICH began work on eCTD 4.0 around 2010, and more than two years after the FDA started accepting it, no agency has set a date to retire v3.2.2 across the board. A few things explain the pace:
- Existing applications can't switch yet. At the FDA, only new applications can be filed in v4.0. Most of a sponsor's lifecycle work happens on existing applications, so most submissions stay on v3.2.2 by necessity.
- Nothing forces the move. With v3.2.2 still accepted everywhere and only one EU mandate on the calendar, few sponsors have a deadline that justifies the cost now.
- Every region moves separately. Each agency sets its own regional module, vocabularies, validation rules, and dates, so a global sponsor has to be ready for several versions of the same transition.
- The tool chain has to move together. Publishing, validation, viewing, and document management all need v4.0 support and validation before a team can file with confidence.
Will real-time data exchange overtake eCTD 4.0?
It may overtake parts of it. eCTD 4.0 improves how documents are packaged and sent, but it is still a document exchange: a sponsor assembles a sequence and transmits it, and the agency reviews what arrives. Two efforts are working on something different, where structured data is shared and updated in near real time.
- Structured quality data at the FDA. The FDA's Pharmaceutical Quality/Chemistry, Manufacturing and Controls (PQ/CMC) project is defining structured data for parts of Module 3, using HL7 FHIR as the exchange format. The first part of its implementation guide has been published as a Standard for Trial Use. The FDA says the standard is not meant to structure all eCTD quality information and has not announced when it will accept or require it. Its KASA system (Knowledge-aided Assessment and Structured Application) is designed to assess this kind of structured data.
- Cloud-based exchange between sponsors and regulators. Accumulus Synergy, a nonprofit industry association backed by large biopharma companies, launched a platform in February 2024 for real-time information exchange between sponsors and the agencies that review their products. The association reports that regulators in a reliance pilot used it to ask questions and receive sponsor answers on a post-approval change, that one post-approval CMC dossier reached a reference country and nearly two dozen reliance countries at the same time, and that by August 2025 more than 60 countries had access. These are the association's own reports, and use so far centres on pilots and reliance procedures rather than primary approvals.
Neither effort replaces eCTD today, and neither has a date when it would. The likelier near-term picture is a mix: eCTD 4.0 for the dossier, with structured data exchange growing around it, starting with CMC and post-approval changes. If that happens, some regions may never need to push v4.0 as hard as they pushed v3.2.2.
What should regulatory teams do now?
Prepare for eCTD 4.0 in ways that also pay off if structured data exchange arrives first. Both depend on the same groundwork.
- Clean up document metadata and build a sponsor keyword list that maps to the new controlled vocabularies.
- Keep a single source of truth for each submitted document, so reuse and lifecycle tracking work in either model.
- Ask your publishing vendor for its v4.0 support and validation status for each agency you file with.
- Pick a candidate for your first v4.0 filing: a new application at the FDA, or a new centrally authorised MAA in the EU (after contacting the EMA's eCTD v4.0 team).
- Watch PQ/CMC and reliance-based exchange pilots if CMC or post-approval changes are a large part of your submission load.
How Kivo supports eCTD 4.0, and how the options compare
Kivo RIM includes an eCTD viewer that supports eCTD 4.0. It runs in the browser on Mac and PC and links live to Kivo's document management system, so each submitted document's metadata and audit trail are one click away. Kivo also provides 450+ pre-formatted ICH templates and tracks submissions, correspondence, and commitments in one place. Kivo does not publish eCTDs itself: it prepares submission-ready packages for your publishing partner and keeps submitted eCTDs viewable and linked to their source documents. Kivo is rated 4.9/5 on G2 and is used by 200+ sponsor, consultant, and CRO teams. See Kivo RIM and the Kivo eCTD Viewer.
Several vendors offer eCTD viewing, archiving, or publishing inside a broader regulatory suite. The table below summarises how Kivo and three alternatives handle eCTD, based on each vendor's published materials.
| Option | Product area | eCTD handling (per vendor materials) | Typically fits |
|---|---|---|---|
| Kivo | Kivo RIM eCTD Viewer, linked to Kivo DMS | Browser-based viewer with sequence, current, and cumulative views; live links to DMS metadata and audit trails; supports eCTD 4.0. Publishing is handled by a partner. | Clinical-stage teams that want viewing tied to document management and RIM |
| Veeva | Vault Submissions Archive | Cloud viewer for eCTD, NeeS, and legacy formats; current, sequential, and regulatory-action views; preserves the eCTD XML backbone and hyperlinks on import. | Teams already on the Veeva Vault platform |
| Ennov | Ennov Regulatory Suite (Ennov Dossier) | Generates, manages, publishes, validates, and archives eCTD, NeeS, and eCopy submissions within a suite that includes document management and RIM. | Teams that want publishing and RIM in one suite |
| ArisGlobal | LifeSphere Publishing / Regulatory | Plans, compiles, publishes, and validates submissions with eCTD lifecycle management, integrated with document management for review. | Teams that want publishing and RIM on one platform |
This table is not an independent ranking. It does not assess implementation quality, market share, or fit for any particular organisation, and capabilities change, so confirm details, including eCTD 4.0 support, with each vendor and validate against your own requirements.
FAQ
When did the FDA start accepting eCTD 4.0?
CDER and CBER have accepted new regulatory applications in eCTD 4.0 since September 16, 2024. Existing applications that started in v3.2.2 cannot move to v4.0 yet, and the FDA has not announced when it will stop accepting v3.2.2.
Is eCTD 4.0 required in the EU?
Not yet. The EMA has accepted eCTD 4.0 optionally for new centrally authorised marketing authorisation applications since December 22, 2025. It plans to make v4.0 mandatory for those applications from Q1 2028, with use strongly recommended from Q1 2027.
Who inside a sponsor needs to learn eCTD 4.0?
Regulatory operations needs the deepest knowledge, since it assembles and submits the package. Medical writers, statisticians, data managers, and CMC teams need to understand context of use and keywords, and IT or quality may need to upgrade and validate the systems involved.
Will real-time data exchange replace eCTD?
Not today. FDA's PQ/CMC structured data standard has no acceptance date, and sponsor-regulator exchange platforms are still mostly in pilots and reliance procedures. Structured exchange may grow alongside eCTD 4.0, starting with CMC and post-approval changes, rather than replace it outright.
Next up: a deeper dive into the new concepts of eCTD 4.0.

