Best Practices for Post-FDA Meeting Follow-Up

A Pre-Submission or Pre-IDE meeting with FDA is a significant regulatory event — but the real work begins after the meeting ends. The feedback received in the meeting is only as valuable as the follow-up process that captures it accurately, addresses open questions, and translates FDA's guidance into a concrete development or submission plan. Manufacturers who treat the meeting as an end point — rather than a transition point — risk misapplying FDA's feedback or losing the evidentiary value of a documented FDA agreement.

Immediately After the Meeting: Internal Debrief

Before FDA sends draft minutes, conduct an internal debrief with your regulatory team within 24–48 hours of the meeting while the discussion is fresh. The debrief should document:

• FDA's responses to each question, including any nuance or qualification FDA expressed verbally
• Any open items FDA indicated it would address in the written minutes
• Any apparent ambiguity in FDA's position — places where FDA's verbal response was qualified or where the team members present interpreted FDA's statement differently
• Immediate action items for the regulatory team (e.g., additional data to generate, protocol language to revise, a follow-up Pre-Sub to file for unresolved questions)

Capture this debrief in writing. Internal documentation of the meeting — separate from FDA's formal minutes — provides a check on whether FDA's minutes accurately reflect what was said. Discrepancies between the internal debrief and FDA's draft minutes are easier to resolve when the internal record exists.

Reviewing FDA's Draft Meeting Minutes

FDA's MDUFA commitment is to send draft meeting minutes within 30 calendar days of the meeting. When the draft arrives, the review process should be structured and thorough:

Check Each Q&A Pair

For every question submitted in the Pre-Sub package, verify that FDA's written response in the draft minutes matches FDA's verbal response in the meeting. Specific areas to check:

• Does FDA's written response in the minutes reflect any qualifications or conditions that FDA expressed verbally (e.g., "this would be acceptable provided that X is also addressed")?
• Does the minutes language omit a verbal FDA commitment or statement of agreement that the manufacturer understood to be part of FDA's response?
• Is FDA's written response narrower or broader in scope than the verbal response suggests it should be?

Verify Accuracy of Meeting Details

Confirm that the minutes correctly identify the parties present, the date and format of the meeting (teleconference vs. in-person), and the Q-Sub submission number. Small factual errors are easiest to correct in draft and should not be left uncorrected simply because they seem minor.

Flag Open Items

If FDA indicated during the meeting that it would provide additional feedback or a written response to a specific point, confirm that the draft minutes acknowledge the open item and capture FDA's intended follow-up. If it is absent, raise it in the manufacturer's comments on the draft minutes.

Responding to Draft Minutes

When inaccuracies or omissions are identified, the manufacturer should respond in writing within the review period. Typical manufacturer comment responses run 3–10 business days from receipt. Responses should be:

• Specific: Quote the draft minutes language that is inaccurate and propose specific corrected text.
• Factual: Reference the internal debrief notes and, where possible, the specific question submitted in the Pre-Sub package. Do not argue about what FDA should have said — focus on what FDA did say.
• Non-adversarial: The objective is an accurate record, not a dispute. Frame comments as clarifications, not challenges.

FDA reviews manufacturer comments and either incorporates them into the final minutes, explains why the original language was correct, or proposes alternative language. Final minutes are typically issued within 30 days of the manufacturer's comment response.

Acting on the Finalized Minutes

Once minutes are finalized, update the development plan to reflect FDA's feedback. For each question where FDA provided a clear answer:

• Document the specific action required (e.g., revise the clinical protocol primary endpoint per FDA's feedback in Question 3)
• Record the Q-Sub submission number and question number as the source of the requirement
• Assign a responsible party and a target date for the action item

For questions where FDA's response was ambiguous or conditional, assess whether a follow-up Pre-Sub is warranted before proceeding. Acting on an ambiguous FDA response without seeking clarification is a common source of AI requests during subsequent formal reviews — reviewers may interpret the prior FDA feedback differently than the manufacturer did.

Referencing Prior FDA Feedback in a Subsequent Submission

When a Pre-Sub produced FDA's documented agreement on a critical element — a clinical protocol, a predicate strategy, a testing approach — referencing that agreement in the subsequent 510(k) or IDE submission is both appropriate and valuable. Include the Q-Sub submission number and quote the relevant Q&A from the finalized minutes. Reference the meeting date.

This creates a documented chain from FDA's prior feedback to the manufacturer's approach, which allows reviewers to confirm that the approach was previously discussed. Reviewers who believe a previously agreed approach is inadequate are expected to escalate internally rather than contradict prior documented FDA feedback without explanation. Properly referenced prior meeting minutes significantly reduce the risk of an AI request on a point that FDA already reviewed.

Frequently Asked Questions

What are FDA meeting minutes and why do they matter?

FDA meeting minutes are the official written record of a Pre-Submission, IDE, or other formal FDA meeting. FDA prepares a draft of the minutes after the meeting and sends it to the manufacturer for review. The finalized minutes become part of the official regulatory record and constitute FDA's documented position on the questions discussed. Meeting minutes matter because they are the authoritative reference if a question about FDA's feedback arises later — during a 510(k) or IDE review, an AI response, or a dispute about FDA's prior statements. Inaccurate minutes that go uncorrected can create significant problems downstream.

How long does FDA take to send draft meeting minutes?

FDA's MDUFA commitment is to send draft meeting minutes to the manufacturer within 30 calendar days of the meeting date. In practice, draft minutes may arrive within 2–3 weeks for routine meetings or closer to the 30-day target for complex meetings requiring more internal review. Manufacturers should set a calendar reminder 30 days after a Pre-Sub meeting to follow up with FDA if draft minutes have not been received.

What should I do if the FDA meeting minutes are inaccurate?

If FDA's draft meeting minutes do not accurately reflect what was discussed — or if they omit a key FDA statement or commitment — the manufacturer should respond to FDA in writing within the review period (typically 5–7 business days after receipt). The response should identify the specific inaccuracy or omission, quote the relevant text from the draft minutes, and propose corrected language. Responses should be factual and specific. FDA will review the manufacturer's comments and either accept the corrections, explain why the original language stands, or propose alternative language. The goal is a finalized minutes document that accurately reflects the meeting — disputes about minutes content are far easier to resolve before finalization than after.

Can I reference pre-submission meeting minutes in a later 510(k) or IDE submission?

Yes — and doing so is a best practice. When a Pre-Sub meeting produced FDA's agreement on a study design, performance testing approach, or predicate strategy, referencing that agreement in the subsequent 510(k) or IDE submission is appropriate and useful. Include the Q-Sub or Pre-IDE submission number and the specific question and answer (from the finalized minutes) that established the agreement. This gives the reviewing division immediate context that the approach was discussed with FDA and provides a record of the prior interaction. Reviewers who disagree with a prior FDA feedback position are encouraged to escalate internally rather than contradict prior minutes without explanation.