publishing software to generate the eCTD XML structure. Each sequence is uniquely numbered and contains submission metadata.

Assign appropriate submission type: Define if the submission is initial, response to query, supplement, or variation. Update lifecycle operators accordingly (new, replace, delete).

Ensure technical compliance: Validate bookmarks, hyperlinks, file names, and document granularity according to regional specifications.

Refer to tools such as pharma validation software and eCTD compilers like Lorenz docuBridge, Extedo eCTDmanager, or GlobalSubmit.

Key Technical Requirements for eCTD:

1. PDF Requirements:

• Must be PDF v1.4 to 1.7 compatible
• All documents must be text searchable and unlocked
• Include bookmarks for sections over 10 pages
• Use black text on white background with no scanned pages
• File size must not exceed 100 MB unless justified

2. Hyperlinking and Bookmarks:

• Cross-reference related sections using internal hyperlinks
• Hyperlinks must be functional and embedded, not pasted
• Use relative linking paths for portability

3. Folder and File Naming:

• Follow ICH eCTD specifications (e.g., m5/535-study-report.pdf)
• Avoid special characters and spaces in file names
• Use underscores (_) for spacing in file names

4. Metadata Requirements:

Metadata such as product name, sequence number, submission type, and application number must be filled into the XML envelope. This enables health authorities to automate dossier tracking.

5. Lifecycle Management:

Each submission (sequence) reflects a lifecycle state — whether a file is being newly added, replaced, or deleted. This allows clear tracking of document history and dossier evolution.

• New: Initial upload of a document
• Replace: Updated version of an existing document
• Delete: Remove document from view (retains record)

This concept is central to managing rolling submissions, variation filings, and responses to health authority queries.

Validation and Technical Review:

Before submission, every eCTD must be validated using region-specific tools:

• FDA: Validator tools like Lorenz eValidator, GlobalSubmit Validate
• EMA: EU M1 eCTD checker
• Health Canada: eCTD Validator from Paraxel or Extedo

Validation checks include:

• File format errors
• Broken hyperlinks
• Incorrect XML entries
• Incorrect lifecycle operations

Any issues must be resolved before finalization and dispatch via electronic gateways.

Best Practices for eCTD Submissions:

• Start eCTD planning early in the development process
• Train internal teams or outsource to certified eCTD publishers
• Maintain submission-ready formats for all documents
• Keep version control across draft and final documents
• Perform pilot validation prior to regulatory deadlines

Leverage stability testing data and GMP documents in CTD-compliant format to reduce rework.

Regulatory Considerations and Regional Differences:

Though based on ICH guidelines, each agency has specific expectations:

• USFDA: Requires Module 1 in SPL format with ESG gateway submission
• EMA: Uses CESP or IRIS portals with EU regional Module 1
• CDSCO: Accepts eCTD pilot formats and requires submission via SUGAM portal
• TGA (Australia): Uses eCTD v3.2.2 but still accepts NeeS formats

Ensure alignment with regional guidance and consult their respective pharma regulatory requirements.

Conclusion:

Preparing and submitting an eCTD-compliant dossier is critical for regulatory success. With the right tools, structured planning, and technical accuracy, you can reduce delays, improve compliance, and enhance communication with global health authorities.

Following the guidance above ensures that your electronic submissions are complete, traceable, and technically validated across agencies.