This article explains how the Q-Sub program works, when it delivers the most value, how to write a Pre-Submission that generates actionable FDA feedback, and how that feedback should flow back into your QMS and design controls.

What is the FDA Pre-Submission program?

The Pre-Submission program is administered by FDA's Center for Devices and Radiological Health (CDRH) and Center for Biologics Evaluation and Research (CBER). It allows device manufacturers to request FDA's feedback on specific technical, regulatory, or clinical questions before completing a formal submission.

FDA formalized the Q-Sub program in its Pre-Submission Program guidance document, most recently updated in 2023. The guidance defines four types of interactions available under the program:

• Written feedback only: FDA responds to submitted questions in writing without a meeting
• Teleconference: a call between the manufacturer and FDA reviewers to discuss the submission questions
• In-person meeting: face-to-face discussion at FDA’s facilities for complex issues
• Informational meeting: a one-way briefing to FDA on a topic, such as an emerging technology, without requesting feedback

Most Pre-Submissions result in written feedback within 70 calendar days from FDA's acknowledgment of the submission. Teleconferences and in-person meetings are typically scheduled within 90 days.

When a Pre-Submission delivers the most value

The Q-Sub program is most useful when there is genuine uncertainty about a specific question that FDA is positioned to answer. The situations where Pre-Submissions consistently pay for the time and resources invested include:

Novel device technology with no predicate. When a device uses a new mechanism of action or technology type, the regulatory pathway (510(k), De Novo, or PMA) may not be self-evident. A Pre-Submission requesting feedback on the intended regulatory pathway prevents investing six months of 510(k) preparation only to receive a "Not Substantially Equivalent" determination.

Testing strategy questions. FDA's guidance documents describe performance testing categories but rarely specify exact test methods, sample sizes, or acceptance criteria for a given device type. A Pre-Submission asking FDA to confirm that your proposed test methods are acceptable before you run them prevents the common scenario of completing all testing and then receiving feedback that a different test or additional samples are needed.

Clinical data requirements. For Class III devices or novel Class II devices where the predicate pathway is unclear, the amount and type of clinical evidence required can vary substantially. A Pre-Submission requesting feedback on whether bench testing alone is sufficient, or whether clinical data will be required, gives manufacturers a clear basis for their development and clinical strategy.

Software and cybersecurity questions. FDA's Software as a Medical Device (SaMD) guidance and its cybersecurity guidance for medical devices have become increasingly specific. A Pre-Submission asking FDA to confirm the software level of concern determination or to review a proposed cybersecurity architecture prevents repeated cycles of additional information requests during formal review.

Human factors study design. FDA's 2016 Human Factors guidance and subsequent recommendations describe the type of human factors validation testing expected, but the specific study design often requires FDA's input to confirm adequacy. A Pre-Submission is the standard mechanism for getting that confirmation.

How to prepare a Pre-Submission that generates useful feedback

The quality of FDA's feedback correlates directly with the quality of the Pre-Submission. Submissions that ask vague questions or that do not provide enough context for FDA to understand the device and its intended use generate vague or hedged responses.

A well-structured Pre-Submission includes:

Device description: A clear, concise description of what the device is, what it does, and how it achieves its intended effect. Include a diagram if the mechanism of action is not obvious from the text description. FDA reviewers read many Pre-Submissions across many device categories; assume no prior familiarity with your specific device.

Intended use and indications for use: The exact language you plan to use in your submission. If you are uncertain about the indications language, note this and ask FDA for feedback on whether alternative formulations would change the regulatory strategy.

Regulatory history summary: Identify any prior 510(k)s or PMAs you have reviewed as potential predicates. If you have identified a specific predicate, state it. If you are not certain your device has a predicate, say so explicitly and make it one of your questions.

Specific questions: Pre-Submissions should contain no more than five to eight specific, numbered questions. Each question should be answerable. "What testing does FDA recommend?" is not answerable. "Does FDA agree that the proposed biocompatibility testing battery under ISO 10993 is sufficient for a device with the described patient contact duration and contact type?" is answerable.

Proposed testing plan summary: For testing strategy Pre-Submissions, include a draft of the testing you propose to run, including test methods, sample size rationale, and acceptance criteria. FDA can confirm agreement with, or flag issues in, a specific plan; it cannot generate a plan from scratch for you.

How Pre-Submission feedback flows into your QMS

FDA's written feedback from a Pre-Submission is not legally binding, but it is highly material to your development and submission strategy. How that feedback is handled within your QMS determines whether it actually changes your development program or simply gets filed away.

Treating Q-Sub feedback as a design input change is the correct approach. If FDA confirms that your proposed test methods are acceptable, document that confirmation as part of your verification and validation plan, linked to the specific design input requirements the tests address. If FDA indicates that additional testing is required, open a change record in your design controls system and update the design and development plan accordingly.

Regulatory feedback from FDA should also be captured in your risk register where it affects risk decisions. A Pre-Submission response that identifies a new performance concern represents new information about the device's risk profile, which requires a documented risk management review.

Teams that fail to integrate Q-Sub feedback into their formal QMS processes often find themselves facing the same questions again during formal review because their submission documents do not reflect the alignment they thought they had achieved.

Pre-Submissions and 510(k) preparation timelines

Adding a Pre-Submission to the development timeline does not automatically extend it. A well-timed Pre-Submission can actually shorten the time to 510(k) clearance by preventing testing cycles that would need to be repeated after a Refuse to Accept or Additional Information request.

The calculation is straightforward: a Pre-Submission takes approximately 70 days to receive feedback. A single Additional Information request during 510(k) review typically adds 90 to 180 days to the review clock, plus the time to conduct whatever additional testing was requested. For testing-intensive submissions, one avoided Additional Information request more than recovers the time invested in a Pre-Submission.

The most efficient sequencing is to submit a Pre-Submission after completing initial design verification testing to confirm that the test methods and results will be acceptable, and before investing in full-scale validation testing. This places the Pre-Submission at a point in the timeline where FDA feedback can still influence the validation strategy without requiring completed testing to be repeated.

What happens after you receive FDA's feedback

FDA's written feedback in response to a Pre-Submission must be read carefully for what it confirms and what it does not address. FDA often provides conditional agreement: "If the device is used as described, the proposed testing would be acceptable." Conditions matter.

Points where FDA explicitly declines to provide feedback, or where the response is ambiguous, identify areas of continued uncertainty that should be flagged for the formal submission cover letter. Proactively acknowledging areas where FDA feedback was not obtained, and explaining the basis for your approach in those areas, is better than allowing a reviewer to identify gaps independently.

Pre-Submission feedback should be archived and referenced in the formal submission. FDA reviewers assigned to a formal submission will look for evidence that the manufacturer addressed Q-Sub feedback when it was received.

Documenting Pre-Submission interactions in your QMS

Each Pre-Submission interaction, including the original submission, FDA's acknowledgment, the meeting minutes if a meeting was held, and FDA's written feedback, should be stored in your design history file or the relevant QMS record for the device in development.

If the Pre-Submission raises questions that require changes to your regulatory strategy, update your regulatory affairs plan and the associated design and development plan with documented rationale. This creates a complete record of how your development strategy evolved in response to regulatory feedback, which is exactly what FDA expects to see when reviewing the DHF.

Cloudtheapp's Design Controls and Document Control applications support this workflow, allowing Pre-Submission correspondence to be linked directly to design inputs, verification plans, and risk management records within a single integrated QMS. The complete development record, from initial user needs through Pre-Submission feedback and final submission, is traceable and audit-ready.

Schedule a demo to see how Cloudtheapp manages medical device development documentation: https://www.cloudtheapp.com/demo/

See also: Medical device 510(k) submission: QMS requirements and design control checklist

Key takeaways

The FDA Pre-Submission program is a formal mechanism for receiving written FDA feedback before a 510(k), De Novo, or PMA submission. It is most valuable for novel device pathways, testing strategy confirmation, clinical evidence questions, and software and human factors issues.

A Pre-Submission that asks specific, answerable questions with adequate device context generates actionable feedback. That feedback must be integrated into the QMS through design controls, risk management records, and updated development plans, not simply filed as correspondence. Teams that use Pre-Submissions strategically and integrate the feedback properly into their QMS reduce their formal submission review timelines and avoid the most common causes of Additional Information requests.

This post created by and appeared first on Cloudtheapp