Egypt’s Proposed Mandatory eCTD Framework: What EDA’s Draft Guidance Means for Pharmaceutical Companies

Egypt’s Proposed Mandatory eCTD Framework: What EDA’s Draft Guidance Means for Pharmaceutical Companies



Introduction


The Egyptian Drug Authority (EDA) has published a new draft regulatory guidance titled “Technical Guidance for eCTD Submissions in Egypt – Version 1/2026” for stakeholder consultation.

The draft represents an important step in Egypt’s transition towards a standardised electronic regulatory submission environment. It establishes detailed technical and lifecycle requirements for preparing, submitting and maintaining regulatory information in electronic Common Technical Document (eCTD) format.

Stakeholders may submit comments on the draft from 2 September until 14 October 2026.

Importantly, the guidance is currently published as a consultation draft. Its cover page does not yet specify an issue date or effective date, and it should therefore not be treated as a final, effective guideline at this stage.


What Is the Major Proposed Change?

The most significant feature of the draft is its mandatory approach to eCTD.

If finalised in its current form, the guidance would make eCTD the mandatory format for regulatory submissions falling within its scope in Egypt. Although the draft itself uses mandatory language, the applicable implementation timetable and effective date have not yet been announced.

The scope covers electronic regulatory submissions for human medicinal products, biological products and innovative products falling within EDA’s competence. This includes, among others:

  • Prescription medicinal products
  • Over-the-counter medicinal products
  • Small-molecule products
  • Biotechnology products
  • Vaccines
  • Blood products
  • Advanced therapy medicinal products

The draft is intended to apply throughout the regulatory lifecycle, including:

  • New marketing authorisation applications
  • Variations
  • Renewals
  • Active Substance Master Files
  • Plasma Master Files
  • Marketing authorisation withdrawals
  • Other submission types defined by EDA’s controlled vocabulary

From CTD Documents to an eCTD Lifecycle

One of the most important concepts for Regulatory Affairs teams is that an eCTD submission is not simply a CTD dossier converted into electronic folders.

Under the proposed framework, an eCTD application may comprise several regulatory activities. Each regulatory activity may, in turn, consist of one or more sequences submitted at different stages of the procedure.

For example, a regulatory activity could begin with an initial variation sequence and subsequently include separate sequences containing responses to validation issues, responses to questions or additional information.

Each sequence therefore becomes part of the cumulative regulatory lifecycle of the relevant eCTD application. The lifecycle must be maintained correctly so that EDA can identify the current and historical status of every submitted document.

This requires Regulatory Affairs teams to manage not only dossier content but also the relationships between:

  • Applications
  • Regulatory activities
  • Submission types
  • Submission units
  • Sequences
  • Related sequences
  • Documents and their lifecycle operations


Each Strength and Dosage Form Requires a Separate eCTD Lifecycle

This is one of the most important requirements for companies to consider when assessing their operational readiness.

According to the draft, an applicant should submit one eCTD application for each strength or dosage form. Each application would then be maintained independently throughout its regulatory lifecycle.

The draft states that submitting a single sequence covering more than one strength or dosage form would not be possible under the proposed approach.

For example, if the same product is available as:

  • 10 mg tablets
  • 20 mg tablets
  • Oral solution

Each strength and dosage form would require a separate eCTD application and a separately maintained lifecycle. Regulatory activities and subsequent sequences would need to be submitted and tracked independently for each applicable eCTD.

This requirement may significantly increase the number of individual applications and lifecycles that companies with large product portfolios need to establish and maintain.


What Does the Draft Define?

The draft goes considerably further than merely requiring companies to “submit in eCTD.” It establishes a proposed technical framework addressing areas such as:

  • eCTD application and sequence structure
  • Egyptian Module 1
  • Envelope metadata
  • Submission types and submission units
  • Egyptian submission modes
  • Procedure tracking and application identifiers
  • File formats and PDF requirements
  • File and folder naming
  • Document placement and granularity
  • XML requirements
  • Leaf lifecycle operations
  • Related sequences
  • Bookmarks and hyperlinks
  • Node extensions
  • Technical validation
  • Baseline submissions and re-baselining
  • Handling of Modules 2–5
  • New marketing authorisation applications
  • Variations and renewals
  • Active Substance Master Files
  • Plasma Master Files
  • Parallel variations
  • Withdrawals
  • Controlled vocabulary for Egyptian submissions

The proposed framework therefore affects both the technical construction of submissions and the internal regulatory processes used to prepare, approve, submit and maintain them.


What Happens to Existing Dossiers?

The draft addresses the transition of products whose dossiers are currently maintained in paper or non-eCTD electronic formats.

For an existing dossier, the next submission relating to a new regulatory activity would need to be submitted in eCTD format.

However, an ongoing regulatory activity that began in a previous format should be completed in the same format in which it started. For example, responses to questions relating to an ongoing variation submitted in non-eCTD format should continue in that format until the regulatory activity is completed.

The transition to eCTD would therefore apply to the next new regulatory activity rather than automatically converting every ongoing procedure.


Establishing a Baseline eCTD Submission

When transitioning from paper or a non-eCTD electronic format, the draft requires the applicant to establish a technical baseline.

A baseline submission is a compilation of the currently valid dossier documents that were previously submitted to EDA in another format. Its purpose is to make the valid regulatory documentation available within the new eCTD lifecycle.

The baseline should normally:

  • Be submitted as Sequence 0000
  • Be submitted separately from any new regulatory activity
  • Contain as much of the currently valid dossier as possible
  • State clearly in the cover letter that the dossier content has not changed and that only its format has changed
  • Use “none” as the submission type
  • Use “reformat” as the submission unit
  • Apply the lifecycle operation “new” to the included documents

The baseline must not include the first new regulatory activity. That activity would normally be submitted separately as Sequence 0001.

Where high-quality electronic source documents are unavailable, the draft indicates that good-quality scanned documents may be acceptable. Optical Character Recognition is preferred because it makes the documents searchable.


The Tracking Table Becomes Essential

The draft requires a sequence tracking table to be included in every submission across all procedure types.

The tracking table provides a consolidated record of the sequences submitted within the eCTD lifecycle. It helps EDA understand the purpose, regulatory activity, submission type, related sequence, submission unit and submission date associated with each sequence.

Companies will therefore need reliable internal controls to ensure that their sequence histories remain complete and consistent throughout the product lifecycle.


Technical Validation and Submission Through the EDA Portal

The draft indicates that eCTD submissions to EDA must be made through the designated EDA portal.

Each submission would undergo technical validation to assess whether the submitted package complies with the applicable eCTD specifications, Egyptian Module 1 requirements and EDA validation criteria.

Companies should distinguish between:

  • Technical validation, which examines whether the eCTD package has been constructed correctly; and
  • Regulatory content validation and assessment, which examine the completeness and substance of the submitted regulatory information.

A dossier may contain the required scientific and regulatory information but still fail technical validation because of an incorrect structure, invalid metadata, improper file naming, missing XML elements, broken lifecycle operations or other technical defects.

Technical validation should therefore become an integral part of the submission-preparation process rather than a final administrative check.


Why This Matters for Pharmaceutical Companies

The transition to eCTD is not simply a change in file format.

It changes how Regulatory Affairs teams prepare, publish, validate, submit, update, track and maintain regulatory dossiers throughout the product lifecycle.

Companies will need to consider their readiness in areas including:

  • eCTD publishing capabilities
  • Application and lifecycle management
  • Sequence planning and tracking
  • Document version control
  • Structured metadata
  • Egyptian Module 1 requirements
  • Document granularity
  • Lifecycle operations
  • Technical validation
  • Submission governance
  • Regulatory archiving
  • Staff training and responsibilities

The requirement to maintain separate lifecycles for different strengths and dosage forms may also substantially increase the operational workload for companies with large product portfolios.

Early preparation is therefore important, even while the guidance remains under consultation.


How Can Companies Begin Preparing?

While awaiting the final guidance and implementation timetable, Regulatory Affairs teams can begin taking practical preparatory steps.

1. Map the product portfolio

Identify every product, strength and dosage form that may require a separately maintained eCTD application.

2. Review existing dossier documentation

Determine whether the currently valid dossier documents are complete, accessible and available in suitable electronic formats.

3. Identify ongoing regulatory activities

Separate activities that may need to be completed in their existing format from future activities that may need to begin in eCTD.

4. Assess baseline readiness

Identify the documents that would be required to establish a baseline for each existing dossier and evaluate the quality of any scanned records.

5. Review document-management practices

Confirm that document versions, approval status, effective dates and regulatory history can be reliably identified and controlled.

6. Establish lifecycle governance

Define responsibility for assigning sequences, maintaining tracking tables, managing related sequences and applying document lifecycle operations.

7. Assess publishing and validation capabilities

Determine whether the company has the systems, technical resources and trained personnel required to construct and validate compliant eCTD submissions.

8. Train the relevant teams

Ensure that Regulatory Affairs, quality, medical, manufacturing and document-management personnel understand how their documents and processes will contribute to the eCTD lifecycle.

What Is Not Yet Final?

Because the document remains a consultation draft, companies should continue monitoring EDA communications before making final implementation decisions.

Matters that remain to be confirmed or may change include:

  • The final wording of the guidance
  • The official issue date
  • The effective date
  • The implementation timetable
  • Any phased rollout or transitional period
  • The final Egyptian Module 1 specification
  • The applicable validation criteria
  • The final controlled vocabularies
  • Detailed baseline content requirements
  • Portal procedures and technical requirements
  • Amendments resulting from stakeholder feedback
  • Any supplementary guidance or questions and answers issued by EDA

Companies should therefore begin preparing for the proposed framework while retaining sufficient flexibility to accommodate changes in the final requirements.


Looking Ahead

The publication of the draft is a significant signal of Egypt’s continued movement towards a more structured and digitally enabled regulatory submission environment.

The distinction between the current and future positions remains important:

Current position: Draft technical guidance published for stakeholder consultation.

Next stage: Final guidance, confirmed technical requirements and an official implementation timetable following EDA’s review of stakeholder feedback.

Regulatory teams should begin understanding the proposed requirements, evaluating their internal readiness and identifying potential operational gaps now. At the same time, implementation decisions should continue to be reviewed against the final guidance and any related technical documents subsequently issued by EDA.



How MODREG Supports Regulatory Readiness

The transition to eCTD will require companies to manage an increasing number of applications, regulatory activities, submission sequences, responsibilities and deadlines across their product portfolios.

MODREG EASE helps pharmaceutical and healthcare companies centralise, manage and track their regulatory portfolios and workflows. It enables Regulatory Affairs teams to monitor registration activities, variations, renewals, tasks, responsibilities, deadlines and supporting documents through one structured platform.

This becomes particularly important under the proposed eCTD framework, where separate lifecycles may need to be maintained for different product strengths and dosage forms. Effective regulatory tracking can help companies coordinate their internal workflows, maintain visibility over ongoing activities and prepare for the increased operational complexity associated with lifecycle-based submissions.

MODREG is also closely monitoring the finalisation of Egypt’s eCTD framework and the related technical, validation and submission requirements.

As part of the continued development of the MODREG ecosystem, MODREG PASS is being designed to support the future preparation, technical validation and lifecycle management of eCTD submissions in accordance with the requirements ultimately adopted by EDA.

The functionality and implementation of MODREG PASS will be aligned with the final EDA guidance, Egyptian Module 1 specifications, validation criteria and applicable portal or gateway requirements once officially issued.

Together, MODREG EASE and the planned MODREG PASS are intended to support companies across the broader regulatory journey—from managing regulatory portfolios and internal workflows to preparing for structured, lifecycle-based electronic submissions.

MODREG will continue publishing practical updates as EDA finalises the framework and provides further implementation details.

Official EDA Sources

EDA announcement and stakeholder consultation

Draft Technical Guidance for eCTD Submissions in Egypt – Version 1/2026

Stakeholder consultation closes on 14 October 2026.