Enactment is not implementation. A public law is a set of instructions; implementation is the machinery that turns those instructions into programs â the rulemakings run under the Administrative Procedure Act, the guidance documents, the OIRA review queue, the appropriations and OMB apportionments that fund the work, and the statutory deadlines that start running the moment the ink dries. This is the pipeline that House and Senate staff draft, that agencies execute, and that everyone else waits on. What follows is the sequence: what a statute actually says to an agency, how a proposed rule becomes a final one, where the Congressional Review Act sits in the chain, why an authorized program without an appropriation is a paper program, and what happens when the calendar wins. If you draft statutes, comment on rules, or wait impatiently on an agency, this is the order of operations.

What the Statute Actually Says to the Agency
The President signs. The enrolled bill receives a public law number, is printed as a slip law, and is eventually codified into the U.S. Code. A single act can amend a dozen titles â an infrastructure law will touch transportation, environment, energy, and tax in one document. The first implementation question is always the same: what does this law require, by when, and with what money.
Every implementation statute carries a standard inventory. Effective dates, sometimes phased across years. Rulemaking mandates. Report requirements to Congress. Authorizations of appropriations. Waiver and exemption authority. Severability clauses. The operative words matter more than the topic sentences. âShall promulgateâ creates a duty. âMay issueâ creates an option. âNot later than 180 days after the date of enactmentâ creates a clock, and the clock starts at signature â not at publication, not at the agencyâs convenience.
A typical mandate reads: Not later than 180 days after the date of enactment, the Secretary shall promulgate regulations to carry out this section. One sentence, three consequences: a legal duty, a running deadline, and standing for someone to sue later. Agencies triage accordingly. Mandatory and dated work comes first. Discretionary and undated work waits.
The Implementation Sequence, Step by Step
The sequence runs in five steps: interpretation, OIRA review, proposal, final rule, and the congressional review window. Each step has its own clock, and the clocks rarely align with the statutory deadline.
Step 1: Interpret, Plan, and List the Work
The program office, the general counsel, and the budget shop read the statute together â rarely in full agreement, always in writing. Since the Supreme Courtâs 2024 decision in Loper Bright Enterprises v. Raimondo, courts no longer defer to an agencyâs reading of an ambiguous statute, so agencies now draft with the statutory text pinned to the wall. The text survives review; the agencyâs confidence in its own reading does not. Work in progress gets listed in the Unified Agenda, the public face of the regulatory plan OIRA maintains. If a deadline is running, a project plan follows. If the deadline is short, the project plan is fiction.
Step 2: OIRA Review, Before the Public Sees Anything
Under Executive Order 12866, rules deemed significant â major economic effect, adverse effects the agency would rather not quantify, inconsistency with another agencyâs priorities, novel legal or policy questions â go to the Office of Information and Regulatory Affairs before publication. OIRA coordinates interagency comment. Its meetings are logged and public. The review clock generally runs 90 days, with extensions available and withdrawal always an option. The independent regulatory commissions â the Federal Reserve, the SEC, the FTC, the FCC, the NLRB â sit outside this process, which is why their calendars behave differently from the executive departmentsâ.
Step 3: The Proposed Rule and the Comment Period
The Notice of Proposed Rulemaking is published in the Federal Register, and the Federal Registerâs reader documentation is the fastest orientation to what a notice actually contains. The APA requires a reasonable comment opportunity. Thirty days is the informal floor, 60 is the norm, and major rules often get 90. The docket fills. The agency must address significant issues raised in the comments and show that the final rule is a logical outgrowth of the proposal. If the final rule surprises the commenters, the commenters can demand a second round â and courts sometimes agree.
Step 4: Final Rule, Effective Dates, and the 30-Day Rule
Under 5 U.S.C. § 553(d), a substantive rule cannot take effect until 30 days after publication. A rule that grants an exemption or relieves a restriction is excepted â it may take effect on publication. So may a rule issued on a good-cause finding. The asymmetry is deliberate: rules that lift burdens bite faster than rules that add them. Emergencies get interim final rules, effective on publication, with comments accepted after the fact.
Now run the hypothetical 180-day deadline against the real clock: 45 days to draft, 60 days at OIRA, 60 days of comments, 60 more days to analyze and clear the final rule. That is 225 days of scheduled work against a 180-day clock, and the schedule assumes nothing slips. Congress writes ânot later than 180 daysâ the way other people write New Yearâs resolutions: sincerely, and without a calendar.
Step 5: The Congressional Review Act Window
Every final rule goes to Congress and to GAO. Major rules â under the CRAâs own definition, $100 million or more in annual economic effect â cannot take effect until 60 days after publication and submission. A joint resolution of disapproval moves on expedited procedures: a petition of 30 members forces a House committeeâs hand, a Senate vote is guaranteed floor time, and the resolution still needs the Presidentâs signature or a veto override. Successful disapprovals are rare and concentrated in the opening months of new Congresses. The lookback provision hands late-session rules a fresh 60-day window in the next Congress. A rule finalized in December can be killed by a Congress seated in January. Agencies know this. It explains the shape of every November regulatory calendar.

Money: Authorization Is Not Appropriation
An authorization creates a program and, usually, an account. It moves no dollars. The money travels a separate track. The budget resolution sets 302(a) allocations to the Appropriations Committees. Each committee divides its allocation among subcommittees through 302(b) suballocations. The subcommittees draft the bills, the bills pass both chambers, and the President signs. Then OMB apportions the enacted funds to the agencies under Circular A-11, agencies allot internally, and obligations begin. The Antideficiency Act (31 U.S.C. § 1341) bars obligations beyond the appropriation; 31 U.S.C. § 1517 bars obligations beyond the apportionment. Career staff treat both as tripwires, because they are.
The consequences are structural. A program can be authorized for five years and funded for one. Such sums as may be necessary is an authorization formula, not a bank balance. Funds arrive as one-year, multi-year, or no-year money, and the distinction controls spending pace. Hiring, grant notices, and contracts all sit downstream of apportionment â which is how a signed statute can produce a program office that cannot yet hire. An authorization without an appropriation is a promise, not a check.
Not Everything Goes Through Notice-and-Comment
Rules get the attention, but statutes are also implemented through quieter instruments. Guidance documents â interpretive rules and general statements of policy â are exempt from notice-and-comment under 5 U.S.C. § 553(b)(A). Guidance binds neither courts nor the public. It binds agency staff until someone above them says otherwise. That exemption is among the most litigated stretches in administrative law, because a binding rule dressed as guidance is a recurring litigation theory, whichever direction the challenge comes from.
Other channels do the work without rulemaking at all. Adjudication applies the statute case by case, through licensing, permitting, and benefits decisions. Direct administration builds forms, systems, and staff. Waivers excuse compliance one grant at a time. Emergency authorities let agencies act first and paper the file later â OSHAâs emergency temporary standard is the canonical example: effective on issuance, litigation to follow.
When the Agency Misses the Deadline
The Food Safety Modernization Act of 2011 set deadlines for seven foundational rules. FDA missed most of them by years. Citizen suits followed, and courts imposed schedules. That is the standard arc. Under 5 U.S.C. § 706(1), a court shall compel agency action unreasonably delayed, but Norton v. Southern Utah Wilderness Alliance (2004) confines relief to discrete acts the agency is legally required to perform â not generalized foot-dragging. The pattern holds across agencies: they rarely lose outright; they lose control of the calendar. A court-ordered schedule is a worse master than a self-set one.
What to Watch While a Law Is Being Implemented

Implementation is watchable if you know where to stand. Read the daily Federal Register table of contents for your agencies. Track the Unified Agenda entry and its status codes. Read the OIRA meeting logs for who is talking to whom before the rule is final. Read GAOâs implementation reports and the appropriations report language, which guides without binding. Track disapproval resolutions on Congress.gov. Each source answers a different question: what moved, what is planned, who intervened, what Congress is doing about it, and what the appropriators actually intend.
This is also where this column lives. A standing feature â call it Deadline Watch â pairs each major statute with its rulemaking mandates, the running clocks, and the current status. Send a statute you want tracked; the queue is open.
Frequently Asked Questions
How long does it take a federal agency to implement a new law?
For a major statute with a rulemaking spine, 18 to 36 months from enactment to a functioning program is the realistic band. Self-executing provisions bind on their own effective dates. Rules add the rest, and deadline litigation can push a single rulemaking past five years. The Food Safety Modernization Act is the cautionary benchmark: enacted in 2011, its foundational rules were still arriving years later.
Can a law take effect before agencies finish writing its rules?
Yes, in part. Rates, penalties, and eligibility changes often operate directly on their statutory dates with no rulemaking at all. Provisions that condition operation on regulation do nothing until the rule issues. Read the effective-date section and the rulemaking section together; they are drafted by different hands, and they do not always agree.
Can Congress block a rule after it is finalized?
Yes, three ways. The Congressional Review Act allows an expedited joint resolution of disapproval, subject to the Presidentâs signature or a veto override. Appropriations riders can bar funds for implementation. And Congress can amend the statute itself. The CRA lookback gives a new Congress a fresh window for rules issued late in the prior session.
What is the difference between a rule and a guidance document?
A legislative rule carries the force of law and generally requires notice and comment before it binds. Guidance states the agencyâs interpretation or enforcement posture; it binds neither courts nor the public, only agency staff, and only until the agency changes its mind. The line between the two is contested, and crossing it is a recurring litigation theory.
What happens when an agency misses a statutory rulemaking deadline?
The deadline does not self-execute, but it creates litigation exposure. Under 5 U.S.C. § 706(1), courts can compel agency action unreasonably delayed, though Norton v. Southern Utah Wilderness Alliance limits relief to discrete, legally required acts. Agencies rarely lose outright; they negotiate schedules they no longer control.
The Order of Operations, Condensed
Trigger, then interpretation, then OIRA, then proposal, then comments, then final rule, then the CRA window, then appropriation, then apportionment, then operation. Ten links in the chain, and every one of them is a place it can break. Enactment starts the machine. It does not run it. Watch the clocks â everyone inside the machine is watching them too.