Assyro AI logo background
mid cycle meeting fda
fda mid-cycle communication
nda review mid-cycle
pdufa mid-cycle meeting

FDA Mid-Cycle Meeting: Purpose, Timing, and Preparation

Guide

Understand FDA mid-cycle meetings during NDA/BLA review, including when they occur, what FDA communicates, how to prepare, and their impact on PDUFA timelines.

Assyro Team
11 min read

FDA Mid-Cycle Meeting: Purpose, Timing, and Preparation

Quick Answer

An FDA mid-cycle meeting (also called a mid-cycle communication) occurs approximately midway through the PDUFA review cycle for NDAs and BLAs. Its primary purpose is for FDA to communicate the status of the review, identify any outstanding issues, and signal whether significant problems have been identified. Under PDUFA VII, FDA committed to providing mid-cycle communications for all standard and priority review applications. This is not a decision-making meeting but a status checkpoint that helps sponsors prepare for the remainder of the review.

Key Takeaways

Key Takeaways

  • Mid-cycle communications occur around Month 5-6 from filing for standard review and Month 2-3 for priority review
  • FDA communicates review status, significant issues, anticipated information requests, and advisory committee considerations
  • The mid-cycle meeting does not change the PDUFA goal date; it is a communication checkpoint, not a regulatory action
  • Under PDUFA VII, FDA committed to providing mid-cycle communications for all standard and priority review NDA/BLA applications
  • What FDA does not say at mid-cycle can be as informative as what it does say — a brief, unremarkable meeting often signals a smooth review
  • The FDA mid-cycle meeting is one of the defined communication points during the review of a New Drug Application or Biologics License Application. Established as part of PDUFA performance commitments, mid-cycle communications provide sponsors with a structured opportunity to understand where the review stands and whether major issues have surfaced.
  • For regulatory teams, the mid-cycle meeting is a critical planning moment. The information FDA shares, and sometimes what it does not share, influences how the sponsor allocates resources for the remainder of the review cycle and prepares for potential advisory committee meetings, information requests, or approval.
  • In this guide, you will learn:
  • When mid-cycle meetings occur during the PDUFA review timeline
  • What FDA communicates during mid-cycle meetings
  • How to request and prepare for a mid-cycle meeting
  • Key discussion topics and what to expect
  • How mid-cycle meetings differ from late-cycle meetings
  • The relationship between mid-cycle communications and the PDUFA timeline
  • ---

When Does the Mid-Cycle Meeting Occur?

Timing Within the Review Cycle

The mid-cycle meeting typically occurs at or near the midpoint of the PDUFA review period.

Review TypePDUFA Goal (from submission)Approximate Mid-Cycle Timing
Standard review10 months (approximately 8 months from filing)Month 5-6 from filing date
Priority review6 months (approximately 4 months from filing)Month 2-3 from filing date
Class 2 resubmission6 months from resubmissionMonth 3 from resubmission

For standard review applications, the mid-cycle communication typically occurs around Month 5 from the filing date, which is roughly Month 7 from the original submission date. For priority review applications, the compressed timeline means mid-cycle communications occur earlier, often around Month 2-3 from filing.

Pro Tip

The exact timing of the mid-cycle meeting depends on the review division's workload and the complexity of the application. Do not assume the mid-cycle communication will occur at precisely the midpoint. Some divisions hold it slightly earlier or later depending on the pace of their review. If you have not received a mid-cycle communication by the expected window, contact the FDA project manager to inquire.

Purpose of the Mid-Cycle Meeting

What FDA Communicates

The mid-cycle meeting serves as a status update, not a pre-decision discussion. FDA's objectives during this communication include:

PurposeDescription
Review statusFDA indicates which disciplines have completed or are actively reviewing their portions of the application
Significant issues identifiedFDA may flag major concerns that have surfaced during the review (e.g., efficacy questions, safety signals, CMC deficiencies)
Information requests anticipatedFDA may indicate that formal information requests will be forthcoming
Advisory committee considerationFDA may signal whether an advisory committee meeting is being considered
Inspection statusFDA may provide an update on pre-approval inspection (PAI) scheduling or results
Timeline concernsFDA may indicate whether the review is on track for the PDUFA goal date

What FDA Does Not Communicate

The mid-cycle meeting is explicitly not:

  • A pre-approval decision or recommendation
  • A guarantee of the review outcome
  • A comprehensive listing of all potential deficiencies
  • A negotiation forum for labeling or approval conditions
  • A substitute for formal information requests or discipline review letters
Pro Tip

Pay close attention to what FDA does not say during the mid-cycle meeting. If FDA's review is progressing without issues, the mid-cycle communication may be relatively brief and unremarkable. If FDA raises specific concerns, treat those signals seriously and begin preparing your response even before a formal information request is issued.

How to Request and Prepare

Request Process

Under PDUFA VII commitments, FDA is committed to providing mid-cycle communications for NDA and BLA applications. The sponsor does not typically need to formally request a mid-cycle meeting; FDA's review division will initiate the communication as part of the standard review process.

However, if the expected mid-cycle window passes without communication:

  1. Contact the FDA project manager assigned to your application
  2. Reference the PDUFA commitment for mid-cycle communication
  3. Request scheduling of the mid-cycle interaction

Meeting Format

Mid-cycle communications may take different formats depending on the review division and application complexity:

FormatDescriptionWhen Used
Written communicationFDA provides a written update on review statusCommon for straightforward reviews with no significant issues
TeleconferenceInteractive call between FDA review team and sponsorWhen FDA has questions or wants to discuss identified issues
In-person meetingFace-to-face meeting at FDARare; typically reserved for complex applications with multiple significant issues

Preparation Checklist

Even though the mid-cycle meeting is FDA-initiated, sponsors should prepare:

Preparation StepPurpose
Review all FDA communications received to dateUnderstand the context of any issues already raised
Prepare a status update on any pending sponsor actionsIf FDA has requested information informally, be ready to provide status
Identify potential questions FDA may raiseConduct an internal gap analysis of your application
Prepare subject matter expertsHave clinical, CMC, and statistical experts available for the meeting
Draft a list of sponsor questionsIf the format permits, prepare questions about review timeline, inspection scheduling, or advisory committee plans
Review PAI readinessIf pre-approval inspection has not yet occurred, confirm your manufacturing site is ready

Key Discussion Topics

Clinical Review Status

FDA may share preliminary observations about:

  • Whether the clinical data support the proposed indication
  • Concerns about the primary efficacy endpoint results
  • Safety signals identified during the review
  • Questions about clinical study design or statistical methodology
  • Subgroup analysis considerations

CMC/Manufacturing Review Status

FDA may discuss:

  • Status of the chemistry review
  • Any CMC deficiencies identified
  • Pre-approval inspection scheduling or preliminary results
  • Stability data adequacy
  • Manufacturing process concerns

Advisory Committee Considerations

One of the most strategically important mid-cycle signals is whether FDA is considering convening an advisory committee meeting. If FDA raises this possibility:

  • It does not necessarily indicate a problem; novel products, first-in-class mechanisms, and products with significant public health interest often trigger advisory committee review
  • It does affect the sponsor's timeline planning (advisory committee meetings typically occur 1-3 months before the PDUFA date)
  • The sponsor should begin advisory committee preparation immediately if FDA signals this intent

Labeling Discussions

FDA may raise preliminary labeling considerations during mid-cycle, particularly:

  • Proposed indication language adjustments
  • Potential boxed warning considerations
  • Safety-related labeling requirements
  • REMS considerations

Mid-Cycle vs Late-Cycle Meetings

The PDUFA review cycle includes multiple communication touchpoints. Understanding the difference between mid-cycle and late-cycle meetings prevents confusion.

AttributeMid-Cycle MeetingLate-Cycle Meeting
TimingMidpoint of review (Month 5-6 for standard review)Last 2-3 months of review
PurposeStatus update; flag significant issues earlyResolve remaining issues; finalize labeling; discuss approval conditions
FDA's postureInformationalMore directive; closer to decision
Issues raisedPreliminary; may not be fully developedMore defined; often accompanied by specific requests
Sponsor preparationGeneral readiness; gap analysisSpecific responses to identified issues; near-final labeling proposals
NegotiationMinimalLabeling negotiation may occur
Advisory committeeFDA may signal intentAdvisory committee typically completed or scheduled
Regulatory basisPDUFA commitmentPDUFA commitment
Pro Tip

Think of the mid-cycle meeting as a weather forecast and the late-cycle meeting as the storm preparation briefing. Mid-cycle tells you what might be coming; late-cycle tells you exactly what you need to do before the PDUFA date.

Impact on PDUFA Timeline

Does the Mid-Cycle Meeting Affect the PDUFA Date?

No. The mid-cycle meeting itself does not change the PDUFA goal date. It is a communication event, not a regulatory action. The PDUFA date is only affected by:

  • Major amendments submitted by the sponsor (3-month extension)
  • Refuse to file decisions (clock never starts)
  • Application withdrawal by the sponsor

Mid-Cycle Signals and Timeline Planning

While the mid-cycle meeting does not change the PDUFA date, the information FDA shares may indicate whether the PDUFA date is realistic:

FDA SignalInterpretationSponsor Action
"Review is progressing on schedule"PDUFA date likely to holdContinue launch planning on schedule
"We have questions that will require an information request"Potential for minor or major amendmentPrepare for IR response; assess PDUFA date risk
"We are considering an advisory committee"AdComm may be scheduled before PDUFA date; timeline may be tightBegin AdComm preparation; confirm PDUFA date is achievable
"Significant concerns have been identified"CRL risk is elevatedPrepare contingency plans; consider requesting a meeting to discuss
"Pre-approval inspection has not been scheduled"Inspection-related delay possibleContact ORA to expedite PAI scheduling

PDUFA VII Mid-Cycle Communication Commitments

Under PDUFA VII (fiscal years 2023-2027), FDA committed to specific communication milestones during the review cycle:

CommitmentDescription
Mid-cycle communicationFDA will communicate with the sponsor at approximately the midpoint of the review cycle
Late-cycle meetingFDA will meet with the sponsor during the last 2-3 months of review if significant issues remain
Content of communicationStatus of the review, preliminary identification of significant issues, anticipated information requests
Format flexibilityCommunication may be written, teleconference, or in-person depending on complexity

These commitments apply to original NDA and BLA applications, efficacy supplements, and Class 2 resubmissions. They generally do not apply to Class 1 resubmissions (which have a 2-month review period) or to ANDAs (which are governed by GDUFA commitments).

Is the mid-cycle meeting mandatory?

Under PDUFA VII, FDA has committed to providing mid-cycle communications. It is not optional from FDA's perspective for covered applications. However, the format (written vs meeting) is at FDA's discretion.

Can I decline a mid-cycle meeting?

You can, but there is no strategic reason to do so. The mid-cycle meeting provides valuable intelligence about the review status. Declining forfeits an opportunity to learn about potential issues early.

Does a positive mid-cycle signal guarantee approval?

No. The mid-cycle meeting is a status checkpoint. Even if FDA reports no significant issues at mid-cycle, new concerns can emerge during the remainder of the review, during the pre-approval inspection, or at the advisory committee meeting.

What if FDA raises concerns at mid-cycle that I disagree with?

Note the concerns and assess whether they warrant a formal response. If FDA's concerns are based on a misunderstanding of your data, you may be able to provide clarification through informal channels or a formal meeting request. Do not ignore mid-cycle signals.

Does the mid-cycle meeting apply to priority review applications?

Yes. PDUFA commitments for mid-cycle communications apply to both standard and priority review applications, though the timing is compressed for priority review (occurring around Month 2-3 from filing rather than Month 5-6).

What if I have not heard from FDA by the expected mid-cycle window?

Contact the FDA project manager to inquire about the status of the mid-cycle communication. Delays may occur due to FDA workload, but the commitment is for FDA to provide the communication.

References