What Regulatory Meetings Do Across Drug Development

Regulatory meetings across drug development are opportunities to resolve defined scientific and procedural uncertainty before a sponsor commits to expensive work. Their output is advice or an agency position based on the current record, not a promise that a later application will be approved, and the strongest meeting package behaves like a concise review file. It states the product and stage, summarizes the evidence, proposes a path, presents credible alternatives, and asks questions that can lead to an actionable answer.

Key points#

• Choose a meeting type based on urgency, development stage, and the decision that must be made.
• Ask a limited number of specific questions and provide the evidence needed to answer each one.
• Submit the package on time and keep its data, proposal, and questions internally consistent.
• Treat preliminary comments as substantive review input, not an obstacle to discuss past.
• Convert minutes and clarifications into controlled assumptions, actions, and program changes.

Meeting types map to different needs#

FDA's 2023 final guidance describes six formal PDUFA meeting types: Type A, Type B, Type B end-of-phase, Type C, Type D, and INTERACT.

Type A meetings address stalled programs or other urgent issues such as a clinical hold, dispute, or special protocol assessment impasse, though their urgency does not make them a venue for every unresolved question.

Type B meetings include common milestone interactions such as pre-investigational new drug, pre-new drug application, and pre-biologics license application meetings, and these occur at points where agreement on the next body of work has high value.

Type B end-of-phase meetings focus on transition to the next phase, especially whether available data and the proposed confirmatory program are adequate to proceed. The end-of-phase 2 meeting is often where dose, population, endpoints, safety database, statistical approach, and remaining nonclinical or manufacturing work converge.

Type C covers issues outside the other categories and can address substantive development questions. Type D is intended for a narrow set of issues, generally no more than two focused topics, that can receive a faster interaction, but it should not be used to split a complex multidisciplinary discussion artificially.

INTERACT meetings are early interactions for novel products before a pre-IND meeting, when preliminary proof-of-concept exists but definitive toxicology and a full clinical plan are not yet mature. FDA's Office of Therapeutic Products provides program-specific detail for cellular and gene therapies. Meeting names and eligibility are governed by current guidance and user-fee commitments, so verify the current framework for your center and your product rather than relying on an old slide deck.

The development stage changes the useful question#

Before an IND, useful questions may concern the adequacy of pharmacology and toxicology, the starting dose rationale, safety monitoring, chemistry and manufacturing controls, or the initial clinical protocol. The goal is not to have FDA design the program. It is to test a reasoned proposal against regulatory expectations before human dosing.

During early clinical development, emerging pharmacokinetics, dose-response, safety, biomarker performance, and population findings shape the next study; a meeting can address whether the planned dose-ranging work and endpoints will support later choices.

At end of phase 2, uncertainty becomes expensive, so the proposed phase 3 program should define the indication, estimand, control, dose, endpoints, multiplicity strategy, subgroup plans, treatment duration, safety population, and handling of intercurrent events. Manufacturing readiness and nonclinical obligations must align with the same product and timeline.

Before NDA or BLA submission, the interaction shifts toward application readiness: content and format, datasets, integrated analyses, electronic submission, proposed labeling, outstanding studies, inspections, and known review issues. This is not the moment to discover that pivotal endpoints do not support the proposed claim. Postapproval meetings may address commitments, safety signals, labeling changes, manufacturing changes, additional indications, or required studies. Product lifecycle decisions continue after the initial application.

A sharp question contains a proposal#

“Does FDA agree with our phase 3 plan?” is too broad. A reviewable question identifies the choice and why it is supported:

“Does the Agency agree that the proposed primary endpoint at week 24, analyzed with the specified treatment-policy estimand, is appropriate to support the proposed indication in population X?”

The package would then summarize the disease context, endpoint validity, phase 2 relationship, missing-data plan, intercurrent events, analysis, and alternatives. The question can receive a yes, no, conditional answer, or request for more information.

Questions should be ordered by consequence. A dose-selection issue that changes the protocol belongs before a formatting preference. Each question should have one clear sponsor position. Presenting several options without a recommendation asks the agency to do your decision work for you. Avoid compound questions whose parts need different expertise or evidence. If the answer to one part changes the premise of the next, show that dependency.

The briefing package is the meeting#

Reviewers form preliminary positions from the package. Slides you show later cannot repair evidence that arrived after the review timeline.

A strong package usually includes:

1. product, indication, mechanism, development stage, and regulatory history;
2. concise nonclinical, clinical, statistical, and manufacturing summaries relevant to the questions;
3. prior agency advice and how it was addressed;
4. important unfavorable or uncertain findings;
5. the proposed path and alternatives considered;
6. numbered questions with sponsor positions and rationale;
7. referenced protocols, tables, figures, and appendices;
8. a participant list matched to the discussion.

Data should be traceable to cut dates and product versions. Numbers in the executive summary, tables, and question rationale must agree. Selective favorable summaries erode trust and invite basic clarification instead of useful advice. The package should be as short as the questions permit, not artificially brief. A narrow Type D request and an end-of-phase program discussion need different depth.

Preliminary responses should change meeting preparation#

FDA may provide preliminary written responses before a scheduled meeting. These responses can answer some questions fully, raise new conditions, or reveal that the sponsor's proposal was misunderstood.

The team should triage each response:

• Accept and confirm it without spending meeting time.
• Seek clarification of a specific phrase or condition.
• Present a focused new fact that could change the answer.
• Defer the question because the required evidence is not ready.

Rearguing every unfavorable response wastes the interaction. A productive discussion tests the reasoning, identifies the remaining gap, and determines which evidence would resolve it.

Internal rehearsal should include clinical, statistics, safety, regulatory, nonclinical, manufacturing, and operations only as relevant. Assign one lead for each question and a moderator who prevents digressions. Rehearsal should test contradictory assumptions, not polish speeches.

Limits of regulatory advice#

Formal minutes document the agency's understanding of the discussion. Advice is based on the submitted facts, current science, and current law. New safety findings, product changes, failed studies, or evolving standards can change what is needed.

Agreement on a protocol feature is not agreement that the resulting data will be favorable or sufficient. Agreement that a submission may be filed is not approval. Regulatory language should preserve those distinctions.

If the minutes do not reflect an important point, FDA procedures allow a timely request for clarification under defined conditions. Clarification should identify the exact ambiguity, not reopen a settled disagreement through a new argument.

EMA scientific advice is a separate European procedure. It can address medicine-development questions and protocol assistance for orphan medicines, but it is not legally binding authorization and does not replace FDA interaction. Parallel or sequential advice may reveal differences that the global plan must reconcile.

Turn the record into program memory#

After the meeting, create a decision log that links each question to:

• sponsor proposal;
• written preliminary response;
• meeting discussion;
• official minute;
• final interpretation;
• affected protocol, analysis, manufacturing, or evidence document;
• owner and due date;
• open risk if advice is not followed.

Distinguish direct agency statements from internal inference. “FDA stated X” should quote or cite the record accurately. “The team interprets X to require Y” is a controlled internal decision and may need confirmation.

If the sponsor chooses a different path, document the scientific and regulatory rationale and the risk. Advice can be nonbinding while still being highly consequential.

A meeting-readiness test#

Your program is ready when you can answer:

1. What decision must be made now?
2. Why is this the correct meeting mechanism?
3. What is the sponsor's proposed answer?
4. Which data directly support it?
5. Which unfavorable data or uncertainty could change it?
6. What practical action follows each possible agency response?
7. Are product versions, populations, endpoints, and timelines consistent across disciplines?
8. Has all prior advice been addressed or explicitly reconsidered?

If the team cannot state the action that follows an answer, the question may not yet be useful.