Assyro AI
Assyro AI logo background
ectd module 3 structure
ectd module 3
module 3 ectd

eCTD Module 3 Structure: Quality and CMC Documentation Guide

Guide

eCTD Module 3 structure guide covering quality CMC sections, drug substance, drug product, appendices, regional information, and literature references.

Assyro Team
Published March 19, 2026
10 min read

Quick Answer

eCTD Module 3 contains quality and CMC documentation. Its structure includes 3.1 table of contents, 3.2 body of data, and 3.3 literature references. The body of data is organized into 3.2.S drug substance, 3.2.P drug product, 3.2.A appendices, and 3.2.R regional information. Module 3 is harmonized under ICH M4Q, with regional expectations added where applicable.

Key Takeaways

  • Module 3 is the quality module of the CTD.
  • Section 3.2.S covers the drug substance.
  • Section 3.2.P covers the drug product.
  • Section 3.2.A contains appendices such as facilities, adventitious agent safety evaluation, and excipients where applicable.
  • Section 3.2.R contains regional information required by specific authorities.
  • This article focuses on eCTD Module 3 structure. For a deeper quality documentation article, see the eCTD Module 3 quality guide. For the complete five-module framework, see eCTD structure explained.

Why Module 3 Is High Impact

Module 3 is often the module that creates the most lifecycle work after approval. Manufacturing process changes, specification changes, analytical method updates, facility changes, supplier changes, stability commitments, and container closure changes can all affect the quality story in Module 3.

That means Module 3 should be built with traceability in mind. Reviewers should be able to move from the QOS in Module 2.3 to the detailed Module 3 section and find consistent information. Regulatory teams should also be able to find which quality records support each statement when a later amendment, supplement, annual report, or variation is needed.

The best Module 3 packages are not just complete. They are internally consistent and easy to maintain.

What Is eCTD Module 3?

eCTD Module 3 is the quality and chemistry, manufacturing, and controls module. It contains the detailed information reviewers use to evaluate the identity, strength, quality, purity, manufacturing control, stability, and overall quality of the product.

Module 3 supports:

  • Drug substance control
  • Drug product control
  • Manufacturing process understanding
  • Analytical method suitability
  • Specifications and acceptance criteria
  • Stability and shelf-life
  • Container closure suitability
  • Facility and regional quality expectations

Module 2.3 summarizes Module 3, but the detailed evidence belongs in Module 3.

eCTD Module 3 Section Structure

SectionTitlePurpose
3.1Table of Contents of Module 3Navigation for Module 3
3.2Body of DataDetailed quality and CMC data
3.2.SDrug SubstanceQuality information for the active substance
3.2.PDrug ProductQuality information for the finished product
3.2.AAppendicesFacilities, adventitious agent safety, excipients, and related appendices
3.2.RRegional InformationRegion-specific quality information
3.3Literature ReferencesQuality literature references

This structure is based on ICH M4Q. The same high-level structure applies across ICH regions, but some details and regional documents may differ.

Source Records Behind Module 3

Module 3 content usually depends on controlled quality and CMC records. Before finalizing the submission, confirm the source records are approved and current.

Common source records include:

  • Manufacturing process descriptions
  • Batch records and executed batch data
  • Specifications and analytical procedures
  • Method validation or verification reports
  • Process validation or process performance evidence
  • Stability protocols and reports
  • Container closure evidence
  • Supplier and material qualification records
  • Facility and equipment information
  • Change controls, deviations, CAPA, and investigations that affect CMC content

The submission should not rely on draft or uncontrolled versions unless the regulatory context clearly supports that approach and the status is transparent.

Section 3.2.S: Drug Substance Structure

Section 3.2.S contains drug substance information.

SectionContent
3.2.S.1General information, nomenclature, structure, and properties
3.2.S.2Manufacture, manufacturer, process, controls, materials, and validation
3.2.S.3Characterization, impurities, and elucidation of structure
3.2.S.4Control of drug substance, specifications, analytical procedures, and validation
3.2.S.5Reference standards or materials
3.2.S.6Container closure system
3.2.S.7Stability data and conclusions

Drug substance structure should support traceability from manufacturing process to control strategy. Reviewers should be able to understand what is made, how it is made, how it is controlled, and how stability supports retest or storage conditions.

Section 3.2.P: Drug Product Structure

Section 3.2.P contains finished drug product information.

SectionContent
3.2.P.1Description and composition
3.2.P.2Pharmaceutical development
3.2.P.3Manufacture
3.2.P.4Control of excipients
3.2.P.5Control of drug product
3.2.P.6Reference standards or materials
3.2.P.7Container closure system
3.2.P.8Stability

Drug product structure should connect formulation, development rationale, manufacturing process, control strategy, packaging, and stability. A weak Module 3 often has data, but not a clear quality story.

CMC Consistency Checks

Before filing, compare Module 3 against Module 2.3 and source documents for:

  • Drug substance and product names
  • Manufacturer, site, and role descriptions
  • Process flow and critical process controls
  • Batch formula and composition
  • Specifications and acceptance criteria
  • Analytical procedure titles and versions
  • Method validation references
  • Stability time points, storage conditions, and shelf-life conclusions
  • Container closure descriptions
  • Regional information placement

Most CMC questions do not come from missing documents alone. They often come from small inconsistencies across summaries, tables, reports, and specifications.

Module 3 and Lifecycle Management

Module 3 should be organized so lifecycle changes can be managed later. Postapproval changes may affect manufacturing sites, process descriptions, analytical methods, specifications, packaging, container closure, stability, suppliers, or facilities.

For each important Module 3 statement, the team should know:

  • Which source quality record supports it
  • Which application or market uses it
  • Whether a later change requires regulatory assessment
  • Whether implementation is blocked until approval or notification
  • Which sequence or submission updated the content

This is where QMS records, RIM context, and eCTD lifecycle management meet. A clear Module 3 structure reduces future rework.

Sections 3.2.A, 3.2.R, and 3.3

Section 3.2.A contains appendices. These may include facility information, adventitious agent safety evaluation, novel excipients, or other appendices depending on the product.

Section 3.2.R contains regional information. Its content depends on the agency and application type.

Section 3.3 contains literature references for Module 3.

These sections should not become a dumping ground. Each document should be placed where the CTD structure and regional requirements expect it.

Regional Information Needs Discipline

Section 3.2.R can be misunderstood because it is regional. That does not mean anything uncertain should be placed there. Regional information should be used when the health authority or application context expects region-specific quality content.

Before placing a document in 3.2.R, ask:

  • Is this content specifically regional?
  • Does FDA or the target authority identify this placement?
  • Should the document instead be in 3.2.S, 3.2.P, or 3.2.A?
  • Does the QOS in 2.3 need to reference it?
  • Will the placement be clear during lifecycle updates?

Good Module 3 structure keeps harmonized quality data in the harmonized sections and regional material in the regional section only when that is the right regulatory home.

Common Module 3 Structure Errors

ErrorWhy It Matters
Specifications differ between Module 3 and Module 2.3Creates review questions and data inconsistency
Stability conclusion does not match submitted dataShelf-life or storage condition may be challenged
Process description is not aligned with validation or control strategyManufacturing readiness becomes unclear
Analytical method validation is misplaced or incompleteControl strategy may not be supported
Regional quality documents placed in harmonized sectionsRegional review and validation can be affected
Drug substance and drug product cross-references are unclearReviewers may struggle to trace quality decisions

Module 3 is usually large. Structure discipline matters because reviewers need to locate evidence quickly and compare it against the QOS.

How Assyro Supports Module 3 Readiness

Assyro helps teams compare Module 3 content against Module 2.3, labeling, specifications, stability conclusions, and manufacturing documents. eCTD Validation, eCTD Authoring, and Regulatory Gap Analysis can help catch mismatched specifications, stale QOS text, missing stability support, and inconsistent cross-references before submission.

For source-record readiness, see From CAPA to eCTD, quality records for regulatory submissions, and regulatory impact assessment in change control.

For Module 3, the value is quality consistency: the CMC package should support the same manufacturing and control story from summary to source document.

eCTD Module 3 is the quality and CMC module. It contains detailed drug substance and drug product information.

References

This guide reflects FDA and ICH eCTD structure information current as of May 2026. Confirm current ICH M4Q guidance, FDA submission standards, and application-specific quality 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.

Demos available this week