Four Dates Separate a Proposed Rule From the Cash Flow It Changes

A headline says a regulator has moved, and the screen reacts inside a second. Behind that headline there is a document, and the document carries a publication date, a comment deadline, an effective date, and a docket number. Those are four different dates. The headline collapses them into one.

The gap between them is where most of the trade lives. A proposed rule is not a rule. A final rule is not a rule in force. A rule in force can still have its date moved by the agency that wrote it or by a court reviewing it. Each of those transitions is a separate event with a published date, and each one can be checked before a position is sized against it.

This is not an argument that regulation fails to reach revenue. It is an argument that the date on which it reaches revenue is printed somewhere, and is usually much later than the date the story runs.

The Pipeline Has Named Stages, and Every One of Them Is Dated

The general schedule comes from the Administrative Procedure Act. Under 5 U.S.C. 553(b), general notice of proposed rulemaking is published in the Federal Register, and that notice must state the time, place and nature of the proceedings, reference the legal authority under which the rule is proposed, and set out either the terms of the proposed rule or a description of the subjects and issues involved.

Under 553(c), the agency must then give interested persons an opportunity to participate by submitting written data, views or arguments. When it issues the final rule, it must incorporate in it a concise general statement of the rule's basis and purpose. That statement is the record of what the comments changed, which is the reason the final text is not reliably the proposed text.

Two stages sit in front of all of this and are visible earlier. Executive Order 12866 directs each agency to forward its Regulatory Plan to the Office of Information and Regulatory Affairs by June 1 of each year, and provides that the plans are published annually in the October publication of the Unified Regulatory Agenda. The same order sets the review clock: under Section 6(b)(2)(B), review of a draft regulatory action runs up to 90 calendar days after submission, or 45 days where OIRA has previously reviewed the information and there has been no material change. Section 6(b)(2)(C) allows that review to be extended once by no more than 30 calendar days on the written approval of the Director, and again at the request of the agency head.

Section 6(a)(1) of the same order provides that agencies should in most cases include a comment period of not less than 60 days.

Read as a sequence, the ordering matters more than any single number. By the time a proposal is published and a headline is written, an agency plan and an interagency review have already run their course. The information is not new. It is newly formatted.

Publication Day Is Not Compliance Day

The clearest single line in the statute is 5 U.S.C. 553(d): the required publication or service of a substantive rule shall be made not less than 30 days before its effective date. The subsection carries its own exceptions, for rules granting or recognising an exemption or relieving a restriction, for interpretative rules and statements of policy, and for any rule for which the agency finds and publishes good cause.

For larger rules a second clock runs on top of that one. Under 5 U.S.C. 801(a)(1), before a rule can take effect the agency must submit to each House of Congress and to the Comptroller General a copy of the rule, a concise general statement including whether it is a major rule, and the proposed effective date.

Under 801(a)(3), a major rule may not take effect until 60 days after the later of two dates: the date Congress receives that report, and the date the rule is published in the Federal Register. A major rule published on 1 March whose report reaches Congress the same day cannot take effect before 30 April, whatever the coverage says on 1 March.

What counts as major is defined in 5 U.S.C. 804(2). It is a rule that the Administrator of OIRA finds has resulted in or is likely to result in an annual effect on the economy of $100,000,000 or more, a major increase in costs or prices for consumers or individual industries or government agencies, or significant adverse effects on competition, employment, investment, productivity or innovation. The threshold is worth holding onto, because it inverts the intuition. The rules large enough to move a revenue line are the rules that carry the additional 60-day floor. The small ones move faster.

The Review Window Can Reopen After It Looks Closed

The same chapter creates a window in which Congress can act. Under 5 U.S.C. 802(a), a joint resolution of disapproval may be introduced in a period that begins when Congress receives the report and ends 60 days later, excluding days on which either House is adjourned for more than three days during a session. Those are session days, not calendar days, which means the window on a wall calendar is longer than 60 days and its end is not fixed in advance.

Inside that window the procedure is unusually fast by legislative standards. Under 802(c), if the committee has not reported the resolution at the end of 20 calendar days after the submission or publication date, a petition signed by 30 Senators discharges it. Under 802(d)(2), Senate debate on the resolution is limited to not more than 10 hours, divided equally.

The consequence of enactment is not a delay. Under 801(b)(2), a rule that does not take effect may not be reissued in substantially the same form, and a new rule that is substantially the same may not be issued, unless specifically authorised by a law enacted after the date of the joint resolution. That is a durable outcome rather than a postponement, and it is the one branch in this structure that removes a rule rather than moving it.

There is also a provision that quietly defeats calendar arithmetic. Under 801(d), where the report is submitted within 60 session days in the Senate or 60 legislative days in the House before Congress adjourns a session, the rule is treated as though it had been published on the 15th session day, or 15th legislative day, after the succeeding session first convenes. A rule finalised late in a session can therefore have its review clock restart months later, in front of a differently composed Congress. Any claim that the review window has closed is a claim that needs a calendar check rather than an assumption.

An Agency or a Court Can Move the Date After It Is Printed

5 U.S.C. 705 is one sentence containing two separate powers. When an agency finds that justice so requires, it may postpone the effective date of action taken by it, pending judicial review. And on such conditions as may be required, and to the extent necessary to prevent irreparable injury, the reviewing court may issue all necessary and appropriate process to postpone the effective date of an agency action or to preserve status or rights pending conclusion of the review proceedings.

Neither power requires the rule to be rewritten. The text can stand while the date moves, and the date can move from either direction, which is why a printed effective date behaves more like a scheduled event than a settled one.

For position management, the distinction between the branches is the part that carries weight. A rule removed under 801(b)(2) and a rule postponed under 705 have very different half-lives, and a position built on the assumption that a rule is gone should be able to say which of the two happened.

How Much Traffic Moves Through the Pipe

The volumes are worth seeing because they cut against the way rule changes are usually narrated. In each of the five years shown, final rules published outnumbered proposed rules published: 3,257 against 2,094 in 2021, and 2,441 against 1,498 in 2025. Both series fell over the window, but the ordering held every year.

The reason is in the exceptions. 553(b) does not require notice for interpretative rules, general statements of policy, or rules of agency organisation, procedure or practice, and it allows an agency to dispense with notice when it finds for good cause that notice is impracticable, unnecessary or contrary to the public interest. A substantial share of published final rules therefore never had a proposal stage at all.

Two things follow. The absence of a visible proposal is not evidence that no rule is coming, so a screen built only on proposals will miss a class of actions entirely. And raw volume carries almost no signal: thousands of final rules are published each year, while the ones capable of reaching a revenue line are the subset designated major under 804(2). That designation is stated in the report the agency submits under 801(a)(1), which makes it the cheapest available filter and the first one worth applying.

What the Tape Can Be Pricing at Each Stage

The stages differ in what is known at each one, and the difference is not subtle.

• Agenda stage. A subject exists and an agency intends to act. There is no text. Any repricing here is a position on the existence of future text.
• Proposed rule. Text exists and is public, and nothing in it binds anyone. Because 553(c) requires the agency to consider the submissions it receives, the final terms can differ from the proposed terms, and in most cases the comment period alone runs not less than 60 days.
• Final rule. Text is fixed and an effective date is printed. The date remains movable through 705 or the disapproval process.
• Effective date. Obligations begin, subject to any phase-in written into the rule itself.

The common failure is not that traders react to headlines. It is that a position sized for the proposal stage gets carried as though it were the effective-date stage. The elapsed time between the two is not dead time. It is a run of scheduled, checkable dates on which the original thesis can be re-tested at no cost.

A second gap sits underneath the first one. The cost a rule imposes on a firm is not the change it makes to that firm's revenue. Whether a compliance cost reaches the revenue line depends on pass-through, on substitution by customers, on whether competitors face the same requirement, and on the phase-in schedule written into the rule text. None of that is in the headline. The phase-in schedule is usually in the DATES section of the Federal Register document, which is one click from the article that omitted it.

What Would Invalidate This

• The exceptions can swallow the timeline. Both 553(b) and 553(d) contain good-cause exceptions. Where an agency finds and publishes good cause, notice can be skipped and the 30-day delay dispensed with, and a rule can be published and effective on the same day. If the document at issue invokes one of those findings, the pipeline argument does not apply to it.
• The 60-day floor is for major rules. The 801(a)(3) clock attaches to rules designated major under 804(2). A rule below that threshold takes effect as otherwise provided by law, and the extra window is simply not there.
• Agency-specific statutes override the default. The APA schedule is a default. Many actions are issued under statutes carrying their own deadlines, and a sector rule can be on a timetable that has nothing to do with the sequence described here. The schedule that governs is the one cited in the document.
• Correct anticipation removes the later moves. If participants price the final outcome at the proposal stage and are right about it, the subsequent dates produce no additional repricing. Pipeline length is an argument about when information becomes certain. It is not an argument that price must move at each date.
• Economic response can precede legal obligation. A proposed rule can change behaviour long before it is final, through deferred capital spending, renegotiated contracts or repositioned inventory. Those effects are real and they occur early. The claim here is narrow: the legal obligation begins on the effective date, not that nothing happens before it.
• Exchange and self-regulatory rules are a different pipeline. Rule filings by self-regulatory organisations run under the Exchange Act rather than the general schedule set out above. That process was not examined for this piece, and no claim is made here about its timetable. Anyone trading around an exchange rule change should read that process directly rather than assume these dates transfer.

Concrete Framework

1. Find the document, not the article. Every Federal Register document carries a document number and a publication date, and rules carry an effective date field. The record also carries docket identifiers, regulation identification numbers and a regulations.gov link, which together are the tracking key for the whole proceeding rather than for one story.
2. Write down four dates before sizing anything. Publication date of the proposal, close of the comment period, publication date of the final rule, and effective date. If any of the four is unknown, that is the position's real uncertainty, and it is knowable.
3. Read the DATES section in full. Compliance dates and phase-in dates are frequently later than the effective date and frequently staggered. A single effective date in a headline often hides a schedule.
4. Check major-rule status. The report submitted under 801(a)(1) states whether the agency treats the rule as major. If it does, apply the 801(a)(3) 60-day floor measured from the later of congressional receipt and Federal Register publication.
5. Check whether an exception was invoked. Search the document for a good-cause finding under 553(b) or 553(d). If one is present, the delay assumptions collapse and the timeline should be rebuilt from the document's own text.
6. Check the session calendar before assuming the window closed. If the report reached Congress within 60 session or legislative days of an adjournment, 801(d) restarts the clock in the following session.
7. Separate the cost line from the revenue line. Write down the pass-through assumption explicitly, note whether the requirement is industry-wide or firm-specific, and mark which phase-in date the estimate depends on.
8. Set a review date rather than a price target. Put the next scheduled date from step 2 in the calendar and re-test the thesis on that date. If the thesis has not survived to the effective date, the position should not either.

None of this predicts direction, and none of it needs to. It replaces a single ambiguous event with a short list of dated ones, each of which can be verified in a public document before capital is committed to it.