Building a Regulatory Strategy Before You Need One: Pre-IND Meeting Prep

Why the Pre-IND Meeting Matters More Than Sponsors Often Realize

The Pre-IND meeting (a Type B meeting under FDA's meeting classification system) is the sponsor's opportunity to get FDA's input on the nonclinical package, the proposed clinical protocol, the CMC plan, and the overall development strategy — before committing to an IND submission and, ultimately, dosing human subjects. It matters for a few concrete reasons:

None of this is news to experienced regulatory teams. What's often underappreciated, particularly at small biotechs without a dedicated regulatory affairs lead, is how early the real preparation needs to begin.

The Core Problem: Treating It as an Event, Not a Process

The instinct at many small companies is to treat the Pre-IND meeting as a discrete task: assemble a briefing book, submit it, show up, get feedback, move on. That framing misses what actually determines whether the meeting is useful.

A Pre-IND meeting is only as good as the questions you bring to it — and the data you have to support your proposed positions. If your regulatory strategy has been developed reactively, cobbled together in the weeks before the meeting request, you'll likely end up asking generic questions and getting generic, less useful answers. If instead your strategy has been shaped deliberately over the preceding months, informed by precedent, nonclinical data, and a clear development rationale, the meeting becomes a genuine strategic conversation rather than a box-checking exercise.

Building the Strategy: What Should Happen Before You Request the Meeting

Start with precedent, not just your own data

Before drafting a single question for FDA, understand what similar programs have done. This means:

• Reviewing FDA guidance documents relevant to your drug class, indication, and any special designations you might pursue (orphan drug, breakthrough therapy, fast track)
• Studying approved labels and review documents for comparable drugs — particularly the clinical pharmacology and nonclinical review sections available through Drugs@FDA
• Understanding the specific review division's history with your drug class or mechanism, since divisions can differ meaningfully in their expectations and areas of emphasis
• Identifying any special regulatory pathways that might apply (accelerated approval, tissue-agnostic development, rare pediatric disease designation) early enough that they shape rather than follow your development plan

This groundwork should happen well before the Pre-IND meeting is on the calendar, ideally in parallel with late preclinical work, so that your nonclinical program is being designed with regulatory expectations in mind rather than retrofitted afterward.

Build the nonclinical package with the clinical plan in view

One of the most common sources of Pre-IND feedback gaps is a nonclinical package that was designed in isolation from the clinical development plan. Toxicology studies, in particular, need to be scoped to support the intended clinical dose, duration, and patient population — not just generic safety characterization.

Key questions to resolve internally before the meeting:

• Does the toxicology program support the duration and dose range you intend to study clinically?
• Are the species and study designs appropriate and justified for your specific mechanism and modality?
• Is your safety pharmacology package adequate for the intended patient population, including any special populations you might need to study later?
• Do you have a clear rationale for your starting dose calculation, and is it defensible under FDA's guidance on estimating the maximum recommended starting dose?

Draft your clinical protocol synopsis early, even in rough form

FDA expects to see a proposed clinical protocol synopsis at the Pre-IND stage — not a finished protocol, but enough detail to evaluate your proposed approach. Sponsors sometimes under-invest in this because it feels premature relative to where the program is. In practice, drafting even a rough synopsis early forces useful discipline:

• It clarifies your primary and key secondary endpoints, and whether they're likely to be regulatorily meaningful
• It surfaces dose-selection questions (increasingly important given Project Optimus expectations in oncology, and analogous dose-optimization scrutiny in other therapeutic areas)
• It forces early thinking about patient population, inclusion/exclusion criteria, and any biomarker-based enrichment strategy
• It reveals where your nonclinical data does or doesn't adequately support the proposed clinical approach

Identify your real questions, not generic ones

The single biggest determinant of a Pre-IND meeting's value is the quality of the questions submitted to FDA. Vague questions get vague, low-value answers. Specific, well-supported questions get specific, actionable feedback.

The stronger question does several things: it's specific enough that FDA can give a real answer, it demonstrates that you've already done the analytical work rather than asking FDA to do it for you, and it creates a documented position you can reference later if the same question resurfaces during IND review.

Loop in CMC earlier than feels necessary

Chemistry, manufacturing, and controls issues are a common source of IND delays, and Pre-IND is an underused opportunity to surface CMC questions early. Small biotechs, especially virtual or asset-light companies relying on contract manufacturers, sometimes treat CMC as a parallel workstream that doesn't need regulatory input until later. This can be a costly assumption.

Questions worth resolving or at least raising at Pre-IND:

• Is your proposed manufacturing process and analytical characterization adequate for Phase 1 material?
• Are there specific impurity, stability, or formulation questions where early FDA input would change your manufacturing timeline?
• For biologics and complex modalities in particular, are there platform-specific CMC expectations you should understand before IND submission?

Assemble the briefing book as a strategic document, not an administrative one

The briefing book is where all of this preparation becomes concrete. It should:

• Present a clear, coherent development rationale, not just a data dump
• Organize nonclinical, clinical, and CMC sections so FDA can efficiently connect your questions to the supporting data
• State your proposed positions explicitly, not just ask open questions. FDA responds more efficiently to "we propose X, please confirm or provide alternative guidance" than to "what should we do about X?"
• Be submitted with enough lead time to meet FDA's briefing book deadline (typically at least 30 days before the meeting, though sponsors should confirm current requirements), since a late or incomplete briefing book can jeopardize the meeting itself

Timing: When to Start

A rough, program-dependent guide for small biotechs:

This timeline compresses considerably for programs with strong existing regulatory infrastructure and expands for first-time sponsors or novel modalities where precedent is thinner. The point isn't the specific number of months; it's that meaningful strategic work needs to happen well before the meeting request, not in the weeks immediately preceding it.

Common Mistakes Small Biotechs Make