Seven Ways to Waste an INTERACT Meeting

An INTERACT meeting (INitial Targeted Engagement for Regulatory Advice on CBER/CDER ProducTs) is FDA’s earliest formal touchpoint for a novel therapy. It exists for sponsors facing a genuinely new or challenging problem, one that could stall the program before it ever reaches the clinic, and who need the agency’s read before a pre-IND meeting makes sense.

It is deliberately early, science-focused, and non-binding. FDA generally grants one INTERACT per program, but even with these restrictions companies typically don’t get the most out of these programs. The problem is rarely that FDA was unhelpful. It is that the sponsor brought the wrong question, at the wrong altitude, in a package that made the reviewers work to understand the basics.

The good news: every common failure is avoidable, and most are decided before the meeting is ever scheduled. This playbook walks the seven ways INTERACT meetings go wrong, from wrong expectations to weak follow-through, and what good looks like at each step.

01 · THE WRONG MENTAL MODEL

Treating INTERACT like a pre-IND or a blessing

Two mistakes account for most disappointing INTERACT meetings, and they pull in opposite directions. The first is treating INTERACT like a pre-IND: showing up with a nearly complete development plan and expecting the agency to review it. That is the wrong venue, and that level of maturity is more appropriate for a pre-IND. The second is treating INTERACT like an informal blessing that locks in FDA’s position, without realizing this is the first in a long journey of FDA interactions.

Neither is what the meeting is for. INTERACT is very early, science-focused, and gives early feedback on challenging issues not captured in existing FDA Guidance. Its job is narrow: surface major feasibility or safety red flags before you invest in IND-enabling work, and sanity-check your overall development concept and the key experiments behind it. If your issue is not novel or blocking, or if it already has a clear answer in existing guidance, INTERACT is not the right tool.

02 · QUESTIONS THAT ARE TOO BROAD

Vague asks get generic answers

The fastest way to waste the meeting is to ask questions FDA can only answer at 30,000 feet. “What do you think of our program?” “What CMC package will you need for the IND?” “Is our overall clinical plan reasonable?” These feel efficient, but they force the reviewers into high-level, generic responses, and the meeting ends without a single takeaway you can act on.

The fix is to make every question specific and science-based, tied to a decision you are actually trying to make. A good INTERACT question names the option you are weighing, the risk you are trying to characterize, and the constraint you are working under, so the reviewer can give you a real read rather than a platitude.

03 · QUESTIONS THAT ARE TOO DETAILED

IND-level questions burn the slot

The opposite error is just as costly. Sponsors arrive with near-final protocols, a detailed CTD structure, or line-by-line data gaps and ask the agency to work through them. INTERACT reviewers will not do that this early. They will tell you the question is more appropriate for a pre-IND meeting and decline to give detailed, line-by-line comments. You will have spent your one slot to be redirected.

Calibrating altitude is the whole game. INTERACT is for the novel, blocking question that sits where the guidance runs out, not for confirming details that a pre-IND or the IND review will settle anyway. Before you submit, sort every candidate question: if it has a clear answer in existing guidance, drop it; if it is really a pre-IND question, hold it; what remains is your INTERACT agenda.

04 · A WEAK BRIEFING PACKAGE

Making FDA reconstruct the basics

When a package is poorly built, the reviewers spend their limited preparation time just trying to understand your product, and answer your real questions only in whatever time is left. That is the most common and most fixable way to lose value. The recurring defects are predictable.

• Mechanism of action or biological rationale that is missing, buried, or unclear.
• Proof-of-concept data described only in prose, with no figures, no tables for explanation.
• No clear description of product identity, critical quality attributes, or the proposed manufacturing concept.
• A long, disorganized document with no upfront summary of the big questions you actually want answered.

A strong package provides a clear mechanism of action and the rationale, presents each key result as a figure or table, describes the product and manufacturing concept plainly, and states your questions up front with your position so a reviewer knows what you need before reading page two.

05 · AN UNALIGNED INTERNAL TEAM

Fragmented on the call, confused after it

INTERACT is cross-functional by nature, and it exposes any internal disagreement in real time. When clinical, CMC, nonclinical, and regulatory have not aligned before the call, two things happen. The discussion fragments, with different functions pulling FDA in different directions, and afterward the team cannot agree on what was actually recommended.

Alignment means two decisions made in advance, not one. First, the top three to five questions and the answer each function is hoping to hear from FDA. Second, and more often skipped, align on what concessions you are willing to make if FDA raises a concern. Walking in knowing your fallbacks is what lets you respond coherently instead of improvising when a reviewer pushes back.

06 · OVER-INTERPRETING THE FEEDBACK

Encouragement is not clearance

It is tempting to hear what you came to hear. Sponsors routinely over-read INTERACT feedback: treating high-level encouragement as an approval path, reading “we have no objection in principle” as a binding green light, or assuming that silence on a topic means tacit agreement. None of that is true.

FDA feedback at INTERACT stage rests on early, incomplete information. Every point will be revisited, more rigorously, at the pre-IND meeting and again during the IND review, when FDA is looking at a fuller record. Encouragement tells you a path is not obviously blocked. It does not tell you the path is cleared, and it commits the agency to nothing.

07 · WEAK FOLLOW-THROUGH

Losing the value after the meeting ends

The last way to waste an INTERACT meeting is to let its output evaporate. On one side, teams fail to systematically track each FDA comment and how they will address it, and never update the nonclinical plan, CMC strategy, and early clinical concept to reflect what they heard. On the other, equally damaging side, teams make large internal commitments based on ambiguous FDA language without ever clarifying it in writing.

The discipline that prevents both is a post-INTERACT action log. Capture every FDA comment, assign an owner and a timeline, and record exactly where it will be addressed, so the meeting flows into your actual submission rather than into a slide no one reopens.

08 · THE ONE-PAGE VERSION

Do and don’t for your next package

Run this against your agenda and your briefing package before you submit the request. If any row on the left describes your plan, fix it before you spend the slot.

09 · FAQ

Frequently asked questions

Why do INTERACT meetings fail to add value? An unsuccessful meeting is rarely because FDA was unhelpful. It’s almost always because the sponsor brought the wrong question, at the wrong altitude, and in a package that made reviewers work to understand the basics. Most of these failures are decided before the meeting is ever scheduled and are based in how the questions are scoped and the briefing package is built.

What makes a good INTERACT question? A specific, science-based question tied to a decision you are actually trying to make. It describes the option you are weighing, the risk you are trying to characterize, and why you think your approach is appropriate so the reviewer can perform an in-depth assessment and give you actionable feedback.

Is FDA’s feedback at an INTERACT meeting binding? Neither INTERACT nor Pre-IND is technically binding, but you should expect the feedback to be FDA’s final position in the absence of new information. For INTERACT specifically, FDA’s feedback is based on very early and incomplete information, so there is more chance that new developments to your product and program change FDA’s position. But, if you have no new information, be prepared for the same position at Pre-IND and IND.

How is an INTERACT meeting different from a Pre-IND meeting? INTERACT is earlier and narrower: a concept-level check on a novel, blocking feasibility or safety question, before IND-enabling work is complete. A Pre-IND meeting comes later and aligns on the data package needed to support the IND. Arriving at INTERACT with near-final protocols or IND-level detail wastes an opportunity for discussion with the review team; keep the appropriate level of detail for the FDA meeting type.

What should be in an INTERACT briefing package? A clear mechanism of action and biological rationale, each key result presented as a figure or table rather than buried in prose, a plain description of product identity and the manufacturing concept, and an upfront summary that states your questions and your position on each. The reviewer should never have to reconstruct the basics or invent a rationale for your gaps.

FDA sources & references

• Formal Meetings (PDUFA) Guidance — FDA meeting types, including INTERACT, and the expectations for meeting requests and packages. fda.gov ↗
• OTP INTERACT Meetings — Office of Therapeutic Products resource on INTERACT qualification criteria, process, and common reasons for denial. fda.gov ↗
• SOPP 8101.1 — CBER standard procedure governing how early regulatory meetings are requested, evaluated, and conducted. fda.gov ↗
• Preclinical Assessment of Investigational Cellular and Gene Therapy Products — FDA guidance on the nonclinical program supporting first-in-human studies. fda.gov ↗
• Considerations for the Design of Early-Phase Clinical Trials of Cellular and Gene Therapy Products — FDA guidance on early-phase clinical development for advanced therapies. fda.gov ↗
• 21 CFR Part 312 — Investigational New Drug Application regulations that INTERACT feedback ultimately feeds toward. fda.gov ↗

This document is general educational information about INTERACT meetings and early FDA engagement. It is not legal or regulatory advice and does not create an attorney–client or consulting relationship, nor does it substitute for FDA’s guidance documents or the applicable regulations. Early regulatory engagement is highly product- and indication-specific, and FDA’s views are informal and non-binding. Confirm current FDA procedures and consider professional review of your specific program before acting.