Pre-IND Meeting with FDA: How to Prepare and What to Expect

I once watched a startup burn four months and roughly $600,000 because they skipped the pre-IND meeting. Their reasoning was efficient-sounding: "We know the requirements, the data is clean, let's just file." They got a clinical hold on Day 33. Two of the issues FDA flagged — starting dose justification and a missing reproductive toxicity rationale — would have come up in a pre-IND meeting. FDA would have told them, in writing, before they spent the money.

The pre-IND meeting is technically optional. Practically, it's the closest thing to an open-book exam that exists in drug development.

What a pre-IND meeting actually is

It's a Type B meeting under 21 CFR 312.82 and the FDA Formal Meetings guidance. You submit a meeting request to the relevant review division. FDA has 21 calendar days to grant or deny it. If granted, you submit a briefing document at least 30 days before the meeting. The meeting itself is 60 minutes.

Here's what most people don't realize: the meeting is almost secondary. The real value is in FDA's written response to your briefing document. You get that response before the meeting happens. The review division reads your briefing document, discusses it internally, and sends you preliminary comments. Those comments are the product. The meeting is where you clarify anything ambiguous.

Some teams treat the meeting like a pitch. It's not a pitch. FDA doesn't need to be convinced your drug is promising. They need to know whether your development plan will generate the data they require to evaluate safety.

When to request it

The timing question matters more than people think. Too early, and you don't have enough data to ask meaningful questions — FDA will tell you to come back when you've done more work. Too late, and you've already committed to studies that FDA might have told you to design differently.

The sweet spot: request the meeting when you have preliminary pharmacology data, a draft nonclinical development plan, a general sense of your CMC strategy, and a concept for your Phase 1 clinical protocol. You don't need final data. You need enough to ask specific questions.

For a typical small molecule program, that's usually 12-18 months before your target IND filing date. Biologics programs should start earlier — 18-24 months — because the CMC questions are more complex and manufacturing timelines are longer.

The meeting request letter

This is where the administrative work starts. Your meeting request needs:

1. Product name and application type — IND
2. Chemical name and proposed indication — be specific
3. Meeting type — Type B (pre-IND)
4. Brief statement of purpose — 2-3 sentences on why you need the meeting
5. List of specific objectives — what decisions you want from FDA
6. List of proposed questions — numbered, specific, answerable
7. Proposed meeting dates and times — give FDA options
8. List of attendees — from your side

The letter itself is short — usually 2-3 pages. Don't overthink it. The questions list is the part that matters.

Writing questions FDA can actually answer

This is where most teams go wrong. They write vague questions and get vague answers.

Bad question: "Is our nonclinical package adequate?"

Good question: "We propose to support our Phase 1 single ascending dose study (7 days dosing) with a 14-day repeat-dose toxicity study in rats and dogs conducted under GLP per ICH M3(R2) Table 1. Is this study duration sufficient, or does the Division recommend 28-day studies given the intended chronic clinical use?"

See the difference? The second question tells FDA exactly what you're planning and asks a binary question. FDA can say "14 days is sufficient" or "we recommend 28-day studies" and give you a specific reason. The first question gets you a paragraph of general advice that doesn't help with any actual decision.

I aim for 5-8 questions. More than 10 and you're diluting the important ones. Fewer than 4 and you're probably not getting enough value from the meeting.

Questions worth asking

Based on what I've seen work:

Nonclinical package:

• Species selection and justification (especially for biologics under ICH S6(R1))
• Study duration and design for repeat-dose toxicity
• Whether your safety pharmacology core battery is complete
• Reproductive toxicity timing — can you defer to post-Phase 1?
• Starting dose selection methodology (NOAEL-based vs. MABEL)

CMC:

• Specification limits that FDA will accept for Phase 1 supply
• Comparability approach if manufacturing process changes are planned
• Reference standard strategy

Clinical:

• Dose escalation design and stopping rules
• Patient population — healthy volunteers vs. patients
• Safety monitoring plan adequacy

The briefing document

The briefing document is your main deliverable. It's a 50-100 page document that covers your entire development program in enough detail for FDA reviewers to evaluate it.

Structure it around your questions. Each section should provide the context a reviewer needs to answer the corresponding question. Don't make them hunt.

A workable outline:

1. Executive summary (1-2 pages) — drug, indication, development stage, key questions
2. Product overview — mechanism of action, therapeutic rationale
3. Nonclinical development — completed and planned studies, key findings
4. CMC summary — manufacturing, characterization, stability
5. Clinical development plan — proposed Phase 1 design, endpoints, dose rationale
6. Questions for discussion — numbered, matching the request letter

For the nonclinical section, reference specific ICH guidelines. If you're presenting pharmacokinetic data, include the key parameters: Cmax, AUC, half-life, clearance, bioavailability. If you're discussing genotoxicity, specify which assays you've completed and which are planned. FDA reviewers appreciate precision. Generic statements like "a comprehensive nonclinical program was conducted" tell them nothing.

One mistake I've seen repeatedly: burying bad data. If your drug has a finding — say, liver enzyme elevations in dogs at the high dose — put it up front. Discuss the dose-response relationship. Explain how it factors into your clinical dose selection. FDA will find it anyway. The question is whether they find it in your transparent discussion section or in the appendix tables where it looks like you were hiding it.

The meeting itself

Most pre-IND meetings now happen by teleconference. FDA discontinued in-person meetings for pre-IND during COVID and hasn't fully gone back. From a practical standpoint this changes very little.

The format: FDA starts by presenting their preliminary responses (which you've already received in writing). Then you ask clarification questions. Total time is 60 minutes, which goes fast.

Who should be in the room:

• Regulatory affairs lead — runs the meeting
• Nonclinical scientist — answers pharmacology and toxicology questions
• CMC lead — answers manufacturing questions
• Clinical lead — answers protocol design questions
• Someone taking notes — this is important, and it should be someone who isn't also trying to answer questions

Who shouldn't be in the room: your CEO, unless they have a regulatory or scientific background and can resist the urge to give a corporate overview. FDA doesn't want to hear about your company's mission. They want to discuss your data.

After the meeting, FDA sends official minutes within 30 calendar days. Review them carefully. If anything in the minutes doesn't match what was discussed, you have 30 days to submit a written response disputing specific points. This almost never happens, but it's worth knowing.

The written response is the prize

I want to emphasize this because I've talked to teams who were disappointed by their pre-IND meeting — "FDA didn't really tell us anything new." They're usually referring to the 60-minute call. The written response they received beforehand, the one with specific comments on each of their questions, is sitting in their email. That document is the guide.

FDA's written responses tend to follow a pattern:

• Agreement: "The proposed approach is acceptable." This is what you want. Proceed.
• Conditional agreement: "The proposed approach is acceptable provided that [specific condition]." Do what they say.
• Disagreement with explanation: "The Division recommends [alternative approach] because [reason]." This is valuable. They're telling you what will trigger a clinical hold before you file.
• Deferral: "This issue cannot be fully addressed without additional data. The sponsor should discuss this further in the IND." Translation: we need to see the actual data before we commit.

Save this document. Reference it in your IND submission. When you file the IND, explicitly state how you addressed each point from the pre-IND meeting feedback. Reviewers remember — or more accurately, the same reviewer who wrote the pre-IND response may review your IND.

Common mistakes

Filing the request to the wrong division. FDA's division structure is organized by therapeutic area, not by drug modality. Your oncology antibody goes to the Office of Oncologic Diseases, not to the Office of Therapeutic Biologics. Check the FDA division directory before you file.

Asking yes/no questions about things FDA can't commit to. Don't ask "Will our IND be approved?" FDA doesn't approve INDs — they either allow them to proceed or issue a clinical hold. And they won't tell you in advance which one it'll be. Ask about specific study designs and data packages instead.

Not updating the briefing document after new data comes in. If you get significant new nonclinical data between submitting the request and the meeting date, submit an addendum. FDA would rather review current data than hear about it for the first time on the call.

Treating the meeting as a checkbox. Some teams go through the motions — they ask generic questions, submit a thin briefing document, sit through the call, and move on. They're leaving enormous value on the table. The pre-IND meeting is the only time in the IND process where FDA tells you what they want before you give it to them.

Timeline

Here's a realistic timeline from decision to meeting:

Total from request to minutes: roughly 4-5 months. Factor this into your development timeline.

What happens after

You take FDA's feedback, revise your development plan, and execute. If FDA told you to run 28-day repeat-dose studies instead of 14-day, you adjust your CRO contracts and timelines. If they flagged a gap in your safety pharmacology core battery, you schedule the missing study.

Then when you file the IND, you include a section — usually in the Nonclinical Overview — that references the pre-IND meeting and describes how each piece of FDA feedback was addressed. This closes the loop. The reviewer sees that you listened.

The teams I've talked to who had smooth IND reviews almost always had a pre-IND meeting. The ones who got clinical holds disproportionately skipped it.

That's not a coincidence. It's an hour of your time and 4-5 months of planning for feedback that can save you 6-12 months of delays. Take the meeting.

---

Related reading:

• FDA IND Submission Checklist 2026 — complete requirements by CTD module
• 5 Most Common IND Deficiencies — what FDA flags most often
• How to Check Preclinical Studies Against ICH Guidelines — 8-step gap analysis

Want to check your nonclinical package against FDA requirements before your pre-IND meeting? Try the compliance checker at regfo.com — paste your study summaries and get specific ICH citations in 20 seconds.

FAQ

Is a pre-IND meeting with FDA required?

No — it's not legally required under 21 CFR 312.82 or any FDA regulation. But "not required" and "optional" aren't quite the same thing in practice. FDA explicitly encourages pre-IND meetings, and the data on outcomes is clear: programs that skip the meeting are disproportionately represented among IND clinical holds. A clinical hold costs 6-12 months and $2-4M. The pre-IND meeting costs roughly 4-5 months of calendar time and $50-100K in preparation costs. Two issues that would have surfaced in a 60-minute meeting — starting dose justification and a missing reproductive toxicity rationale — triggered a Day 33 clinical hold for one company, costing $600K and 4 months. If you have a genuinely straightforward program with a well-precedented compound class, clean nonclinical data, and an experienced regulatory team, you might reasonably skip it. In every other situation, take the meeting.

How do I request a pre-IND meeting with FDA?

Submit a meeting request letter to the FDA review division responsible for your therapeutic area. Find the correct division in the FDA's CDER Office and Division directory — don't file to the wrong division, it costs weeks. The request letter should be 2-3 pages and include: your compound name and proposed indication, the meeting type (Type B pre-IND), a brief purpose statement, a numbered list of specific questions you want answered, proposed meeting dates, and your attendees. Submit it electronically via FDA's Electronic Submissions Gateway if your program has an existing IND or NDA number, or by mail/portal for new programs. FDA has 21 calendar days to grant or deny the request. If granted, you then have roughly 6 weeks to prepare the briefing document, which is due 30 days before the scheduled meeting date.

How long does it take to get a pre-IND meeting with FDA?

From the day you submit the meeting request to the day you receive FDA's official minutes, the full process takes roughly 4-5 months. Here's the breakdown: FDA acknowledges the request within 21 calendar days. If granted, you then prepare the briefing document (4-6 weeks). The briefing document is due 30 days before the meeting. FDA sends preliminary written responses approximately 5 days before the meeting. The meeting itself is 60 minutes. FDA sends official minutes within 30 calendar days after the meeting. The part that catches most teams off guard is that the preparation timeline is substantial — a 50-100 page briefing document that covers your entire development program isn't a weekend project. Budget 4-6 weeks of internal work to write it well. If you start your meeting request before the briefing document is fully drafted, you can compress the total elapsed time to 3-4 months.

What should I include in the pre-IND meeting briefing document?

The briefing document is 50-100 pages and covers your entire development program in enough detail for FDA reviewers to answer your specific questions. Standard structure: executive summary (1-2 pages with your compound, indication, and key questions), product overview (mechanism of action, therapeutic rationale), nonclinical development (completed and planned studies with key findings), CMC summary (manufacturing, characterization, stability status), clinical development plan (proposed Phase 1 design, dose rationale, endpoint strategy), and the numbered questions. For the nonclinical section, include specific ICH citations and actual data parameters: Cmax, AUC, half-life, NOAEL values, exposure margins. For genotoxicity, name the assays completed and planned. Don't bury adverse findings — if your dog study showed liver enzyme elevations at the high dose, address it directly with dose-response context. FDA will find it. The question is whether they find it in your transparent discussion or in an appendix.

What questions should I ask FDA at a pre-IND meeting?

Ask about decisions you're actually uncertain about and that FDA's answer will change what you do. Good questions are specific and binary. For nonclinical: "We propose to support a 14-day Phase 1 with a 28-day rat and dog repeat-dose tox study per ICH M3(R2) Table 1. Does the Division agree this duration is sufficient?" For CMC: "Our drug substance specification includes a [X] limit for [impurity]. Is this acceptable for Phase 1 supply?" For clinical: "Given the tumor type and patient population, does the Division agree that a MABEL-based starting dose is more appropriate than an NOAEL-based HED calculation?" Aim for 5-8 questions. Don't ask whether your IND will be approved — FDA doesn't approve INDs, they allow them to proceed or issue holds, and they won't commit to that outcome in advance. Don't ask general questions like "Is our nonclinical package adequate?" — you'll get a general answer that doesn't help any decision.

What will FDA not answer at a pre-IND meeting?

FDA won't tell you whether your IND will be placed on clinical hold, whether your drug will ultimately be approved, or whether your efficacy data is compelling enough to justify development. They also won't commit to accepting data packages they haven't reviewed — if you ask "will you accept data generated at a non-FDA-inspected foreign CRO?", you'll get a deferral. They won't answer questions that require reviewing actual data you haven't yet submitted — "will this impurity level be acceptable?" without the actual analytical data gets you a non-answer. Questions that require interdisciplinary deliberation beyond the reviewing division scope also tend to get deferred. The practical rule: FDA answers questions about whether a proposed study design or development plan meets guideline requirements. They don't make advance commitments about outcomes, they don't provide scientific opinions on efficacy, and they won't evaluate data that isn't in front of them.

Can I have a pre-IND meeting for a biologic or cell therapy?

Yes — pre-IND meetings are available for all product types reviewed by CDER or CBER. For biologics regulated by CDER (most monoclonal antibodies, antibody-drug conjugates, some cell therapies), you file the request to the appropriate CDER therapeutic area division. For biologics regulated by CBER (gene therapies, certain cell therapies, vaccines), you file to the relevant CBER office — typically the Office of Tissues and Advanced Therapies for gene and cell therapies. The process is the same: Type B meeting request, 21-day FDA acknowledgment timeline, 30-day briefing document submission. The content differences are significant: biologic pre-IND meetings typically focus heavily on ICH S6(R1) species selection (pharmacologically relevant species justification), manufacturing comparability and characterization, and — for cell and gene therapies — potency assay strategy, adventitious agent testing, and unique safety considerations not covered by standard ICH guidelines. Budget more time for the briefing document: CBER programs often need 80-120 pages to adequately cover the CMC complexity.