Preparing for a Successful Pre-IND Meeting with the FDA

Introduction to Pre-IND Meetings

A Pre-Investigational New Drug (Pre-IND) meeting is one of the most valuable opportunities for sponsors to engage with the FDA early in the drug development process. Classified as a Type B meeting, it enables sponsors to align their nonclinical, clinical, and Chemistry, Manufacturing, and Controls (CMC) plans with FDA expectations before submitting an IND application.

The objective is to de-risk the IND submission by obtaining feedback on data gaps, clinical protocol design, and regulatory concerns. While Pre-IND meetings are not mandatory, they are strongly encouraged—especially for novel molecules, complex products, or first-in-human (FIH) studies.

Regulatory professionals frequently consult international regulatory portals such as India’s Clinical Trials Registry (CTRI) to understand how similar investigational products were planned and approved.

When Should You Request a Pre-IND Meeting?

Sponsors typically request a Pre-IND meeting 6–12 months prior to submitting their IND. This timing allows enough flexibility to:

• Incorporate FDA feedback into the development plan
• Complete additional nonclinical studies if required
• Revise the clinical protocol or CMC data

The ideal timing depends on your program’s complexity. For high-risk drugs such as gene therapies or cytotoxic agents, early interaction is critical.

Requesting the Meeting: Key Requirements

Sponsors must submit a formal meeting request to the appropriate FDA division. The request should include:

• Proposed meeting format (teleconference, written response, or face-to-face)
• Rationale for the meeting
• A list of proposed questions
• Timeline of development activities

The FDA typically responds within 21 calendar days, confirming whether the meeting is granted and specifying the date (usually 60 days from acceptance).

Preparing the Briefing Package

The briefing package is the foundation of the meeting and must be submitted no later than 30 days before the scheduled meeting. It must be clear, concise, and structured to enable efficient FDA review.

The standard contents of a briefing package include:

• Executive Summary
• Product description and mechanism of action
• Summary of completed and planned nonclinical studies
• Overview of CMC, including formulation and stability data
• Draft clinical protocol or study synopsis
• Specific, numbered questions for FDA input

Sample Table: Pre-IND Questions Format

Strategic Tips for an Effective Pre-IND Meeting

Simply securing a Pre-IND meeting isn’t enough — the goal is to extract meaningful feedback. Consider these best practices:

• Prioritize high-impact questions over low-value administrative ones
• Use cross-functional teams to prepare answers to anticipated FDA queries
• Keep briefing documents under 100 pages, unless justified
• Use standard CTD module formats for ease of review

Meeting Execution and Post-Meeting Actions

Conducting the Meeting: Roles and Responsibilities

Pre-IND meetings are typically held as teleconferences. The meeting is led by the FDA project manager, and attendees may include nonclinical, clinical, and CMC reviewers.

The sponsor team should include a regulatory lead, subject matter experts, and a designated note-taker. Key roles include:

• Regulatory Lead: Drives agenda and manages time
• Clinical Lead: Answers protocol-related questions
• CMC Lead: Addresses manufacturing and formulation queries

The sponsor should rehearse the meeting in advance, including potential follow-up questions. It’s also wise to prepare contingency slides or data to address unanticipated concerns.

FDA Responses: Interpreting and Using the Feedback

The FDA will issue official meeting minutes within 30 days, which become part of the regulatory record. These minutes will reflect:

• The FDA’s responses to each submitted question
• Clarifications or follow-ups discussed during the meeting
• Agreements or disagreements on trial design and data plans

Sponsors should not assume verbal comments override written responses. Regulatory actions must be based on documented FDA positions.

Addressing Gaps and Follow-Up Actions

Based on the meeting outcomes, sponsors may need to:

• Conduct additional safety studies
• Revise the clinical protocol or dosing plan
• Update CMC controls or release specifications

For instance, if the FDA recommends a lower starting dose, the sponsor should update the protocol and justify changes in the IND cover letter.

Integrating Pre-IND Feedback into the IND Package

Incorporating FDA feedback improves the quality and reviewability of the final IND. When submitting the IND, sponsors should include a section summarizing how each Pre-IND comment was addressed.

This shows responsiveness, regulatory maturity, and risk-based thinking — key values that FDA reviewers appreciate. It may also reduce the likelihood of a clinical hold.

Global Perspective: Similar Meetings in Other Jurisdictions

Many countries have equivalent mechanisms for early regulatory interaction. Examples include:

• EU (EMA): Scientific Advice Meeting
• Japan (PMDA): Consultation Meetings
• Canada (Health Canada): Pre-CTA Meetings

These processes vary in formality but serve the same purpose — aligning on data expectations and minimizing regulatory risk.

For comparative insights, sponsors may consult databases like ANZCTR (Australia & New Zealand Clinical Trials Registry).

Conclusion: Leveraging the Pre-IND Meeting for Regulatory Success

A Pre-IND meeting is more than a procedural step — it is a strategic engagement that can shape the trajectory of a drug development program. Thoughtfully preparing the briefing package, asking the right questions, and fully leveraging FDA insights can significantly improve IND quality and reduce review timelines.

Sponsors should treat the Pre-IND meeting as an opportunity to demonstrate scientific readiness, regulatory diligence, and commitment to patient safety. When executed correctly, this meeting becomes a foundational moment in successful IND planning and clinical trial authorization.