Every 510(k) argues substantial equivalence — the same statutory finding, whichever form the argument takes. But FDA accepts the argument in three forms: Traditional, Special, and Abbreviated. Teams routinely choose by folklore — “Special is the fast one” — and folklore here is expensive, because the types differ not in ambition but in eligibility. The right question is not which sounds fastest. It is: what changed, whose device is the predicate, and what does your evidence lean on?

Traditional — the default

The Traditional 510(k) is the complete form of the argument: full device description, full comparison against the predicate you chose, full performance data, under the content requirements of 21 CFR 807.87. Any device eligible for the pathway can file one, against any legally marketed predicate. When people say “510(k)” without qualification, this is the one they mean — and when either alternative's eligibility is in doubt, this is the one you fall back to. Nothing about Traditional is a penalty; it is simply the whole argument, made explicitly.

Special — for changes to your own device

The Special 510(k) reframes the comparison: the predicate is your own legally marketed device, and the change you made to it is the whole subject. Its logic is borrowed from design controls — if your 21 CFR 820 design verification and validation procedures are well-established for the kind of change in question, and their results can be summarized in a submission rather than fully re-reviewed, FDA commits to a 30-day review. That is the fastest clock anywhere in the device premarket world, and it is real.

The eligibility is narrow by design. The current program — rebuilt by guidance in 2019 — asks two questions: is the change to your own device, and can substantial equivalence be established by reviewing summary design control information? Changes to intended use almost never qualify. Changes to fundamental scientific technology do not qualify. And a Special 510(k) that reaches past its eligibility is not rejected — it is converted to a Traditional and the review starts over on the 90-day goal, which is how a plan built on 30 days quietly becomes a quarter late.

Abbreviated — the argument by reference

The Abbreviated 510(k) changes what the evidence leans on. Where a device-specific FDA guidance exists, where special controls define what Class II safety looks like for the type, or where FDA-recognized consensus standards cover the performance questions, the submission can rely on them: summary reports on how the guidance was followed, declarations of conformity to the standards, in place of data the reviewer must otherwise reconstruct line by line. The MDUFA goal is the same 90 FDA days — the gain is a review with less to argue about, because the agency pre-agreed the questions when it recognized the standard.

Choosing in practice — three questions in order
  1. Is this a modification to your own legally marketed device, provable through summary design control outputs? File a Special 510(k) and plan on FDA's 30-day goal.
  2. Is a device-specific guidance, special control, or set of recognized standards doing the heavy lifting in your evidence? An Abbreviated 510(k) lets the declarations carry it.
  3. Neither cleanly true? File Traditional. A converted Special or a thin Abbreviated costs more time than the Traditional ever would have.

Where the choice goes wrong

Filing a Special for a change that touches intended use

The 30-day clock is only real inside the program's eligibility. An indications change raises clinical questions that design verification summaries cannot answer, so FDA converts the file to Traditional — after you have already spent weeks in queue. The conversion is not a rejection; it is worse, because the launch plan was built on the wrong clock.

Choosing Abbreviated because it sounds shorter

Abbreviated abbreviates the submission, not the review clock. If no guidance or recognized standard actually covers your device's performance questions, the declarations have nothing to declare, the reviewer asks for the underlying data anyway, and you have written a Traditional 510(k) with extra steps.

Forgetting the pathway is not the argument

All three types end in the same finding: substantial equivalence to a predicate. Teams polish the format and neglect the comparison — but a Special with a weak change rationale and an Abbreviated with an ill-fitting standard both fail for the same old reason. The type is packaging. The predicate comparison is still the product.

Frequently asked questions

Can a Special 510(k) change the indications for use?

As a rule, no. The Special 510(k) program exists for changes whose substantial equivalence can be established by design control outputs summarized in the submission — and changes to indications for use rarely qualify, because they raise questions design verification alone cannot answer. Submit one anyway and FDA converts it to Traditional, and the 30-day plan you built around it is gone.

Is an Abbreviated 510(k) reviewed faster?

It carries the same MDUFA performance goal as a Traditional 510(k) — 90 FDA days. The efficiency is in the review, not the clock: declarations of conformity to recognized standards and summary reports against guidance give the reviewer less to reconstruct. A well-built Traditional and a well-built Abbreviated often finish in similar time; the Abbreviated is simply harder to build wrong.

What is Third Party Review?

For certain lower-risk device types, an FDA-accredited Third Party Review Organization conducts the initial 510(k) review and forwards its recommendation to FDA, which issues the final determination — typically within 30 days of receiving it. No MDUFA user fee applies, though the review organization charges its own. It is a route, not a 510(k) type: the file you write is the same.

Sources & further reading

  1. FDA Guidance — The Special 510(k) Program (2019) fda.gov
  2. FDA Guidance — The Abbreviated 510(k) Program (2019) fda.gov
  3. FDA — Premarket Notification 510(k): the three submission types compared fda.gov
  4. FDA — 510(k) Third Party Review Program fda.gov

This lesson is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal or regulatory advice.