Every document submitted inside an eCTD sequence carries a hidden instruction most publishing teams never look at directly: a lifecycle operator, recorded on that document's "leaf" entry in the sequence's backbone XML. ICH M8 defines exactly four values for it — new, append, replace, delete — and treats the choice as a statement about what happened to the content, not a formatting preference. Publishing tools default this field quietly. The decision underneath it is not quiet at all.

What ICH M8 actually governs

The eCTD specification did not start under the M8 topic code. Early eCTD work sat inside the M2 Expert Working Group, the ICH group responsible for electronic standards generally. In November 2010, the ICH Steering Committee endorsed a dedicated Expert Working Group and Implementation Working Group for the eCTD, assigning it the topic code M8 and carrying forward the work the eCTD sub-group had already been doing inside M2. The specification that resulted — eCTD v3.2.2 — is still the backbone most submissions worldwide are built on, alongside the harmonized CTD structure M8's documents sit inside.

4
Lifecycle operators defined on every eCTD leaf: new, append, replace, delete.
1
Reference required on every replace or delete leaf, pointing to the exact prior leaf it acts on.
M2 → M8
The eCTD specification moved from the M2 Expert Working Group to its own M8 topic in Nov. 2010.

Four operators, each a different claim about your document

The operation attribute on a leaf is not cosmetic metadata. It is the mechanism by which the backbone reconstructs the application's current view — which documents are live, which have been superseded, and which have been withdrawn — across every sequence a sponsor has ever submitted. Each value makes a specific, checkable claim:

  • New. This leaf has no predecessor. It is the first time this document exists in the application.
  • Append. This leaf adds content without superseding anything already submitted — a genuine addition, not a revision.
  • Replace. This leaf supersedes a specific earlier leaf, identified by its unique ID. The reference is mandatory; the backbone has nothing else to tell it which document is being revised.
  • Delete. This leaf removes a specific prior leaf from the application's current view, again by reference. A delete leaf's title can be left empty — it is withdrawing something, not adding it.
The operator is not telling the viewer how to render a file. It is telling the reviewer what happened to your submission — and the viewer takes that claim at face value. Why a wrong reference is not a cosmetic error

Where this goes wrong, and what it costs

Three failure modes show up repeatedly once a publishing process relies on tool defaults instead of a deliberate classification step. Mark a genuine revision as new instead of replace, and the backbone treats it as an unrelated document — the current view can end up showing two coexisting versions of what should be one, and the lifecycle trail a reviewer would use to see what changed across sequences simply isn't there. Mark a genuinely new document as replace against the wrong prior leaf, and the reference either fails technical validation outright or, worse, resolves to a document it was never meant to supersede. Use append where a replace was called for, and a stale, superseded version keeps standing in the current view beside its intended update, leaving the reviewer to guess which one is authoritative.

A sequence-integrity check before your next submission
  1. Classify before you publish. For every document, decide — new, addition, revision, or withdrawal — before the publishing tool assigns an operator by default.
  2. Verify every reference. Confirm each replace or delete leaf's reference resolves to the exact prior leaf you intend, not merely to a leaf that happens to validate.
  3. Reconstruct the current view. Render the full application state from your sequence history and confirm it matches what you believe is live, superseded, and withdrawn.
  4. Audit your template defaults. If your eCTD publishing tooling defaults an operator without an explicit classification step, that default is making a regulatory decision no one reviewed.

None of this requires new tooling. It requires treating the operator field as the regulatory statement it is, built into regulatory operations as a checked step rather than left to whatever a template assumes. The cost of getting it wrong rarely shows up as a dramatic rejection — more often it surfaces as a reviewer unable to reconstruct what changed between sequences, which is its own kind of friction heading into a decision point like FDA's refuse-to-file gate. Teams that build the classification step into their CMC regulatory affairs workflow stop finding out about sequence problems from the agency.

Frequently asked questions

What are the eCTD lifecycle operators?

ICH M8's eCTD backbone (index.xml) assigns every submitted document, or "leaf," an operation attribute with one of four values: new (an initial document with no prior version), append (added content that does not supersede anything), replace (a document that supersedes an earlier leaf, referenced by its unique ID), and delete (removal of a leaf from the application's current view). Replace and delete both require a valid reference to the leaf they act on.

What happens if I use "replace" instead of "new" in an eCTD sequence?

The backbone reads it as a supersession, not a new document. If the reference points to the wrong prior leaf, or to one that does not exist, validation can reject the sequence outright. If the reference resolves but was never the intended predecessor, the current view silently shows the wrong document as authoritative, and the real revision history a reviewer would reconstruct no longer matches what actually happened.

Is eCTD v4.0 mandatory yet?

Not uniformly. Regions are moving on different timelines, and some have settled on binding dates while others have published only a roadmap. Confirm your target region's current eCTD v4.0 requirement directly with its agency before assuming v3.2.2 rules still govern your next submission.

Sources & further reading

  1. EMA. ICH M8 Electronic Common Technical Document (eCTD) v4.0 — Scientific Guideline. ema.europa.eu
  2. FDA. Providing Regulatory Submissions in Electronic Format — eCTD specifications and technical resources. fda.gov
  3. ICH M8 EWG/IWG. eCTD v4.0 Work Plan (2026). database.ich.org

This article is provided for general informational purposes and reflects the regulatory landscape as of November 2026. It is not legal or regulatory advice. Confirm current ICH M8 and regional eCTD requirements with the relevant agency or qualified counsel before acting.