FDA Q-Submission Program
The FDA Q-Submission (Q-Sub) Program is the umbrella pathway for pre-submission interactions between device sponsors and CDRH/CBER. The Pre-Sub is the most-used member of the family — a written request for FDA feedback on a planned 510(k), De Novo, PMA, IDE or HDE — but the program also includes Submission Issue Requests, Study Risk Determinations, Informational Meetings, PMA Day-100 Meetings and Breakthrough Devices Program interactions. Used well, a Pre-Sub saves months of submission cycle time.
01What a Q-Submission is
A Q-Submission is the formal mechanism for a device sponsor to ask the FDA a question, propose a study, or request a meeting, in writing, before a marketing or investigational submission. The June 2023 guidance consolidated several historical mechanisms into one program. Each Q-Sub gets a unique 'Q' tracking number and the FDA's response is binding within the bounds of the information provided — a sponsor who follows Pre-Sub feedback has a much stronger position when the eventual submission is reviewed.
02Members of the Q-Sub family
- Pre-Sub — written request for FDA feedback on a planned submission (most-used member).
- Submission Issue Request (SIR) — feedback during review of an existing submission with an Additional Information request.
- Study Risk Determination — confirmation that a planned study is non-significant-risk under IDE rules.
- Informational Meeting — sponsor presents new technology to FDA reviewers without asking a specific question (read-only).
- PMA Day-100 Meeting — statutory meeting 100 days after PMA filing to discuss review status.
- Breakthrough Devices Program interactions — designation request, Sprint Discussions, Data Development Plan.
- Agreement Meeting and Determination Meeting — pre-PMA mechanisms for protocol agreement.
- Accessory Classification Request — request to classify an accessory under section 513(b).
03Anatomy of a Pre-Sub
A well-constructed Pre-Sub is short, specific and bounded. FDA expects:
- Cover letter naming the planned submission type, expected timing and the meeting format requested (written feedback only, teleconference, or face-to-face).
- Device description sufficient to ground the questions — intended use, indications, technology, predicate or comparator landscape.
- Regulatory history — prior FDA interactions, related Q-numbers, any 483/Warning Letter context.
- Specific questions, each numbered, each with a proposed sponsor position and the supporting rationale. The FDA answers the questions; vague open-ended prompts get vague answers.
- Supporting data attached as appendices — pre-clinical, bench, clinical pilot, literature.
- Proposed meeting agenda if a teleconference or face-to-face is requested.
04Timing and FDA service levels
| Sub-type | FDA target turnaround |
|---|---|
| Pre-Sub written feedback only | 70 days from acceptance |
| Pre-Sub with teleconference | 70 days from acceptance to meeting |
| Pre-Sub with face-to-face meeting | 75-90 days subject to scheduling |
| SIR | 21 days for written response |
| Study Risk Determination | 30 days |
| Breakthrough designation request | 60 days |
Plan Pre-Subs so feedback lands at least 60 days before the planned submission to allow rework.
05Fees
Q-Submissions do not carry MDUFA user fees. They are free to file. The cost is internal — preparing a Pre-Sub of acceptable quality typically takes a multidisciplinary team several weeks.
06Highest-value use cases
- Novel intended use or indication that does not fit cleanly into an existing classification.
- Predicate-selection uncertainty for a 510(k) — confirm FDA agrees the chosen predicate is appropriate.
- Clinical study design — endpoints, sample size, comparator, statistical plan.
- Non-clinical test plan — biocompatibility battery, electrical safety standards version, software documentation level.
- Cybersecurity documentation strategy under the 2023 premarket guidance.
- Real-World Evidence strategy — whether RWE is acceptable as a pivotal-trial substitute.
- Combination-product jurisdiction questions (CDRH vs CDER vs CBER lead centre).
07Common pitfalls
- Asking 'Do you agree our device is substantially equivalent?' — FDA will not pre-decide the submission. Ask about the building blocks instead.
- Submitting a Pre-Sub before the device is well-enough characterised — FDA pushes back asking for clarifications, wasting the cycle.
- Bundling too many unrelated questions into one Pre-Sub — split into separate Q-Subs.
- Ignoring previous Pre-Sub feedback in the eventual submission — reviewers cross-reference.
- Treating Pre-Sub feedback as binding when material new information emerges — file a follow-on Pre-Sub or SIR rather than assume the original answer still holds.
08eSTAR and submission format
FDA's eSTAR templates include Q-Sub formats. Q-Subs supporting a planned 510(k) increasingly use eSTAR for consistency. Use the latest template version available on FDA's eSTAR program page, and the FDA Customer Collaboration Portal for submission and tracking.
09How V5 handles this
Frequently asked questions
Q.Is FDA bound by Pre-Sub feedback?+
FDA states that feedback reflects the agency's best advice given the information provided. It is not legally binding, but in practice reviewers stand behind documented Pre-Sub positions unless new information justifies a different view.
Q.Can a Pre-Sub be filed for a combination product?+
Yes. For combination products, file with the lead Center; for jurisdictional uncertainty use an RFD (Request for Designation) first, then a Pre-Sub with the assigned Center.
Q.Are Pre-Subs confidential?+
Yes. Q-Submissions are not publicly disclosed. FDA may anonymise themes in guidance development but does not publish individual Q-Subs.
Q.How many Pre-Subs is too many?+
There is no statutory cap, but reviewers notice when sponsors file unfocused Pre-Subs repeatedly. Concentrate questions and use SIRs for in-review issues.
Primary sources
Further reading
V5 Ultimate ships with the FDA Q-Submission Program controls already wired in — audit trail, e-signatures, validation evidence. Free trial, no credit card, onboard in days, not months.
