Regulatory publishing guide
What is eCTD 4.0?
A plain-language guide to the next Electronic Common Technical Document standard — what it changes, why it matters, and how to get ready.
How eCTD 4.0 differs from eCTD 3.2.2
The version most companies use today, eCTD 3.2.2, has been in service for well over a decade. eCTD 4.0 keeps the same Common Technical Document structure (Modules 1–5) but changes the machinery underneath. The most important shifts:
| Area | eCTD 3.2.2 | eCTD 4.0 |
|---|---|---|
| Message standard | Region-specific XML backbone | HL7 RPS (Regulated Product Submission) |
| Document reuse | Re-submitted or linked per location | One document referenced in many places |
| Vocabularies | Fixed in the DTD | Controlled vocabularies maintained and updated separately |
| Metadata | Limited attributes | Keyword-based metadata for richer context |
| Communication | Mostly one-way | Two-way between applicant and agency |
Why the change matters
The practical wins are reuse and maintainability. In eCTD 3.2.2, the same document that belongs in several sections has to be handled in each location. eCTD 4.0's reuse model means a document is submitted once and referenced wherever it is needed, which reduces dossier size and the risk of version drift. Controlled vocabularies can be updated by regulators without re-issuing the whole standard, so the format can evolve without a disruptive migration each time.
Regional timelines
eCTD 4.0 is being introduced region by region rather than in a single global switch-over. The FDA and other ICH regions have run pilots and staged voluntary-then-mandatory windows, and 3.2.2 remains valid during the transition. The right planning question is not “are we too early?” but “which of our target markets moves first, and is our tooling and our vendor ready for both formats at once?”
How to prepare
- Confirm which of your submission regions have published 4.0 timelines and pilot options.
- Make sure your publishing partner can compile both 3.2.2 and 4.0 and manage lifecycle across the transition.
- Audit your document templates and metadata now — clean, well-structured source is what makes reuse and validation painless later.
- Validate every sequence against the applicable specification before submission; a four-stage QA catches structural issues before the agency does.
“The transition to eCTD 4.0 rewards teams that get their source documents and metadata clean now. Reuse only helps you if the underlying files are consistent — that discipline is where a publishing partner earns its keep.”Prashanth Krishna, Practice Head — Content Transformation & Regulatory Operations, B2K
Talk to B2K about your submission
Tell us the region, sequence type and file volume, and we’ll scope the work and commit to a date we can hold.
Start a project →Frequently asked questions
What is the difference between eCTD 3.2.2 and eCTD 4.0?
eCTD 3.2.2 uses a region-specific XML backbone, while eCTD 4.0 is built on the HL7 Regulated Product Submission (RPS) message. eCTD 4.0 adds document reuse (one document referenced in many locations), separately-maintained controlled vocabularies, richer keyword metadata and two-way communication with the agency. Both keep the Module 1–5 CTD structure.
Is eCTD 4.0 mandatory yet?
Not universally. eCTD 4.0 is being phased in region by region through pilot and voluntary periods before becoming mandatory, and eCTD 3.2.2 remains valid during the transition. The exact timeline depends on your target markets, so plan for both formats at once.
Do we need to re-do existing submissions in eCTD 4.0?
No. Existing 3.2.2 lifecycles continue to be accepted during the transition. New sequences can move to 4.0 where a region supports it, and a capable publishing partner manages the lifecycle across both formats.
What is the HL7 RPS message?
RPS (Regulated Product Submission) is the HL7 messaging standard that underpins eCTD 4.0. It replaces the older XML backbone and enables the document reuse, controlled vocabularies and two-way communication features of 4.0.