eCTD Module 1 Explained: Region-Specific Administrative Information

Module 1 is where most eCTD submissions go wrong — and ironically, it is the most underestimated module of the entire CTD structure.

eCTD Module 1 Explained: The Complete Guide to Region-Specific Requirements

If you’ve worked with eCTD submissions, you know that Module 1 stands apart from the rest of the Common Technical Document. While Modules 2 through 5 follow a harmonized, globally standardized structure, Module 1 is deliberately region-specific—designed to accommodate the unique administrative, legal, and regulatory requirements of each health authority.

This guide provides a thorough explanation of eCTD Module 1, covering its purpose, structure, regional variations, and the operational challenges regulatory teams face when assembling it. Whether you’re new to regulatory affairs or a seasoned professional looking for a consolidated reference, this eCTD module 1 explained resource will help you navigate this critical submission component.

Where Module 1 Fits in the CTD Structure

The Common Technical Document comprises five modules:

• Module 1: Administrative and regional information (region-specific)
• Module 2: Summaries and overviews
• Module 3: Quality documentation
• Module 4: Nonclinical study reports
• Module 5: Clinical study reports

Modules 2 through 5 were harmonized through ICH guidelines, enabling sponsors to prepare a single set of technical documentation for submissions worldwide. Module 1, however, was intentionally excluded from harmonization. Each regulatory authority requires different administrative forms, application types, fee structures, labeling formats, and legal certifications.

This design reflects a practical reality: while the science behind a drug product is universal, the administrative and legal frameworks governing its approval are not. Understanding this distinction is fundamental to eCTD module 1 explained in proper context.

Why Every Health Authority Has Its Own Module 1 Specification

Health authorities maintain independent Module 1 specifications for several reasons:

• Legal frameworks differ: Patent certifications, exclusivity claims, and establishment registration requirements vary by jurisdiction
• Application types vary: NDAs, ANDAs, BLAs, INDs, CTAs, MAAs, and their regional equivalents each have unique documentation requirements
• Labeling regulations differ: Prescribing information formats, patient leaflets, and packaging requirements follow regional standards
• Administrative processes differ: Fee payment documentation, agent authorizations, and correspondence protocols are jurisdiction-specific

This means regulatory teams must maintain familiarity with multiple Module 1 specifications and update their knowledge as health authorities revise their requirements—often multiple times per year.

Module 1 Sections: General Structure

While specific section numbers and headings vary by region, most Module 1 specifications include these core components:

Cover Letter

The cover letter introduces the submission, identifies the application type, summarizes the submission contents, and highlights any specific requests or time-sensitive matters requiring reviewer attention.

Application Forms

Region-specific forms that capture product identification, sponsor information, manufacturing sites, and application-specific data. These forms often require electronic signatures and must match the current version published by the health authority.

Administrative Information

This section encompasses correspondence history, meeting requests and minutes, patent information, exclusivity claims, establishment information, and agent authorizations.

Labeling

Draft or final prescribing information, patient labeling, container labels, and carton labeling. Many regions require both clean and annotated versions showing changes from previous submissions.

Environmental Risk Assessment

Where applicable, environmental assessment documentation or categorical exclusion claims. Requirements vary significantly between FDA, EMA, and other authorities.

Investigator’s Brochure

For clinical trial applications, the current Investigator’s Brochure is typically placed in Module 1, though its location varies by region.

Regional Variations in eCTD Module 1

FDA Module 1 (United States)

FDA’s Module 1 structure includes:

• 1.1 Forms: FDA Forms 356h, 1571, 1572, 2252, and others depending on application type
• 1.2 Cover Letter: Submission introduction and content summary
• 1.3 Administrative Information: Contact information, patent certifications (Paragraph IV, etc.), exclusivity requests, and debarment certifications
• 1.4 References: Letters of authorization, DMF references
• 1.14 Labeling: Draft labeling, SPL files
• 1.15 Annotated Labeling: Track-changes versions showing modifications
• 1.16 Risk Evaluation and Mitigation Strategies (REMS)

FDA requires Structured Product Labeling (SPL) format for labeling, which presents unique technical requirements compared to other regions.

EU Module 1 (EMA and National Competent Authorities)

The EU Module 1 follows EMA’s specification and includes:

• 1.0 Cover Letter
• 1.2 Application Form: The eAF (electronic Application Form)
• 1.3 Product Information: SmPC, Package Leaflet, Labeling texts
• 1.4 Expert Information: Quality, nonclinical, and clinical expert statements
• 1.5 Specific Requirements: Including Environmental Risk Assessment, Orphan Drug documentation, Pediatric Investigation Plans
• 1.6 Environmental Risk Assessment
• 1.7 Orphan Drug Documentation
• 1.8 Other Information: Including responses to questions, commitments

The Investigator’s Brochure in EU submissions typically resides in Module 1.8.2 for clinical trial applications.

Health Canada

Health Canada maintains separate Module 1 structures for Clinical Trial Applications (CTAs) and New Drug Submissions (NDS). Key differences include specific administrative forms, regional labeling requirements in both English and French, and unique sections for Drug Identification Numbers (DINs).

PMDA (Japan)

Japan’s Module 1 accommodates Japanese-language documentation requirements, specific application forms (FD applications), and unique administrative requirements. PMDA also requires Japanese translations of key documents and specific formatting for manufacturing information.

Other Regulatory Authorities

Swissmedic (Switzerland): Follows a structure similar to EU but with Swiss-specific administrative requirements and fee documentation.

GCC (Gulf Cooperation Council): Requires specific registration forms, GCC-DR administrative documentation, and product information in Arabic.

MHRA (United Kingdom): Post-Brexit, MHRA maintains its own Module 1 specification that diverges from EU requirements in administrative sections while maintaining some structural similarities.

ANVISA (Brazil): Requires Portuguese-language documentation, specific Brazilian administrative forms, and region-specific stability data references in Module 1.

The 5 Most Common Module 1 Mistakes

Based on common validation errors and health authority feedback, these Module 1 mistakes occur frequently:

1. Wrong Cover Letter Format

Each region specifies cover letter content requirements. FDA expects specific elements including application numbers and cross-references, while EMA has different expectations. Avoidance strategy: Maintain region-specific cover letter templates and update them when guidance changes.

2. Missing or Outdated FDA Forms

FDA regularly updates form versions, and submitting an outdated form can trigger a Refuse to Receive. Avoidance strategy: Verify form versions against FDA’s current list immediately before submission assembly. Modern publishing tools can flag outdated form versions automatically.

3. Inconsistent Labeling References

Labeling in Module 1 must align with labeling references elsewhere in the submission. Version mismatches between draft labeling and annotated labeling create review confusion. Avoidance strategy: Implement a labeling version control process that tracks document versions across submission sections.

4. Wrong File Naming Conventions

Each region specifies file naming rules—character limits, allowed characters, and naming patterns. Non-compliant file names fail validation. Avoidance strategy: Use publishing tools with built-in file name validation for each target region.

5. Missing Regional Metadata in index.xml

The eCTD backbone (index.xml) requires region-specific metadata elements. Missing or incorrect metadata causes validation failures. Avoidance strategy: Use validated publishing tools that auto-generate correct regional metadata based on submission parameters.

How Modern Publishing Tools Auto-Build Module 1

Contemporary eCTD publishing platforms dramatically reduce Module 1 assembly effort through automation:

• Region selectors: Choose the target health authority, and the system presents only relevant Module 1 sections and requirements
• Template libraries: Pre-configured templates for cover letters, administrative documents, and regional forms
• Metadata-driven assembly: Enter product information once; the system populates it across all required locations
• Integrated validation: Real-time validation against current regional specifications catches errors before submission
• Form version management: Automatic alerts when regulatory forms are updated

This automation is particularly valuable for Module 1, where regional complexity creates significant manual effort and error risk in traditional document-based workflows.

Module 1 Lifecycle: Why Replace Operations Are Tricky

eCTD submissions use lifecycle operations—new, append, replace, and delete—to manage document versions across submission sequences. Module 1 replace operations present unique challenges:

• Form replacements: When replacing FDA forms, the new version must maintain proper cross-references to existing submission content
• Labeling updates: Replacing labeling documents requires coordinating clean and annotated versions while maintaining reviewer context
• Administrative updates: Some administrative documents can be replaced; others require append operations depending on regional rules
• Lifecycle tracking: Module 1 documents often have different replacement rules than Module 2-5 documents, requiring careful lifecycle management

Understanding these nuances is essential when planning submission sequences, particularly for amendments, supplements, and variations that modify previously submitted Module 1 content.

Frequently Asked Questions

Is Module 1 required for every eCTD submission?

Yes. Every eCTD submission to any health authority requires a Module 1 section. The contents vary by submission type—an amendment may have a minimal Module 1 with just a cover letter, while an original application requires comprehensive administrative documentation.

Can I reuse Module 1 content across different regions?

Some content, such as reference lists and certain administrative information, may be adaptable across regions. However, application forms, labeling, and many administrative documents are strictly region-specific and must be prepared individually for each health authority.

How often do health authorities update their Module 1 specifications?

Update frequency varies by authority. FDA, EMA, and Health Canada typically issue multiple updates per year, ranging from minor clarifications to significant structural changes. Regulatory teams should subscribe to health authority notification systems and review specifications before each submission.

What happens if my Module 1 fails validation?

Validation failures must be corrected before the submission is accepted for review. Technical validation failures (file naming, XML structure) prevent gateway acceptance. Content-related issues may result in Refuse to Receive or information requests that delay review timelines.

How does eCTD Module 1 differ for clinical trial applications versus marketing applications?

Clinical trial applications (INDs, CTAs) include Investigator’s Brochure and protocol-related documents in Module 1, while marketing applications (NDAs, MAAs) emphasize labeling, patent certifications, and post-marketing commitments. The administrative form requirements differ substantially between these application types.