Logo
U.S. Constitution

Authorizations vs Appropriations

April 10, 2026by Eleanor Stratton

People talk about “Congress funding” something as if it is one vote, one bill, one clean yes or no.

But in Washington, the power of the purse usually works like a two-key system. One key says, “This program may exist.” The other says, “This program may spend money.” If you only have one of those keys, the lights still do not turn on.

There is an important caveat up front: Congress can sometimes fund activities even when an authorization is lapsed or missing, and agencies can sometimes keep operating using prior-year money, multi-year or no-year funds, user fees, trust funds, revolving funds, or other budget authority already on the books. Still, for the typical discretionary program people argue about every fall, the two-step structure is the difference between a press release and a functioning operation.

That split is not a trivia fact. It is the reason you can hear that a program is “authorized” and still watch it limp along without new funding. It is also why budget fights can spiral into continuing resolutions and shutdown showdowns, even when everyone claims they “support” the same agencies.

A congressional hearing room in Washington, DC during a House Appropriations Committee meeting, with lawmakers seated at a dais and staff at tables in front, news photography style

Join the Discussion

The constitutional anchor: Congress holds the purse

The Constitution does not micromanage the budget process, but it does set the core rule that makes the whole system possible.

Article I gives Congress the power to raise revenue and spend it, and the Appropriations Clause adds a hard stop: “No Money shall be drawn from the Treasury, but in Consequence of Appropriations made by Law.” (Article I, Section 9, Clause 7.)

That sentence is the guardrail. Agencies can have missions, personnel, regulations, and legal authority. But without an appropriation or other budget authority enacted by law, they do not have permission to draw money from the Treasury to carry those missions out.

What an authorization does

An authorization is Congress creating, continuing, or modifying a federal program or agency, and setting the terms under which it operates.

Authorizations are the blueprint

Authorization laws commonly do things like:

  • Create a program or agency (or reauthorize one that is expiring).
  • Define goals and eligible activities.
  • Set standards, oversight requirements, reporting rules, and guardrails.
  • Authorize appropriations, meaning they recommend or permit funding up to a level, often for a set number of years.

That last bullet is where many people get confused. An authorization can say “$X is authorized to be appropriated.” That is permission, not payment.

In other words: authorizations often tell appropriators what Congress could spend, not what it will spend. In practice, those authorized levels can function like ceilings or targets, and appropriators may come in under them, meet them, or sometimes ignore them entirely.

A legislative staffer in a Capitol Hill office reviewing printed bill pages on a desk with folders and notes, candid news photo style

What an appropriation does

An appropriation is the law that actually provides budget authority, allowing federal agencies to incur obligations and make payments from the Treasury.

Appropriations are the check

Appropriations laws answer questions authorizations usually do not:

  • How much money does the program get this fiscal year?
  • How long is the money available (one year, multiple years, no-year)?
  • For what purposes can it be used, and what is prohibited?
  • Under what conditions must the agency report back or seek approval to shift funds?

Appropriations can arrive through multiple vehicles, not just the regular annual bills. Congress also uses omnibus or minibus packages, supplementals, and other stopgap measures when needed.

This is where the Constitution’s “no money drawn” rule bites. Without current appropriations or some other existing budget authority, a federal program might be legally authorized in theory but financially stalled in practice.

Authorized but unfunded is not a contradiction

“Authorized but unfunded” sounds like Washington nonsense until you translate it into plain English:

  • Authorized: Congress wrote a law saying the program can exist and describing what it is supposed to do.
  • Unfunded: Congress did not pass a law giving it money to do those things (or did not give it enough new money to matter).

This can happen for several reasons, some political and some structural:

1) Priorities change, authorizations stay

Authorization laws can last years. Appropriations are typically annual. So you can have a program designed for yesterday’s problem competing in today’s funding environment.

2) Support is easier than paying

Members may like the idea of a program, or like being seen as supporting it, but disagree on the dollar amount. Authorization votes can be politically safe; appropriation votes force tradeoffs.

3) Budget caps and dealmaking squeeze the middle

Even if a program is popular, it can get crowded out by mandatory spending obligations, defense priorities, disaster funding, or simply the arithmetic of spending ceilings and negotiated toplines.

4) Authorization becomes messaging

Sometimes a bill is passed mainly to set a policy direction or create a framework, with the realistic expectation that funding will be partial or delayed.

The result is a government full of “existing” programs that are legally alive but fiscally thin, and occasionally programs that are funded even though their authorizations have technically lapsed.

How committees mirror the split

The authorization and appropriation divide is built into Congress itself.

Authorizing committees handle subject matter and policy. They are the “what are we doing and why” committees.

Appropriations committees handle funding. They are the “how much are we paying for it this year” committees.

This is one reason budget debates can feel like parallel conversations. A member can be deeply involved in authorizing a program’s mission and still have limited influence over whether it receives robust funding in a given fiscal year.

In headlines, these layers often collide: policy committees define what a program is supposed to do, while appropriators decide what it can actually afford to do right now.

A wide-angle view of a Senate hearing room in Washington, DC during an appropriations hearing, with senators seated and witnesses at a table, news photography style

Mandatory vs discretionary: the third concept

If authorization is the blueprint and appropriation is the check, there is a third concept that explains why some programs seem to run on autopilot: mandatory spending.

Discretionary spending

This is the world of the annual appropriations bills. Many agencies and programs live here. They need Congress to pass appropriations to keep operating at full legal capacity.

Mandatory spending

This is spending set largely by authorizing laws that does not depend on annual discretionary appropriations for benefit payments in the same way. Social Security and Medicare are classic examples. The authorizing law creates a benefits structure, and spending flows based on eligibility and formulas.

Two nuances are worth keeping in view. First, many mandatory programs still rely on appropriations acts for some administrative expenses. Second, some budget authority that behaves like “mandatory” can be provided through appropriations mechanisms (including certain accounts funded by offsetting collections). The labels describe the dominant pathway, not every line item.

That is why some parts of government are less exposed to yearly appropriations fights, while others become the center of continuing resolution brinkmanship.

(If you are wondering how that plays out during a shutdown or under a continuing resolution, those dynamics are their own story, and worth reading separately.)

Where continuing resolutions fit

A continuing resolution, or CR, is not an authorization law. It is not a new blueprint for what the government is supposed to do.

A CR is an appropriations stopgap. It temporarily extends funding, usually at prior-year levels, to avoid a lapse in appropriations when Congress has not passed regular appropriations bills.

This is why you can see two headlines that look contradictory but are actually describing different layers:

  • “Program X was reauthorized for five years.”
  • “Congress passes a short-term CR to keep agencies open.”

The first is about permission and policy structure. The second is about keeping money legally available right now.

Why shutdowns center on appropriations

Shutdowns are often described as “the government ran out of money.” The more precise version is this: parts of the government ran out of appropriations authority.

Agencies may be fully authorized to exist. Their missions may be widely supported. But if appropriations lapse, the Appropriations Clause and related federal law, especially the Antideficiency Act, restrict agencies from continuing non-excepted operations as normal. OMB guidance then governs what counts as excepted activity and how agencies manage the gap.

That is why shutdown politics are frequently less about the merits of authorizations and more about the leverage created by must-pass funding deadlines.

A simple example: two votes

Imagine Congress creates the “National River Cleanup Program.”

  • Authorization bill: Sets up the program inside an agency, defines what counts as cleanup, requires annual reporting, and says “$500 million per year is authorized to be appropriated.”
  • Appropriations bill: For the upcoming fiscal year, Congress actually provides $120 million, or $0, or $500 million, and attaches conditions on how it can be spent.

All three outcomes are legally possible. That is the point.

The authorization tells you what Congress says the program is. The appropriation tells you what Congress is willing to pay for right now.

What this split protects and breaks

The authorization-appropriation divide exists for a reason. It is meant to separate policy design from annual spending control. In theory, that produces:

  • Accountability, because agencies must justify funding regularly.
  • Flexibility, because Congress can adjust spending without rewriting entire programs.
  • Oversight leverage, because appropriations can require reports, audits, and compliance.

In practice, it can also produce:

  • Zombie authorizations, where programs continue without updated guidance.
  • Unfunded promises, where authorizations create expectations that appropriations do not meet.
  • High-stakes deadlines, where appropriations become a bargaining chip.

If the system feels messy, that is not an accident. It is the constitutional design of a legislature that wanted friction as a feature.

The quick takeaway

If you remember only one thing, make it this:

  • Authorizations create and shape programs, and may recommend funding.
  • Appropriations are what legally let money leave the Treasury (unless a law has already provided other budget authority, like fees or trust funds).
  • A program can be authorized but unfunded because those are different votes serving different purposes.

Once you see the two-step system, a lot of Washington headlines stop sounding like contradictions and start sounding like what they are: a Constitution built to make power slow, expensive, and hard to use without repeated consent.

The exterior of the U.S. Treasury building in Washington, DC on a clear day, with columns and pedestrians in the foreground, news photography style