Practice·July 23, 2026 · 4 min read

The deadline that doesn't email you

A Federal Register comment period can run ten days or nine months, and nothing on the page warns you which. The field that has the real answer, and the habit that checks it every week.

By Connor Griggs — Regulatory & Quality Strategist

A proposed rule on device classification posts with a ninety-day comment window. Three weeks later, a draft guidance on a related question posts with sixty. A narrower draft guidance, the same month, gives interested parties ten days. Nothing on the Federal Register page tells you this variation exists — usually you notice it by having missed one.

There is no default

It is tempting to memorise “comment periods are sixty days” the way you memorise a CFR citation, and it is wrong often enough to be dangerous. Comment windows are set case by case, per document, by the office issuing it. FDA’s own guidance on the docket and comment process describes how to participate without promising a standard length, and the published record shows why a promise would be false: comment periods on FDA device-related documents run anywhere from about ten days to nine months, depending on what is being proposed and how urgent the agency judged it. Memorising a typical number is exactly the habit a monitoring practice is supposed to replace.

The one place a number actually exists

Draft guidance is the exception, and it is worth knowing precisely why. FDA’s Good Guidance Practices regulation — 21 CFR 10.115 — governs how the agency develops and issues guidance, and FDA’s own background on the rule states that a sixty-to-ninety-day comment period is generally appropriate for most Level 1 (significant) draft guidance. That is a real, citable policy position, not folklore — and it is exactly why it should not be generalised to every other document type, where no equivalent commitment exists. A draft guidance is a comment opportunity FDA has committed, in writing, to holding open for a predictable window. A proposed rule is not making you that promise.

The field that actually answers the question

Every Federal Register document carries a comments_close_on value in the agency’s own structured record — not a convention, a field, populated per document, present in the API the Federal Register publishes for exactly this purpose. Comments are filed against a docket — a unique docket ID minted per rulemaking, through regulations.gov — and both the docket ID and the closing date exist in the record from the day the document posts. The discipline is simple to state and easy to skip under volume: read the field, every time, for every document that touches your CFR parts. Do not infer the date from the document type. The one time the inference is wrong is the one that costs you the window.

A monitoring habit that memorises typical values is a habit waiting for the atypical one.

The weekly habit that catches it

FDA publishes to the Federal Register on essentially every day it is open for business, which means a document relevant to your CFR parts can post on a Tuesday and close before a monthly review ever looks at it. The operating cadence that works for a small RA team is a standing weekly pass: pull the current week’s device-relevant documents, and for each one, log three things on a running board — the docket ID, the comments_close_on date, and a one-line note on whether it touches your portfolio. Then review the board itself weekly, sorted by closing date, not by when the item was logged. A window that opened eight weeks ago and closes next Friday is more urgent than one that opened yesterday and closes in the spring, and a board sorted by arrival order hides exactly that.

Whether to comment at all, and what to say, is a judgment call this post is not making for you — it depends on your product, your competitive position, and your counsel’s read of the docket. This is regulatory intelligence about where the deadline lives, never regulatory advice about what to file against it. What the habit buys you is the part that is not a judgment call: knowing the window is open, and how many days are left in it, before it closes without you.

FDA Radar runs this same field through its own pipeline — every Federal Register item we ingest carries its own comments_close_on date and docket IDs as structured facts, not something a reader has to go find. Deciding whether a given docket is worth your comment is still yours. Knowing it exists, and when it closes, no longer has to be.

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
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