The Workbench · Craft
Every 510(k) exemption carries the same two limits
This blog has already covered how a device's UDI exemption comes from a named list in 21 CFR 830, not a default a labeler gets to assume. Most Class I devices, and a long list of specific Class II device types, carry a structurally similar exemption from the ordinary 510(k) premarket notification duty — and it runs into the same trap. Almost nothing in how that exemption gets announced makes clear that it was never unconditional. Every device-classification part from 862 through 892 closes with its own numbered section, always ending in “.9,” that keeps exactly two named limits in force underneath the exemption for as long as the device stays on the market — and a device that trips either one owes a 510(k) exactly as if the exemption had never applied to it at all.
The exemption is real, and it was never the whole rule
FDA's device classification regulations exempt most Class I devices, and a substantial share of Class II device types, from the section 510(k) premarket notification a newly marketed device would otherwise owe. That exemption sits in the same classification regulation that assigns the device its generic type — but the regulation doesn't stop at granting it. Each part closes with a section, numbered to match the part (862.9, 870.9, 880.9, and on through the rest), titled “Limitations of exemptions from section 510(k)” — and that section, not the exemption announcement itself, is what actually governs how long the exemption keeps holding.
Two conditions, named specifically
21 CFR 880.9 states the limitation in two parts, and every other device-classification part's own “.9” section states the same two: a device is not exempt where it's intended for a use different from the intended use of a legally marketed device in that generic type — the regulation's own examples are a different medical purpose, or lay use where the prior intended use was professional-only — or where it operates using a different fundamental scientific technology than a legally marketed device in that generic type, such as a surgical instrument that cuts with a laser beam rather than a sharpened blade, or an in vitro diagnostic that identifies an infectious agent by DNA probe or nucleic acid hybridization rather than culture or immunoassay. Nothing else is on the list. A manufacturing change, a labeling update, or a cosmetic redesign doesn't reopen the exemption on its own — only a shift in intended use or in the device's own underlying technology does.
The consequence is filing exactly as if unexempt
Where either limit applies, the regulation doesn't create a lighter, partial filing for a device that was exempt until recently. The manufacturer has to submit a premarket notification before introducing or delivering the device for commercial distribution, on the same terms as a device that was never exempt in the first place. The exemption doesn't taper off or grandfather in prior marketing history — it simply stops applying the moment either condition is met, and the device re-enters ordinary 510(k) review from that point.
The trigger is usually a later change, not the device at launch
Because both limits test the device against “a legally marketed device in that generic type” rather than against the device's own original clearance file, the moment that actually matters is often years after a device first reached the market — when an already-exempt manufacturer changes its own device's indication or its own operating principle, not when some other company's new device enters the category. This blog has already covered the two-prong test 21 CFR 807.81(a)(3) runs for a device that's already been cleared; an exempt device runs a parallel but separate test, and a change-control process that only checks a modification against its own internal thresholds, without asking the “.9” question specifically, can miss the one change that quietly ended the exemption months or years before anyone noticed.
Where this meets the file
A 510(k)-exemption record needs the two limitations tracked as their own standing fields against the device's current intended use and current operating technology — re-checked at every design change, not verified once at the device's original market entry and filed away. A 510(k)-exemption monitoring worksheet built around that structure is previewed in the launch catalog. If your program tracks exemption status 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.