Skip to content
Assyro AI
Back to Glossary
Submission & Approval

eCTD(Electronic Common Technical Document)

eCTD is the standard electronic format for pharmaceutical regulatory submissions, organizing CTD content into five modules with a machine-readable backbone so an agency can navigate an application and track every amendment across its lifecycle.

Usage Examples

  • Every amendment to that NDA goes in as a new eCTD sequence, not as an email attachment.
  • The eCTD failed validation on Module 1 because the regional XML did not match the form data.
  • We are still on eCTD v3.2.2 for that product; the v4.0 move is scheduled after the next supplement.

What is eCTD (Electronic Common Technical Document)?

eCTD is the standard electronic format for pharmaceutical regulatory submissions, organizing CTD content into five modules with a machine-readable backbone so an agency can navigate an application and track every amendment across its lifecycle.

eCTD exists because a marketing application is not a document, it is a decade-long conversation. A sponsor files an original application and then hundreds of amendments, supplements, and reports against it. eCTD gives the agency a machine-readable structure for that stream, so a reviewer can see the current state of an application without reassembling paper binders or a folder of loose PDFs.

eCTD covers applications, amendments, supplements, and reports submitted to FDA's Center for Drug Evaluation and Research and Center for Biologics Evaluation and Research: NDAs, ANDAs, BLAs, INDs, and master files. eCTD is a format, not content. What belongs in each module is set by the CTD issued by the ICH M4 Expert Working Group; eCTD specifies only how that content is structured, transmitted, and versioned.

eCTD is applied in practice as a numbered series of sequences. Each submission against an application is a new sequence that declares, file by file, whether content is new, replaced, appended, or deleted. eCTD therefore rewards teams who plan the lifecycle up front: a mis-declared operation in sequence 0012 still distorts the reviewer's cumulative view of the application years later.

Not to be confused with

CTD
CTD is the content standard from ICH M4 that defines what goes in each module; eCTD is the electronic format that carries CTD content and adds file-level versioning. A paper CTD is still a CTD, and it is not an eCTD.
FDA Electronic Submissions Gateway (ESG)
the ESG is the transport channel that delivers a submission to FDA; eCTD is the format of what travels through it. A valid eCTD sent by the wrong route and a malformed eCTD sent by the right one both fail.
eCTD v4.0
v4.0 is a separate version of the eCTD standard, not a rebranding of v3.2.2. FDA lists which eCTD versions it currently supports in the FDA Data Standards Catalog, so "eCTD" on its own never fully specifies what you have to build.
Module 1
Module 1 is region-specific and differs by agency, while Modules 2 through 5 carry the harmonized CTD content. An eCTD accepted by FDA is therefore not automatically an eCTD accepted by another regulator.

eCTD obligations attach to the submission type, the format version, and the module structure.

What you must do

  1. 1Submit NDAs, ANDAs, and BLAs in eCTD format; the requirement has applied since 5 May 2017FDA eCTD compliance dates: 5 May 2017 and 5 May 2018
  2. 2Submit INDs and master files in eCTD format; the requirement has applied since 5 May 2018FDA eCTD compliance dates: 5 May 2017 and 5 May 2018
  3. 3Use eCTD for every amendment, supplement, and report against a covered application going to CDER or CBER, not only for the original filingFDA eCTD standard format (CDER and CBER)
  4. 4Organize submission content into the CTD module structure defined by the ICH M4 Expert Working GroupICH M4 CTD content basis for eCTD
  5. 5Build each sequence in an eCTD version FDA currently supports, as published in the FDA Data Standards CatalogFDA Data Standards Catalog (supported eCTD version)
  6. 6Plan the move to eCTD v4.0, which CDER and CBER have supported for new NDAs, BLAs, ANDAs, INDs, and master files since 16 September 2024eCTD v4.0 support from 16 September 2024

Common mistakes

  • Assuming one eCTD serves every agency

    Modules 2 through 5 are harmonized CTD content, but Module 1 is region-specific. Teams that budget a single publishing effort discover a second regional Module 1, a second forms set, and a second validation profile at the point in the program where the timeline has the least slack.

  • Building to an eCTD version FDA no longer supports

    electronic submissions must use a version listed in the FDA Data Standards Catalog, and CDER and CBER have supported eCTD v4.0 for new NDAs, BLAs, ANDAs, INDs, and master files since 16 September 2024. A sequence built outside the supported versions does not meet the requirement no matter how complete the underlying science is.

  • Treating eCTD as a packaging step at the end

    eCTD is a lifecycle format, not an export. Publishing decisions rushed in the final week (wrong operation attributes, a document filed under the wrong module, a reused sequence number) persist in the application's cumulative view for its whole life, and each one has to be corrected by a later sequence the reviewer also has to read.

When This Matters

  • Every amendment to that NDA goes in as a new eCTD sequence, not as an email attachment.
  • The eCTD failed validation on Module 1 because the regional XML did not match the form data.
  • We are still on eCTD v3.2.2 for that product; the v4.0 move is scheduled after the next supplement.

Frequently Asked Questions

Yes. NDAs, ANDAs, and BLAs have been required in eCTD format since 5 May 2017, and INDs and master files since 5 May 2018. The requirement covers amendments, supplements, and reports to those applications, not only the original filing to CDER or CBER.

Related Use Cases

Related Regulatory Intelligence

Related Actions

Sources & References

Share this page
Agent CTA Background

Simplify Electronic Common Technical Document compliance

Book a Demo