Skip to content
Entourage

How do you keep eCTD publishing and regulatory operations reliable when there are more submissions than the team can carry?

We build, validate and transmit submissions: the eCTD backbone, lifecycle sequences, technical validation and dispatch through the ESG, CESP or an agency portal. Regulatory operations is not an appendix to the filing but the point where a finished dossier can fail on technical grounds.

Overview

Why does a finished submission fail on technical grounds?

eCTD build, lifecycle operations and technical validation · dispatch through the FDA ESG and CESP · electronic records under 21 CFR Part 11 · Modules 1 to 5 in the ICH CTD format

Last updated: September 16, 2026

The content of a dossier and its technical form are owned by different people, and the agency checks both. Four places where a dossier that is finished on paper gets stuck.

  • The file does not meet the requirements. Locked or electronically signed PDFs cannot be processed further, bookmarks and hyperlinks are missing or point to the wrong place, and scanned pages without text recognition are not searchable for the reviewer.
  • The lifecycle operation is wrong. Whether a document is replaced, appended or marked as deleted determines the agency's cumulative view; the wrong operation makes older versions current again or hides the current one.
  • Validation happens on the filing date. The EU eCTD Validation Criteria and the FDA Technical Rejection Criteria report errors whose correction costs another publishing round, and the clock keeps running.
  • The transmission route is not prepared. Accounts, certificates and test transmissions for the FDA ESG or CESP are not created on the day of filing, and without an acknowledgement a submission counts as not received.

Services

How we support you

eCTD build and publishing

Building the backbone across Modules 1 to 5 under ICH M4 and ICH M8, with the regional Module 1, bookmarks, hyperlinks and a granularity that still works across the lifecycle.

Technical validation before filing

Checking against the EU eCTD Validation Criteria and the FDA Technical Rejection Criteria, covering PDF properties, fonts, hyperlinks and study data, with a findings list and remediation.

Dispatch and acknowledgement

Filing through the FDA ESG, CESP or the portal of the relevant authority, with accounts and certificates prepared in advance and a documented acknowledgement for every sequence.

Remediation of existing dossiers

Cleaning up sequences that have grown over time: locked files, broken hyperlinks, inconsistent granularity and missing leaf titles, before they surface in the next filing.

What it comes down to

A dossier rarely fails on its argument and regularly fails on a file. The agency checks two things: the content, and the form it arrives in. That form is called eCTD, and it is not a folder of PDFs but a backbone that carries every document with a title, a location and a lifecycle operation. Those operations produce the reviewer's cumulative view, and that is exactly where a mistake keeps working: a misplaced replace makes an old version authoritative again, and the only way to correct it is the next sequence.

The second place is validation. The EU eCTD Validation Criteria and the FDA Technical Rejection Criteria check the backbone, file properties, fonts, hyperlinks and study data formats. They report nothing scientific, but they hold a submission up while the clock keeps running. A run while corrections are still possible costs hours; the same run on the deadline costs the filing.

The third is the transmission route. Accounts, certificates and a test transmission for the FDA Electronic Submissions Gateway or the Common European Submission Portal are not created on the day of filing. And what counts as proof in the end is not the dispatch but the authority's acknowledgement.

Our approach

Our approach

01

Scope and schedule

An agreed submission type, target authorities and a schedule that plans validation and remediation before the deadline.

02

Document intake

Source files checked against the properties the format requires, rather than locks discovered during publishing.

03

Building the sequence

A built sequence with correct lifecycle operations, leaf titles and hyperlinks.

04

Validation

A validation report without blocking findings, with documented remediation of the rest.

05

Dispatch

A transmitted sequence with the authority's acknowledgement.

06

Archiving and handover

An archived version, an updated cumulative view and a sequence list the next filing can build on.

Common pitfalls

Where projects commonly fail

Electronically signed or otherwise locked PDFs enter the publishing stage.

They can no longer be bookmarked or converted, and correcting them costs another approval round with the author.

Granularity is changed mid-lifecycle.

Merging a document that was previously filed separately breaks the link between sequences and with it the agency's cumulative view.

Hyperlinks point to pages instead of sections.

The reviewer lands in the wrong place as soon as pagination shifts in a new version.

Technical validation is treated as a formality and pushed to the end.

The FDA Technical Rejection Criteria lead to a rejection without any scientific review, and the clock keeps running in the meantime.

The acknowledgement is not filed.

Without the gateway confirmation there is no later proof that a submission was made, or when.

Regulatory Affairs

Do any of these pitfalls apply to you?

In a first call we assess your situation and say what needs clarifying first in your case. Without obligation, reply usually within one working day.

FAQ

Frequently asked questions

The CTD under ICH M4 describes the content structure of a dossier in Modules 1 to 5. The eCTD under ICH M8 is its electronic form: a backbone that carries every document as a leaf with a title, a location and a lifecycle operation, so that the agency has a cumulative view of the current status across all sequences.

Sources
  • ICH M4: the Common Technical Document for the Registration of Pharmaceuticals for Human Use, structure of Modules 1 to 5
  • ICH M8: Electronic Common Technical Document (eCTD), specification and implementation guide
  • US FDA: 21 CFR Part 11, 21 CFR 314.50, 21 CFR 601.2
  • FDA Guidance: Providing Regulatory Submissions in Electronic Format, Certain Human Pharmaceutical Product Applications and Related Submissions Using the eCTD Specifications
  • FDA: Technical Rejection Criteria for Study Data
  • EU eCTD Validation Criteria and EU Module 1 Specification (eSubmission)
  • Regulation (EC) No 1234/2008 and Regulation (EC) No 726/2004
  • Regulation (EU) 2017/745 (MDR), Article 10 and Annexes II and III

Image notice: The images on this page were generated using artificial intelligence. They do not depict real people, places, or events.

Life Science Journal

Regulatory updates, straight to your inbox.

New requirements, authority decisions and practice notes. Once a month, unsubscribe any time.

Regulations & standards considered

  • ICH M4 (Common Technical Document, structure of Modules 1 to 5)
  • ICH M8 (Electronic Common Technical Document, eCTD)
  • 21 CFR Part 11 (electronic records and electronic signatures)
  • 21 CFR 314.50 (content and format of an NDA) and 21 CFR 601.2 (BLA)
  • FDA Guidance: Providing Regulatory Submissions in Electronic Format, Certain Human Pharmaceutical Product Applications
  • FDA Technical Rejection Criteria for Study Data
  • EU Module 1 Specification and EU eCTD Validation Criteria
  • Regulation (EC) No 1234/2008 (variations filed as their own sequence)
  • Regulation (EC) No 726/2004 (centralized procedure and electronic filing with the EMA)
  • EU 2017/745 (MDR), Article 10(14) (retention of the technical documentation)

Have a concrete project?

Briefly outline your situation. We'll respond with an initial assessment, usually within one business day.

Prefer direct? +39 02 8904 1000
info@theentourage.it

  • Reply usually within one working day
  • 4 offices: DE · CH · IT · US
  • 100% life sciences