A 513(g) reply isn't a classification decision

A sponsor unsure how FDA will classify a device, or which requirements attach to it once classified, has a formal way to ask before committing to a submission strategy: file a Section 513(g) Request for Information. Read the reply as it's actually written, though, and it answers something narrower than “here is your device's class.” Section 513(g) of the Food, Drug, and Cosmetic Act, codified at 21 U.S.C. 360c(g), lets a requester obtain FDA's views on classification and applicable requirements — it doesn't authorize FDA to issue a classification decision inside that reply, and FDA's own guidance on the mechanism says so directly. A sponsor who files a 513(g), gets an answer, and treats that answer as settled has mistaken a stated view for a determination.

What a 513(g) request can actually ask

Section 513(g), codified at 21 U.S.C. 360c(g), lets a requester get FDA's written views on the class into which a device has been classified, or on the requirements applicable to a device under the Act. FDA's own guidance on the mechanism, FDA and Industry Procedures for Section 513(g) Requests for Information, describes what the request is supposed to contain: a well-defined device description, the specific intended use, and a specific classification or requirements question — not an open invitation to ask FDA to evaluate a device generally. What the guidance is equally clear a 513(g) doesn't do is review the underlying safety or effectiveness data behind that question. FDA doesn't assess performance data, testing protocols, or a substantial equivalence argument as part of answering it. A request built like a miniature 510(k), with bench data attached and an expectation that FDA will weigh it, is asking the mechanism to do something it isn't built to do.

The reply says what it is, inside the letter itself

FDA's response to a 513(g) request states its own limits as part of the response: it's the agency's current thinking on the classification or requirement question asked, not a classification decision and not a clearance or approval for marketing. Getting an actual, reviewable classification determination runs through a different pathway entirely — most often a 510(k) that FDA accepts, reviews, and rules on, or a formal reclassification petition under section 513(e) for a device already assigned to a class. A 513(g) reply can shape which of those pathways a sponsor pursues next, and can be a reasonable thing to cite as context, but it doesn't substitute for going through the pathway itself, and FDA isn't bound by it the way the agency is bound by an actual clearance or approval order.

Not the same tool as a jurisdiction call or a pre-sub meeting

It's worth being precise about which question 513(g) answers, because two other mechanisms answer adjacent-sounding ones. A Request for Designation answers a different question altogether: which FDA center has jurisdiction over a combination product, not what class a device falls into or what a straightforward device's requirements are. A Q-Submission meeting request is different again — informal, interactive feedback from a review division ahead of a planned submission, with FDA's comments explicitly non-binding but delivered through a conversation rather than a single written reply. A 513(g) sits in a narrower slot than either: one written question about class or applicable requirements, answered in writing, without the back-and-forth a Q-Sub meeting allows and without the jurisdictional determination an RFD produces. Reaching for the wrong one of the three wastes the specific thing each is built to do.

Why a sponsor files one anyway

None of this makes a 513(g) a weak tool for the question it's actually built to answer. A device that could plausibly fall into more than one classification regulation, or a novel product where no existing device type clearly applies, benefits from a written FDA answer before a sponsor commits engineering and clinical resources to a submission built on the wrong assumption. The value is informational, not procedural — it narrows the range of reasonable submission strategies before a 510(k) or De Novo request gets drafted, which is a real cost saved even though the letter that does the narrowing carries no binding weight of its own.

Where this meets the file

A regulatory strategy file that logs a 513(g) reply as though it settled a classification question has recorded the wrong kind of milestone — the same mistake, in a different corner of the process, as reading a PMA's filing acceptance as a verdict on the science inside it. What the file should carry instead is the question actually asked, the date of FDA's written reply, and which formal pathway the reply pointed the sponsor toward next. A pre-submission strategy worksheet that keeps a 513(g) reply, a Q-Sub outcome, and an RFD determination in separate, clearly labeled fields — rather than one undifferentiated “FDA feedback” column — is previewed in the launch catalog. If your program tracks these differently, the shelf takes that correction directly.