Quick Answer
An NDA submission is the New Drug Application package a sponsor files with FDA to request approval to market a new drug in the United States. FDA expects the NDA to contain the drug's full development story: clinical evidence, nonclinical data, CMC information, proposed labeling, safety information, manufacturing controls, and administrative forms. Modern NDA submissions to CDER and CBER are organized in eCTD format across Modules 1-5.
Key Takeaways
- FDA describes the NDA as the vehicle through which drug sponsors formally propose that FDA approve a new pharmaceutical for sale and marketing in the United States.
- The data gathered during animal studies and human clinical trials under the IND become part of the NDA.
- FDA's NDA review addresses whether the drug is safe and effective, whether proposed labeling is appropriate, and whether manufacturing methods and controls preserve identity, strength, quality, and purity.
- 21 CFR 314.50 describes NDA content and format, including application form, summary, CMC, nonclinical, clinical, labeling, and supporting information.
- eCTD is the standard format for submitting applications, amendments, supplements, and reports to CDER and CBER.
- An NDA submission is one of the most consequential filings in drug development. It turns years of IND-stage work into a marketing application: clinical study reports, CMC data, nonclinical studies, integrated summaries, proposed labeling, and manufacturing information all need to be complete, internally consistent, and reviewable.
- NDA failure is rarely just a formatting issue. Submissions struggle when the story does not hold together: the indication is broader than the evidence, Module 3 does not support commercial manufacturing, the labeling lacks adequate support, study data are difficult to navigate, or cross-references do not match the eCTD backbone.
- This guide explains the core NDA submission requirements, how the eCTD modules fit together, and what to check before filing.
- In this guide, you will learn:
- What an NDA submission is and how it differs from an IND
- FDA's core review questions for NDAs
- Module-by-module NDA requirements
- How the NDA submission process and filing review work
- How to build an NDA submission checklist
- Related guides:
- NDA approval timeline
- NDA rejection reasons
- Pre-NDA meeting guide
- What is eCTD
- eCTD validation guide
What Is an NDA Submission?
A New Drug Application (NDA) is the submission through which a sponsor asks FDA to approve a new drug for marketing in the United States. The NDA contains the information FDA needs to evaluate safety, effectiveness, labeling, and manufacturing quality.
FDA's NDA page explains that the data gathered during animal studies and human clinical trials under an Investigational New Drug application become part of the NDA. The NDA is therefore not just a final document package; it is the culmination of the full development program.
FDA identifies three core review questions:
- Safety and effectiveness: Is the drug safe and effective for the proposed use, and do benefits outweigh risks?
- Labeling: Is the proposed labeling appropriate, and what should it contain?
- Manufacturing and quality: Are the manufacturing methods and controls adequate to preserve identity, strength, quality, and purity?
The NDA must tell the drug's complete story, including clinical results, nonclinical data, ingredients, pharmacology, manufacturing, processing, packaging, and proposed labeling.
NDA vs IND
| Filing | Purpose | Timing | Core Question |
|---|---|---|---|
| IND | Authorize clinical investigation of an investigational drug | Before human clinical trials in the U.S. | Can clinical investigation proceed safely? |
| NDA | Request approval to market a drug | After sufficient clinical, nonclinical, and CMC evidence is available | Should FDA approve the drug for the proposed use? |
The IND is about permission to study. The NDA is about permission to market.
NDA vs BLA vs ANDA
| Application | Product Type | Evidence Model |
|---|---|---|
| NDA | New small molecule drugs and certain other drug products | Full evidence of safety and effectiveness, unless using 505(b)(2) reliance |
| BLA | Biological products | Safety, purity, and potency under the biologics framework |
| ANDA | Generic drugs | Sameness and bioequivalence to a reference listed drug |
For pathway selection, see NDA vs ANDA, BLA vs NDA, and 505(b)(2) pathway.
NDA Submission Requirements Under 21 CFR 314.50
21 CFR 314.50 describes the content and format of an NDA. The regulation predates modern eCTD workflows, but the required content maps into the CTD/eCTD module structure used for current submissions.
| 21 CFR 314.50 Requirement | eCTD Location | Practical Meaning |
|---|---|---|
| Application form | Module 1 | Form FDA 356h and administrative data |
| Index / table of contents | eCTD backbone and module TOCs | Navigation and cross-reference structure |
| Summary | Module 2 | Integrated summaries and overviews |
| Chemistry, manufacturing, and controls | Module 3 | Drug substance, drug product, controls, stability, facilities |
| Nonclinical pharmacology and toxicology | Module 4 plus Module 2 summaries | Animal and in vitro evidence |
| Human pharmacokinetics and bioavailability | Module 5 plus Module 2 summaries | Clinical pharmacology and bioavailability data |
| Microbiology | Module 3 or 5 as applicable | Anti-infective microbiology data when relevant |
| Clinical data | Module 5 plus Module 2 summaries | Clinical study reports and integrated analyses |
| Labeling | Module 1 | Proposed prescribing information and supporting annotations |
| Financial disclosure | Module 1 | Clinical investigator financial certification/disclosure |
The exact package depends on product type, application type, development history, and FDA feedback. A 505(b)(2) NDA, for example, may rely in part on FDA's prior findings or published literature, while a 505(b)(1) NDA generally contains the sponsor's full safety and effectiveness package.
NDA eCTD Structure: Module-by-Module Checklist
FDA identifies eCTD as the standard format for submitting applications, amendments, supplements, and reports to CDER and CBER. In practice, a complete NDA submission is organized across Modules 1-5.
Module 1: Administrative and Prescribing Information
Module 1 contains region-specific administrative content for the U.S. application.
| Module 1 Area | Content |
|---|---|
| Cover letter | Submission purpose, application type, key context, contact information |
| Form FDA 356h | Application form for NDAs and BLAs |
| User fee information | PDUFA user fee cover sheet or waiver information |
| Debarment certification | Certification required for covered applications |
| Financial disclosure | Clinical investigator financial certification/disclosure |
| Labeling | Proposed prescribing information, carton/container labels, Medication Guide or patient labeling when applicable |
| Patent and exclusivity information | Patent forms and exclusivity claims when applicable |
| REMS | Risk Evaluation and Mitigation Strategy, if proposed or required |
| Environmental information | Environmental assessment or categorical exclusion claim |
| FDA correspondence | Pre-NDA meeting minutes, agreements, and key regulatory history |
Module 1 should make it easy for FDA to identify what is being submitted, who is responsible, what labeling is proposed, and which prior communications govern the review.
Module 2: Summaries and Overviews
Module 2 is the reviewer's roadmap. It synthesizes the technical data in Modules 3-5.
| Module 2 Section | Purpose |
|---|---|
| 2.2 Introduction | Product overview and development context |
| 2.3 Quality Overall Summary | CMC summary for drug substance and drug product |
| 2.4 Nonclinical Overview | Integrated interpretation of nonclinical evidence |
| 2.5 Clinical Overview | Benefit-risk assessment and clinical development interpretation |
| 2.6 Nonclinical Written and Tabulated Summaries | Structured nonclinical summaries |
| 2.7 Clinical Summary | Clinical pharmacology, efficacy, and safety summaries |
Module 2 should not merely repeat module contents. It should explain the logic of the application and help FDA understand how the evidence supports approval.
Module 3: Quality / CMC
Module 3 is where many NDA readiness problems surface. It needs to demonstrate that the commercial product can be manufactured consistently and controlled appropriately.
| Module 3 Area | Content |
|---|---|
| Drug substance | Nomenclature, structure, manufacturer, manufacturing process, controls, characterization, impurities, specifications, analytical methods, validation, stability |
| Drug product | Formulation, manufacturing process, process controls, excipient controls, specifications, analytical methods, container closure, stability |
| Manufacturing sites | Facilities, responsibilities, and quality controls |
| Batch data | Development, clinical, registration, and stability batches as applicable |
| Reference standards | Qualification and use of standards |
| Stability | Data supporting proposed shelf life and storage |
| Regional information | U.S.-specific quality information |
CMC should align with the proposed labeling, clinical formulation history, commercial process, and inspection readiness. If Module 3 does not support the product FDA is being asked to approve, the application is not ready.
Module 4: Nonclinical Study Reports
Module 4 contains pharmacology, pharmacokinetic, and toxicology study reports. It supports the safety basis for clinical exposure and marketing approval.
| Module 4 Area | Examples |
|---|---|
| Pharmacology | Primary pharmacodynamics, secondary pharmacodynamics, safety pharmacology |
| Pharmacokinetics | ADME, toxicokinetics, tissue distribution |
| Toxicology | Single-dose, repeat-dose, genotoxicity, carcinogenicity, reproductive/developmental toxicity, local tolerance |
| Other reports | Special studies required by product class or FDA feedback |
The nonclinical package should be traceable to IND development, clinical exposure, proposed dose, route, duration, and patient population.
Module 5: Clinical Study Reports
Module 5 contains the clinical evidence supporting safety and effectiveness.
| Module 5 Area | Content |
|---|---|
| Tabular listing of clinical studies | Index of all clinical studies |
| Clinical pharmacology reports | PK, PD, dose-response, drug interaction, special population studies |
| Efficacy and safety reports | Pivotal, supportive, and other clinical study reports |
| Integrated datasets and analyses | Integrated summaries and statistical outputs |
| Literature references | Published literature supporting the application |
| Case report forms and tabulations | When required by FDA or regulation |
The clinical module should support the proposed indication, dosing regimen, patient population, warnings, contraindications, and benefit-risk assessment.
NDA Submission Process and Timeline
The NDA process begins before final submission. A well-run filing usually includes a pre-NDA meeting, final agreement on content expectations, eCTD publishing, quality control, ESG submission, and FDA filing review.
| Stage | Activity | Risk to Manage |
|---|---|---|
| Pre-NDA planning | Confirm submission content, datasets, labeling, and review strategy | Late FDA disagreement on package completeness |
| Application assembly | Build Modules 1-5 and finalize cross-references | Inconsistent module narratives or missing reports |
| eCTD publishing | Generate eCTD backbone, lifecycle attributes, and submission sequence | Technical validation errors |
| Submission | Transmit through ESG using assigned application number | Wrong application number, file, sequence, or missing forms |
| Filing review | FDA determines whether the application is sufficiently complete for review | Refuse-to-file risk |
| Substantive review | Multi-discipline FDA review | Information requests, major amendments, advisory committee, CRL |
| FDA action | Approval letter or Complete Response Letter | Launch delay or resubmission |
For detailed timing, see our NDA approval timeline guide.
Filing Review
After submission, FDA conducts a filing review to determine whether the NDA is sufficiently complete to permit substantive review. If FDA refuses to file the application, the sponsor must address the deficiencies and resubmit.
Common filing-readiness risks include:
- Missing or incomplete clinical study reports
- Incomplete CMC information
- Inadequate labeling support
- Missing required forms or certifications
- Datasets or study data that do not meet technical expectations
- Poorly organized eCTD structure
- Major inconsistency between the proposed indication and evidence package
PDUFA Goal Dates
PDUFA timelines depend on standard vs priority review and current user fee commitments. The application also undergoes a filing review period before FDA determines whether the submission is sufficiently complete for substantive review. Teams should plan around both FDA goal dates and the practical risk of information requests, major amendments, inspections, and advisory committee scheduling.
NDA Submission Checklist
Use this checklist before final eCTD publishing and ESG submission.
| Area | Checklist Item |
|---|---|
| Regulatory strategy | Confirm NDA type: 505(b)(1), 505(b)(2), resubmission, supplement, or other applicable category. |
| Application number | Confirm pre-assigned application number and ESG account readiness. |
| FDA agreements | Reconcile pre-NDA meeting minutes, written responses, protocol agreements, and FDA feedback. |
| Module 1 | Verify Form FDA 356h, cover letter, user fee information, labeling, certifications, financial disclosures, and environmental claim. |
| Module 2 | Confirm summaries are current, internally consistent, and aligned with Modules 3-5. |
| Module 3 | Verify commercial process, specifications, analytical validation, stability, container closure, batch data, and manufacturing site information. |
| Module 4 | Confirm all nonclinical reports and summaries are included and cross-referenced. |
| Module 5 | Confirm clinical study reports, integrated analyses, datasets, literature, and case report forms where needed. |
| Labeling | Ensure every claim in prescribing information is supported by application data. |
| Study data | Confirm required datasets, define files, reviewer guides, and standards conformance. |
| eCTD validation | Validate backbone, sequence, file names, lifecycle operators, bookmarks, hyperlinks, and leaf titles. |
| Cross-references | Check all references across modules and summaries. |
| Quality control | Perform independent regulatory, medical writing, CMC, statistics, and publishing QC. |
How Assyro Supports NDA Submission Readiness
NDA readiness is not only about uploading an eCTD sequence. The real work is making the application coherent: Module 2 should match Modules 3-5, labeling should match the evidence, CMC should support the commercial product, and eCTD validation should catch technical issues before submission.
Assyro supports drug submission teams through eCTD Authoring, eCTD Validation, and Regulatory Gap Analysis. The goal is to identify missing documents, inconsistent cross-references, weak readiness signals, and validation issues before they become FDA review delays.
For NDA teams, the most valuable workflow is pre-submission readiness: validate the structure, check the evidence-to-labeling logic, and confirm that every module is telling the same regulatory story.
An NDA submission is the application a sponsor files with FDA to request approval to market a new drug in the United States. It contains clinical, nonclinical, CMC, labeling, administrative, and supporting information that FDA uses to evaluate whether the drug should be approved.
References
This guide reflects FDA NDA and eCTD submission expectations current as of May 2026. Regulatory requirements evolve; confirm the latest FDA guidance, eCTD standards, study data standards, and review-division feedback before filing.
About the author
Assyro Team
Expert regulatory operations consultants helping pharmaceutical companies navigate complex compliance challenges.
See Assyro in action
Catch eCTD and eSTAR errors before your FDA review cycle.
Book a 20-minute demo this week. We'll validate a sample of your submission live and show you exactly where Assyro catches what your current QC misses.