The anatomy of a Q-Submission request that gets a useful answer

A Pre-Submission meeting is free, structured, and open to nearly every device sponsor — and a lot of sponsors still walk out of one with an answer they can't actually use. The problem is rarely FDA's discipline. It's almost always the request.

FDA finalized updated guidance on the Q-Submission Program in May 2025, superseding the version issued in June 2023. The mechanics changed at the margins; the underlying structure of the program, and the reason most requests underperform it, did not.

The mechanism is a menu, not one thing

“Q-Sub” is a family, not a single request type: Pre-Submissions, Submission Issue Requests, Study Risk Determinations, and Informational Meetings each exist for a different moment in a device's life and answer a different kind of question. A Pre-Submission is built for early, open strategic questions before a submission is drafted. A Submission Issue Request exists for a narrow, specific problem inside a submission that's already been filed. Sending a broad strategy question through the mechanism meant for a narrow, already-filed issue — or the reverse — doesn't just get a slower answer; it can get an answer to a question you weren't actually asking, because the reviewing division is scoped to the request type you chose.

A specific-answer question, not an agreement question

This is the highest-leverage edit most requests need, and it's the same structural flaw the checklist has when it asks for agreement instead of evidence. “Is our overall testing strategy acceptable?” invites a hedge, because it isn't a question with one committable answer — it's an invitation to list caveats. “Is the bench-test protocol described in Section 4.2 sufficient to support substantial equivalence for the mechanical-strength characteristic?” invites a specific yes, no, or a specific gap. FDA's written feedback responds to the literal question posed; a vague question reliably gets a vague, hedged, largely unusable answer back, and the sponsor has spent a meeting slot finding that out.

Background has to do the reviewer's homework

The reviewing division did not spend the last six months living with your device. A request that makes them reconstruct the device description, the predicate or comparator context, and the proposed regulatory pathway from scratch spends the meeting's limited time on orientation instead of on the actual question. The strongest requests state, concisely and up front: what the device is, what pathway and classification the sponsor believes applies, and what specifically is uncertain about the plan — so every minute of scarce review time goes toward the question that's actually open.

The minutes are the artifact, not the meeting

The meeting itself is not what gets filed. The written feedback or meeting minutes are what survives into the submission file and gets cited later, sometimes years later, in an entirely different review. That's the real argument for asking narrow, specific questions: a specific question produces a specific, quotable answer in the minutes, while a broad one produces a paragraph of context that's hard to cite as a firm commitment from FDA when it matters.

A Q-Submission request template built around this structure — type selection, background, and question-writing guidance — is previewed in the launch catalog. It sits alongside the shelf's other document-craft pieces; if you've built a Q-Sub request that consistently gets useful answers back, the shelf would take a look.