A Type C meeting with the U.S. Food and Drug Administration (FDA) is a regulatory discussion used to clarify regulatory expectations, discuss scientific questions, and align on the path forward for a product candidate when a Type A or Type B meeting isn’t the most appropriate setting. These meetings provide a formal channel to obtain FDA input on topics such as protocol design, study endpoints, or regulatory strategy without the urgency or milestone focus of other meeting types. Proper preparation and clear questions help ensure productive dialogue and useful agency guidance.
What Is A Type C Meeting?
A Type C meeting is a non-urgent FDA meeting used to discuss regulatory issues that do not fit the criteria for Type A (urgent matters requiring avoidance of substantial delay) or Type B (milestone-driven) meetings. It is often employed for questions about regulatory expectations, study design, labeling concepts, or exploratory discussions about the regulatory pathway. It is advisory in nature and does not bind the FDA to a specific outcome, but it helps shape an applicant’s strategy and timelines.
When To Request A Type C Meeting
A Type C meeting is appropriate when a sponsor seeks FDA input on topics that are important but not time-critical or milestone-driven. Typical scenarios include discussing non-clinical testing plans, proposed endpoints for pivotal trials, chemistry, manufacturing, and controls (CMC) considerations, or questions about regulatory pathways for a novel mechanism. It can also be used to clarify agency interpretation of guidance documents or to align on a general development plan before formal plans are in place.
How To Request And Prepare For A Type C Meeting
The request process involves submitting a formal meeting package to the appropriate FDA center. Essential elements include a description of the topic, specific questions, a proposed agenda, background data, and a concise justification for why the Type C meeting is needed. Preparation steps include:
- Develop a clear, prioritized list of questions with justification for each item.
- Provide succinct supporting data or references to relevant literature and prior discussions.
- Propose an agenda with time allocations and expected FDA input areas.
- Coordinate internally to ensure cross-functional alignment on objectives and potential regulatory implications.
- Submit the package within the FDA’s specified timelines and formats to avoid delays.
Communication should be precise and well-organized, as the agency will review the questions to determine the scope of the meeting and who should attend.
What Happens During A Type C Meeting
During a Type C meeting, FDA representatives discuss the sponsor’s questions and provide interpretations of regulatory expectations. The session typically includes:
- Overview of the development plan and the questions to be addressed.
- FDA responses, clarifications, and, when applicable, recommendations for alternative approaches.
- Identification of any data gaps or additional analyses the sponsor should consider.
- Discussion of potential regulatory pathways and alignment on next steps.
Notes are typically taken and shared with the sponsor after the meeting. Because Type C meetings are advisory, the FDA’s input is not binding, but it can strongly influence decision-making and study designs.
Post-Meeting Actions And Follow-Up
Post-meeting activities are critical to translating FDA input into actions. Key steps include:
- Review the FDA meeting summary for accuracy and capture any nuances or clarifications.
- Update the development plan, study designs, and regulatory strategy based on the FDA guidance.
- Address any data gaps or additional analyses requested by the FDA in a timely manner.
- Maintain documentation of decisions, rationale, and alignment with the agency to support future submissions.
Timely follow-up demonstrates responsiveness and helps maintain alignment with FDA expectations as development progresses.
Common Questions And Best Practices
Frequently asked questions include how to determine if a Type C meeting is appropriate, what data to bring, and how to maximize productive dialogue. Best practices include:
- Engage early when questions are forming to avoid late-stage changes.
- Keep questions focused, with a clear linkage to regulatory outcomes or study design.
- Provide concise background data and references to support each question.
- Propose concrete next steps and timelines to enable practical follow-through.
- Ensure internal stakeholders (clinical, regulatory, CMC, quality) participate to capture diverse perspectives.
Anticipate potential interpretations or disagreements and plan how to address them in subsequent submissions.
Resources And References
For sponsors seeking a Type C meeting, useful resources include the FDA’s official meeting request guidance, template packages, and center-specific contact points. Typical sources of information include:
- FDA meeting guidance documents and sample packages.
- FDA center/office-specific guidance on advisory discussions.
- Checklists for required documents, formatting, and submission timelines.
- Contact points at CDER, CBER, or CDRH depending on the product category.
Keeping up-to-date with FDA policy changes and best practices is essential for successful Type C interactions and subsequent development decisions.