FDA Pre-Submission (Q-Sub) Meetings: What They Are and When to Request One

One of the most underused tools in a medical device company's regulatory toolkit is also one of the most available. The Pre-Submission program lets you ask the FDA direct, specific questions about your device and get written answers before you file anything. It does not guarantee a particular clearance or approval outcome. It does get your questions on the record, clarify what the agency expects, and reduce the risk of costly Additional Information (AI) requests during formal review.

For founders and marketing leaders, the Q-Sub matters for two reasons. First, it de-risks the regulatory timeline that your launch plan is built around. A cleared-up question about clinical data requirements before submission is worth months of timeline insurance. Second, the Q-Sub response sometimes contains language about device classification, intended use scope, or clinical indication boundaries that directly informs what you can credibly say about your device once it is cleared.

This article explains what the Pre-Submission program is, when to use it, what to include in a request, and what the process looks like from submission to response.

The Pre-Submission Program: Authority and Background

The FDA's Pre-Submission program is governed by the guidance document "Requests for Feedback and Meetings for Medical Device Submissions: The Q-Submission Program" (finalized May 29, 2025, superseding the June 2, 2023 version). The Federal Register availability notice is at https://www.federalregister.gov/documents/2025/05/29/2025-09618/requests-for-feedback-and-meetings-for-medical-device-submissions-the-q-submission-program-guidance. This guidance is the primary reference for the program's scope, procedures, timelines, and content requirements. It superseded earlier guidance on pre-IDE meetings and other pre-submission interactions.

The authority for the FDA to provide pre-submission feedback flows from the broader FDA mandate to work with device companies prior to formal submissions, as reflected in the MDUFA V performance goals (fiscal years 2023 through 2027), which include commitments for Q-Sub response timelines as part of the FDA's performance metrics.

The Q-Sub program covers a wide range of interaction types: written feedback only (no meeting), teleconference, or in-person meeting. For most straightforward questions, written feedback is sufficient and faster. For complex strategy discussions, a meeting with the review division is more appropriate.

When a Q-Sub Makes Sense

A Q-Sub is not needed for every device. For a routine Class II device with a clear predicate and established performance testing standards, submitting a well-prepared 510(k) and responding to AI requests is often faster than the Q-Sub cycle. But several circumstances make a Q-Sub worth the time.

Novel technology with no clear predicate. If you are considering De Novo classification or are uncertain whether your device has a viable 510(k) predicate, a Q-Sub asking the FDA to confirm your proposed predicate or validate your De Novo pathway is directly time-saving. An NSE determination after months of 510(k) preparation is expensive. A Q-Sub response pointing you to De Novo before filing is not.

Uncertain classification. If your device sits on the boundary between Class II and Class III, or involves a combination product, a Q-Sub asking the FDA to confirm its classification before you invest in your regulatory strategy reduces risk.

Clinical data requirements. If you are unsure whether bench testing and animal data are sufficient for substantial equivalence, or whether the FDA will require human clinical data, a Q-Sub framed around your testing protocol is the most direct way to find out. Clinical studies are expensive; a Q-Sub that confirms bench testing is sufficient saves real time and money.

Software as a Medical Device (SaMD). FDA's software policy has evolved significantly in recent years. A Q-Sub asking the FDA to confirm whether your software constitutes a medical device, its proposed classification, and what performance testing is needed is particularly valuable for SaMD products, where the policy landscape is active.

Post-market modification strategy. If you are planning modifications to a cleared device and are unsure whether a new 510(k) is required, a Q-Sub asking about the modification's regulatory implications is more reliable than internal analysis alone.

Clinical study design. For PMA applicants, a Q-Sub early in clinical study planning (sometimes called a "pre-study Q-Sub") asks the FDA to review and comment on proposed primary endpoints, sample size methodology, and statistical analysis plan before the study begins. A clinical study that generates data the FDA rejects as insufficient for a PMA decision is not an outcome anyone wants.

What to Include in a Q-Sub Package

The FDA's Q-Sub guidance specifies the content required. A complete Q-Sub package typically includes the following.

Cover letter. States the submission type (Pre-Submission), the device name, the proposed regulatory pathway (510(k), De Novo, PMA, etc.), the submitter's contact information, and a request for the desired interaction type (written response, teleconference, or in-person meeting). The cover letter should state the date by which a meeting, if requested, would be useful given the company's regulatory timeline.

Device description. A concise description of the device: what it is, how it works, the intended use, and the indication(s) for use. Include enough technical detail for the FDA reviewer to understand the device without a lengthy engineering deep-dive.

Proposed regulatory pathway. A description of your proposed pathway (510(k) with identified predicate, De Novo, PMA) and the basis for that pathway selection.

Specific questions. This is the core of the Q-Sub. Questions must be specific, numbered, and focused on one issue per question. Vague questions ("what do you think of our device?") receive vague answers. Specific questions ("Is the named device, with its K-number, an acceptable predicate for a 510(k) submission for a specific device with a specific intended use?") receive usable answers. The FDA's guidance recommends limiting questions to those the company genuinely needs answered before proceeding; packing a Q-Sub with every conceivable question is discouraged and reduces the quality of responses.

Proposed answers. For each question, include the company's proposed answer and the rationale for it. This framing practice serves two purposes: it shows the FDA you have thought through the issue, and it allows the FDA to agree with your proposed answer (which is faster than writing an original response from scratch) or explain where and why your proposed answer is incorrect.

Supporting data and documentation. Attach whatever data is necessary for the FDA to understand the basis for your questions. If your question is about whether a bench testing protocol is sufficient to support substantial equivalence, attach the protocol. If your question is about predicate selection, include a brief comparison of your device and the proposed predicate.

The Q-Sub Review Process and Timeline

After submission, the FDA acknowledges receipt and assigns the Q-Sub to the appropriate review division. FDA's target for Q-Sub written feedback (no meeting) is 70 days from receipt. For a Q-Sub that includes a meeting request, FDA schedules the meeting to occur within roughly 70 to 75 days of receipt, and provides written feedback in advance of the meeting.

These are goals, not guarantees. Division workload, submission volume, and the complexity of the questions can affect actual response times. The FDA's MDUFA performance reports include Q-Sub metrics, and historical data suggests most responses arrive within or close to the 70-day target.

The FDA's written response is a formal document from the review division. It typically addresses each question in numbered sequence, states the FDA's position or feedback, and identifies any areas where the agency cannot provide feedback without additional information (a common outcome for questions that are too abstract or device-specific in ways that require more data than the Q-Sub package contained).

Q-Sub feedback is not a binding commitment. The FDA's guidance is explicit that pre-submission feedback "represents FDA's current thinking" and "does not bind the agency or the applicant." A Q-Sub response stating that your proposed testing approach appears adequate does not guarantee the FDA will accept that testing in a subsequent formal submission. It does, however, represent the considered feedback of the division that will likely review your submission, and a major departure from that feedback during formal review would typically require an explanation.

Common Q-Sub Mistakes

The Q-Sub program is useful precisely when used well. Several patterns undermine Q-Sub value.

Questions that are too broad. "What are FDA's requirements for our device?" is unanswerable in a useful way. The FDA's requirements depend on the specific device, its intended use, its classification, and its technological characteristics. Specific questions get specific answers.

Submitting too early. Asking questions before the device design is sufficiently defined means the FDA cannot give specific feedback. A question about testing protocols is only useful if you have a proposed protocol to ask about.

Not proposing answers. Companies that skip the "proposed answer" section of each question miss the efficiency benefit. A Q-Sub where the FDA can simply confirm agreement with your proposed approach takes less time to respond to, and the response is clearer.

Treating the Q-Sub as a substitute for regulatory counsel. The Q-Sub is a tool for getting FDA's specific feedback on specific questions. It is not a substitute for having a qualified regulatory professional frame those questions correctly, interpret the responses, and integrate them into your regulatory strategy.

How Q-Sub Responses Affect Your Marketing Program

A Q-Sub response that confirms your proposed indications for use provides documentary support for the intended use language you will write into your clearance application and, ultimately, your marketing materials. It is not a guarantee that those indications will be cleared, but it does reduce the risk that you have designed your entire product launch around an intended use the FDA will not support.

More directly: a Q-Sub response that confirms the De Novo pathway for a novel device tells your marketing team that the device will be the first of its kind, that a predicate competitor in the 510(k) database does not exist, and that "De Novo granted" (not "cleared") will be the marketing term. Those facts shape your launch narrative before you file a single page of your formal submission.

Buzzbox Media builds marketing programs for medical device companies that are engineered around the actual regulatory record, not optimistic assumptions about clearance scope. If your Q-Sub response is in hand and you want to build a launch plan that reflects what the FDA actually said, we can help. Start with 30 minutes at https://www.buzzboxmedia.com/book.