CTD and eCTD: Building a High-Quality Regulatory Submission

Introduction

In the pharmaceutical industry, a high-quality regulatory submission is essential for obtaining marketing authorization, maintaining product registrations, and ensuring compliance with applicable health authority requirements. As regulatory expectations evolve and submission volumes increase, pharmaceutical companies must establish structured, accurate, and consistent approaches to compiling and managing regulatory documentation.

The Common Technical Document (CTD) provides a harmonized structure for presenting the quality, safety, and efficacy information required to support the registration of a medicinal product. The electronic Common Technical Document (eCTD) builds on this structure by providing an electronic format for submitting, reviewing, and maintaining regulatory information throughout a product’s lifecycle.

Although CTD and eCTD are closely related, they serve different purposes. CTD defines how the dossier is organized, while eCTD defines the electronic structure and technical framework used to submit and manage the dossier in supported regulatory environments.

A successful submission requires more than collecting documents and placing them into predefined folders. It depends on scientific accuracy, regulatory strategy, document consistency, technical validation, effective cross-functional collaboration, and a clear understanding of the requirements of the target health authority.

This article explores the key differences between CTD and eCTD, the structure of a regulatory dossier, the responsibilities of the teams involved, and the procedures that help organizations build high-quality regulatory submissions.

1. Understanding the Common Technical Document (CTD)

The Common Technical Document is a harmonized format developed through the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH).

Its primary objective is to organize regulatory information in a standardized format, making submissions more consistent and facilitating regulatory review across participating regions.

The CTD is generally organized into five modules, each serving a specific purpose.

Module 1: Regional Administrative Information

Module 1 contains administrative and regional information required by the relevant health authority.

Depending on the jurisdiction and submission type, it may include:

• Application forms and administrative documents
• Product information, including labeling and package leaflets
• Manufacturing and marketing authorization details
• Local regulatory certificates and declarations
• Information concerning the applicant or marketing authorization holder
• Regional-specific requirements and supporting documents

Regulatory consideration: Module 1 is region-specific. Applicants must verify the applicable requirements of the target authority rather than assuming that a dossier prepared for one market can be submitted unchanged to another.

Module 2: CTD Summaries

Module 2 provides an overview of the information presented in Modules 3, 4, and 5.

It includes the quality overall summary, nonclinical and clinical overviews, and relevant written and tabulated summaries.

Its purpose is to help reviewers understand the key scientific findings and navigate the supporting evidence.

The summaries must accurately reflect the detailed information in the underlying modules. Any inconsistency between a summary and its supporting reports may raise questions during regulatory review.

Module 3: Quality

Module 3 contains the pharmaceutical quality documentation supporting the product’s quality, manufacturing, and control strategy.

Depending on the product, it may include:

• Drug substance information
• Drug product composition and formulation
• Manufacturing processes and controls
• Specifications and analytical procedures
• Validation and verification data
• Stability studies and proposed shelf life
• Container closure system information
• Relevant quality risk assessments

The Regulatory Affairs team coordinates the presentation of the information, while Quality Assurance, Quality Control, Manufacturing, Analytical Development, and other technical teams provide and review the supporting evidence.

Module 4: Nonclinical Study Reports

Module 4 contains nonclinical study reports supporting the assessment of the product’s safety, including relevant pharmacology, pharmacokinetics, and toxicology information.

The specific documentation required depends on the product, development pathway, and applicable regulatory requirements.

Nonclinical experts and regulatory specialists must ensure that the submitted evidence is complete, appropriately referenced, and consistent with the conclusions presented in Module 2.

Module 5: Clinical Study Reports

Module 5 contains clinical study reports and associated documentation supporting the assessment of the product’s safety and efficacy.

Depending on the product and application, it may include clinical pharmacology studies, efficacy and safety studies, and relevant post-marketing or other clinical evidence.

Clinical Development, Medical, Biostatistics, and Regulatory Affairs teams contribute to ensuring that the evidence is accurately represented and appropriately linked to the summaries and product information.

For generic products and certain other application types, the scope of Modules 4 and 5 may differ according to the applicable legal basis and regulatory pathway.

2. What Is the Electronic Common Technical Document (eCTD)?

The electronic Common Technical Document is the electronic implementation of the CTD structure. It enables regulatory submissions to be assembled, transmitted, reviewed, and maintained electronically where accepted by the relevant health authority.

An eCTD submission is not simply a scanned copy of a paper dossier or a collection of PDF documents.

It includes a defined electronic structure, metadata, document organization, and lifecycle information. The submission sequence and associated technical components allow the authority to identify documents, understand their placement, and track changes across subsequent submissions.

Key elements include:

• Documents organized according to the applicable CTD structure
• An electronic backbone, commonly based on XML, that describes the submission structure
• Metadata identifying documents and their attributes
• Links and references where supported by the applicable specification
• Lifecycle operations for managing document replacement, addition, or deletion
• Technical validation to confirm that the submission meets the applicable specifications

The exact technical requirements depend on the relevant eCTD specification, implementation guidance, and health authority requirements.

Key distinction: CTD describes the dossier’s organizational structure; eCTD adds the technical framework required to manage that dossier electronically.

3. CTD vs. eCTD: Understanding the Difference

Although the terms are often used together, they should not be treated as interchangeable.

The appropriate format must always be confirmed with the target health authority. Not every authority, application type, or regulatory procedure necessarily follows the same eCTD implementation.

4. Building a High-Quality Regulatory Submission

A high-quality dossier is built through a controlled process rather than a final document-assembly exercise.

The following steps provide a practical framework.

Step 1: Define the Regulatory Strategy

Before dossier compilation begins, the Regulatory Affairs team should identify:

• The target market and competent authority
• The applicable application type
• The legal basis for the application
• The required submission format
• Applicable technical specifications and templates
• Local administrative requirements
• Expected submission milestones
• The need for translations, legalization, or local certificates
• Any product-specific guidance or authority requirements

This initial assessment reduces the risk of preparing a dossier that is scientifically complete but administratively or technically unacceptable.

Step 2: Conduct a Gap Assessment

The team should compare the available product documentation with the requirements of the target application.

The gap assessment should identify missing documents, outdated reports, inconsistent product information, expired certificates where relevant, and unresolved technical or regulatory questions.

Each gap should be assigned an owner, an agreed deadline, and an appropriate follow-up mechanism.

A gap tracker can help Regulatory Affairs monitor progress and escalate delays before they affect the planned submission date.

Step 3: Collect and Organize Source Documents

Source documents should be obtained from the functions responsible for generating and maintaining them.

Examples include:

• Quality documentation from Quality Assurance, Manufacturing, and Analytical Development
• Nonclinical and clinical reports from the relevant scientific teams
• Safety documentation from Pharmacovigilance
• Product information and administrative documents from Regulatory Affairs
• Certificates and supporting declarations from the appropriate internal or external stakeholders

Document owners should confirm that the information is current, approved where required, and appropriate for the intended regulatory purpose.

Step 4: Compile the Dossier

Regulatory Affairs coordinates the placement of documents in the appropriate CTD sections and ensures that the dossier presents a coherent regulatory narrative.

Compilation includes verifying document titles, section placement, references, cross-references, and consistency across modules.

The objective is to make the submission complete, logically organized, and easy for the reviewer to navigate.

Step 5: Perform Content and Quality Checks

Before submission, the dossier should undergo a structured review.

Content checks should cover completeness, consistency, document currency, scientific accuracy, and alignment with the application strategy.

Technical checks should cover the applicable file formats, document properties, hyperlinks, bookmarks, navigation, and other requirements specified by the relevant authority.

A technically valid submission may still contain scientific or administrative deficiencies. Both content quality and technical compliance must therefore be assessed independently.

Step 6: Obtain Final Approval and Submit

The responsible regulatory lead should confirm that required reviews and approvals have been completed.

The submission should then be transmitted through the authority’s accepted channel, with the applicable submission records and acknowledgments retained.

The submission date, sequence information where applicable, and evidence of successful transmission should be documented in the regulatory tracking system.

Step 7: Manage Regulatory Questions

Following submission, the authority may request clarification, additional data, revised documents, or other responses.

Regulatory Affairs should coordinate the response, assign questions to the appropriate subject-matter experts, track deadlines, and ensure that the final response is consistent across all affected documents.

All responses and subsequent submissions should be managed through controlled processes.

5. Roles and Responsibilities in CTD and eCTD Preparation

A high-quality submission requires clearly defined responsibilities and effective coordination across functions.

Regulatory Affairs

Regulatory Affairs typically leads the overall submission process.

Its responsibilities include defining the regulatory strategy, interpreting regional requirements, coordinating dossier compilation, managing submission timelines, conducting completeness checks, communicating with health authorities, and coordinating responses to regulatory questions.

Quality Assurance and Quality Control

Quality functions provide and review applicable quality-system documentation, manufacturing controls, specifications, analytical methods, validation information, and other quality evidence.

They help ensure that the documentation accurately reflects approved processes and the product’s established control strategy.

Manufacturing and Technical Operations

These teams provide manufacturing process descriptions, site information, process controls, and relevant supporting documentation.

They must ensure that the information supplied is consistent with the actual manufacturing arrangements and the proposed regulatory application.

Clinical and Nonclinical Teams

These functions supply and review study reports, supporting data, and scientific interpretations relevant to the product’s safety and efficacy.

They help ensure that summaries accurately represent the underlying evidence.

Pharmacovigilance

Pharmacovigilance contributes relevant safety information, including applicable safety documentation and information required to support the product’s safety profile or risk management activities.

The precise documentation required depends on the product, application type, and jurisdiction.

PV and Regulatory Affairs should coordinate closely when safety information affects product labeling, risk management documentation, or responses to authority questions.

Publishing and Regulatory Operations

Where a dedicated publishing function exists, it manages the technical preparation of electronic submissions.

Responsibilities may include document formatting, metadata assignment, hyperlink and bookmark checks, electronic backbone generation, lifecycle operations, and technical validation.

For organizations without a dedicated publishing team, these responsibilities should still be assigned to trained personnel or a qualified service provider.

Project Management

Project management supports the overall process through timelines, action trackers, risk monitoring, escalation, meeting coordination, and follow-up with document owners.

Clear accountability is especially important when several departments, external manufacturers, consultants, or local partners contribute to one submission.

6. eCTD Publishing and Technical Validation

Technical validation is a critical step in eCTD preparation.

A submission can contain all the expected scientific documents and still encounter technical rejection if it does not meet the applicable electronic submission requirements.

Depending on the authority and specification, validation may examine:

• Correct directory and file structure
• XML backbone integrity
• Valid document references
• Required metadata
• Accepted file formats
• Document readability
• Hyperlinks and bookmarks
• Lifecycle operations
• Sequence and submission identifiers
• Compliance with applicable technical validation criteria

Validation tools can identify errors and warnings, but the results must be reviewed by qualified personnel.

An error may require correction before submission, while a warning may require investigation and a documented decision. The appropriate response depends on the applicable validation criteria and authority requirements.

The publishing team should maintain evidence of validation, resolve relevant issues, and ensure that the final submission package corresponds to the approved dossier.

7. Lifecycle Management: Maintaining the Dossier After Approval

Regulatory submissions do not end with the initial marketing authorization application.

Throughout a product’s lifecycle, companies may need to submit variations, renewals, safety-related updates, manufacturing changes, labeling revisions, and other regulatory updates.

In eCTD environments, subsequent submissions are managed using defined lifecycle operations and sequences. These operations help authorities understand how new documents relate to previously submitted information.

Effective lifecycle management requires:

• Maintaining a complete submission history
• Tracking the status of approved and pending changes
• Linking new information to the relevant previous submission
• Ensuring that document replacement and deletion operations are correct
• Retaining records of authority correspondence and decisions
• Keeping internal regulatory systems aligned with the submitted dossier
• Ensuring that applicable country-specific requirements are met

Poor lifecycle management can create confusion about which documents are current and which versions were submitted or approved.

A robust regulatory information management process helps preserve traceability and supports future variations, renewals, and inspections.

8. Common Challenges and How to Prevent Them

Several recurring issues can compromise submission quality.

Incomplete documentation

Prevention: Conduct a structured gap assessment early, assign document owners, and track outstanding items against agreed deadlines.

Inconsistencies between modules

Prevention: Cross-check product names, strengths, dosage forms, manufacturing details, specifications, and other relevant information throughout the dossier.

Outdated or uncontrolled documents

Prevention: Use controlled document repositories, verify version status, and ensure that the submitted files have undergone the required review and approval.

Incorrect regional requirements

Prevention: Confirm the target authority’s current requirements and application-specific guidance before compilation.

Technical validation errors

Prevention: Apply the relevant validation criteria early enough to resolve issues before the submission deadline.

Weak cross-functional coordination

Prevention: Define responsibilities, establish clear review timelines, and escalate delays that threaten submission readiness.

Poor lifecycle traceability

Prevention: Maintain accurate submission records, sequence histories where applicable, and controlled links between current and historical documents.

9. Regulatory Compliance and Inspection Readiness

A high-quality submission process should be supported by documented procedures and appropriate quality oversight.

Organizations should establish procedures covering dossier preparation, document review, approval, electronic publishing where applicable, submission authorization, validation, transmission, and archival.

Records should demonstrate who prepared, reviewed, approved, and submitted the dossier, along with how identified issues were resolved.

Periodic process reviews can help identify recurring errors, improve submission timelines, and strengthen compliance.

For multinational organizations, global procedures should be complemented by local regulatory assessments. Requirements may differ between authorities in submission formats, administrative documents, electronic portals, validation rules, and post-approval procedures.

The guiding principle is to maintain a consistent global quality approach while meeting the specific requirements of each target market.

10. Measuring Submission Quality

Organizations can use performance indicators to evaluate and improve their regulatory submission processes.

Potential indicators include:

• First-pass technical validation success rate
• Number of critical errors identified before submission
• Frequency of incomplete or outdated source documents
• Percentage of deliverables received by the agreed deadline
• Number of authority questions attributable to avoidable dossier inconsistencies
• Time required to compile and publish a submission
• Timeliness of responses to regulatory questions
• Accuracy of regulatory tracking and archival records

These indicators should be interpreted in context. For example, the number of authority questions does not necessarily indicate poor submission quality, as questions may reflect legitimate scientific or regulatory concerns.

The purpose of performance monitoring is to identify process weaknesses, improve efficiency, and strengthen the quality of regulatory deliverables.

11. The Future of Regulatory Submissions

Regulatory operations are increasingly supported by digital document management, structured content, automation, and regulatory information management systems.

These tools can improve document traceability, reduce repetitive manual tasks, and support more consistent submission preparation.

However, automation does not remove the need for qualified review.

Organizations must still verify document accuracy, metadata, technical output, and compliance with the applicable requirements. Changes to systems, templates, and publishing workflows should be appropriately assessed and controlled.

As electronic submission practices continue to evolve, regulatory teams should monitor relevant ICH guidance, technical specifications, and health authority implementation updates.

The most effective approach combines standardized processes, reliable technology, qualified personnel, and strong quality oversight.

Baupharma Regulatory Submission Support

Baupharma supports pharmaceutical companies with Submission & Registration Excellence, including CTD dossier development, eCTD and NeeS preparation and publishing, technical accuracy, and country-specific adaptation. These services support structured submission preparation and regulatory compliance across relevant markets, from dossier compilation to health authority query management.

Key Takeaways

• CTD standardizes dossier organization, while eCTD provides an electronic framework for submission and lifecycle management.
• A CTD dossier contains five modules covering regional administrative information, summaries, quality, nonclinical data, and clinical data.
• Module 1 is region-specific, making local regulatory assessment essential.
• High-quality submissions depend on accurate documentation, cross-module consistency, effective project management, and early gap assessment.
• Regulatory Affairs coordinates the submission, while scientific, quality, manufacturing, pharmacovigilance, and publishing teams contribute according to their responsibilities.
• eCTD technical validation is essential where the format is required or accepted, but technical validation does not replace scientific and regulatory review.
• Lifecycle management preserves traceability across variations, renewals, and other subsequent submissions.
• Controlled procedures, clear accountability, and documented quality checks strengthen regulatory compliance and inspection readiness.
• Organizations should monitor applicable authority requirements because submission formats and technical expectations can vary by jurisdiction.
• Ultimately, a high-quality regulatory submission is not simply a complete dossier; it is an accurate, consistent, technically compliant, and well-controlled presentation of the evidence required for regulatory decision-making.

Ultimately, a high-quality regulatory submission is not simply a complete dossier; it is an accurate, consistent, technically compliant, and well-controlled presentation of the evidence required for regulatory decision-making.