Understanding CTD Modules: Perspectives from FDA and ICH

Introduction: Why CTD Modules Matter

The Common Technical Document (CTD) is the globally harmonized structure for regulatory submissions, and the electronic CTD (eCTD) has become the mandatory format for US FDA submissions under the Electronic Submissions Gateway (ESG). CTD modules organize regulatory information into five core sections, ensuring consistency, completeness, and efficient review by regulators. For sponsors, correct structuring of modules is critical, as deficiencies often result in technical rejections, Refuse-to-File (RTF) decisions, or inspection findings. The FDA and ICH provide clear expectations on module content, structure, and lifecycle management.

According to the Japan Registry of Clinical Trials, over 95% of global submissions rely on the CTD/eCTD structure, with regulators citing Module 3 (Quality) and Module 5 (Clinical) as the most common sources of deficiencies.

Overview of CTD Modules

The CTD consists of five core modules, with Module 1 region-specific:

While Modules 2–5 are harmonized across ICH regions, Module 1 remains specific to each regulatory agency. Sponsors must therefore tailor submissions for FDA, EMA, Health Canada, and other regulators.

Regulatory Expectations by Module

FDA and ICH expectations include:

• Module 1 (FDA): Must include Form FDA 1571 (IND), labeling, and environmental assessments. Technical rejection is common if forms are incomplete.
• Module 2: Requires integrated summaries of quality, nonclinical, and clinical data. FDA expects clarity and consistency across modules.
• Module 3: Requires validated manufacturing controls, stability data, and cross-references to batch records. This is a frequent source of deficiencies.
• Module 4: Must include complete GLP-compliant nonclinical reports. Missing appendices often trigger information requests.
• Module 5: Requires all pivotal clinical study reports, datasets, and case report forms. FDA frequently cites missing clinical datasets as major deficiencies.

EMA and WHO emphasize the same principles, though retention periods and labeling requirements may differ.

Common Audit Findings in CTD Modules

FDA and EMA inspections frequently identify module-level issues:

Example: FDA refused to file an NDA because Module 5 lacked datasets supporting pivotal clinical trial results. The sponsor had not verified completeness before submission, leading to costly delays.

Root Causes of Module-Level Deficiencies

Typical root causes include:

• No SOPs defining responsibilities for CTD module preparation and QC.
• Inadequate vendor oversight in publishing and data compilation.
• Lack of integration across regulatory, clinical, and CMC functions.
• Failure to validate electronic publishing tools for eCTD submissions.

Case Example: In a biologics BLA, Module 3 stability data were incomplete because the CMC team and regulatory group operated in silos. Root cause analysis revealed insufficient cross-functional review processes.

Corrective and Preventive Actions (CAPA) for CTD Modules

CAPA can address module deficiencies effectively:

1. Immediate Correction: Submit missing documents or datasets, update hyperlinks, and correct technical validation errors.
2. Root Cause Analysis: Identify gaps in SOPs, cross-functional oversight, or vendor performance.
3. Corrective Actions: Revise SOPs, strengthen cross-functional QC reviews, and validate publishing software.
4. Preventive Actions: Establish submission readiness checklists, conduct mock validations, and implement vendor audits.

Example: A US sponsor introduced a cross-functional CTD review committee. This reduced Module 3 and Module 5 deficiencies by 80% in subsequent submissions.

Best Practices for CTD/eCTD Modules

To align with FDA and ICH expectations, best practices include:

• Develop SOPs for each CTD module, defining responsibilities and QC processes.
• Use validated eCTD publishing tools compliant with FDA technical guidance.
• Train regulatory staff on CTD module structure and FDA expectations.
• Integrate cross-functional reviews across clinical, nonclinical, and CMC teams.
• Conduct mock submissions to identify and correct deficiencies before ESG transmission.

KPIs for CTD module oversight:

Case Studies in Module Oversight

Case 1: FDA RTF decision due to missing datasets in Module 5, resolved through cross-functional SOPs.
Case 2: EMA identified inconsistencies in Module 2 summaries, requiring resubmission.
Case 3: WHO review highlighted missing appendices in Module 4, recommending harmonized global templates.

Conclusion: Embedding Quality in CTD Modules

CTD modules are the backbone of global submissions, and FDA requires strict adherence to eCTD technical specifications. Common deficiencies—such as missing datasets, incomplete stability data, or poor integration across modules—undermine regulatory confidence. By embedding CAPA, validating tools, and implementing cross-functional reviews, sponsors can ensure modules are complete, consistent, and inspection-ready. Robust CTD modules not only minimize regulatory risks but also accelerate review timelines and strengthen sponsor credibility.

Sponsors who prioritize CTD module quality transform submissions into reliable, regulator-friendly dossiers that withstand global scrutiny.