Method·July 23, 2026 · 4 min read

The warning letter has two dates

One starts your compliance clock. The other is what the public sees, and it can lag by weeks. Confuse them and the subject line's real signal goes unread too.

By Connor Griggs — Regulatory & Quality Strategist

A CDRH warning letter carries two dates that are easy to conflate and expensive to conflate wrong: the date FDA issued it, and the date FDA posted it publicly. They are rarely the same day, and the letter does not explain the gap. Neither does the subject line, which reads like a sentence and is actually closer to a taxonomy. Both are worth reading correctly.

The date that starts your clock

The compliance clock does not start when the letter appears on fda.gov. It starts when the recipient receives it — close to the letter’s issue date, not its posting date — and FDA’s Regulatory Procedures Manual sets out the standard closing language nearly every warning letter carries: a written response describing corrective action, generally due within fifteen working days of receipt. That number is customary, not a statute, and FDA has departed from it: in late 2025 two device firms received thirty business days instead of fifteen, stated plainly in their own letters. What survives both cases is the same instruction — read the deadline the letter itself states, and count from receipt, not from whenever you happened to notice the letter existed.

The date that is not the clock

The posted date answers a different question: when did this become public, and therefore visible to a competitor, a journalist, or you, if the letter was never addressed to you. FDA’s warning letter database carries both dates as distinct fields for exactly this reason — conflating them produces two different errors. Treat the posted date as the clock and you may believe a firm has more time than it does. Treat the issue date as when the public could see it and you may believe you missed something that has not, in fact, been published yet. FDA Radar keeps both fields separate in every letter it ingests, because a monitoring product that reported one date as the other would be wrong on the one detail this product exists to get right.

The subject line is a taxonomy, not a sentence

Read a CDRH warning letter’s subject line closely and it is not prose — it is a short list of violation categories separated by slashes, drawn from a small, recurring vocabulary FDA reuses letter after letter: Quality System/Medical Device/Adulterated, or some neighbouring combination. Read one letter and it is a label. Split a quarter’s worth of subject lines on that slash, tally the categories, and the label becomes data: which failure mode CDRH is currently finding often enough to write about repeatedly, in your corner of the industry, this quarter rather than last.

You do not need this product to run that exercise once. Filter FDA’s warning letter database to the Center for Devices and Radiological Health, sort by posted date, and pull the last thirteen weeks in your device class. For each letter, note the issue date rather than the posted date, and split the subject into its categories. What comes out is not gossip about individual firms — it is, in miniature, CDRH’s enforcement agenda for your quarter, built entirely from language FDA itself chose to put in a subject line.

One warning letter is a fact about one firm. A quarter of them, read as a set, is a fact about what FDA is looking for.

What this is not

None of this tells you what to do if a letter names you, a competitor, or a supplier. Reading the enforcement theme in your device class is a monitoring habit; deciding what it implies for your quality system, your risk file, or your own submission is a regulatory judgment for a professional looking at your specific facts — this post, like the rest of Signals, is intelligence about how to read the record, never advice about what your record should say.

FDA Radar ingests CDRH warning letters, keeps issue date and posted date as separate fields, and parses the subject line into its component violation themes automatically — what reaches a reviewer is the structured version of the above; what the reviewer still decides is whether it is material to you. See what we source and how often for the rest of the pipeline.

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
Method
A Class I device, a Class I recall
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
How to monitor FDA without drowning
Practice
Your predicate was recalled. Now what?
Method
Why no item reaches you without a human