This joint resolution uses the Congressional Review Act (chapter 8 of title 5, U.S.C.) to declare the Federal Trade Commission’s rule titled “Premerger Notification; Reporting and Waiting Period Requirements” (89 Fed. Reg. 89216; Nov. 12, 2024) disapproved and places that rule beyond legal effect.
The resolution is concise: it names the specific Federal Register entry and states that the rule "shall have no force or effect."
That outcome would do more than strike a paragraph from the Federal Register. If enacted, the disapproval would erase the rule’s regulatory force and, by operation of the CRA, bar the FTC from issuing a replacement that is "substantially the same" without express statutory authorization.
The practical effects would be immediate for parties subject to premerger notification requirements, for the FTC’s regulatory toolkit, and for how agencies calibrate merger review going forward.
At a Glance
What It Does
The joint resolution declares null and void the FTC’s premerger notification rule published at 89 Fed. Reg. 89216 and states the rule "shall have no force or effect." It invokes the Congressional Review Act framework for statutory disapproval of agency rules.
Who It Affects
Entities required to comply with Hart‑Scott‑Rodino (HSR) premerger notification rules, antitrust and transactional counsel, the FTC as regulator, and counterpart enforcement bodies that coordinate on merger review will be directly affected. Market participants planning transactions may see changes to filing obligations and timing risk.
Why It Matters
A successful CRA disapproval wipes the rule from the regulatory code and prevents the agency from reissuing a substantially identical rule without new congressional authorization, making this a blunt long‑term constraint on agency rulemaking in the HSR/premerger space.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The resolution is short and surgical: it names the FTC rule by title and citation and states that Congress disapproves it under chapter 8 of title 5, which is the Congressional Review Act. The resolution’s operative text contains no carve-outs, savings clauses, or transitional provisions; it simply asserts that the named rule "shall have no force or effect." The bill therefore relies on the CRA’s established legal consequences rather than restating them.
Under the CRA, a successfully enacted disapproval resolution accomplishes three core outcomes: it nullifies the named rule as if it had never had legal effect; it requires that the agency submit a report of the rule to Congress and that the rule remain non‑operative; and it creates a statutory bar on reissuing the same or a substantially similar rule unless Congress later enacts new law authorizing that content. Those collateral effects are not spelled out in the short text of this joint resolution, but they are the predictable legal consequences if the resolution becomes law.For regulated parties and counsel, the immediate compliance question is binary: the rule either remains available for use by the FTC in enforcement and filing guidance, or it is removed and replaced by the prior regulatory baseline.
That shift changes both what filings are required and how the FTC may proceed administratively to address the policy goals the rule sought to meet. For the agency, the resolution would eliminate a rulemaking outcome after completion and limit the FTC’s near‑term regulatory options on the same subject unless Congress acts.Finally, the resolution raises implementation and litigation questions that are not answered in its text: how the FTC will adjust its enforcement posture, whether private parties will press courts over the resolution’s retroactive effects on pending actions, and how the agency might attempt a materially different rule to achieve similar ends without running afoul of the CRA’s prohibition on substantially identical replacements.
The Five Things You Need to Know
The resolution expressly disapproves the FTC’s rule titled "Premerger Notification; Reporting and Waiting Period Requirements," citing 89 Fed. Reg. 89216 (Nov. 12, 2024).
It states that the named rule "shall have no force or effect," which, if enacted, removes the rule from the body of operative federal regulation.
The disapproval is framed under chapter 8 of title 5, U.S.C. (the Congressional Review Act), triggering the CRA’s statutory bar on reissuing a substantially identical rule without new congressional authorization.
The resolution contains no transitional language or exceptions—its text does not address pending filings, ongoing investigations, or grandfathering of actions taken under the rule.
Enactment requires the standard legislative process for a joint resolution: passage by both chambers of Congress and presentment to the President; only then do CRA consequences attach.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Express disapproval of the FTC rule
This single paragraph identifies the rule by title and Federal Register citation and states that Congress disapproves it. The practical significance of that wording is that the resolution targets one discrete agency action rather than proposing amendments to statute or offering an alternative regulatory scheme. Because the resolution is limited to disapproval, it does not itself specify replacements, exceptions, or timing for unwinding regulatory changes.
Nullification: rule "shall have no force or effect"
The resolution’s operative sentence declares the rule devoid of legal force. Under established CRA doctrine, that language vacates the rule’s regulatory status and removes it from the Code of Federal Regulations. The resolution does not attempt to define retroactivity or address consequences for compliance steps already taken under the rule, leaving those issues to courts, agency guidance, or future legislation.
Citation and administrative record reference
By including the precise Federal Register citation and publication date, the resolution pins its scope to that published rule text. That specificity matters in any post‑enactment disputes about whether later or narrower FTC actions fall within the disapproval’s reach. It also focuses attention on the administrative record underlying the cited Federal Register notice, since challenges over whether a subsequent rule is "substantially the same" will hinge on textual and functional comparisons to that precise document.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Transaction parties seeking regulatory predictability: Corporations and private-equity firms that opposed the FTC’s changes gain the status quo ante for HSR filing obligations, avoiding any new reporting or timing burdens the rule would have imposed.
- Deal counsel and compliance teams: Legal and compliance advisers avoid a near‑term requirement to rewrite HSR checklists, compliance playbooks, and closing conditions to reflect the rule’s changes.
- Businesses that rely on existing waiting-period certainty: Firms with time‑sensitive transactions preserve previously understood timing exposure and do not face potentially extended waiting periods or altered filing triggers.
Who Bears the Cost
- Federal Trade Commission: The agency loses a finalized regulatory tool and the policy effects the rule would have delivered; it also expends political and administrative capital to respond and may need to restart a contested rulemaking.
- Competition advocates and parties favoring stricter merger oversight: Groups and state enforcers that backed the FTC rule face the cost of reduced regulatory authority and may need to pursue litigation or legislative fixes to achieve similar outcomes.
- Market participants that sought clearer notice: Companies that would have benefited from any clarified standards or thresholds in the rule now face continued uncertainty until the agency or Congress acts, potentially increasing transaction risk and compliance costs.
Key Issues
The Core Tension
The central dilemma is between Congress using a blunt statutory tool to check an agency’s regulatory output and the agency’s need to adapt technical rules to changing markets; rescission resolves a political objection to a discrete rule but may also block necessary regulatory updates or drive the agency to less transparent means of achieving similar policy goals.
The resolution’s brevity creates implementation strains. It disapproves and nullifies, but it does not address pending matters—no language preserves or cancels filings made under the rule, nor does it specify whether investigations commenced under the rule continue.
That silence creates litigation risk: affected parties may sue to determine whether enforcement actions based on the now‑disapproved text are valid, and courts will face threshold questions about retroactivity and reliance interests.
Another unresolved question is the scope of the CRA bar on reissuing a "substantially similar" rule. That standard is fact‑intensive and will invite strategic behavior: the FTC can attempt to achieve similar policy goals through enforcement priorities, guidance, or a materially different rule, but drawing the line between permissible change and prohibited duplication will likely end up before courts.
Finally, because the CRA permanently restricts agencies only via the narrow mechanism of congressional disapproval, significant policy shifts that the rule sought to implement may require affirmative congressional action—an often slower and more politically fraught path than agency rulemaking.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.