Assyro AI
Resources
IND - NDA - BLA - ANDA - 510(k)
eCTD Modules 1-5

Regulatory Submission Templates

Most submission delays do not come from the science. They come from rebuilding the same dossier structure from a blank page, missing a required form, or letting Module 2 summaries drift away from the data underneath them. These template families give regulatory teams a compliant skeleton for every major FDA pathway, so authoring starts from a structure that already matches what reviewers expect.

Each family below is organized around the Common Technical Document (CTD) and the FDA forms that pathway requires. They cover the administrative cover layer, the Module 2 overviews and summaries, the quality and CMC sections, and the nonclinical and clinical study report structure. Pair them with Assyro's validation and gap analysis so the package is not just well-structured but submission-ready before the review clock starts.

Template Families

One structured starting point per submission type

Each template encodes the table of contents, required forms, and CTD module placement for its pathway, so teams spend their time on content and evidence rather than on document architecture.

Pre-clinical to first-in-human

IND Application Templates

Investigational New Drug application templates cover the Form FDA 1571 cover structure, the introductory statement and general investigational plan, the investigator's brochure, and the protocol shell. They pre-format the chemistry, manufacturing, and controls (CMC) section, the pharmacology and toxicology summaries, and prior human experience so a sponsor can assemble a 30-day-review-ready package without re-deriving the table of contents each time.

505(b)(1) and 505(b)(2)

NDA Submission Templates

New Drug Application templates structure the full CTD dossier for small-molecule approval: the Module 2 clinical and nonclinical overviews and summaries, the integrated summary of safety and integrated summary of efficacy, labeling drafts aligned to 21 CFR 201.57, and the financial disclosure and patent certification forms. They keep Module 2 summaries traceable back to the underlying Module 4 and Module 5 datasets so cross-module claims stay consistent.

Biologics License Application

BLA Submission Templates

Biologics License Application templates extend the CTD structure for biologics and gene or cell therapies. They include the comparability and characterization narrative shells, the manufacturing process and control strategy sections under the heavier Module 3 burden biologics carry, the establishment description for each facility, and lot release and stability summary tables formatted to CBER review expectations.

Generic drug approval

ANDA Submission Templates

Abbreviated New Drug Application templates focus the dossier on what generics actually need to prove: the bioequivalence study report shell, the comparison to the reference listed drug, the basis-for-submission statement, and the patent and exclusivity (Paragraph I-IV) certification structure. The CMC sections mirror the NDA Module 3 layout so the same control-strategy discipline applies without rebuilding it.

Medical device clearance

510(k) Submission Templates

510(k) premarket notification templates are built around the substantial-equivalence argument: the predicate device comparison table, the indications-for-use statement, the device description and technological characteristics, the performance testing (bench, biocompatibility, software) summaries, and the truthful-and-accuracy and financial certification forms. The structure follows the eSTAR sectioning the FDA now expects.

Modules 1-5 backbone

eCTD Module Templates

eCTD module templates provide the granular folder-and-leaf backbone for the electronic submission itself. Module 1 carries the region-specific administrative forms and labeling; Module 2 holds the CTD summaries; Module 3 the quality dossier; Module 4 the nonclinical study reports; and Module 5 the clinical study reports. The templates map document granularity and node placement to the ICH eCTD specification so the package validates cleanly before lifecycle sequencing.

Start from a compliant structure, not a blank document

Templates remove the structural rework. The next step is making sure the filled-in dossier holds up: that Module 2 matches Modules 4 and 5, that every required form is present, and that the package validates before lifecycle sequencing. That is where Assyro's eCTD templates and gap analysis come in.