Best Practices and Common Pitfalls in FDA Pre-Submission Meetings

Why Pre-Submission Meetings Matter

FDA pre-submission meetings—whether Type A, B, or C—are pivotal for shaping the direction of a drug, biologic, or device development program. These sessions offer sponsors the chance to receive guidance, resolve issues, and align expectations with regulators early in the process. However, to derive value from these interactions, sponsors must understand how to conduct themselves, what to avoid, and how to present a cohesive regulatory strategy.

Missteps in these meetings can lead to miscommunication, delays, or even incorrect assumptions about the regulatory pathway. Conversely, a well-prepared sponsor can build trust with the agency and accelerate their submission timelines.

Top 5 Dos for Pre-Submission Interactions

Let’s begin with the key practices every sponsor should adopt:

1. Do Submit a Clear, Focused Briefing Package: Frame questions with background context and highlight any data limitations. The FDA appreciates clarity, not vagueness.
2. Do Align Internally Beforehand: Ensure clinical, CMC, nonclinical, and regulatory teams agree on data interpretations and proposed strategies.
3. Do Rehearse the Meeting: Conduct mock meetings internally to fine-tune responses and test the team’s preparedness.
4. Do Treat the Meeting as Official Record: Everything discussed is subject to minutes, so choose language carefully and stay on-message.
5. Do Follow Up Professionally: Review FDA-issued minutes promptly and request corrections if warranted within the 7-day window.

Top 5 Don’ts in Pre-Submission Interactions

Equally important are the actions you should avoid at all costs:

1. Don’t Ask Hypothetical or Vague Questions: Avoid “what if” scenarios that lack a defined context or data support.
2. Don’t Introduce New Data During the Meeting: FDA reviewers base their responses on submitted materials—surprises are counterproductive.
3. Don’t Challenge Feedback in the Meeting: If disagreement arises, follow up post-meeting with a formal response rather than arguing live.
4. Don’t Let Multiple Functions Speak Uncoordinated: Designate one spokesperson to prevent confusion and duplication.
5. Don’t Exceed Allotted Time: Respect the schedule. Long-winded explanations limit the opportunity for valuable discussion.

Continue with Real-World Examples, Role of RA, Templates, and Global Learnings

Real-World Example: A Sponsor’s Costly Misstep

In one pre-NDA Type B meeting, a sponsor submitted a strong briefing package but presented new stability data during the teleconference that wasn’t included in the submission. The FDA refused to discuss it, stating that review of new information required a formal submission. This caused a six-week delay, as the sponsor had to resubmit and request another meeting.

This highlights the importance of fully incorporating all intended discussion materials within the original package.

The Role of Regulatory Affairs in Ensuring Meeting Success

Regulatory Affairs (RA) acts as the central coordinator of all meeting activities, including:

• Scheduling meetings and preparing requests
• Managing briefing document creation and submissions via eCTD
• Running internal rehearsal sessions
• Serving as the spokesperson or moderating the session
• Ensuring timely review of FDA minutes and corrections

RA’s leadership helps mitigate risks and ensures regulatory expectations are interpreted correctly.

Briefing Document Template: What to Include

• Cover Letter: States meeting type, objective, and product overview
• Proposed Agenda: Itemized discussion points with time allocation
• List of Questions: Specific, targeted, and backed by rationale
• Supporting Data: Summary tables, module references, safety summaries
• Appendices: Draft protocols, relevant regulatory precedents

Formatting should follow FDA eCTD specifications and be placed in Module 1.6.1.

Case Study: Successful Pre-IND Meeting

A clinical-stage company developing a generic nasal spray scheduled a Type B pre-IND meeting to clarify:

• Whether a comparative PK study with U.S. reference product was sufficient
• If additional nonclinical safety data were needed
• Strategies for meeting nasal deposition equivalence standards

Due to well-formulated questions and cross-functional preparedness, the FDA provided favorable responses. The sponsor avoided a costly 6-month toxicology study and proceeded directly to a pivotal BE study.

Global Best Practices for Regulatory Interactions

While FDA provides structured Type A/B/C meeting formats, other agencies like the EMA and PMDA have similar engagement protocols. For example:

• EMA uses Scientific Advice Procedures (SAP) with pre-defined question structures
• PMDA requires pre-consultation meetings before formal evaluations

Sponsors pursuing global approvals should coordinate agency interactions using a harmonized global development plan.

External Resource for Real-World Interactions

To explore past global regulatory meetings and drug development strategies, the Canada Clinical Trials Database offers insight into Canadian trial approvals and consultation timelines.

Conclusion: Discipline and Preparation Drive Success

Pre-submission interactions with the FDA are opportunities to gain clarity, prevent errors, and accelerate development. But the quality of these engagements depends entirely on how well they’re prepared and managed. Sponsors should treat these meetings as regulatory milestones, with clear structure, discipline, and documented execution.

By adhering to the dos and avoiding the don’ts, regulatory teams can build strong agency rapport and ensure their development plans are set on a compliant and efficient path.

Strategies to Effectively Prepare for a Type B FDA Meeting

What Is a Type B Meeting and Why Is It Critical?

In the U.S. drug development process, structured communication with the Food and Drug Administration (FDA) is essential for aligning clinical, regulatory, and manufacturing strategies. Type B meetings are formal, scheduled interactions between sponsors and the FDA designed to address key development milestones, including Pre-IND meetings, End-of-Phase 2 meetings, and Pre-NDA/BLA meetings.

These meetings allow sponsors to clarify regulatory expectations, mitigate potential risks, and gain critical feedback before committing major resources to clinical trials or submission activities. Poor preparation, vague questions, or missing documents can derail the utility of the meeting and delay development timelines.

Sponsors also monitor global regulatory frameworks through platforms such as WHO ICTRP to understand precedents for similar meetings worldwide.

When to Request a Type B Meeting

The FDA recognizes the following as formal Type B meetings:

• Pre-IND Meeting: Before initial IND submission
• End-of-Phase 2 Meeting (EOP2): To discuss pivotal trial design
• Pre-NDA/BLA Meeting: To align on final submission strategy

These meetings are generally granted within 60 days of request, with meeting dates confirmed 21 days after FDA receives the initial request.

Preparing the Meeting Request

A successful FDA engagement starts with a clear and focused meeting request. This document should include:

• Purpose of the meeting and specific regulatory milestone
• Proposed agenda and list of discussion topics
• Draft questions to be addressed
• Preferred format (face-to-face, virtual, or written response)
• Brief background on the investigational product

Requests must be sent to the appropriate division electronically through the FDA’s CDER NextGen Portal or ESG.

Developing a High-Impact Briefing Package

The briefing package provides FDA reviewers with essential information to prepare for the meeting. It must be submitted no later than 30 days before the meeting and should include:

• Cover letter and executive summary
• Product overview, mechanism of action, and indication
• Clinical development history and status
• Nonclinical, CMC, and clinical data summaries
• Numbered, specific questions for FDA feedback

Sample Table: Draft Questions for a Type B Meeting

Execution, Documentation, and Post-Meeting Actions

Internal Preparation and Role Assignments

A well-coordinated internal preparation plan can make or break a Type B meeting. Sponsors should assign clear roles:

• Regulatory Lead: Owns the meeting agenda and communication with the FDA
• Clinical Lead: Responds to questions on trial design and endpoints
• CMC Lead: Addresses manufacturing, stability, and product quality queries
• Medical Monitor: Handles safety and adverse event strategy

Conduct a mock meeting or rehearsal to anticipate possible FDA follow-up questions, especially for End-of-Phase 2 meetings.

Conducting the Meeting: What to Expect

Type B meetings are typically 1 hour long and held via teleconference. The FDA project manager will lead the session, and FDA reviewers from relevant disciplines will participate.

Key tips:

• Stick to the agenda — time is limited
• Do not present lengthy slides unless requested
• Clarify ambiguities without debating FDA positions
• Take detailed notes and confirm FDA statements post-meeting

FDA Meeting Minutes and Their Importance

The FDA will issue official meeting minutes within 30 calendar days. These minutes are binding and should reflect the meeting’s discussions and conclusions accurately.

Sponsors should review the draft minutes carefully and request corrections within 7 calendar days if discrepancies exist.

Post-Meeting Actions and Alignment

After the meeting:

• Circulate minutes internally to align all stakeholders
• Document all decisions and rationale in the regulatory strategy file
• Update protocols, CMC plans, or timelines as agreed upon
• Prepare for follow-up meetings if further guidance is needed

All commitments and clarifications should be traceable in the IND submission history and eCTD sequence.

Global Variations in Regulatory Engagement

While the FDA’s Type B meeting structure is well-defined, other regulatory agencies offer similar scientific advice or pre-submission meetings:

• EMA: Scientific Advice Procedures
• PMDA (Japan): Clinical Trial Consultation
• TGA (Australia): Pre-submission meetings for clinical trial applications

Regulatory teams should align global development plans with feedback from multiple authorities to ensure harmonization.

Conclusion: Maximizing Value from Your Type B FDA Meeting

A Type B meeting with the FDA is a powerful regulatory milestone that can accelerate drug development, clarify expectations, and de-risk clinical programs. Success depends on strategic planning, precision in communication, and structured documentation.

By crafting a focused agenda, asking high-value questions, and aligning internally, sponsors can turn FDA meetings into catalysts for forward momentum. Thorough meeting preparation is not just best practice — it’s a regulatory imperative.