eCTD Lifecycle Management: Sequences, Amendments, and Version Control

eCTD Lifecycle Management: Sequences, Amendments, and Version Control

Key Takeaways

What Is eCTD Lifecycle Management?

The eCTD (electronic Common Technical Document) is not a single submission. It is a living dossier that evolves over the lifetime of a drug application. From the original submission through amendments, supplements, annual reports, and responses to agency questions, the eCTD grows as an accumulation of sequences, each containing documents that build upon, modify, or supersede documents in prior sequences.

Lifecycle management is the mechanism that keeps this dossier coherent. Without it, regulatory reviewers would have no way to determine which version of a document is current, which documents have been superseded, and what the complete, current state of the application looks like at any point in time.

The eCTD lifecycle is governed by ICH M2 and M8 specifications, with regional implementations defined by FDA (US), EMA (EU), Health Canada, PMDA (Japan), and other regulatory authorities.

eCTD Sequence Numbering

How Sequences Work

Every submission to a regulatory authority within a single application receives a unique, four-digit sequence number, starting at 0000. Sequences are numbered sequentially and cannot be reused or skipped.

Rules for Sequence Numbering

1. Sequence numbers are strictly sequential. You cannot skip numbers. If the last submitted sequence was 0015, the next must be 0016, regardless of the submission type.
2. Each sequence has exactly one submission type. A sequence cannot contain both a supplement and an annual report. Each submission type gets its own sequence.
3. Agency sequences count. In the US, FDA may issue sequences (e.g., approval letters, complete response letters) that consume sequence numbers in the lifecycle. The applicant must account for these when numbering their next submission. FDA publishes acknowledgment sequences that the applicant must incorporate.
4. Sequence numbers are per-application. Each NDA, ANDA, or BLA has its own independent sequence numbering. Sequence 0005 for NDA 123456 has no relationship to sequence 0005 for NDA 789012.

Sequence Directory Structure

Each sequence is a directory within the eCTD application folder:

Lifecycle Operations

The Four Operations

Every document included in an eCTD sequence must be assigned a lifecycle operation that tells the receiving authority what to do with that document relative to the existing dossier. The four operations defined in the ICH eCTD specification are:

When to Use Each Operation

New: Used in the original submission (sequence 0000) for all documents, and in subsequent sequences when a document is being submitted at a location where no document previously existed.

Example: Submitting a new stability study report in Section 3.2.P.8 that was not included in the original application.

Append: Used when adding an additional document at the same CTD section without replacing the existing document. Both the original and appended documents remain active in the dossier.

Example: Adding a second validation report to Section 3.2.P.5 alongside the existing validation report. Both reports are relevant and current.

Replace: Used when a document supersedes a previously submitted document. The previous document is marked as replaced, and the new document becomes the current version at that location. The replace operation must reference the document being replaced (by its unique leaf ID).

Example: Submitting an updated Quality Overall Summary (Section 2.3) that supersedes the version submitted in sequence 0000. The old version is retained in the dossier history but is no longer the current document.

Delete: Used to remove a document from the active dossier. The document is not physically deleted from the eCTD archive; it is marked as deleted in the lifecycle. Delete operations must reference the document being deleted.

Example: Removing a stability study report that was submitted in error or that is no longer applicable.

Lifecycle Operation Rules

The eCTD XML Backbone

Structure of the XML Backbone

The eCTD XML backbone is the metadata file that describes the contents and lifecycle state of each sequence. For US submissions, this file follows the FDA regional DTD and schema specifications.

Key elements of the XML backbone relevant to lifecycle management:

In a subsequent sequence replacing this document:

The modified-file attribute references the leaf ID of the document being replaced, creating the lifecycle chain.

Leaf IDs and Document Tracking

Each document (leaf) in the eCTD is assigned a unique identifier. This ID is used to track the document across the lifecycle. The leaf ID format and generation method vary by publishing tool, but it must be unique within the application.

The lifecycle chain for a document might look like:

At any point, a reviewer can trace the complete history of the document by following the modified-file references backward through the sequences.

Amendment vs. Supplement Sequences

Amendments

An amendment is a submission that adds to or modifies a previously submitted sequence. Amendments are used to:

• Respond to FDA Information Requests during review
• Provide additional data requested by the agency
• Correct errors in a previous submission
• Submit data that was not available at the time of the original submission

An amendment gets its own sequence number and references the sequence it is amending. In the US regional envelope, the amendment identifies the related sequence.

Supplements

A supplement is a new submission type (PAS, CBE-30, CBE-0) that proposes a change to the approved application. A supplement also gets its own sequence number. The supplement's eCTD sequence contains only the modules and sections affected by the proposed change, plus required Module 1 administrative documents.

Relationship Between Amendments and Supplements

A supplement may have its own amendments. For example:

Each of these sequences is a separate eCTD submission with its own XML backbone, but they are linked through the regional envelope metadata indicating their relationship.

Document Versioning Best Practices

File Naming Conventions

While the eCTD specification does not mandate specific file naming conventions (the XML backbone handles document identification), consistent naming practices improve internal management:

Internal Version Control

Regulatory publishing teams should maintain an internal document inventory that tracks:

Common Versioning Errors

Regional Lifecycle Differences

US (FDA)

FDA's eCTD implementation follows the US Regional DTD and Technical Conformance Guide. Key regional specifics:

EU (EMA)

EMA's implementation differs in several ways:

Canada (Health Canada)

Japan (PMDA)

The Submission Tracking File (STF)

Purpose

Some regions use or have used a Submission Tracking File to provide a high-level overview of the submission lifecycle. The STF is a separate XML file that tracks the sequence of submissions, their types, and their relationships.

Current Status by Region

Managing Complex Lifecycle Scenarios

Scenario 1: Concurrent Supplements

When an applicant has multiple supplements under review simultaneously, lifecycle management becomes more complex. Each supplement is filed as a separate sequence, but both may modify the same sections of the application.

Example:

Both supplements reference the same Section 3.2.P.3 document. If Supplement A is approved first, the document in Section 3.2.P.3 is now different from what Supplement B was originally filed against.

Resolution: The applicant should inform the review division about concurrent submissions. When the second supplement is approved, an amendment may be needed to reconcile the overlapping changes.

Scenario 2: Withdrawal and Resubmission

If an applicant withdraws a supplement, the sequence number is consumed (it cannot be reused). The resubmission gets a new sequence number.

Documents from the withdrawn sequence (0011) should not be referenced by lifecycle operations in subsequent sequences. The resubmission (0012) should use new operations for its documents, not replace operations referencing the withdrawn sequence.

Scenario 3: Agency-Initiated Changes

When FDA approves a supplement, it may require modifications to the proposed changes. The applicant must then submit a post-approval sequence incorporating FDA's required modifications.

The Sequence 0012 submission uses replace operations to update the documents affected by FDA's conditions.

Validation of eCTD Lifecycle

Pre-Submission Validation

Before submitting an eCTD sequence, the applicant should validate:

Common Validation Failures

Key Regulatory References

References