How to Prepare and Submit eCTD-Ready Applications to the FDA

Tag icon Regulation/Guidelines
category icon

Summary:

  • The eCTD is the FDA-mandated electronic format for regulatory submissions to CDER and CBER.
  • eCTD enables structured organisation, metadata tagging, easy navigation, and lifecycle management of regulatory documents.
  • FDA requires eCTD for most drug and biologics submissions, including NDAs, ANDAs, BLAs, INDs, DMFs/BMFs, and post-approval submissions.
  • FDA supports both eCTD v3.2.2 and eCTD v4.0, provided submissions comply with official technical specifications.

Short Description

FDA’s Electronic Common Technical Document (eCTD) is an important regulatory document that has a clear structural framework and submission requirements. Knowing the types of applications requiring eCTD, accepted eCTD versions, core module organisation, and key steps for preparing and managing eCTD submissions in line with FDA guidance support regulatory compliance and efficient review.

What Is eCTD and Why Does It Matter?

Introduction 

The Electronic Common Technical Document (eCTD) is the Food and Drug Administration’s (FDA) standard electronic format for regulatory submissions of drug and biologics applications to the Center for Drug Evaluation and Research (CDER) and the Center for Biologics Evaluation and Research (CBER).1 It replaces older paper or non-standard electronic formats to make the review easier and faster.

Understanding the eCTD Framework

The eCTD is an internationally harmonised format developed by the International Council for Harmonisation (ICH) and adopted by the FDA for electronic regulatory submissions. It allows reviewers to efficiently navigate, assess, and track submissions throughout a product’s lifecycle.1

eCTD simplifies regulatory submissions by enabling:

  • Structured and accessible submissions help FDA review data efficiently.2
  • Tracking across original applications, amendments, supplements, and annual reports.

Types of Submissions Requiring eCTD Format

According to FDA regulations and guidance, the following submissions must generally be provided in eCTD format:3

  • New Drug Applications (NDAs)
  • Abbreviated New Drug Applications (ANDAs)
  • Biologics License Applications (BLAs)
  • Commercial Investigational New Drug (IND) applications
  • Drug Master Files (DMFs) and Biologics Master File (BMF)
  • Supplements, amendments, and annual reports

eCTD Versions Accepted by FDA

FDA continues to support both formats:3

  • eCTD v3.2.2: the long-standing industry standard.
  • eCTD v4.0: the latest version accepted voluntarily for new submissions since September 16, 2024.

Note: Sponsors can submit new applications in either version, but both must follow the official technical specifications.

Core Structure of an eCTD Submission

a. CTD ModulesThe eCTD is organised into five structured modules, each serving a specific regulatory purpose and collectively enabling standardised, efficient review by the FDA. Table 1 summarises the module-wise organisation of the eCTD and the key content elements required within each module.

eCTD ModuleModule TitleKey Contents
Module 1Administrative Information and Prescribing InformationFDA regional eCTD backbone files; cover letter and reviewers’ guide; patient experience data; cross-references to previously submitted non-eCTD information; labelling; advertisements and promotional labelling material; marketing annual reports; information amendments; field copy certification; REMS; RMAT designation
Module 2SummariesBioequivalence summary tables
Module 3Quality (CMC)Lot distribution data; structure-data files; literature references
Module 4Nonclinical Study reports; datasets; literature references
Module 5Clinical Tabular listing of all clinical studies; study reports;  CRFs; periodic safety reports; IND safety reports; literature references; data sets, aECG waveform

FDA: Food and Drug Administration; eCTD: Electronic Common Technical Document; REMS: Risk Evaluation and Mitigation Strategy; RMAT: Regenerative Medicine Advanced Therapy; CRFs: case report forms; IND:  Investigational New Drug Application; aECG: Annotated Electrocardiogram

b. Technical Backbone and Metadata

An eCTD submission is driven by an XML backbone that:

  • Defines document hierarchy
  • Assigns metadata (study type, document title, lifecycle action)
  • Enables navigation and version control

eCTD Submission Process

To ensure acceptance by the FDA, sponsors must prepare eCTD submissions that meet both regulatory content and technical conformance requirements:2

  1. Review FDA electronic submission resources, including eCTD guidance, eCTD Submission Standards (v3.2.2 and v4.0), the FDA Data Standards Catalogue, and other supporting materials. For clarification, sponsors may contact the FDA directly. Early planning and advance communication with the appropriate review division are strongly encouraged.
  2. Obtain a pre-assigned application number from CDER or CBER before submission. Sponsors should allow adequate time for this step, as errors in application numbering can lead to significant submission and processing issues.
  3. Register for the FDA Electronic Submissions Gateway (ESG) well in advance. ESG registration involves a multi-step process, including submission testing through the ESG test environment. Only after successful testing is access granted to the ESG production system for live submissions.
  4. Optionally submit a sample eCTD or standardised study data package to the FDA for early feedback, particularly for first-time submitters or those adopting eCTD v4.0. Sample submissions are separate from ESG account testing and help identify structural or technical issues before final submission.
  5. Submit the validated eCTD application via the ESG, ensuring the submission size is within the 10 GB limit for electronic transmission. Sponsors should validate submissions against FDA eCTD conformance criteria (v3.2.2 or v4.0) prior to submission to minimise technical errors and avoid delays.

Note: Many pharmaceutical companies rely on eCTD publishing services USA to ensure FDA-compliant electronic submissions and efficient lifecycle management.

Post-Submission Lifecycle Management

eCTD submissions are designed to support lifecycle management across the entire regulatory history of a product. FDA expects all subsequent regulatory interactions to be submitted as new eCTD sequences using appropriate lifecycle operators. Key lifecycle principles include:

  • Use of lifecycle actions (new, replace, append, delete) to maintain document version control
  • Clear linkage between original submissions and follow-up sequences
  • Consistent use of metadata to ensure accurate tracking of regulatory history

Conclusion

The eCTD has become the FDA’s standard for electronic regulatory submissions, enabling structured organisation, efficient review, and effective lifecycle management of regulatory information.

Successful preparation of an eCTD-ready application requires early planning, adherence to FDA technical and content standards, accurate metadata and XML backbone creation, and disciplined lifecycle management across submissions. 

References 

1. Contains Nonbinding Recommendations [Internet]. [cited 2026 Feb 9]. Available from: https://www.fda.gov/media/93818/download

2. Electronic Common Technical Document (eCTD) | FDA [Internet]. [cited 2026 Feb 9]. Available from: https://www.fda.gov/drugs/electronic-regulatory-submission-and-review/electronic-common-technical-document-ectd

3. Submit Using eCTD | FDA [Internet]. [cited 2026 Feb 9]. Available from: https://www.fda.gov/drugs/electronic-regulatory-submission-and-review/submit-using-ectd

CliniExperts

CliniExperts - Your reliable partner for Comprehensive Compliance Solutions. We offer 360 degree Global Regulatory Solutions related to Pharma, Medical Devices and In-Vitro Diagnostics.

CliniExperts

CliniExperts Services Pvt. Ltd.


Contact us

Please feel free to talk to us if you have any questions. We endeavour to answer within 24 hours.