eCTD Lifecycle Operations Checklist: New, Replace, Append, Delete
eCTD lifecycle operations checklist
New, replace, append and delete: what each operation needs, and the FDA, EU and Health Canada validation rules that check it — side by side.
The history the reviewer sees
Every leaf in an eCTD carries one of four operations. New adds a document. Replace supersedes one. Append adds to one. Delete removes one from the current view. Together they decide which version of each document a reviewer sees as current. A wrong choice is permanent once the sequence is sent, so the checks matter most before it goes.
Eight lifecycle checks before you send
A preview of the 20 in the free checklist, with FDA, EU and Health Canada rule numbers for each.
- New means no modified file — a new leaf never points at an earlier one. FDA 1068 · EU 11.8
- Replace names what it replaces — and that file is in an earlier sequence of the same application. FDA 1170, 1153 · EU 11.7, 11.9
- Same section — a replacement goes where the original was. EU 11.10 · HC G32
- No branches — each document is replaced or deleted once. EU 11.12 · HC F18, G28
- Delete has no file — and no checksum. FDA 1051, 1426 · EU 11.5
- No append in Canadian Module 1 — replace instead. HC F28
- Every file referenced — no files in the sequence without a leaf. FDA 1306 · HC C07
- Versions never go back — the regional DTD version is never older than one already used. FDA 2001 · EU 1.4
New, replace, append, delete
The free PDF adds the full checklist and where lifecycle goes wrong.
A document sent for the first time in this place. Modified file: no. File: yes.
A revised version that supersedes an earlier document. Modified file: yes. File: yes.
Adds to an earlier document without superseding it. Modified file: yes. File: yes.
Removes an earlier document from the current view. Modified file: yes. File: no.
Where lifecycle goes wrong
New instead of replace
Two current versions of one document. It passes validation, so it is common.
Replacing an old version
The modified file must be the current version, or the history branches.
Moving a document
A replacement stays in the same section. A move is a delete plus a new.
Append for replace
The reviewer reads both. Canada does not allow append in Module 1.
Lost history
A migration without the full lifecycle leaves modified files that cannot be found.
Unreferenced files
Every file in the sequence needs a leaf.
The eCTD lifecycle operations checklist
For publishers and regulatory operations teams. Print it, or copy it into your own procedure.
- 20 lifecycle checks with FDA, EU and Health Canada rule numbers
- The four operations and what each needs
- Where lifecycle goes wrong, and practices that help
Frequently asked
What are the eCTD lifecycle operations?
New, replace, append and delete. Every leaf in an eCTD carries one. New adds a document, replace supersedes an earlier one, append adds to an earlier one, and delete removes one from the current view.
What is the difference between replace and append in eCTD?
Replace supersedes the earlier document, so the reviewer sees only the new version as current. Append adds to the earlier document, so the reviewer reads both together. Health Canada does not allow append in Module 1.
What is the modified file in eCTD?
The earlier leaf that a replace, append or delete acts on. It must exist in an earlier sequence of the same application. A new leaf has no modified file.
Can I move a document to a different eCTD section with replace?
No. A replacement must be in the same section as the document it replaces (EU rule 11.10, Health Canada G32). To move a document, delete it in the old section and submit it as new in the new one.
Lifecycle from the application’s own history
DnXT Publisher keeps every sequence and shows the cumulative view the reviewer will see, so lifecycle is chosen from the current version.