← All guides

FDA Regulatory Submission Project Gantt Chart

FDA submissions — 510(k), NDA, BLA, PMA — require months of parallel preparation. Here's the Gantt chart template for managing every workstream from dossier planning to agency response.

FDA Regulatory Submission Project Gantt Chart

The Problem: FDA Submissions Are Project Management Problems, Not Just Document Assembly

A Common Technical Document (CTD) for an NDA or BLA can contain 100,000+ pages of clinical, nonclinical, and chemistry, manufacturing, and controls (CMC) data. A 510(k) for a medical device requires substantial equivalence arguments, performance testing data, and software documentation. A Pre-Market Approval requires clinical data from pivotal studies, manufacturing process validation, and labeling. In each case, the submission is the product of a multi-year development program — but the act of compiling, reviewing, and submitting it is itself a complex project that can take 6–18 months.

Regulatory submissions fail for project management reasons: sections submitted by different teams that don't cross-reference correctly, clinical data that doesn't match the statistical analysis plan, CMC sections that describe a manufacturing process that has since changed, or a submission date that cannot be met because the final clinical study report hasn't been completed. gantt-chart.io gives regulatory affairs teams a single timeline that ties every section of the submission to the team that owns it and the data it depends on.

Prerequisites

  • Regulatory pathway confirmed (510(k), De Novo, NDA, BLA, or PMA); FDA agreement via pre-submission if needed
  • Complete clinical, nonclinical, and CMC data package identified and assessed
  • Regulatory affairs lead and submission project manager assigned
  • Submission target date set based on data availability and FDA review timelines
  • Regulatory writing resources (internal or contract) confirmed and allocated

FDA Regulatory Submission Gantt Chart Template

Phase 1: Submission Planning and Gap Analysis (Months 1–2)

  • [ ] Conduct submission readiness assessment: identify all required sections and data gaps
  • [ ] Develop submission project plan with section-level owners and due dates
  • [ ] Confirm formatting and technical requirements (eCTD sequence, FDA eSubmitter)
  • [ ] Engage FDA via Type B or Type C meeting if outstanding scientific questions exist
  • [ ] Initiate regulatory writing contracts for clinical overview, nonclinical summary, CMC sections
  • [ ] Establish document management system for version control and review tracking

Phase 2: Module Drafting and Data Lock (Months 2–8)

  • [ ] Complete clinical study reports (CSRs) for all pivotal and supportive studies
  • [ ] Draft Module 2 clinical and nonclinical summaries; validate against source data
  • [ ] Compile CMC (Module 3) documentation: drug substance, drug product, manufacturing controls
  • [ ] Complete nonclinical study reports; verify GLP compliance documentation
  • [ ] Finalize statistical analysis: outputs match SAP and are traceable to source datasets
  • [ ] Lock datasets; archive in submission-ready format (CDISC SDTM/ADaM)

Phase 3: Internal Review and QC (Months 7–10)

  • [ ] Conduct cross-functional review of all modules: medical, statistical, regulatory, CMC
  • [ ] Perform consistency check: all cross-references between modules are accurate
  • [ ] Complete internal quality review checklist against FDA submission guidance
  • [ ] Resolve all review comments; track open items to closure
  • [ ] Prepare labeling (prescribing information or device labeling) for internal review
  • [ ] Complete publishing and technical QC: hyperlinking, bookmarks, file format validation

Phase 4: Submission and FDA Interaction (Months 10–14)

  • [ ] Submit to FDA via ESG (Electronic Submissions Gateway); receive acknowledgment letter
  • [ ] Track 74-day filing review period (NDA/BLA) or 15-day acceptance (510(k))
  • [ ] Respond to Information Requests (IRs) or Refuse to File (RTF) issues within stated timeframes
  • [ ] Prepare for advisory committee if scheduled; develop briefing documents and presentations
  • [ ] Respond to Complete Response Letter (CRL) or additional information requests
  • [ ] Negotiate labeling with FDA division; finalize prescribing information or device labeling

Phase 5: Approval and Post-Approval (Month 12+)

  • [ ] Receive approval letter; verify conditions of approval and post-marketing commitments
  • [ ] Register product in FDA databases (NDC, 510(k) database, Orange/Purple Book)
  • [ ] Set up post-marketing surveillance per approval conditions
  • [ ] Submit annual reports per regulatory requirements
  • [ ] Archive submission files per records retention requirements

Common Pitfalls

  • Clinical study reports not started until trials complete: CSRs take 3–6 months to write and review. Starting CSR writing in parallel with trial completion — not after — compresses the submission timeline significantly.
  • CMC section not updated to reflect commercial manufacturing: CMC documentation written during development may not reflect the final commercial manufacturing process. A pre-approval inspection revealing discrepancies leads to a Complete Response Letter.
  • Dataset submission standards not confirmed early: FDA requires CDISC SDTM and ADaM datasets with reviewers' guides. Retrospectively converting legacy data formats to CDISC takes months and introduces errors.
  • Labeling negotiation underestimated: Finalizing the prescribing information often takes as long as the rest of the review. Start the internal labeling review process at the same time as the submission, not after the approval letter arrives.

What Good Looks Like

A submission that reaches FDA with complete, consistent, and well-organized documentation receives a filing acceptance with no information requests in the first 30 days, a standard review without major amendments, and label negotiations that conclude within 60 days of approval action. Regulatory affairs teams that manage submissions as formal projects — with section owners, version control, and QC checkpoints — consistently outperform those that treat it as document assembly.