Question 1

What is eCTD publishing software?

Accepted Answer

eCTD publishing software assembles drafted regulatory content into an electronic Common Technical Document package that meets the technical specifications of the target authority's submission gateway. It generates the XML backbone, applies lifecycle operations (new, replace, append, delete), structures leaves into the correct modules, produces PDF bookmarks and hyperlinks, computes checksums, and packages the final sequence for transmission through FDA ESG or an equivalent regional gateway. Good publishing software keeps source-to-leaf traceability intact so revisions can be tracked end-to-end.

Question 2

Does Assyro support eCTD v4.0.0 publishing?

Accepted Answer

Yes. Assyro produces eCTD v4.0.0 Regulated Product Submission (RPS) messages with controlled vocabularies, lifecycle operations, and the message envelope required for FDA and other regulators that have adopted v4.0.0. Teams on v3.2.2 for legacy programs can continue publishing in that format where required. The publishing engine is maintained against the current ICH specifications and the FDA Technical Conformance Guide, which reduces the operational burden of keeping pace with technical spec updates.

Question 3

How is eCTD publishing different from authoring?

Accepted Answer

Authoring is the process of drafting and reviewing the actual submission content: Module 2 summaries, Module 3 CMC documents, Module 5 clinical study reports, regional Module 1 forms. Publishing is the process of taking that finalized content and assembling it into the eCTD file structure with the correct XML backbone, lifecycle operations, and metadata. In most teams, authoring and publishing happen in different tools with different owners. Assyro connects the two so authoring decisions flow into publishing without a blind handoff.

Question 4

What is the publishing-to-validation handoff risk?

Accepted Answer

In a traditional workflow, authoring sends a finalized content package to publishing, publishing assembles the eCTD, validation runs at the end, and any structural or lifecycle defect discovered at that point has to be traced back through authoring to fix. The time cost is measured in days, and the fix often introduces new defects elsewhere in the sequence. Assyro runs validation during publishing and upstream in authoring, so the publishing team receives a sequence that is already validated clean.

Question 5

Can Assyro handle supplements, amendments, and annual reports?

Accepted Answer

Yes. Assyro publishes the full range of sequence types: original submissions (IND, NDA, BLA, ANDA, 510(k)), supplements (Prior Approval, CBE-30, CBE-0), amendments, annual reports, PSURs, PBRERs, and variation filings for non-US markets. Lifecycle operations across sequences are tracked so an append or replace in a supplement references the correct prior operation in the original sequence.

Question 6

Does Assyro replace our current publishing vendor?

Accepted Answer

It can. Assyro provides the end-to-end publishing capability on its own. Teams with heavy prior investment in Lorenz docuBridge, Veeva Vault Submissions Publishing, or GlobalSubmit sometimes adopt Assyro alongside for authoring, validation, and lifecycle management while running final publishing on the legacy tool during transition, then consolidate to Assyro once the operating model is aligned. Both patterns are supported.

Question 7

How fast can a sequence be published in Assyro?

Accepted Answer

A well-prepared IND or NDA supplement with 30-50 leaves typically assembles in 15-45 minutes of active work plus automated processing. The bottleneck in legacy workflows is not the publishing mechanics themselves but the cleanup time spent fixing validation defects that should have been caught upstream. Because Assyro validates continuously, the publishing step in most cycles becomes the 45-minute part rather than the two-day part.

Question 8

Is Assyro's publishing output accepted by FDA ESG?

Accepted Answer

Yes. Assyro produces eCTD packages that conform to the FDA Electronic Submissions Gateway (ESG) technical specifications for acceptance. Packages pass gateway technical validation, which is the first acceptance step before content review. The same output is compatible with Health Canada's Common Electronic Submissions Gateway and the EMA gateway for regions where Assyro's publishing capability applies. Validation of regional Module 1 requirements is handled in-platform before packaging.

eCTD Publishing Software

How eCTD Publishing Fits the Submission Workflow

Publish Clean Sequences on the First Attempt

Trace Any Leaf Back to Its Source Document Instantly

Skip the Manual 5-Hour Sequence Assembly

Stop Repeating the Same Publishing Checks Every Cycle

Controls and Traceability for eCTD Publishing

Keep eCTD Publishing Audit-Ready

Scale Across Programs Without Adding Complexity

Questions About eCTD Publishing

See eCTD Publishing in a Live Submission Workflow.