Quick Answer
The eCTD organizes regulatory content into five modules: regional administrative information, summaries, quality, nonclinical reports and clinical reports. CTD section numbers describe content placement. Electronic files, metadata and lifecycle rules implement that structure differently across eCTD versions and regions. Identify the document's purpose, receiving authority and applicable specification before assigning its final location.
This reference covers the main module map and selected document placements, with FDA and EU examples checked against official sources on October 6, 2026. It is not an exhaustive list of documents required for every application. The application type, development stage and submission purpose determine which content is needed.
eCTD modules at a glance
| Module | Content purpose | Start here for these documents |
|---|---|---|
| 1 | Regional administrative and prescribing information | Application forms, cover letters, regional labeling and correspondence |
| 2 | Summaries and overviews | Quality Overall Summary, nonclinical overview and summaries, clinical overview and summaries |
| 3 | Quality information | Drug substance and finished-product manufacture, controls and stability |
| 4 | Nonclinical study reports | Pharmacology, pharmacokinetics and toxicology reports |
| 5 | Clinical study reports | Biopharmaceutic, clinical pharmacology, efficacy and safety reports |
The module organization comes from ICH M4(R4), dated June 15, 2016. Module 1 is regional; Modules 2–5 use the harmonized CTD framework. Harmonization does not make every regional evidence requirement identical: Module 3 itself includes a regional-information section, 3.2.R.
A summary and its supporting report usually belong in different places. For example, a quality summary belongs in Module 2, while its supporting quality data belong in Module 3. Preserve the relationship through appropriate references rather than treating the summary as a substitute for the source material. Our ICH M4 guide explains the content framework in more detail.
Module 1: select the region before the section
A section number without its region can be misleading. FDA's 1.6 is meetings; EU 1.6 is environmental risk assessment. The shared module number does not create a shared regional table of contents.
Selected FDA Module 1 placements
The following entries use FDA's Comprehensive Table of Contents Headings and Hierarchy, version 2.3.5, February 18, 2025, in its v3.2.2 submission standards. They are selected lookup entries, not a complete US Module 1 checklist. FDA table of contents, pages 1–4.
| Content | FDA heading | Placement distinction |
|---|---|---|
| Forms | 1.1 | Select the applicable form type |
| Cover letter | 1.2 | Separate from scientific summaries |
| Financial certification/disclosure | 1.3.4 | Administrative information |
| Patent and exclusivity information | 1.3.5 | Use the relevant subheading |
| Letter of authorization | 1.4.1 | References here concern authorization, not a general literature library |
| Meeting materials | 1.6 | Requests, background materials and meeting correspondence have separate children |
| Pediatric administrative information | 1.9 | Distinct from the information-amendment headings under 1.11 |
| Environmental analysis | 1.12.14 | Not FDA 1.6 |
| Labeling | 1.14 | Distinguish draft, final and other applicable labeling branches |
| Promotional material | 1.15 | Not a miscellaneous attachment under 1.12 |
| Risk management plan | 1.16 | Non-REMS and REMS branches are distinct |
| Risk Evaluation and Mitigation Strategy | 1.16.2 | Select the relevant REMS document subheading |
| Postmarketing studies | 1.17 | Includes correspondence regarding commitments and requirements |
A clinical report about postmarketing experience and administrative correspondence about a postmarketing commitment are different document functions. Do not route both solely because their titles contain “postmarketing.” The same reasoning applies to pediatric study reports versus pediatric administrative requests.
For eCTD v4.0, use FDA's corresponding v4.0 table of contents and controlled vocabularies from its submission standards page. A human-readable heading is not, by itself, a v4.0 code or implementation instruction.
EU Module 1 uses its own hierarchy
The EU Module 1 specification has different placements, including 1.6 for environmental risk assessment and 1.8 for pharmacovigilance information. It also defines regional metadata and technical handling. Use the EU Module 1 specification, version 3.1.1, June 2025, rather than translating a US folder tree by changing its country code.
The EU eSubmission index identifies EU M1 version 3.1.1 and validation criteria 8.2 as mandatory from December 1, 2025 for the referenced v3.2.2 submissions. Its companion Harmonised technical guidance is version 6.0.1. These are separate version numbers for separate documents.
Use the Module 1 guide for a deeper administrative mapping and the regional requirements guide when planning content across authorities.
Module 2: place the interpretation and summaries
Module 2 connects the detailed evidence to the conclusions presented for review. Its major sections are:
| Section | Content | Supporting material |
|---|---|---|
| 2.1 | CTD table of contents for Modules 2–5 | CTD organization; electronic implementation determines navigation handling |
| 2.2 | CTD introduction | Product context |
| 2.3 | Quality Overall Summary | Module 3 quality information |
| 2.4 | Nonclinical overview | Interpretation of nonclinical evidence |
| 2.5 | Clinical overview | Interpretation of clinical evidence |
| 2.6 | Nonclinical written and tabulated summaries | Module 4 studies |
| 2.7 | Clinical summary | Module 5 studies |
These headings describe CTD content; they do not instruct you to create one PDF or folder for every row. The electronic granularity rules matter when splitting or combining documents. ICH M4(R4) organization and granularity annex.
Within 2.6, pharmacology uses 2.6.2 and 2.6.3 for written and tabulated summaries; pharmacokinetics uses 2.6.4 and 2.6.5; toxicology uses 2.6.6 and 2.6.7. Do not label 2.6.4 “toxicology” when building a template. ICH M4S(R2), December 20, 2002.
Clinical summary sections distinguish biopharmaceutics, clinical pharmacology, efficacy and safety. Keep an individual clinical study report in its Module 5 location even when its findings contribute to several summaries. The Module 2 structure guide covers this summary-to-evidence relationship in more detail.
Module 3: distinguish drug substance from drug product
In the established quality structure, S identifies drug-substance information and P identifies drug-product information. The same scientific topic can therefore have two different destinations.
| Topic | Drug substance | Drug product |
|---|---|---|
| Manufacture | 3.2.S.2 | 3.2.P.3 |
| Specifications and analytical controls | 3.2.S.4 | 3.2.P.5 |
| Reference standards/materials | 3.2.S.5 | 3.2.P.6 |
| Container closure | 3.2.S.6 | 3.2.P.7 |
| Stability | 3.2.S.7 | 3.2.P.8 |
Drug-product description/composition belongs under 3.2.P.1; pharmaceutical development under 3.2.P.2; excipient controls under 3.2.P.4. Appendices sit under 3.2.A, regional quality information under 3.2.R and quality literature references under 3.3. ICH M4Q(R1), September 12, 2002.
For example, finished-product stability data map to 3.2.P.8.3 in FDA's table of contents. Their quality-summary discussion belongs in the corresponding QOS content, not in place of the data. If a file is named only “stability report,” identify whether it concerns the substance or finished product, and whether it is data, a summary or a protocol, before assigning a final section. FDA detailed quality headings.
Use the Module 3 structure reference for the complete hierarchy and the Module 3 quality guide for content preparation. A module overview cannot establish that a particular CMC package is scientifically complete.
Modules 4 and 5: route reports by their purpose
Module 4 groups nonclinical reports into pharmacology, pharmacokinetics and toxicology. Module 5 organizes clinical evidence into more specific report categories. The lookup below preserves those distinctions without reproducing every study-tagging rule.
| Report or material | Main location | Scope cue |
|---|---|---|
| Nonclinical pharmacology report | 4.2.1 | Select the pharmacology subtype |
| Nonclinical pharmacokinetic report | 4.2.2 | Distinguish absorption, distribution, metabolism and other subtypes |
| Repeat-dose toxicity report | 4.2.3.2 | Supporting report, not the toxicology summary |
| Tabular listing of clinical studies | 5.2 | Listing rather than report body |
| Biopharmaceutic study report | 5.3.1 | Includes relevant bioavailability/bioequivalence branches |
| PK study using human biomaterials | 5.3.2 | Distinct from the clinical PK study categories |
| Human PK study report | 5.3.3 | Select the applicable population or factor branch |
| Human PD study report | 5.3.4 | Select the relevant PD category |
| Controlled efficacy/safety study report | 5.3.5.1 | Confirm the report's study purpose and applicable classification |
| Report of postmarketing experience | 5.3.6 | Distinct from administrative commitment correspondence |
| Case report forms/individual patient listings | 5.3.7 | Follow applicable regional handling |
The nonclinical framework is described in ICH M4S(R2), and the clinical framework in ICH M4E(R2), June 15, 2016. FDA's comprehensive table of contents supplies the detailed headings and related-information mapping used in these examples.
A study involving human biomaterials should not automatically be treated as a Module 4 report because it occurred in vitro. Likewise, “Phase 1” alone does not tell you the final report category: review the study's purpose. For expanded placement, use the Module 4 guide and Module 5 guide.
Content headings, folders and XML are different layers
The content heading tells the reviewer what a document is. Its metadata establishes how it appears and behaves in the electronic submission. Its physical path identifies the stored file. A plausible filename does not prove correct placement, and correct placement does not prove the package is technically valid.
A limited v3.2.2 file-location example
ICH's eCTD specification v3.2.2, July 16, 2008, places index.xml and its checksum file in the submission sequence directory. The regional XML backbone belongs inside the relevant regional Module 1 directory. ICH specification, section 6 and Table 6-2.
0000/
index.xml
index-md5.txt
m1/
us/
us-regional.xmlThis excerpt shows selected file locations for a US v3.2.2 example. It omits content, utility files and other required elements; it is not a complete submission template. Do not put the regional XML at the sequence root just because a simplified diagram shows it beside index.xml.
FDA eCTD v4.0 uses a submissionunit.xml message to organize ICH and regional content. Context of Use and associated keywords establish document placement. Consult the separate Technical Conformance Guide, version 1.5, June 2026, and the supported implementation guide and controlled vocabularies. Do not reuse a v3.2.2 index.xml/DTD example as a universal v4.0 design. FDA's implementation status page distinguishes new v4.0 applications from future forward-compatibility implementation for existing v3.2.2 applications.
There is no single path-length or filename rule established here for every version and authority. A path below an assumed “180-character limit” has not thereby passed technical validation. Use the applicable rule set in the file-naming guide, and the XML backbone guide for implementation details.
A sequence is not the entire current dossier
Later submissions can update an existing dossier. The current view depends on the accumulated content and its lifecycle relationships, not just the files in the latest sequence directory. The v3.2.2 specification describes the leaf operations used for that lifecycle. ICH eCTD v3.2.2, section 6.
This matters during review: a later sequence containing only changed quality material is not automatically missing four modules. Determine what that submission is intended to update and inspect it in the application's existing context. Conversely, finding all five module folders does not establish that the required content is present.
For v4.0, the FDA guide describes lifecycle handling through context groups. A folder rename alone cannot express the intended regulatory change. Review the document's placement, the content it updates and the relevant metadata together before accepting the resulting dossier view. FDA v4.0 Technical Conformance Guide, section 1.5.4.
Worked document-placement check
Assume a team is planning content for a US application and using FDA's v3.2.2 table of contents cited above. These synthetic inputs demonstrate placement reasoning, not application completeness or a validated submission.
| Supplied item | Placement decision | Reason |
|---|---|---|
| Quality Overall Summary | 2.3 | Summary of quality evidence |
| Finished-product stability data | 3.2.P.8.3 | Product data rather than substance data or QOS |
| Repeat-dose animal toxicity report | 4.2.3.2 | Nonclinical toxicology report |
| Controlled efficacy/safety study report | 5.3.5.1 | Report category specified in the input |
| Environmental analysis | 1.12.14 | US regional heading |
| File named “stability-final.pdf,” with no other information | Unresolved | Need substance/product identity and document function |
Now change the destination to the EU: the environmental document's Module 1 mapping must be reconsidered using EU 1.6 and its relevant subcategory. Change only the electronic version to v4.0: the scientific document purpose remains, but the electronic implementation must be mapped using the v4.0 specifications. Neither change is solved by renaming a folder.
Before releasing a placement plan, record the document's function, product or study identity, selected section, receiving region, electronic version and source specification. Have unresolved inputs clarified before packaging. Then review the published package's navigation, metadata and document relationships under the applicable technical rules. This keeps a useful content map from being mistaken for evidence that the submission is ready to transmit.
About the author
Assyro Team
Expert regulatory operations consultants helping pharmaceutical companies navigate complex compliance challenges.

