The Workbench · Craft
A nonbinding feedback request is not a 483 response
A Form FDA 483 lists inspectional observations, and the establishment that receives one faces a decision the statute doesn't answer: whether to write back, and how fast. FDA's own practice recommends a written response within 15 business days, but nothing in the Federal Food, Drug, and Cosmetic Act requires that response or sets a deadline for it. A narrower, less-used channel does carry a statutory clock, the same way a 513(g) request answers one narrow classification question and nothing else. Section 704(h) of the FD&C Act, added by the FDA Reauthorization Act of 2017, lets the owner, operator, or agent in charge of a device establishment ask FDA directly whether a proposed corrective action is adequate — and requires FDA to answer within 45 days. The two channels get filed under the same 15-day countdown as if they were one move. They aren't: one is a courtesy the agency extends to every 483, and the other is a statutory entitlement that only reaches a fraction of what a 483 can contain.
A guarantee, not a courtesy
The general 483 response has no statutory deadline; it's the agency's own stated expectation, most recently formalized in a March 2026 draft guidance limited to drug CGMP inspections that says on its face it doesn't extend to device establishments. CDRH's own device-specific expectation runs through a different document: the April 2020 guidance implementing Section 704(h), “Nonbinding Feedback After Certain FDA Inspections of Device Establishments.” That guidance describes the one channel where a device firm's request creates an actual statutory obligation on FDA's side — a 45-day answer, not a hoped-for one.
Three gates, not an open door
Only observations that clear a specific eligibility test can use this channel: proposed actions responding to a report that involves a public health priority, that implicate systemic or major actions, or that relate to emerging safety issues, as FDA determines. The guidance's own examples of what meets that bar: conditions likely, left unaddressed, to result in a violative product that could cause death or serious injury; quality system or subsystem deficiencies likely to produce a nonconforming, violative, or defective device; and emerging safety issues likely to produce devices that cause death or serious injury. A routine documentation gap or an isolated training lapse that doesn't touch product quality doesn't automatically clear that bar, and a firm requesting feedback on an observation the guidance doesn't describe is asking FDA to run a 45-day clock the statute never obligated it to run for that issue.
Same number, two different clocks
Both the general response and this request share a 15-business-day submission window measured from the Form 483's issuance, which reads like a coincidence until the reasons behind each one separate. The general 15 days is how long a firm has to give FDA something to weigh before the agency decides how to classify the inspection; missing it doesn't forfeit anything the firm still holds, it just means the response probably isn't considered before that classification is made. The Section 704(h) 15 days is a submission deadline for using the statutory entitlement at all — miss it, and eligibility for a 45-day answer on that observation is gone, whether or not the firm still owes a written response to the 483 more broadly.
What “nonbinding” doesn't undo
The guidance names the label deliberately: feedback issued under Section 704(h) isn't a device clearance or approval, isn't a commitment that FDA will forgo a Warning Letter or other action, and doesn't substitute for the firm's own 483 response. What it buys is narrower and still real — an early signal on whether a proposed fix is heading toward something FDA will accept, before the firm spends months implementing a corrective action plan the agency was never going to consider adequate. That's a smaller thing than a binding determination, but a firmer thing than silence, which is what a firm gets by default if it never asks.
One request, addressed to the same desk
A request goes to the same FDA contact who would receive the response to the Form 483 itself, and the guidance doesn't describe it as a substitute mailing — a firm still owes whatever response to the 483 it would otherwise owe, on whatever timeline its own compliance strategy calls for. A quality team that treats the nonbinding-feedback request as its 483 response, and stops there, has used the narrower instrument to do the broader instrument's job, and left the actual 483 unanswered by any measure FDA's classification decision will use.
Where this meets the rest of the file
An inspection-response tracker that keeps the general 483 response, the Section 704(h) eligibility screen, and the two independent 15-day windows as separate line items — rather than one countdown covering both — is previewed in the launch catalog. If your program handles a 483 differently, the shelf takes that correction directly.
The Regulatory Toolkit launches soon — a free shelf of source-mapped templates, checklists and browser-only tools for regulatory teams. Get one email when it opens, or contribute a template.