Managing Health Authority Interactions: Pre-IND, Type A/B/C Meetings, and Information Requests

A health authority interaction is the cheapest risk-reduction tool a development program has. A two hour meeting can save a year of wasted clinical work or a refused submission. It can also do real damage if the team walks in unprepared, asks the wrong questions, or commits to something it cannot deliver. This page covers how the meeting machinery actually works at FDA and EMA, what goes into the documents, how to run the process, and how to manage the bad-news correspondence: deficiency letters, refuse-to-file, and complete response letters.

The quality function is rarely the lead on these interactions. Regulatory affairs owns them. But quality is in the room and on the hook whenever the agency asks about manufacturing controls, data integrity, validation status, CMC, or inspection history. If you sit in QA, validation, CMC quality, or data integrity, you will be asked to draft sections of a briefing book, defend a control strategy in front of reviewers, and translate a deficiency into a CAPA. Knowing the process lets you do that well instead of reacting.

Why formal interactions exist and where the rules live

Sponsors and regulators have a structured way to talk before, during, and after a marketing application. The legal and procedural basis is specific, and you should be able to cite it.

In the United States the framework comes from the Food and Drug Administration Safety and Innovation Act (FDASIA) and the prescription drug user fee program. The operative guidance is the FDA guidance Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products (current revised version issued under PDUFA VII). It defines the meeting categories, the timelines, the meeting package requirements, and the commitments the agency makes on scheduling. For biologics and drugs the same guidance applies. There is a separate but parallel guidance for medical devices under the FDA program known as the Q-Submission program, covered in the FDA guidance Requests for Feedback and Meetings for Medical Device Submissions: The Q-Submission Program.

In the European Union the equivalent mechanism is Scientific Advice and Protocol Assistance from the European Medicines Agency, governed by Regulation (EC) No 726/2004 and the EMA procedural guidance on scientific advice. National competent authorities also give scientific advice for nationally authorized products. There is a joint route, EMA-FDA Parallel Scientific Advice, where a sponsor gets both agencies in the same discussion.

Why bother with formality? Three reasons. First, alignment: getting the agency on record about whether a trial design, an endpoint, or a specification is acceptable reduces the chance of a late rejection. Second, the meeting minutes become an official record you can rely on later, the agency’s written response is the durable artifact, not the conversation. Third, user fee programs commit the agency to response timelines, so a sponsor can plan around them.

The risk rationale matters for quality people specifically. If you defer a CMC question, a comparability strategy, or a validation approach until the marketing application, you find out the agency disagrees at the most expensive possible moment. Raising it in a Type C or scientific advice meeting two years earlier costs a briefing document and a few hours.

The FDA meeting taxonomy: Type A, B, B(EOP), C, and INTERACT

FDA sorts formal meetings into categories that drive the scheduling clock and the level of formality. Know these cold.

A few points that trip people up:

• Pre-IND is a Type B meeting. It is the most common first interaction. It is your chance to confirm the nonclinical package, the proposed first-in-human design, the manufacturing and quality plan, and the IND content before you file.
• Type D is the newer, lighter-weight category added under PDUFA VII, for a tightly scoped issue touching no more than a few disciplines. Use it when you have one or two crisp questions and do not need the full milestone apparatus.
• INTERACT (Initial Targeted Engagement for Regulatory Advice on CBER/CDER ProducTs) sits even earlier, before pre-IND, for genuinely novel modalities. It is non-binding and is where cell and gene therapy sponsors often start.
• FDA also runs written response only (WRO) as an option for some meeting types. Instead of a live meeting, the agency answers your questions in writing. For a clean CMC question this is often faster and gives you the same durable record. The trade-off is no back-and-forth.

The meeting format can be face-to-face, teleconference or videoconference, or written responses only. Choose based on the need for dialogue. If a question is likely to spawn follow-ups or the agency’s position is unclear, ask for a live format.

Picking the meeting type: a decision aid

Most teams over-think this. Work from the trigger, not from a preference for a particular format.

If the question has a clear sponsor position and you do not need live debate, layer a written responses only request on top of whatever type fits. You keep the durable record and skip the meeting logistics.

FDA and EMA: the rough equivalence

Programs go global, so it helps to hold the two systems side by side. The mapping is approximate; the procedures differ in detail.

The practical lesson for quality and CMC people: the same control-strategy, comparability, and validation questions can and should be put to both agencies, and Parallel Scientific Advice is the cleanest way to surface where they will disagree before you have built the data package around one agency’s view.

EMA scientific advice and protocol assistance

The EMA route is procedurally different and worth understanding even if your program is US-led, because most programs go global.

Scientific advice is the general mechanism: a sponsor asks the EMA’s Scientific Advice Working Party (SAWP), which prepares advice adopted by the Committee for Medicinal Products for Human Use (CHMP). Protocol assistance is scientific advice for designated orphan medicinal products and includes questions on significant benefit.

Key features:

• It is question-driven and prospective. You frame specific questions, give your position, and ask whether the agency agrees. The advice is not legally binding on either party, but deviating from it later puts the burden on you to justify the deviation.
• The procedure runs on a roughly 40 to 70 day clock depending on whether there is a clarification meeting (a discussion meeting) or a written-only procedure. Pre-submission contact with the EMA secretariat is expected before you formally submit.
• Parallel consultation with health technology assessment (HTA) bodies is available, where the EMA and HTA agencies advise together so you can design a study that satisfies both the regulator and the payers. This matters because a study that earns approval but generates no reimbursement evidence is a commercial failure.
• Parallel Scientific Advice (PSA) with FDA lets you put the same questions to both agencies and hear where they diverge. Divergence is common on endpoints, comparators, and statistical approaches, and learning it early is the point.

For quality and CMC, EMA scientific advice can address comparability strategy, specifications, stability approach, and manufacturing changes. The EMA also runs specific innovation support such as the PRIME (PRIority MEdicines) scheme, which gives enhanced interaction for medicines addressing unmet need, including a dedicated contact point and early scientific advice.

The briefing book: what goes in it and how to build it

The briefing document, called the meeting package by FDA, is the single most important deliverable. The agency’s reviewers read it, form preliminary positions, and often send preliminary responses before the meeting based on it. A weak package produces weak advice. The quality of your questions and background determines the quality of the answers.

FDA meeting package contents

The FDA guidance specifies what a meeting package must contain. Build to this structure:

1. Cover letter / application information. Product name, application number (IND/BLA/NDA), meeting type, requested format, contacts.
2. Product development background. A concise history: indication, mechanism, development stage, prior agency interactions, regulatory designations (fast track, breakthrough, orphan, RMAT).
3. List of attendees for sponsor side, with names, titles, affiliations, and the disciplines they represent (clinical, CMC, nonclinical, statistics, regulatory). Send the requested FDA attendee disciplines too.
4. List of questions, grouped by discipline. This is the core. Each question states the issue, gives the sponsor’s position and rationale, and asks a specific, answerable question.
5. Data and analyses supporting your positions: nonclinical summaries, clinical data, CMC and manufacturing information, statistical analysis plans.
6. Supporting tables, figures, references.

The package is due at the time of the meeting request for some types and a set number of days before the meeting for others. Under the current guidance, for many meeting types the meeting package is submitted with the request; for others it is due roughly 30-50 days before the meeting. Confirm the current timing for your meeting type against the guidance, because the user fee cycle adjusts these. Missing the package deadline can cause the meeting to be cancelled or rescheduled.

How to write a good question

The discipline that separates a productive meeting from a wasted one is question design. A good agency question:

• States the issue and context in one or two sentences.
• Gives the sponsor’s proposed approach and the rationale.
• Ends with a closed, specific ask: “Does the Agency agree that X is acceptable to support Y?” not “What does the Agency think about X?”

Compare these:

Weak: “What are the Agency’s expectations for our stability program?”

Strong: “The sponsor proposes a stability protocol per ICH Q1A(R2) using three primary batches, with 12 months of data at submission and a commitment to complete through 24 months post-approval, supporting a 24 month shelf life with a label storage condition of 2-8 degrees C. Does the Agency agree this stability strategy is acceptable to support the proposed shelf life claim?”

The strong version tells the reviewer exactly what to agree or disagree with. It cites the standard. It states the commitment. The agency can answer yes, no, or yes-with-conditions, and that answer is usable.

A sample question table

This is how a CMC question block might read in a pre-BLA package:

Notice each question is answerable yes/no and references the relevant ICH guidance or validation concept. See process performance qualification and process validation lifecycle for the underlying technical content, and comparability and potency assays for the Q5E comparability approach.

Running the process end to end

Here is the sequence for an FDA formal meeting. EMA differs in detail but the rhythm is similar.

Step 1: Decide you need a meeting and pick the type

Triggered by a development milestone (pre-IND, end of phase 2, pre-BLA) or a specific problem (a clinical hold, a disagreement, a CMC question). Map the need to the meeting type using the table above. If the question is narrow, consider Type D or written responses only.

Step 2: Submit the meeting request

The request states the product, application, meeting type and format, a brief statement of the purpose, the proposed questions (preliminary), the requested attendee disciplines on both sides, and a few proposed dates. FDA acknowledges and grants or denies. A denial usually means the question is premature or belongs in another channel; the agency tells you why.

Step 3: Prepare and submit the meeting package

Assemble the briefing book to the contents above. This is where quality earns its place: the CMC, validation, data integrity, and inspection-history sections are drafted by the relevant SMEs and QA, then integrated by regulatory. Internal review and sign-off matter, because anything in the package is on the record.

Step 4: Read the preliminary responses

FDA sends preliminary responses to your questions, typically a few days before the meeting, often two business days prior. This changes the meeting’s purpose. If the agency already agrees with a question in writing, you do not spend meeting time on it. The meeting becomes a discussion of the disagreements and the nuances. Some sponsors, on receiving preliminary responses that resolve everything, cancel the live meeting and accept the written responses as final. That is a legitimate and efficient move.

Step 5: Prepare for the meeting

Build a presentation only if it adds something, the agency often prefers discussion over slides. Run an internal rehearsal: assign who answers which question, anticipate follow-ups, agree on positions, and decide what you will and will not commit to live. Designate one person to take detailed notes and one regulatory lead to manage the flow. Decide your fallback positions in advance.

Step 6: Hold the meeting

Keep it focused on the disagreements. Do not reopen settled questions. Do not commit to anything you have not cleared internally. If the agency asks something you cannot answer on the spot, say you will follow up in writing. The regulatory lead runs the agenda and watches the clock.

Step 7: Draft and reconcile the minutes

For FDA meetings, the agency issues the official minutes, usually within 30 days. The sponsor also takes its own notes during the meeting. Compare the two. If the official minutes diverge materially from your understanding, or omit an agreement, you can request a correction, but the FDA minutes are the controlling record. Get every agreement and action item documented. Ambiguity in the minutes becomes a fight later.

Step 8: Execute the action items

Translate agreements into program actions. If the agency asked for additional validation, a stability commitment, or a CMC change, that becomes a tracked deliverable. If you committed to something, deliver it, the agency remembers.

Acceptance criteria: what good looks like

You know a health authority interaction was run well when:

• Every question got a clear answer (agree, disagree, or agree-with-conditions), not a vague “the Agency recommends the sponsor consider.”
• The minutes contain no surprises relative to your meeting notes, and every agreement is captured in writing.
• Action items have owners and due dates in the program plan within a week of receiving minutes.
• No live commitment was made that the team had not pre-cleared. Off-the-cuff commitments in a meeting are a common source of later pain.
• The package was submitted on time and complete, so the agency had what it needed to give substantive preliminary responses.
• Disagreements are documented with rationale, so if you proceed against advice you have a defensible record of why.

Roles and responsibilities

The quality-specific lesson: never let a statement go into a briefing book that the quality system cannot back up. If the package says validation is complete, it had better be complete or have a credible, dated plan. The agency may verify it at inspection, and a gap between what you told reviewers and what an inspector finds is a serious credibility problem. See FDA inspection readiness and BLA readiness data package.

Deficiency letters, information requests, and the refuse-to-file decision

After you submit a marketing application the dialogue continues through written correspondence. These are not meetings, but they are health authority interactions and the quality function is heavily involved.

Information requests and discipline review letters

During review the agency sends information requests (IRs), sometimes called discipline review letters (DRLs) when they come from a specific review discipline. These are questions: clarify a method, provide additional stability data, explain a deviation, justify a specification. They come with short response deadlines, sometimes a few days, sometimes a couple of weeks.

The pattern that gets sponsors in trouble is treating an IR casually. Each response goes on the record and can shape the final decision. Quality should review any IR response touching CMC, validation, or data integrity for accuracy before it goes out. A rushed, sloppy IR response can turn a minor question into a major deficiency.

How to handle an IR well:

1. Log it immediately with the deadline and the responsible SME.
2. Understand what the reviewer is really asking. Sometimes the literal question hides a deeper concern. If unclear, you can ask the regulatory project manager for clarification.
3. Draft a complete, accurate, concise response. Answer the question asked. Do not volunteer new problems.
4. Route through quality and regulatory review before submission.
5. Submit on time. If you genuinely cannot meet the deadline, negotiate an extension early, do not go silent.

Refuse-to-file (RTF)

Within the first 60 days after submission, FDA decides whether the application is complete enough to review. If it is not, the agency issues a Refuse to File. This is the worst-case early outcome short of a clinical hold: the application is not even reviewed, and you have to fix the gaps and resubmit, losing months. RTFs commonly cite missing CMC information, incomplete validation, missing safety data, or formatting and content failures in the submission. The quality lesson is that a BLA readiness data package and an honest pre-submission gap assessment prevent RTFs. After an RTF you are entitled to a Type A meeting to understand and resolve the deficiencies.

EMA major objections and the list of questions

In the EU centralized procedure the equivalent is the List of Questions (LoQ) issued by the CHMP rapporteurs around day 120, and the List of Outstanding Issues (LoOI) around day 180. Issues are graded as major objections (could preclude approval if unresolved) or other concerns. Major objections on quality often address comparability, control strategy, sterility assurance, or stability. You respond within the clock-stop windows. Unresolved major objections at the end lead to a negative opinion.

The complete response letter (CRL)

If FDA finishes its review and cannot approve the application as submitted, it issues a Complete Response Letter. This is the formal “not approvable in current form” decision under 21 CFR 314.110 (drugs) and the parallel biologics provisions. It is not a rejection of the program; it is a list of what must be addressed before approval.

What a CRL contains

The CRL describes the deficiencies the agency identified and, where possible, recommends actions to address them. Deficiencies fall into recognizable buckets:

• Clinical / efficacy: the data do not establish effectiveness, or a safety signal needs more work, or an additional trial is needed.
• CMC / manufacturing: specifications, comparability, process validation, stability, or sterility assurance are inadequate.
• Facility / inspection: a pre-approval inspection found deficiencies, or an inspection could not be completed. An unresolved facility inspection finding alone can drive a CRL even when the data are fine. This is where quality is squarely on the critical path.
• Labeling: the proposed labeling is not acceptable.

How to respond to a CRL

1. Read it precisely. Categorize each deficiency by discipline and by severity. Distinguish “do more analysis” from “run another study.”
2. Request a Type A meeting to align with the agency on what a complete response requires before you spend money building it. This is the single most valuable move after a CRL: confirm the path before you walk it.
3. Build the resubmission to address every deficiency, with documented evidence. A facility deficiency means a real CAPA, executed and verified, not a promise. See what is a CAPA and CAPA effectiveness verification.
4. Classify the resubmission as Class 1 (minor, two month review) or Class 2 (major, six month review). The classification sets your timeline and is determined by the nature of the response.
5. Resubmit a complete response addressing all deficiencies. A partial response that ignores a deficiency earns another CRL.

The most damaging CRL pattern for quality teams is the inspection-driven CRL. The clinical and CMC data may be strong, but a pre-approval inspection finds data integrity problems, inadequate validation, or unaddressed deviations, and the application stalls. The fix is not regulatory wordsmithing; it is a genuine remediation that an inspector can verify. See FDA 483 response strategy, 483 and warning letter response, and DI remediation program.

Worked example: turning a CRL into a controlled resubmission

A BLA for a monoclonal antibody receives a CRL with three deficiencies. The team’s first move is to categorize each one by discipline, severity, and the work it implies, before committing to a path.

The path that follows: request a Type A meeting and put one closed question per deficiency to the agency, so the team confirms what “complete” looks like before building anything. Deficiency 1 drives the timeline because a facility finding cannot be answered with analysis; it needs a CAPA executed and effectiveness-verified, with a retrospective review of every result the gap could have touched. Deficiency 2 is analysis on data that is accruing. Deficiency 3 is dependent on 2 and is trivial once 2 lands. Because deficiency 1 is a major change, the whole resubmission is classified Class 2 (six-month review), and the team builds a single complete response that closes all three, rather than a partial response that would earn a second CRL. The lesson: the severity of the worst single deficiency sets the resubmission class and the clock, and a facility or data-integrity finding is almost always that worst deficiency.

Common mistakes and inspection-finding patterns

These are the failures that show up again and again:

• Vague questions. Asking open-ended questions (“What does the Agency think?”) instead of closed ones (“Does the Agency agree?”) produces non-committal answers you cannot rely on.
• Too many questions. A package with 25 questions across every discipline dilutes the meeting. Prioritize the ones that change your development path.
• Overcommitting live. Someone in the room agrees to an extra study or a tighter specification under pressure, and the program is now bound to it. Pre-clear every position and designate who may commit.
• Briefing book that overstates readiness. Stating that validation or comparability is complete when it is not. The agency may verify at inspection, and the gap becomes a credibility and integrity problem.
• Treating IRs casually. Rushed, inaccurate, or evasive IR responses escalate small issues into deficiencies.
• Not reconciling minutes. Accepting the agency minutes without comparing them to your notes, then discovering at the next interaction that a key agreement was not captured.
• Ignoring the inspection dimension. Designing a brilliant clinical and CMC package while the manufacturing site has open deviations, data integrity gaps, or incomplete validation. The pre-approval inspection then drives a CRL.
• Going against advice without documentation. Deviating from scientific advice or meeting agreements is allowed, but doing it without a documented rationale leaves you exposed when the agency asks why.
• Missing package deadlines. Late or incomplete packages cause cancellation or rescheduling and signal poor program control.

Interview-ready questions and answers

Q: Walk me through the FDA formal meeting types. A: Type A is for stalled programs, clinical holds, disputes, post-RTF or post-CRL, scheduled within 30 days. Type B covers milestone meetings, pre-IND, end-of-phase meetings, pre-NDA/pre-BLA, within 60 days, with B(EOP) for end-of-phase-2 within 70. Type C is any other meeting including CMC questions, within 75 days. Type D is a newer narrow-scope category for a few questions and limited disciplines, within 50 days. INTERACT is pre-pre-IND non-binding advice for novel products. The governing guidance is the FDA guidance on Formal Meetings Between FDA and Sponsors under PDUFA VII.

Q: What is a pre-IND meeting for and why does quality care? A: It is a Type B meeting before you file the IND, to confirm the nonclinical package, the first-in-human design, and the CMC and quality plan. Quality cares because the CMC and manufacturing readiness, the analytical methods, the specifications, and the GMP status for the investigational product are all in scope. Getting agency alignment on the control strategy and the validation plan early avoids a hold or a late deficiency.

Q: What is the difference between an information request, a refuse-to-file, and a complete response letter? A: An IR or discipline review letter is a question during review, answered in days to weeks. A refuse-to-file is an early decision, within 60 days, that the application is too incomplete to even review. A complete response letter is the formal end-of-review decision under 21 CFR 314.110 that the application cannot be approved as submitted, with a list of deficiencies to address before resubmission.

Q: You receive a CRL citing a pre-approval inspection finding. What do you do? A: First, separate the inspection deficiency from any data deficiencies. The inspection finding needs a real CAPA, root cause analysis, corrective and preventive actions, executed and effectiveness-verified, not just a letter. I would request a Type A meeting to align with the agency on what closure looks like, remediate the finding so an inspector can verify it, document the evidence, and build that into a complete response resubmission, classified Class 1 or Class 2 depending on scope.

Q: How is EMA scientific advice different from an FDA meeting? A: EMA scientific advice is question-driven and prospective, run through the SAWP with CHMP adoption, on roughly a 40 to 70 day clock. Protocol assistance is scientific advice for orphan products. It is non-binding but deviating puts the justification burden on the sponsor. EMA also offers parallel consultation with HTA bodies and parallel scientific advice with FDA, which FDA meetings do not inherently provide.

Q: What makes a good briefing book question? A: It states the issue and context briefly, gives the sponsor’s proposed approach with rationale, cites the relevant standard, and ends with a closed yes/no ask: “Does the Agency agree that X is acceptable to support Y?” That lets the reviewer give a usable answer instead of a non-committal recommendation.

Q: The agency minutes differ from your notes on a key agreement. What do you do? A: The FDA minutes are the controlling record, so I would not just rely on my notes. I would request a correction through the regulatory project manager, citing the meeting context, and make sure any ambiguity is resolved in writing before the next interaction, because an undocumented agreement effectively does not exist.

Practical tips

• Use written responses only when you can. For a clean CMC question with a clear sponsor position, written responses give you the same durable record faster than a live meeting.
• Treat preliminary responses as the real agenda. When they arrive, replan the meeting around the disagreements. If everything is resolved, consider cancelling and accepting the written responses.
• One owner for the record. Designate a single regulatory lead who owns the package, the agenda, and the minutes reconciliation. Diffuse ownership produces gaps.
• Pre-clear every commitment. Decide in advance what the team can and cannot agree to live, and who has authority to commit.
• Keep a meeting and correspondence log. A running record of every agency interaction, with dates, questions, and agency positions, is invaluable at the next milestone and at inspection.
• Mind the inspection dimension in every interaction. Anything you tell reviewers about validation, data integrity, or GMP status should be true and verifiable, because an inspector may check it.
• For global programs, sequence advice deliberately. Parallel scientific advice with FDA and EMA surfaces divergence on endpoints, comparators, and statistics early, when you can still design around it.

Related reading

• IND, NDA, and BLA pathways
• BLA readiness data package
• eCTD submission architecture
• FDA inspection readiness
• FDA 483 response strategy
• 483 and warning letter response
• FDA vs EMA inspection dynamics
• Process validation lifecycle
• Process performance qualification (PPQ)
• Comparability and potency assays
• What is a CAPA
• CAPA effectiveness verification
• DI remediation program
• Regulatory intelligence and 483 trends