Quick Answer
eCTD Module 2 contains the CTD summaries and overviews. Its structure includes 2.1 CTD table of contents, 2.2 introduction, 2.3 Quality Overall Summary, 2.4 Nonclinical Overview, 2.5 Clinical Overview, 2.6 Nonclinical Written and Tabulated Summaries, and 2.7 Clinical Summary. Module 2 is harmonized under ICH M4 and connects the detailed data in Modules 3, 4, and 5 to the sponsor's regulatory argument.
Key Takeaways
- Module 2 is the summary layer of the CTD.
- It should not introduce unsupported claims that do not trace to Modules 3, 4, or 5.
- Section 2.3 summarizes quality and CMC information from Module 3.
- Sections 2.4 and 2.6 summarize nonclinical information from Module 4.
- Sections 2.5 and 2.7 summarize clinical information from Module 5.
- This article focuses on eCTD Module 2 structure. For deeper writing guidance, see the eCTD Module 2 summaries guide. For the full five-module framework, see eCTD structure explained.
Why Module 2 Matters
Module 2 is where reviewers first see how the sponsor interprets the evidence. It should help the reviewer navigate the application and understand the product's quality, nonclinical, and clinical case before moving into the detailed modules.
That makes Module 2 risky when it is written late or assembled from stale source text. A Module 2 summary can create review questions if it describes a specification that differs from Module 3, summarizes a nonclinical finding differently from Module 4, makes a clinical benefit-risk claim that is not supported by Module 5, uses outdated labeling language, or cross-references the wrong report, table, or section.
Module 2 should not be promotional. It should be clear, traceable, and consistent with the detailed source evidence.
What Is eCTD Module 2?
eCTD Module 2 is the summary and overview module. It gives reviewers a structured path into the application by summarizing quality, nonclinical, and clinical evidence.
Module 2 is not just an executive summary. It is the interpretive layer that explains how the data package supports the application.
The reviewer should be able to read Module 2 and understand:
- What product is being submitted
- What evidence supports quality, safety, and efficacy
- How the sponsor interprets key findings
- Where detailed source information is located in Modules 3, 4, and 5
- How the overall benefit-risk argument is supported
eCTD Module 2 Section Structure
| Section | Title | Purpose |
|---|---|---|
| 2.1 | CTD Table of Contents | Table of contents for Modules 2-5 |
| 2.2 | CTD Introduction | Brief introduction to the drug, class, indication, and application scope |
| 2.3 | Quality Overall Summary | Summary of Module 3 quality and CMC information |
| 2.4 | Nonclinical Overview | Integrated interpretation of nonclinical pharmacology, pharmacokinetics, and toxicology |
| 2.5 | Clinical Overview | Integrated clinical benefit-risk discussion |
| 2.6 | Nonclinical Written and Tabulated Summaries | Structured summaries of nonclinical studies |
| 2.7 | Clinical Summary | Structured summaries of clinical pharmacology, efficacy, safety, and related evidence |
The structure is harmonized under ICH M4. Regional administrative content belongs in Module 1, not Module 2.
How Reviewers Use Module 2
Reviewers use Module 2 to understand the application quickly and decide where to go deeper. The summaries should make the detailed evidence easier to review, not force reviewers to resolve contradictions.
Useful Module 2 writing should:
- Explain the product and application scope
- Summarize the quality control strategy
- Explain nonclinical findings and their relevance
- Summarize clinical efficacy and safety
- Tie conclusions to proposed labeling
- Point reviewers to detailed source documents
- Avoid unsupported claims or selective summaries
Module 2 is especially important for cross-functional consistency because it sits between the administrative story in Module 1 and the detailed evidence in Modules 3-5.
Section 2.3: Quality Overall Summary
The Quality Overall Summary, often called QOS, summarizes the quality information from Module 3.
It should summarize:
- Drug substance information
- Drug product information
- Manufacturing process and controls
- Specifications and analytical procedures
- Container closure system
- Stability data
- Regional quality information where applicable
The QOS should match Module 3. A common problem is that specifications, shelf-life claims, manufacturing descriptions, or stability conclusions differ between 2.3 and Module 3.
Quality Overall Summary Consistency Checks
Before filing, compare section 2.3 against Module 3 for:
- Drug substance and drug product names
- Manufacturer and site descriptions
- Manufacturing process descriptions
- Specifications and acceptance criteria
- Analytical procedure names and validation status
- Container closure information
- Stability data, storage conditions, and shelf-life claims
- Batch data and comparability conclusions
The QOS should summarize, not reinterpret, the detailed CMC package. If the team updates Module 3 late, section 2.3 should be reviewed again.
Sections 2.4 and 2.6: Nonclinical Structure
Section 2.4 is the Nonclinical Overview. It is an integrated interpretation of the nonclinical program.
Section 2.6 contains the Nonclinical Written and Tabulated Summaries. It is more structured and detailed than 2.4.
| Section | Role |
|---|---|
| 2.4 | Interpretive nonclinical overview |
| 2.6 | Written and tabulated summaries of nonclinical studies |
| Module 4 | Full nonclinical study reports |
The structure should let reviewers move from the sponsor's nonclinical interpretation to summary tables and then to full reports.
Sections 2.5 and 2.7: Clinical Structure
Section 2.5 is the Clinical Overview. It presents the integrated clinical interpretation and benefit-risk argument.
Section 2.7 is the Clinical Summary. It contains structured summaries of clinical evidence, including biopharmaceutics, clinical pharmacology, efficacy, safety, and literature references.
| Section | Role |
|---|---|
| 2.5 | Integrated clinical overview and benefit-risk interpretation |
| 2.7 | Structured clinical summaries |
| Module 5 | Full clinical study reports and literature |
The clinical Module 2 structure should connect directly to proposed labeling, indication, dosage, warnings, contraindications, and safety conclusions.
Traceability From Module 2 to Source Evidence
Every important Module 2 conclusion should be traceable to a source location.
| Module 2 Statement | Source to Check |
|---|---|
| Shelf-life conclusion | Module 3 stability data and reports |
| Manufacturing control conclusion | Module 3 process and validation content |
| Nonclinical safety margin | Module 4 toxicology reports and section 2.6 summaries |
| Dose rationale | Clinical pharmacology reports and Module 2.7 |
| Efficacy conclusion | Pivotal clinical study reports in Module 5 |
| Safety warning | Clinical safety data, nonclinical findings, and proposed labeling |
This traceability helps the team catch mismatches before the submission reaches technical or substantive review. It also supports later responses when FDA asks where a conclusion came from.
Common Module 2 Structure Errors
| Error | Why It Matters |
|---|---|
| Summary does not match source module | Reviewers may question data integrity or submission control |
| Overviews repeat data without interpretation | The regulatory argument becomes weak |
| Unsupported benefit-risk statements | Claims may not be traceable to Module 5 |
| QOS differs from Module 3 specifications | CMC review questions can arise |
| Nonclinical summary omits key safety findings | Risk assessment may be incomplete |
| Clinical overview conflicts with proposed labeling | Labeling negotiations and review delays can follow |
Module 2 should be treated as the controlled summary layer for the full application.
Module 2 Readiness Checklist
Before filing, confirm:
- Section 2.2 describes the correct product, indication, and submission scope.
- Section 2.3 matches Module 3 and current CMC documents.
- Section 2.4 and 2.6 align with Module 4 study reports.
- Section 2.5 and 2.7 align with Module 5 study reports, datasets, and labeling.
- Cross-references point to correct files and sections.
- Tables, study identifiers, and report titles are consistent.
- Benefit-risk statements are supported by the evidence.
- Late source-document changes were reflected in the summaries.
Module 2 should be reviewed after final source-module updates, not before.
Module 2 Should Not Create New Evidence
Module 2 is a summary and interpretation layer. It should not introduce new data, new study conclusions, new CMC claims, or new labeling arguments that are absent from the detailed modules.
If a conclusion is important enough to appear in Module 2, the team should know where the underlying evidence lives. If the evidence is not in Module 3, 4, or 5, the right fix is usually to update the source module or revise the Module 2 statement, not to hide the issue in summary language.
This is especially important for benefit-risk language. A strong clinical overview explains the evidence clearly, but it does not replace the clinical study reports, datasets, safety summaries, or proposed labeling support.
How Assyro Supports Module 2 Readiness
Assyro helps teams compare Module 2 summaries against Modules 3, 4, and 5. eCTD Validation, eCTD Authoring, and Regulatory Gap Analysis can help identify mismatched cross-references, unsupported summary statements, stale conclusions, and inconsistencies between Module 2 and source reports.
For Module 2, the value is coherence: the summaries should accurately reflect the detailed evidence and support the same regulatory story.
eCTD Module 2 contains CTD summaries and overviews for quality, nonclinical, and clinical information.
References
This guide reflects FDA and ICH eCTD structure information current as of May 2026. Confirm current ICH CTD guidance, FDA submission standards, and application-specific requirements before filing.
About the author
Assyro Team
Expert regulatory operations consultants helping pharmaceutical companies navigate complex compliance challenges.
See Assyro in action
Catch eCTD and eSTAR errors before your FDA review cycle.
Book a 20-minute demo this week. We'll validate a sample of your submission live and show you exactly where Assyro catches what your current QC misses.