Understanding FDA Type A, B, and C Meetings: Differences and Case Examples

Overview of FDA Pre-Submission Meeting Types

Interacting with the U.S. Food and Drug Administration (FDA) is essential for successful regulatory navigation, especially in drug, biologic, or device development. The agency offers three structured meeting types — Type A, Type B, and Type C — each serving a specific purpose at different points in the product development lifecycle.

Knowing when to request each type and what to expect can significantly influence timelines, clinical program design, and eventual marketing approval.

FDA Type A Meetings: Crisis Resolution or Stalled Programs

Type A meetings are granted to help a sponsor address a stalled development program or to resolve critical regulatory issues that cannot wait. Examples include:

• Dispute resolution after a clinical hold
• Meeting following refusal-to-file (RTF) decision
• Type A meeting following a Complete Response Letter (CRL)

Timelines: FDA schedules these meetings within 30 days of receiving the request. These are generally high priority.

Briefing package: Submitted at the time of meeting request or within 2 days of request acceptance.

FDA Type B Meetings: Key Milestone Interactions

Type B meetings are the most common form of pre-submission interaction. They occur at critical points such as:

• Pre-IND meeting
• End-of-Phase 2 (EOP2) meeting
• Pre-NDA or pre-BLA meeting

These meetings help confirm that safety, efficacy, and CMC strategies align with regulatory expectations.

Timelines: Meeting scheduled within 60 days of request. FDA responds within 14 days of request receipt.

Briefing package: Submitted at least 30 days before the confirmed meeting date.

FDA Type C Meetings: Other Development Topics

Type C meetings are for any topics not falling under Type A or B criteria. Examples include:

• Discussing a novel biomarker development plan
• Seeking clarification on post-marketing study designs
• Requesting early feedback on patient-reported outcomes

These are useful for advancing complex or innovative elements of the development program.

Timelines: Scheduled within 75 days of request; longer than Type A or B.

Continue with a Comparative Table and Real-World Case Studies

Comparative Table: FDA Meeting Types at a Glance

Case Study 1: Type A Meeting to Address CRL

A company received a Complete Response Letter (CRL) for a small-molecule oncology product due to concerns about CMC variability and missing safety data in an elderly subpopulation. A Type A meeting was requested to:

• Clarify what additional clinical trials were required
• Negotiate if bridging data could be used
• Understand timeline for resubmission

The meeting led to FDA agreement on a targeted patient population and allowed for re-analysis using real-world data, ultimately leading to a successful NDA resubmission.

Case Study 2: Type B Pre-IND Meeting

A biotech firm working on a monoclonal antibody for rare autoimmune disease held a pre-IND Type B meeting to:

• Confirm nonclinical study adequacy
• Discuss proposed starting dose in first-in-human study
• Clarify the need for additional reproductive toxicology studies

The company received valuable input, avoiding an unnecessary animal study and confirming their clinical protocol design.

Case Study 3: Type C Meeting on Patient-Reported Outcomes

A sponsor sought feedback on a new quality-of-life endpoint for a chronic pain study. Since this topic didn’t qualify for Type A or B, a Type C meeting was arranged. FDA provided:

• Recommendations on endpoint validation strategy
• Advice on integrating PROs into labeling claims

This early input helped secure FDA agreement on PRO methodology, critical to Phase 3 success.

Strategic Considerations for Meeting Type Selection

Type A: Use judiciously for major regulatory roadblocks. These meetings are rare and require strong justification.

Type B: Always plan ahead. These should be part of your regulatory roadmap and aligned with key submission milestones.

Type C: Ideal for innovative development approaches, risk assessments, or clarifications not tied to formal submissions.

External References and Tools

For examples of meeting types used in global regulatory submissions, visit the Australian New Zealand Clinical Trials Registry to review trial protocols and regulatory pathways involving early agency engagement.

Conclusion: Matching Meeting Type to Development Stage

Properly identifying and requesting the right type of FDA meeting is critical to a sponsor’s regulatory success. Each meeting type serves a distinct purpose, with differing expectations for timelines, content, and feedback. Regulatory teams should develop a long-term meeting strategy, integrated with their submission plan and product development milestones.

When planned effectively, these meetings serve not just as checkpoints but as accelerators toward successful product approval.

How Regulatory Affairs Drives Effective FDA Pre-Submission Strategies

Why Regulatory Affairs Is Central to Pre-Submission Planning

In modern drug development, regulatory success is built not only on robust science but also on the strategic involvement of Regulatory Affairs (RA). The RA function is critical in planning and executing FDA pre-submission meetings, such as pre-IND, EOP2, or pre-NDA Type B meetings. Their role is to ensure regulatory expectations are understood, met, and proactively addressed long before formal submissions are filed.

Regulatory Affairs professionals act as the bridge between cross-functional development teams and global health authorities. They interpret regulatory guidance, advise on engagement strategy, prepare meeting requests and briefing packages, and facilitate direct communication with the FDA.

Regulatory Affairs Responsibilities in the Pre-Submission Phase

Key responsibilities include:

• Meeting Strategy Development: Selecting the appropriate type and timing of the meeting (e.g., Type B vs Type C).
• Preparing the Meeting Request: Drafting the cover letter, agenda, and list of questions per FDA requirements.
• Briefing Document Management: Coordinating authorship, formatting, and internal review cycles.
• Submission via ESG/eCTD: Ensuring the package complies with eCTD structure, naming, and technical validation rules.
• Stakeholder Alignment: Aligning internal teams (Clinical, CMC, Nonclinical) on messaging and data presentation.
• Meeting Execution: Leading the live interaction, taking notes, and ensuring discussions stay focused on regulatory questions.
• Meeting Minutes Review: Reviewing FDA-issued minutes and confirming accuracy or requesting corrections.

Developing a Strategic Regulatory Roadmap

Regulatory Affairs doesn’t work in isolation. Early in development, RA leads the creation of a regulatory roadmap—a document that aligns submission timelines with FDA interaction points and development milestones.

For example, RA may advise:

• Pre-IND at Month 6 to confirm toxicology studies are sufficient
• EOP2 at Month 24 to gain feedback on pivotal trial design
• Pre-NDA meeting at Month 42 to finalize submission structure

These planned touchpoints reduce risk and clarify regulatory expectations.

Continue with Cross-Functional Role, Case Study, Tools, and Global Considerations

Cross-Functional Coordination Led by Regulatory Affairs

RA plays a cross-functional coordination role, ensuring all departments contribute to the briefing document and meeting preparation. Each function—Clinical, CMC, Nonclinical, Biostatistics—needs to align their messaging.

Example scenario:

• Clinical: Designs study and prepares protocol synopsis
• CMC: Provides manufacturing summaries, stability data
• Nonclinical: Summarizes pharmacology/toxicology studies
• RA: Integrates, formats, and ensures regulatory compliance

RA also arranges mock meetings to simulate FDA interactions and test the team’s preparedness.

Case Study: Regulatory Affairs in a Pre-NDA Meeting

A mid-sized sponsor preparing for a pre-NDA Type B meeting for a novel oral anticoagulant tasked their RA team to lead preparations. Their responsibilities included:

• Coordinating with medical writers to draft the 90-page briefing book
• Ensuring all stability data from the updated commercial formulation were included
• Submitting the document in Module 1.6.1 of the eCTD sequence
• Managing the FDA teleconference agenda and post-meeting minutes

Their diligence ensured FDA alignment on remaining labeling and REMS questions, allowing a smooth NDA submission 45 days later.

Tools and Templates Used by Regulatory Affairs

• Briefing Book Template: Pre-approved structure with modular sections
• FDA Meeting Tracker: Spreadsheet tool for status, timelines, and assigned owners
• Submission Checklist: Ensures compliance with Module 1 eCTD placement rules
• Regulatory Intelligence Database: Stores prior meeting outcomes, competitor precedents, and FDA guidance

RA teams often invest in these tools to streamline preparation and reduce errors in documentation.

Global Perspective: RA Coordination Across Agencies

In multinational programs, Regulatory Affairs is responsible for harmonizing pre-submission planning across the FDA, EMA, MHRA, and PMDA. For example:

• FDA Type B meeting scheduled in Q1
• Scientific Advice with EMA planned in Q2
• PMDA pre-Consultation session requested in Q3

This staggered scheduling allows for incorporation of cross-agency feedback and consistency in global development strategy.

Where to Find Additional Guidance

The Japan PMDA Clinical Trial Portal provides valuable regulatory meeting insights and templates applicable across jurisdictions, particularly for combination products or devices.

Conclusion: Regulatory Affairs as the Strategic Anchor

Regulatory Affairs teams are not just compliance enablers—they are the architects of strategic engagement with health authorities. Their early involvement in planning, content management, communication, and execution is what transforms a meeting into a meaningful regulatory milestone.

By understanding and applying best practices in FDA pre-submission strategy, RA professionals help ensure that clinical development stays aligned with regulatory expectations—reducing risk, time, and cost for sponsors.