How Federal Agencies Actually Implement New Laws: From Signature to Obligated Dollar

…

“}

I could pretty-print with newlines between keys — that’s still valid JSON. But “single line string” for html — the html value itself must have no newlines. I’ll put the whole JSON compactly or with minimal formatting. I’ll do:

{
“title”: “…”,
“html”: “…”
}

Both fine. I’ll go with compact single-line-ish but the html is long. Let me format with the two keys on separate lines for readability; html value on one line.

Let me finalize the exact text and write it out. Also double-check “31 U.S.C. 1341–1342” uses en dash. And em dashes throughout use —.

One more accuracy check: “5 U.S.C. 553(b)(3)” — good cause exception is 553(b)(3). Yes.

“5 U.S.C. 706(2)(A)” — arbitrary and capricious. Yes.

“31 U.S.C. 1301(a)” — purpose statute. Yes.

“31 U.S.C. 1502” — bona fide needs. Yes.

“31 U.S.C. 1342” — apportionment excess. I stated “1342 bars obligations in excess of an apportionment” — § 1342 is “Prohibition on obligations or expenditures in excess of apportionments”… Actually let me double check: I recall 31 U.S.C. § 1342: “An officer or employee of the United States Government or of the District of Columbia government may not accept voluntary services… or make or authorize an obligation or expenditure in excess of an apportionment…” Hmm, that might be § 1342 combining voluntary services and apportionment excess. Actually:
– § 1341: Limitations on expending and obligating amounts (in excess or advance of appropriations).
– § 1342: Prohibition on obligations or expenditures in excess of apportionments and reapportionments…

I believe § 1342 reads: “An officer or employee of the United States Government or of the District of Columbia government may not make or authorize an obligation or expenditure in excess of an apportionment or in excess of the amount permitted by regulations prescribed under section 1512(a) of this title.” Hmm, and voluntary services is § 1342? Let me think. The Antideficiency Act provisions: 31 U.S.C. 1341 (obligations in excess/advance of appropriations), 1342 (voluntary services prohibition AND… no). Actually:
– 31 U.S.C. § 1341: “An officer or employee of the United States Government… may not make or authorize an expenditure or obligation exceeding an amount available in an appropriation or fund…”
– 31 U.S.C. § 1342: “An officer or employee of the United States Government or of the District of Columbia government may not accept voluntary services for the United States or the District of Columbia government…” Wait, that’s § 1342? Yes! § 1342 is the voluntary services prohibition. And obligations in excess of apportionment: that’s also in § 1341? Hmm.

Let me recall more carefully. The Antideficiency Act:
– 31 U.S.C. 1341: (a) Prohibition — expenditures/obligations in excess of appropriation, in advance of appropriation, before apportionment (subsection (b): “may not… involve the Government in any obligation… in advance of appropriations… before an apportionment…”). Actually 1341(b) covers “in excess of the amount apportioned” — I think 1341(b)(2)(A)…

Hmm, to be safe: 1341 covers obligations in excess of or in advance of appropriations AND obligations in excess of apportionments/allocations (1341(b)). § 1342 covers voluntary services. So my FAQ statement “31 U.S.C. 1342 bars obligations in excess of an apportionment” would be wrong — it’s § 1341(b) that covers apportionments, and § 1342 is voluntary services.

Let me fix: In Step 2 p1, “under the Antideficiency Act, 31 U.S.C. 1341” — just cite 1341. In FAQ 2: “The Antideficiency Act, 31 U.S.C. 1341, bars obligations in excess or advance of an appropriation, and bars obligations in excess of an apportionment before OMB releases the funds.” Simplify: “No. The Antideficiency Act, 31 U.S.C. 1341, bars obligations in excess of an appropriation, in advance of one, or in excess of OMB’s apportionment.” That’s accurate — 1341(b) covers apportionment excess. Good, drop 1342.

In Step 2 p1: “OMB then apportions that authority under the Antideficiency Act, 31 U.S.C. 1341, on the schedule mechanics in Circular A-11.” Good.

Also “31 U.S.C. 1512” is the apportionment authority (apportionments of appropriations). Could cite 1512(a): OMB apportionment requirement. Actually 31 U.S.C. 1512 is “Apportionments of appropriations” — agencies must submit apportionment requests, OMB apportions. The prohibition on obligating in excess of apportionment is 1341(b). I’ll keep it simple with 1341 and Circular A-11.

Also “31 U.S.C. 1502” — yes, bona fide needs. Good.

One more: “Executive Order 12866” — OIRA review of significant regulatory actions, default 90-day review. Correct.

CRA: 5 U.S.C. 801 — submission to Congress and GAO; disapproval resolution; ~60 legislative days. Correct.

TRAC cite: Telecommunications Research & Action Center v. FCC, 750 F.2d 70 (D.C. Cir. 1984). I’ll cite as (D.C. Cir. 1984). Fine.

Loper Bright Enterprises v. Raimondo, 603 U.S. 369 (2024) — retired Chevron. Correct.

Now also confirm: “effective no earlier than 30 days after publication” — 5 U.S.C. 553(d): substantive rules effective not less than 30 days after publication (exceptions exist). “no earlier than 30 days” ≈ “not less than 30 days”. Good.

Also, one subtlety: “comment period — 30 to 60 days is the working range”. Fine.

OK. Also I say “Overtime and stale account structures do the rest” — hmm, “Overtime”? I removed that; final: “New starts stall. Stale account structures do the rest.” Fine — CRs often prohibit new starts. Good.

Let me also reconsider the phrase “budget shop” — insider jargon, fits persona. Good.

“un-published rule” — I wrote “unpublished rule — vacated for skipped procedure”. “Unpublished” might be odd; better “a rule that skipped notice and comment — vacated for skipped procedure”. Let me rephrase: “risks a court treating the document as a legislative rule issued without notice and comment, and vacating it for that reason.” Cleaner. I’ll write: “and an agency that uses guidance to impose new obligations risks a court treating the document as a rule issued without notice and comment — vacated for skipped procedure.” Good.

Also, ensure no word “validate/validation”. None.

Also the rule “Preserve … headings, FAQ, links, and image tags” — draft is empty, so nothing to preserve; I construct fresh but consistent with the topic.

Final JSON output. Let me write it now, carefully, as one continuous html string.

Also note: “Use single quotes for attributes” — done for href, src, alt, loading.

Also should figcaption exist? “Keep exactly 3 Pexels image embeds with alt text” — embeds with alt text required; figcaption optional but nice. Keep.

Final word count concern: ~1550 — good.

Write the response: only JSON. Let me produce it.{“title”:”How Federal Agencies Actually Implement New Laws: From Signature to Obligated Dollar”,”html”:”

The President signs. The cameras leave. Nothing has been implemented yet.

A public law is a set of instructions, not an operating program. Implementation is the sequence federal agencies run to carry a statute out: read the text, find the money, write the rules, stand up operations, report the results. This piece walks each step in order, because the order is not optional. Skip a step and the program does not run. For what happens before the signature, see our walkthrough of how a bill becomes law.

Step 1: Reading the Statute

Trigger: enactment. Mechanism: the agency’s general counsel, program offices, and budget shop read the new public law against the U.S. Code, the committee reports, and the CBO cost estimate. Outcome: an implementation plan with named owners and dated deadlines.

Three sections of the text control everything downstream. The effective date says when duties attach — on enactment, on a date certain, or only after a rule issues or an appropriation is enacted. The delegation says whether the agency must act: shall starts a clock, may leaves a choice. The definitions say whom the law covers. Everything else — hiring plans, budget requests, the rulemaking calendar — inherits from those three.

Agencies do not read alone. Committee reports and the cost estimate supply interpretive context, and litigation tests the reading. Since Loper Bright Enterprises v. Raimondo (2024) retired Chevron deference, courts exercise independent judgment on statutory meaning instead of deferring to the agency’s own. A vague delegation is now a litigable delegation. Drafting clarity stopped being a courtesy.

Step 2: Finding the Money

Trigger: the authorization becomes law. Mechanism: the budget resolution sets a 302(a) allocation for the Appropriations Committee, the committee divides it into 302(b) suballocations — one per subcommittee — and an appropriations act provides budget authority. OMB then apportions that authority under the Antideficiency Act, 31 U.S.C. 1341, on the schedule mechanics in Circular A-11. Outcome: a program office holding an apportionment can obligate. A program office without one cannot. That sentence is the whole appropriations system.

The distinction people miss: an authorization is permission, an appropriation is money. An authorized program with no appropriation exists on paper. Mandatory spending is the exception — it obligates by formula, without an annual act — but discretionary programs wait for the subcommittee, the floor, and OMB. For the gatekeeping math, see our explainer on 302(b) suballocations.

Three limits govern every dollar once appropriated. Purpose: 31 U.S.C. 1301(a) confines spending to the objects Congress funded. Time: the bona fide needs rule, grounded in 31 U.S.C. 1502, ties the money to the fiscal year for which it was appropriated. Amount: no obligation beyond the appropriation, in advance of it, or in excess of apportionment. GAO’s Principles of Federal Appropriations Law — the Red Book — is the operating manual, and it runs four volumes for a reason.

When the appropriations calendar slips, continuing resolutions keep agencies open at prior-year levels, usually with the same purposes. New starts stall. Stale account structures do the rest.

Step 3: Writing the Rules

Some provisions self-execute — rates, deadlines, direct benefits. Most need machinery. Trigger: the statute orders a rule, or the agency decides it needs one. Mechanism: the Administrative Procedure Act, 5 U.S.C. 553. The agency publishes a notice of proposed rulemaking in the Federal Register, the public gets a comment period — 30 to 60 days is the working range — and the agency considers the comments, then publishes a final rule with a “concise general statement” of basis and purpose. Outcome: a rule with the force of law, effective no earlier than 30 days after publication, codified in the Code of Federal Regulations.

Notice-and-comment is not decoration. A court will vacate a rule that rests on findings the docket does not support, that ignores significant comments, or that switches rationale mid-course without explanation. The comment file is the record. Agencies that treat it as an inbox learn this in litigation.

Two shortcuts exist, and both cost something. Good cause under 5 U.S.C. 553(b)(3) waives notice and comment when procedures would be impracticable, unnecessary, or contrary to the public interest — a standard courts read narrowly. The direct final rule, reserved for noncontroversial technical matters, takes effect unless an adverse comment arrives; one objection sends the agency back to proposed-rule stage.

Before a significant rule publishes, OIRA reviews the draft under Executive Order 12866; the default window is 90 days, the meetings are logged, and the paperwork is public. After publication, the Congressional Review Act, 5 U.S.C. 801, opens a disapproval window — a joint resolution, Senate fast-track, no filibuster. Our Congressional Review Act explainer covers the arithmetic. A rule that clears both gates is still reviewable in court under the APA’s arbitrary-and-capricious standard, 5 U.S.C. 706(2)(A).

Step 4: Standing Up Operations

Rules are the visible work. Operations are the actual work. Agencies rewrite delegations of authority so someone below the Secretary can sign. They build forms, stand up reporting systems, post notices of funding opportunity, and hire — slowly, because competitive service hiring has its own clock. They issue guidance to interpret the rule for staff and the public.

Guidance deserves a caution. It does not bind the public the way a rule does, and an agency that uses guidance to impose new obligations risks a court treating the document as a rule issued without notice and comment — vacated for skipped procedure. Guidance explains. Rules bind. Agencies that reverse the two lose cases.

Then the reporting starts: to Congress, to OMB, to the inspector general. Every statutory deadline goes into a tracker. Miss one and the standard sequence follows — letters, hearings, and sometimes a deadline suit under the APA’s unreasonable-delay doctrine. Courts will order an agency to act. They will not write the rule for it.

Where Implementation Breaks

Four failure modes account for most of the wreckage. The appropriation never comes, and the program exists in statute and nowhere else. The rule is vacated for inadequate reasoning, and the clock resets. The CRA resolution passes, the rule dies, and the agency may not issue a substantially similar one without new authority. Or the deadline passes, the suit is filed, and the negotiated schedule buys time at the cost of credibility.

Frequently Asked Questions

How long does it take an agency to implement a new law?

Self-executing provisions take effect on their effective date. Provisions that require rulemaking commonly run one to three years from proposed rule to effective final rule, longer with litigation. Provisions that require appropriations move at the appropriations calendar’s pace — which is to say, slower.

Can an agency spend before Congress appropriates?

No. The Antideficiency Act, 31 U.S.C. 1341, bars obligations in excess of an appropriation, in advance of one, or in excess of OMB’s apportionment. Violations are reported to the President and Congress, and responsible officials face discipline. This is one of the few rules in federal administration with teeth.

What is the difference between an authorization and an appropriation?

An authorization establishes or continues a program and, usually, a spending ceiling. An appropriation provides the budget authority. An apportionment — OMB’s release of that authority over time — is the last gate before obligation. Three doors, three keys.

Can Congress stop a rule after it is finalized?

Yes, within the Congressional Review Act window, by joint resolution of disapproval. The window runs roughly 60 legislative days from the rule’s submission or later publication, so a rule issued late in a session can stay vulnerable well into the next one.

What happens if an agency misses a statutory deadline?

Nothing, until someone sues. Courts apply the unreasonable-delay factors from Telecommunications Research & Action Center v. FCC (D.C. Cir. 1984) and usually order a schedule, not a rule. The agency writes the rule either way. The suit only decides when.

The Chain, Once More

Read the text, find the money, write the rules, run the program, file the reports. Each link checks the one before it, and every link holds a veto. I have watched a well-drafted law starve waiting for a suballocation and a mediocre one run on time because its committee report and its appropriation were written by people who understood the machinery. Implementation is where a law becomes real — or quietly fails to. The signing ceremony is the easy part.