FDA Q-Submission (Pre-Sub) Meetings: When to Request One and How to Prepare

FDA Q-Submission Meetings: Your Strategic Advantage in the Device Approval Process

If you are developing a medical device and have not yet leveraged the FDA's Q-Submission (Q-Sub) program, you are leaving one of the most valuable regulatory tools on the table. A well-executed Pre-Submission meeting can save months of back-and-forth, prevent costly study redesigns, and give your team documented FDA feedback before you commit significant capital to a clinical or bench testing program.

But like any regulatory tool, its value depends entirely on how and when you use it. This guide breaks down the mechanics of the Q-Sub program, the right moments to engage FDA, and how to prepare a submission that generates actionable feedback rather than generic responses.

What Is a Q-Submission?

The Q-Submission program, formalized under FDA's guidance document 'Requests for Feedback and Meetings for Medical Device Submissions: The Q-Submission Program' (originally issued 2014, updated 2019), is a formal mechanism that allows device sponsors to request FDA feedback before, during, or after a marketing submission. The program encompasses several interaction types, including Pre-Submissions (Pre-Subs), Informational Meetings, and Study Risk Determinations (SRDs).

Pre-Submissions are the most commonly used pathway. Governed under 21 CFR Part 10 for meeting procedures and aligned with MDUFA IV and MDUFA V commitments, the program obligates FDA to provide written feedback within 90 calendar days of acknowledging your request, or to offer a meeting within that same window.

It is important to understand that FDA feedback from a Q-Sub is advisory, not binding. However, it is documented and carries significant practical weight. Deviating from agreed-upon testing approaches without explanation is a reliable way to generate a major deficiency in your 510(k) or PMA review.

When Should You Request a Q-Submission?

Not every question warrants a Pre-Sub, and submitting one prematurely or for questions you can answer through existing guidance will waste your timeline and FDA reviewer bandwidth. The right situations include:

• Regulatory pathway uncertainty: If you are genuinely uncertain whether your device qualifies for 510(k) clearance under 21 CFR Part 807, De Novo classification, or requires a PMA under 21 CFR Part 814, a Pre-Sub is the appropriate mechanism to seek FDA's input on predicate strategy or classification.
• Novel or combination device questions: Devices that blend drug delivery, biologic components, or software as a medical device (SaMD) functions often trigger jurisdictional questions. A Pre-Sub can clarify the lead center and applicable review framework before you build your technical file.
• Clinical study design: If you are planning a pivotal or supporting clinical study, particularly one that will anchor a PMA or a 510(k) with clinical data, getting FDA agreement on your study design, endpoints, and statistical analysis plan before you enroll a single patient is not optional -- it is essential. FDA's guidance on Investigational Device Exemptions (IDE) under 21 CFR Part 812 aligns directly with this use case.
• Substantial equivalence concerns: If your device has technological differences from a proposed predicate that could trigger a 'not substantially equivalent' (NSE) finding, a Pre-Sub allows you to surface those differences proactively and understand FDA's perspective on testing needed to bridge them.
• Software and AI/ML submissions: Given the evolving guidance landscape around SaMD, including FDA's action plan for AI/ML-based software, Pre-Subs are particularly valuable for confirming your software level of concern, intended use framing, and cybersecurity documentation approach.
• Post-market or manufacturing changes: If you are unsure whether a proposed change to your device or manufacturing process requires a new 510(k) under 21 CFR 807.81(a)(3), a Pre-Sub or an informal feedback request can prevent a compliance gap.

How to Prepare a Q-Submission That Gets Real Answers

The quality of FDA's feedback is directly proportional to the quality of your submission. Vague questions produce vague answers. Here is how to structure a Pre-Sub that generates substantive, actionable responses:

1. Lead with a Clear Device Description and Intended Use

Provide a concise but complete description of your device, its indications for use, and the patient population. FDA reviewers may have no prior context for your technology. Do not assume familiarity.

2. State Your Proposed Regulatory Pathway Explicitly

Identify the submission type you are targeting, your proposed predicate (if applicable) with its 510(k) or PMA number, and your device classification under 21 CFR Part 862-892. If you are uncertain, say so -- that uncertainty should itself be framed as a question.

3. Write Specific, Binary Questions

This is where most sponsors underperform. Your questions should be specific enough that FDA can answer 'yes,' 'no,' or 'yes, with the following conditions.' Avoid open-ended questions like 'what testing do you recommend?' Instead, ask: 'Does FDA agree that the proposed bench testing protocol, as described in Attachment B, is sufficient to support substantial equivalence for the identified performance characteristic?'

4. Provide Supporting Data and Rationale

Attach draft test protocols, literature summaries, or preliminary bench data when available. FDA feedback is most useful when reviewers can evaluate your specific approach rather than answer hypothetically.

5. Request a Meeting Only When Necessary

Written feedback from FDA is often sufficient and arrives faster than scheduling a meeting. Request a teleconference or in-person meeting when your questions are complex, iterative, or likely to require dialogue -- such as novel clinical endpoint discussions or combination product jurisdiction disputes.

Common Mistakes That Undermine Q-Sub Effectiveness

• Submitting too early, before you have a defined device concept or testing approach to react to
• Asking questions already answered in FDA guidance documents or device-specific guidance
• Writing questions so broadly that FDA cannot commit to a specific position
• Failing to organize the document logically, making it difficult for reviewers to locate relevant information
• Not following up on FDA feedback with a formal response summary that confirms mutual understanding

The Bottom Line

The Q-Submission program is one of the few mechanisms in FDA's regulatory framework that allows sponsors to reduce uncertainty before making irreversible decisions. Used strategically, it aligns your development program with FDA expectations, reduces the risk of a Refuse to Accept (RTA) or major deficiency letter, and demonstrates to investors and stakeholders that your regulatory strategy is built on a solid foundation.

The firms that navigate FDA review efficiently are not the ones who avoid FDA -- they are the ones who engage early, engage specifically, and come prepared.

At ADB Consulting and CRO Inc., Andre Butler and our regulatory team provide FDA Pre-Sub (Q-Submission) consulting for medical device companies across therapeutic areas, device classes, and submission types. We help you ask the right questions, in the right format, at the right time -- so you get feedback that actually moves your program forward.

Ready to determine whether a Q-Submission is right for your device program? Book a free discovery call with our team at adbccro.com and let us help you build a regulatory strategy that holds up under FDA scrutiny.