A Special 510(k) only works on your own device

The eligibility test is about whose device it is, not how big the change is

The guidance's core condition is ownership, not scope: the modification has to be made by the manufacturer to its own currently marketed device, with the same intended use, using design controls capable of resolving whatever safety and effectiveness questions the change raises. A company launching a new product line closely modeled on a competitor's marketed device can't use the Special 510(k) pathway for that submission, however minor the differences are, because there's no earlier device of its own on file to modify. That submission is Traditional or Abbreviated regardless of how narrow the change would have looked under a different manufacturer's own name.

Design controls carry the argument, not new testing

A Special 510(k) submission summarizes the design control activities and verification-and-validation results the manufacturer's own change-control process already generated, rather than presenting a freshly commissioned study built for the filing. FDA's guidance appendices sample what that summary should contain: redlined requirements, verification and validation protocols and results, and updated risk analysis — reviewed, per the guidance, in summary or risk-analysis format rather than as raw underlying data. Where those results can't be sufficiently reviewed that way, the pathway doesn't fit the modification, whatever the manufacturer's internal design control record actually contains.

“Well-established methods” do double duty here too

The phrase “well-established methods” shows up in Special 510(k) eligibility and, separately, in FDA's 2023 draft predicate-selection guidance — and it answers a different question in each place. In predicate selection, it asks whether the comparator device was cleared on solid methods. In Special 510(k) eligibility, it asks whether the method used to verify this specific change is established: recognized in a relevant standard, or already used for similar changes to this device or device type. The two tests share a phrase, not a meaning, and a sponsor that treats a well-established predicate as evidence the Special 510(k) route is also available has conflated a question about the comparator with a question about the verification method.

Thirty days is a goal, not a deadline the statute sets

FDA aims to review Special 510(k)s within 30 days, against the longer MDUFA review goal a Traditional submission carries — but the guidance is explicit that this timing goal doesn't alter any statutory or regulatory requirement behind the review itself. If FDA determines during review that the design-control summary can't resolve the substantial-equivalence question, the agency can request additional information or the pathway can convert to Traditional review, and that shift resets the review clock rather than preserving the 30-day target alongside it. A submission plan built around the 30-day goal as a guarantee is planning around an aspiration FDA never committed to as a rule.

Where this meets the rest of the file

The Special 510(k) question only comes up after 807.81(a)(3)'s own two-prong test has already concluded a new 510(k) is owed at all — picking a pathway is a second decision, not a substitute for the first. And the well-established-methods language it shares with FDA's 2023 draft predicate guidance is worth reading carefully rather than assumed identical: one tests the comparator device's own clearance basis, the other tests the method used to verify your change, and the shared phrase is where that distinction most often gets missed.

A pathway-selection worksheet built around the Special 510(k)'s own-device test, its design-control-summary requirement, and its non-binding 30-day goal is previewed in the launch catalog. If your program draws the Special-versus-Traditional line differently, the shelf takes that correction directly.