Method·August 27, 2026 · 4 min read

The final rule that isn't final yet

A Direct Final Rule publishes as a finished action — an effective date, a CFR citation, done. FDA's own procedure ships every one with a second, inert document next to it: a companion proposed rule that only activates if someone files an adverse comment, and FDA Radar's own categorizer reads both documents the same way it reads an ordinary rule.

By Connor Griggs — Regulatory & Quality Strategist

A device classification action posts to the Federal Register carrying FDA’s plainest label for a finished action: Rule. Not proposed, not draft, not availability — a rule, with an effective date already printed on the page. Read that as done, and for most of what posts under that label, it is. For a specific kind of rule FDA writes when it does not expect anyone to object, it isn’t — not until its own comment period closes with nothing filed against it.

What a direct final rule actually promises

FDA’s own procedure for issuing what it calls a direct final rule applies when the agency does not anticipate receiving any significant adverse comment on an action — typically a housekeeping change, a technical correction, or a classification update nobody is expected to contest. The rule publishes with a real effective date, usually set some weeks out, and reads exactly like any other final rule sitting next to it in the same issue. Nothing in the document itself marks it as conditional. The condition is procedural, not textual: FDA has committed, in its own guidance on the practice, to pull the rule back the moment anyone objects.

The companion sitting in the same issue

Every direct final rule ships with a second document, published the same day, in the same Federal Register issue, on the identical subject — a companion proposed rule. FDA’s own device-reporting rulemaking from February 28, 2005 is a clean example: Medical Devices; Medical Device Reporting posted as the direct final rule, and immediately next to it, Medical Devices; Medical Device Reporting; Companion to Direct Final Rule posted as an ordinary proposed rule, saying nothing more than that it exists to finish the job through standard notice-and-comment if the direct final rule doesn’t survive its own comment window. Read on its own, the companion looks like a second, unrelated proposal on the same topic. It is not competing with the direct final rule. It is a spare engine, built and installed before anyone knows whether it will ever run.

One document is final unless someone objects. The other document does nothing at all unless the first one fails. The Federal Register prints both as ordinary rules, on the same day, with no field connecting them to each other.

What happens when someone actually objects

If FDA receives what its own procedure calls a significant adverse comment before the direct final rule’s comment period closes, the agency does not let the effective date arrive anyway. It publishes a notice of significant adverse comment and withdraws the direct final rule — within 30 days of the comment period’s close, by its own commitment. Every comment already filed against the withdrawn rule carries over automatically to the companion proposed rule, which becomes the live vehicle, and the action proceeds under ordinary notice-and-comment rulemaking from there. A subscriber who read the direct final rule the week it posted and moved on has no reason to know any of that happened, unless they were watching for the withdrawal notice too.

The practice

FDA Radar’s own Federal Register adapter reads the type field the Federal Register API returns for every document, and it files a document typed Rule as a Final Rule the same way whether it arrived as an ordinary final rule or a direct final rule still waiting on its own comment window. Nothing in that field, or in FDA Radar’s own categorization, links a direct final rule forward to the companion proposed rule sitting beside it, or backward from a later withdrawal notice to the rule it undid. Treating a device classification action as settled the day it posts as Rule skips a step FDA itself built in on purpose: reading the title for the words direct final rule, and if they’re there, checking back after the comment window closes before calling the matter done. Whether a specific pending action is worth that follow-up check is a judgment for whoever is tracking the file, against their own portfolio — this is a description of what the record can promise on the day it posts, regulatory intelligence and method, never a determination that any particular rule survived its own comment period. See what FDA Radar monitors and how often for how the Federal Register feed is built.

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