Method·August 1, 2026 · 3 min read

A Class I device, a Class I recall

FDA assigns a device its regulatory class once, as a permanent attribute of the device type. FDA assigns a recall its class per event, as a snapshot of one defect's severity. Both scales use the identical three labels, and a device's own class predicts nothing about the class of a recall against it.

By Connor Griggs — Regulatory & Quality Strategist

Pull a device recall record from openFDA and two fields sit a few lines apart, both capable of holding the string “Class I”: one describing the recall, one describing the device it recalls. They are not the same fact wearing two hats. They are two separate scales that happen to share a vocabulary, and nothing about either record warns a reader that the collision exists.

What a device’s class actually measures

A device’s regulatory class — Class I, II, or III— is a permanent attribute of the device type, assigned once by FDA’s classification regulation and unchanged until a reclassification order says otherwise. It measures the level of control needed to reasonably assure safety and effectiveness across the category as a whole: Class I devices are subject to general controls only, Class II devices carry special controls in addition, and Class III devices require premarket approval. A tongue depressor and a bandage sit in Class I not because nothing can ever go wrong with either, but because general controls are judged sufficient for the category. The number describes the device type. It says nothing about any single unit that ships.

What a recall’s class actually measures

A recall’s class is a different kind of fact entirely: a per-event severity judgment, made after the fact, about one specific defect. Under 21 CFR 7.41, FDA’s health hazard evaluation classifies a recall Class I when there is a reasonable probability that using or being exposed to the violative product will cause serious adverse health consequences or death, Class II when the consequences are temporary or reversible, or serious harm is merely remote, and Class III when adverse health consequences are not likely at all. That evaluation is about what this particular problem could do to someone, this time — not about which regulatory tier the device type was assigned to years earlier.

A device’s class describes what kind of thing it is. A recall’s class describes how badly this one went wrong. FDA reuses the same three labels for both, and the reuse is a coincidence of vocabulary, not a shared meaning.

Why the two scales can point in opposite directions

Nothing about a device’s baseline class caps or floors the severity a defect against it can reach. A contamination event in a Class I product — gauze, surgical gloves, an antiseptic wipe — can plausibly carry a reasonable probability of serious infection, which is a Class I recall sitting on top of a Class I device: the highest severity label this system has, attached to the lowest regulatory tier this system has. The reverse holds just as easily — a labelling error on a Class III implant, corrected without any plausible health consequence, closes out as a Class III recall. The device’s own class is not a prior on the recall’s class. Reading one as a hint about the other is reading a coincidence as a correlation.

The practice

FDA Radar’s own review queue is built around exactly this distinction, and the code’s own comment states the reasoning bluntly: routine recalls route to a searchable corpus rather than a reviewer’s inbox, with one deliberate exception — “Class I is the exception and the whole point: FDA reserves it for a reasonable probability of serious injury or death. That is the item a Regulatory Affairs Director must see the day it posts.” That gate checks the recall’s own classification field, never the device’s. A Class III device recalled at Class I severity reaches a reviewer immediately; a Class I device recalled at Class III severity does not, and correctly so — the device’s regulatory tier was never the question the gate is asking. Anyone reading recall data by hand should check the same field, for the same reason: what matters this week is what this defect could do, not what shelf the device type sits on.

Which specific recall is worth escalating, and what a given severity finding means for a supplier or a predicate, is a judgment for whoever owns that risk file, on the current record — this is a description of what two identically-labelled fields measure, not a determination about any device or recall in particular. Per what we monitor and how often, both fields run on every recall FDA Radar ingests, kept apart in the data exactly as they are kept apart in the rule.

Regulatory intelligence, not regulatory advice. This post describes method and published FDA records as of its date; decisions about a specific device belong with your regulatory professional.

Method
The PMA clock starts at the last module
Practice
The Q-Sub that doesn't buy you more time
Method
Lapsed and revoked end an EUA differently
Practice
A recall strategy has a grade. openFDA doesn't.
Method
A granted De Novo becomes a predicate.
Practice
Least burdensome changes the ask, not the bar.
Method
The lab is accredited. Not the device.
Practice
Breakthrough is law. STeP is a guidance.
Practice
MDSAP replaces routine. Not for-cause.
Method
No field on a 510(k) says what it treats
Method
Discretion is a policy. Exclusion is a statute.
Practice
Designated by one office. Approved by another.
Method
MedSun sits beside MAUDE, not inside it
Practice
The five-unit device never gets a K-number
Practice
Meeting the criteria isn't a tracking order
Method
The PMA clock doesn't stop at approval
Practice
The K-number doesn't track today's device
Method
A MAUDE report proves it was filed
Practice
Not every MDR starts with the manufacturer
Method
Completed. Not terminated.
Practice
The device-ban list has three entries
Method
The UDI exception has its own deadline
Method
MDUFA VI is being negotiated in public
Practice
The inspection manual changed, not the rule
Method
The count Congress had to legislate
Practice
The small-business rate isn't retroactive
Method
A detention order has no docket to read
Practice
PMA approvals moved off the Federal Register
Method
A citizen petition names names
Practice
A market withdrawal isn't a recall
Method
Not every device letter comes from CDRH
Practice
Closed on one device. Open on the rest.
Method
No IDE is confirmed until the PMA is
Practice
The remedial-action call sets the clock
Method
Jurisdiction is a letter, not a field
Practice
An address is not a footprint
Method
The final rule that isn't final yet
Practice
The special controls aren't in the record
Method
Exempt from GMP. Not from complaints.
Practice
The notify list isn't the shortage list
Method
A constraint can't be skipped. A script can.
Practice
No cron sends this. A person does.
Method
Corrected, not rewritten
Practice
Quiet is a finding, not a default
Method
The summary is public. The statement isn't.
Practice
A competitor's 513(g) leaves no trace
Practice
An empty response field proves nothing
Method
A petition is public. Its outcome isn't.
Practice
The panel is a category, not a meeting
Method
An accessory carries its own classification
Method
A TPLC report is a category, not a device
Practice
A 522 order is a question, not a verdict
Method
A PCCP change leaves no new record
Practice
Not every signal becomes a recall
Method
eSTAR did not remove the acceptance check
Practice
An early alert has no recall number yet
Practice
A consent decree isn't a database row
Method
The record has no cybersecurity field
Practice
Classification Change is not one event
Method
Publication date is not effective date
Method
One event. Many recall numbers.
Practice
Quantity is a sentence, not a number
Practice
How a firm told you is a field too
Method
A RIN outlives the document number
Method
The docket ID is not the comments
Practice
The 510(k) record doesn't name the predicate
Practice
The 510(k) FDA didn't review first
Method
The letter FDA doesn't have to post
Practice
Cleared doesn't say which track it took
Method
The clock stops. The calendar doesn't.
Method
Why a guessed match never reaches you
Practice
The standards list never names a device
Method
The guidance isn't in the Federal Register.
Practice
Filtered. Not discarded.
Method
There are two recall databases, not one
Practice
Breakthrough status is confidential by law
Practice
One MAUDE report is not one malfunction
Method
A supplement number is not a track
Method
Cleared is not approved
Practice
Nationwide doesn't mean your building
Practice
Not every correction reaches FDA
Method
Registered. Not reviewed.
Method
Contact ODE is not a pathway
Practice
Almost no recall is FDA-mandated
Method
FDA's device names read like a card catalog
Practice
openFDA is free. It is not unlimited.
Method
GUDID stores the model. Not the box.
Practice
Detention doesn't need a warning letter
Practice
21 CFR 820 didn't move. Its contents did.
Method
The product code that doesn't exist yet
Practice
The classification posts. The 483 behind it doesn't.
Method
A recall has three dates, and the pipeline had to pick one
Practice
The count is real. The rate is not.
Method
The firm on the record is not the firm on the box
Practice
Low confidence is an instruction, not a hedge
Method
The same company, spelled three ways
Practice
A device that was never a medical device
Method
FDA's warning letters, addressed by column number
Practice
Your regulation has a decimal. FDA's watch doesn't.
Method
Three letters is too short to search for
Practice
Most warning letters never close
Method
The guidance that skipped the draft
Practice
Ongoing, as of when?
Method
The least interesting fact in a 510(k)
Practice
No recall arrives with a product code attached
Practice
The deadline that doesn't email you
Method
The warning letter has two dates
Method
How to monitor FDA without drowning
Practice
Your predicate was recalled. Now what?
Method
Why no item reaches you without a human