Back to Insights
    FDAPre-INDRegulatory StrategyIND
    Share on LinkedIn

    How to Prepare for an FDA Pre-IND Meeting (and What Most Teams Get Wrong)

    August 29, 20267 min readUpdated
    Neta Kela, PhDWritten byNeta Kela, PhDFounder & Managing Partner

    A pre-IND meeting is the cheapest regulatory advice a biotech company will ever receive. It is also, in our experience, the most frequently wasted.

    The pattern is consistent. A team requests the meeting because it is on the checklist, submits a briefing book that describes the program rather than tests it, asks questions the agency can only answer with "refer to the guidance", and comes away with minutes that change nothing. The meeting happened. The value did not.

    What is a pre-IND meeting?

    A pre-IND meeting is a formal interaction with the FDA review division that will handle your investigational new drug application, held before that IND is submitted. It is a Type B meeting. You submit a meeting request with proposed questions, then a briefing package, and FDA either grants a meeting or responds in writing.

    The purpose is narrow and useful: to get the division's view on whether your planned nonclinical package, manufacturing approach, and proposed first-in-human study design will support the IND you intend to file.

    Why it matters more than teams expect

    FDA's answers at pre-IND are not binding, but they are the clearest signal you will get before you have spent the money. A division that flags an inadequate toxicology species, an unresolved impurity question, or a starting dose rationale it does not accept has just saved you a clinical hold and, usually, two to four quarters of program time.

    The economics are asymmetric. The meeting costs weeks of internal preparation. Discovering the same issue after submission costs a filing cycle.

    What to ask

    The single biggest determinant of value is question quality. Good pre-IND questions share three properties:

    • They present your proposed position, not an open enquiry. "We propose rat and dog as the toxicology species based on metabolic comparability shown in Section 4.2. Does the division agree?" is answerable. "Which species should we use?" is not.
    • They concern decisions you have not yet locked. Asking about a study you have already run buys you nothing.
    • They are limited in number. Most teams should bring somewhere between six and ten questions across nonclinical, CMC, and clinical. More than that and the division prioritises for you.

    Typical high value areas: adequacy of the nonclinical safety package, starting dose and dose escalation rationale, the manufacturing and analytical package needed to support first-in-human, patient population and eligibility for the initial study, and whether any expedited pathway or designation is worth pursuing.

    What belongs in the briefing book

    The briefing package is not a data dump and it is not a pitch. It is the argument that supports each of your questions, and nothing else.

    Practical structure that works:

    1. Product and program overview, kept short.
    2. Proposed clinical development plan and the specific first-in-human protocol synopsis.
    3. Nonclinical summary organised around the safety conclusion, not around the study list.
    4. CMC summary: drug substance, drug product, comparability plan, and stability status.
    5. Each question, restated with your proposed position and the data supporting it.

    Two failure modes to avoid. The first is omission: leaving out the data that would let a reviewer agree with you, which guarantees a hedged answer. The second is volume: burying the argument in appendices so the reviewer builds their own view instead of evaluating yours.

    Where teams lose the value

    • Requesting the meeting too late. If the toxicology studies are already running, most of the questions worth asking are moot.
    • Treating the written response as a formality. FDA often answers in writing rather than granting a meeting. That response is the deliverable. It deserves the same analysis as live minutes.
    • Not rehearsing. In a live meeting the division may ask a question you did not anticipate. Teams that have not run an internal rehearsal answer inconsistently, and the inconsistency itself becomes a finding.
    • Not translating minutes into decisions. The meeting produces obligations. If nobody converts them into changes in the nonclinical, CMC, and clinical plans within weeks, the same gaps reappear at submission.

    A realistic timeline

    Work backwards from the IND filing date. Roughly 12 to 18 months out, the program should know what it wants to ask. The meeting request and package need to be built before nonclinical design is fixed, because that is where the leverage is. Preparation itself typically takes six to ten weeks of real effort across regulatory, nonclinical, CMC, and clinical, plus rehearsal.

    The takeaway

    A pre-IND meeting rewards specificity. Come with positions, bring the data that supports them, ask about decisions still open, and rehearse. Teams that do this get answers they can act on. Teams that describe their program get a polite restatement of published guidance.

    If you want senior review of your questions and briefing book before you submit them, that is exactly the work our team does. See FDA regulatory consulting and IND-enabling regulatory strategy, or email Info@PreciseXMed.com.

    Frequently Asked Questions

    How PXM Helps With This

    Related

    Part of FDA & CMC Readiness. Start from the pillar: Operate practice, FDA Regulatory Readiness, CMC & Manufacturing, FDA Expedited Pathways, EU Regulatory Pathways

    Get notified when we publish new funding and regulatory guides

    Practical guidance on FDA and EMA strategy, CMC readiness, and non-dilutive funding — sent only when there is something worth reading.