Orientation. The chamber will want to debate “are government shutdowns bad” — and on that question the advocates win before they stand up, because the 43-day 2025 shutdown was the longest in U.S. history, cost billions, left 1.4 million workers unpaid, and threatened food aid for 42 million people. But that is not what this bill decides. Nearly everyone agrees shutdowns should end; the live question is how. This bill ends them with an automatic continuing resolution and nothing else — no mechanism to make Congress ever finish a real budget. The leading bipartisan proposal, the Prevent Government Shutdowns Act, pairs an auto-CR with a forcing function that locks Congress in session and bars it from other business until it legislates. This bill keeps the auto-CR and drops the forcing function — so it doesn’t just prevent shutdowns, it removes the deadline pressure and risks freezing the government on autopilot at stale prior-year levels, which carries its own well-documented harms. The round turns on auto-CR-with-teeth versus auto-CR-alone, and the side that frames it that way controls the room.
Part I — The Policy Pro/Con Brief
Why this debate is live right now
Shutdowns are a recurring, escalating dysfunction, and the most recent one set records. The October 1–November 12, 2025 shutdown ran 43 days — the longest ever — and the CBO estimated it cost about $11 billion in real GDP; other tallies put the total cost near $17.2 billion, with 1.4 million federal workers unpaid and SNAP food aid for some 42 million Americans put at risk. There have been 21 funding gaps in the modern budget era, and funding was set to lapse again on January 30, 2026 — the crisis is chronic, not one-off.
The fix the bill reaches for is a real, bipartisan, expert-backed idea — but the serious versions look different from this one. The Prevent Government Shutdowns Act, sponsored by Senators Lankford and Hassan and Representatives Arrington and Panetta, pairs an automatic CR at current levels with strong incentives: while the auto-CR runs, Congress may debate nothing but appropriations, official travel is banned, and daily quorum calls are required until the budget is done. The Committee for a Responsible Federal Budget endorses that design.
What’s genuinely contested is the auto-CR mechanism itself. Supporters argue it reduces brinkmanship and that states with auto-CR laws pass budgets on time just as often as states without them; critics counter that auto-CRs remove the motivation to appropriate and surrender Congress’s power of the purse. And a long-running CR is not costless: the GAO documents that continuing resolutions impose “no new starts,” block new military construction, and delay readiness and modernization. That tension — ending an acute crisis at the risk of a chronic one — is what makes this a real debate.
The Case FOR the Bill (Pros)
The advocates’ best ground is that shutdowns are genuinely catastrophic, that automatic CRs are a credible bipartisan fix, and that ending the threat removes a destructive form of hostage-taking.
Shutdowns inflict large, real harm. The 2025 shutdown ran 43 days, cost roughly $11 billion in GDP, and left 1.4 million workers unpaid while endangering SNAP benefits for 42 million people. Ending that is a serious public good.
Auto-CRs are a credible, expert-endorsed fix. This isn’t a fringe idea — the CRFB and a bipartisan group of senators back automatic CRs, and the evidence that they breed inaction is weak: states with auto-CR laws pass budgets on time at the same rate as states without.
It defuses brinkmanship. Shutdown threats are leverage for hostage politics; an auto-CR reduces high-stakes brinkmanship and creates space for holistic budgeting rather than crisis-to-crisis governing.
It protects readiness, markets, and beneficiaries from the cliff. Keeping agencies funded avoids the air-travel strain, benefit-processing freezes, and inspection delays shutdowns cause, and gives federal workers and contractors predictability.
The implementation path is clean. Assigning OMB to issue guidance within 48 hours and report monthly gives agencies a clear handoff and Congress ongoing visibility into how long the auto-CR has run.
Prior-year levels are a neutral default. Continuing the most recently enacted levels avoids handing either party a win-by-default and keeps the government running at a known baseline while negotiations continue.
The Case AGAINST the Bill (Cons)
The opponents’ best ground is not “shutdowns are fine” — it is that this is the auto-CR without the incentives its own supporters insist on, which risks trading an acute crisis for a chronic one.
It drops the forcing function. The Prevent Government Shutdowns Act pairs the auto-CR with hard incentives — Congress can debate only appropriations, travel is banned, daily quorum calls are required. This bill has the auto-CR and none of that, so it removes the deadline pressure without replacing it.
Auto-CR-alone risks permanent autopilot — and permanent CRs harm readiness. With no incentive to finish, funding can freeze at stale prior-year levels indefinitely, and the GAO documents that continuing resolutions block new starts, halt military construction, delay nuclear modernization, and would cut military personnel accounts by an estimated $5.8 billion under a full-year CR. The bill could entrench the very harms it’s meant to prevent.
Frozen levels misallocate money. Prior-year levels, which the bill explicitly defines as excluding supplemental appropriations, underfund growing and emergent needs and overfund wound-down programs, so the longer the auto-CR runs the worse the fit between funding and reality.
It surrenders the power of the purse. The appropriations deadline is one of Congress’s strongest sources of leverage; the main objection to auto-CRs is that they undermine that leverage, and a version with no forcing function gives it away for nothing.
The mandatory/discretionary line is confused. Section 2(C) applies the auto-CR to “all discretionary and mandatory spending programs requiring annual appropriations” — but most mandatory spending (Social Security, Medicare, interest) is permanently appropriated and continues during shutdowns regardless, so the clause references a near-empty, misunderstood category.
The exceptions clause is vague. Section 3(B)’s “exceptions only for constitutionally mandated expenditures” is undefined and tiny — very little federal spending is constitutionally compelled — and it could collide with the mandatory entitlements the bill otherwise sweeps in.
How to Weigh It
The strongest pro is that shutdowns are large, recurring, documented harms, and automatic CRs are a credible bipartisan way to end them without obvious damage in the states that use them. The strongest con is that this version keeps the auto-CR and drops the forcing function, so it removes the only deadline pressure to finish a budget and risks a permanent CR — which the GAO shows carries its own readiness harms — while surrendering Congress’s power of the purse.
The crux is whether ending shutdowns is worth removing the deadline that forces Congress to legislate. If the room weighs the concrete, recurring harm of shutdowns most heavily, the bill is a serious fix and the debate is about tuning. If it weighs the structural cost — autopilot government at stale levels, readiness harm from open-ended CRs, lost budget leverage — the bill trades an acute crisis for a chronic one, and the existence of the better-designed PGSA shows exactly the incentive structure this bill omits. Advocates must argue that even a bare auto-CR beats a shutdown. Opponents must concede shutdowns are bad, then show this is the auto-CR stripped of the teeth that make the idea work.
Source List (grouped by theme)
The 2025 shutdown and the recurring problem
CBS News — The 2025 government shutdown, by the numbers ($17.2B, 1.4M workers, 42M SNAP)
NPR — The longest government shutdown in U.S. history is over
The real bipartisan proposal (auto-CR plus forcing function)
Sen. Lankford — Lankford, Hassan Team Up to End Government Shutdowns (forcing-function details)
Congress.gov — H.R. 5870, Prevent Government Shutdowns Act (119th Congress)
Long-CR harms (why a permanent auto-CR isn’t free)
Background evidence (uploaded)
AAAA Shutdown.docx — Policy/CX evidence file compiling shutdown harms (defense readiness, SNAP/food security, cyber, aviation). Useful for the harm framing; load-bearing facts above are anchored to primary sources rather than the file’s impact cards.
Part II — Congressional Debate Bill Analysis
What the bill does
The bill provides that if Congress misses the September 30 appropriations deadline, funding for all federal agencies automatically continues at the prior fiscal year’s enacted levels until new appropriations pass. It defines the deadline, the prior-year levels (excluding supplemental appropriations), and the covered spending, and tasks OMB with issuing guidance within 48 hours, applying prior-year levels proportionally with exceptions only for constitutionally mandated expenditures, and reporting monthly. It takes effect October 1, 2026, and voids conflicting laws. The factual baseline both sides start from: this is an automatic continuing resolution — a real, bipartisan idea — but the leading version of it pairs the auto-CR with a forcing function that this bill leaves out.
The strongest case for the bill
The advocates’ best ground is that shutdowns are catastrophic and auto-CRs are a credible, bipartisan fix — so lead with the 2025 shutdown, the harm the chamber already feels.
The first argument is the scale of the harm. The 2025 shutdown ran 43 days and cost about $11 billion in GDP, with 1.4 million workers unpaid and SNAP for 42 million at risk — so ending shutdowns is a concrete public good, not an abstraction.
The second argument is credibility. Automatic CRs are endorsed by the CRFB and a bipartisan bloc of senators, so this isn’t a gimmick — and the fear that auto-CRs breed inaction isn’t borne out, since states with them budget on time at the same rate.
The third argument is defusing brinkmanship. The shutdown threat is leverage for hostage politics; an auto-CR reduces high-stakes brinkmanship and makes room for real budgeting instead of cliff-to-cliff governing.
The fourth argument is protecting the public. Keeping agencies funded avoids the benefit freezes, inspection delays, and air-travel strain shutdowns cause and gives workers and contractors predictability.
The fifth argument is implementation. The 48-hour OMB guidance and monthly reporting give agencies a clean handoff and Congress a running view of how long the auto-CR has lasted.
The sixth argument is neutrality. Continuing the most recently enacted levels is a default that favors neither party, keeping the lights on at a known baseline while talks continue.
The strongest case against the bill
The opponents’ best ground is that this is the auto-CR without the incentives — lead with the dropped forcing function, then the permanent-CR readiness harm, then the power of the purse.
The first and sharpest argument is the contrast with the real bill. The Prevent Government Shutdowns Act pairs the auto-CR with hard incentives — appropriations-only floor debate, banned travel, daily quorum calls. This bill has the auto-CR and none of those, so it removes the deadline pressure without replacing it — the version even auto-CR supporters warn against.
The second argument is the procedural catch most of the chamber will miss: auto-CR-alone risks a permanent CR, and permanent CRs damage exactly what shutdowns do. The GAO documents that CRs block new starts, halt military construction, delay nuclear modernization, and would cut military personnel by an estimated $5.8 billion under a full-year CR, so a bill meant to protect readiness could entrench the harm it targets.
The third argument is misallocation. Frozen prior-year levels, which the bill defines to exclude supplementals, underfund growing and emergent needs and overfund wound-down ones, and the fit worsens the longer the auto-CR runs.
The fourth argument is the power of the purse. The appropriations deadline is Congress’s strongest leverage, and the central objection to auto-CRs is that they surrender it — a cost this bill pays without buying the incentives that would justify it.
The fifth argument is the definitional confusion. Section 2(C) covers “mandatory spending programs requiring annual appropriations,” but most mandatory spending is permanently appropriated and continues during shutdowns anyway, so the clause names a category that barely exists.
The sixth argument is vagueness. “Exceptions only for constitutionally mandated expenditures” in Section 3(B) is undefined and minuscule, and it sits awkwardly against the mandatory entitlements the bill elsewhere sweeps in.
Cross-examination questions
Questions for advocates to ask opponents.
“The 2025 shutdown ran 43 days and cost roughly $11 billion in GDP. Do you dispute that shutdowns cause serious harm — yes or no?”
“Automatic CRs are backed by the CRFB and a bipartisan group of senators. Is your position that they’re all wrong?”
“States with auto-CR laws pass budgets on time at the same rate as states without. Where’s your evidence this breeds inaction?”
“Under your status quo, who actually suffers in a shutdown — members of Congress, or 1.4 million federal workers and SNAP recipients?”
“Even a bare auto-CR keeps the government open. Isn’t an imperfect continuation better than a 43-day lapse?”
“If your only concern is the missing forcing function, isn’t that an amendment to add, not a reason to keep shutdowns legal?”
Questions for opponents to ask advocates.
“The Prevent Government Shutdowns Act pairs the auto-CR with a forcing function. Where in this bill is the mechanism that makes Congress ever finish a budget?”
“If funding just continues automatically with no pressure, what stops Congress from running on a frozen prior-year budget indefinitely?”
“The GAO says continuing resolutions block new starts and delay modernization. Doesn’t a permanent auto-CR entrench the readiness harm you say you’re preventing?”
“Prior-year levels exclude supplementals. How does a frozen budget fund a hurricane, a war, or a new program?”
“Section 2(C) covers ‘mandatory programs requiring annual appropriations.’ Which mandatory programs are those — Social Security continues during shutdowns already, doesn’t it?”
“What counts as a ‘constitutionally mandated expenditure’? Name three.”
“The appropriations deadline is Congress’s leverage. Why surrender it without getting the PGSA’s incentives in return?”
“Your bill says ‘all laws in conflict are null and void.’ Does that include the Antideficiency Act — and if so, why doesn’t the bill say so?”
Drafting and definitional traps
The bill’s text rewards close reading and punishes the drafter.
Section 2(C) misunderstands the budget. Applying the auto-CR to “all discretionary and mandatory spending programs requiring annual appropriations” treats mandatory spending as if it needed annual appropriations — but most of it (Social Security, Medicare, interest) is permanently appropriated and continues during shutdowns regardless, so the clause references a near-empty set.
The bill never names the law it overrides. Shutdowns happen because the Antideficiency Act bars spending without appropriations; this bill effectively creates a standing appropriation to override it but never says so, relying on Section 4’s blanket “all laws in conflict are null and void” to do the work — a non-specific implied repeal of the statute at the center of the whole problem.
Section 2(A) lets a “concurrent resolution” reset the statutory deadline, but a concurrent resolution isn’t presented to the President and carries no force of law, so it can’t actually amend a statutory date.
Section 3(B)’s “exceptions only for constitutionally mandated expenditures” is undefined and vanishingly small, and it conflicts with the mandatory entitlements the bill elsewhere sweeps in.
The bill has no forcing function at all — no incentive, deadline, or penalty to make Congress complete appropriations — which is the design feature the leading bipartisan version treats as essential.
Smaller flaws compound it: “OBM” is a typo for OMB, prior-year levels “excluding supplemental” freeze out real emergencies, and the October 1, 2026 effective date and null-and-void clause arrive with no transition rule.
Logical flaws
The deepest problem is a forcing-function non-sequitur. The bill’s goal is a functioning appropriations process, but its mechanism removes the deadline that drives appropriations and adds nothing in its place, so it assumes Congress will keep legislating after deleting the only reason it does — the precise objection auto-CR supporters answer with incentives this bill omits.
The bill is self-defeating on readiness. It is sold as protecting the government from shutdown harm, but an open-ended auto-CR is a permanent CR, and the GAO shows permanent CRs block new starts, stall construction, and cut personnel — so the cure reproduces the disease.
There is a means-end mismatch. If the aim is to make Congress do its budgeting job, freezing the budget on autopilot achieves the opposite: it lets Congress not budget indefinitely while the government coasts on stale numbers.
A category error sits in the definitions. Treating mandatory spending as “requiring annual appropriations” misdescribes how the budget works, so the operative coverage clause is built on a misunderstanding of what shutdowns even affect.
And there’s a power-of-the-purse contradiction. A bill meant to make Congress accountable for funding removes the pressure that produces accountability, surrendering the leverage the deadline creates — so the accountability rationale undercuts itself.
Verdict / how to play it
The chamber will saturate the advocate side, and with unusually good reason: the 2025 shutdown is fresh and record-breaking, “end the shutdowns” is bipartisan, and auto-CRs are genuinely endorsed by serious budget experts. Expect several strong advocacy speeches built on the 43-day record and the harm to workers and SNAP recipients.
This is one of the more balanced bills in the docket, so the opposition has to be precise rather than loud. The rare, higher-value speech is the one that knows the real Prevent Government Shutdowns Act pairs the auto-CR with a forcing function and that this bill drops it — then flips the readiness evidence to show a permanent auto-CR damages readiness the same way shutdowns do. That speech wins because it concedes the goal and attacks the design.
If you are advocating, do not over-claim — concede the bill would be stronger with a forcing function, then argue that even a bare auto-CR beats a 43-day shutdown, lean on the bipartisan and state-level track record, and frame the missing incentives as an amendment, not a defect that justifies keeping shutdowns legal.
If you are opposing, the highest-leverage move is the contrast run as one stroke: the leading bill pairs the auto-CR with hard incentives to finish the budget, this bill keeps the continuation and deletes the pressure, so it doesn’t end the dysfunction — it makes it permanent at frozen funding levels. Stack the GAO readiness harm behind it (a permanent CR hurts the military the way shutdowns do) and the power-of-the-purse surrender on top. Hold the mandatory/discretionary definitional confusion for when an advocate insists the bill is carefully drafted.
Do not let the round collapse into “are shutdowns bad,” which the advocates win; force it onto “does ending shutdowns this way — with no mechanism to ever pass a real budget — fix the dysfunction or freeze it,” which the opponents win. One cross-apply: the “the real bill has a mechanism this one omits” contrast recurs across the docket, and the appropriations/power-of-the-purse frame pairs with any other spending or budget-process measure in the round.
Bibliography
• Committee for a Responsible Federal Budget. “Congress Could End Government Shutdown Drama Once and For All.” CRFB Blog, January 29, 2026. https://www.crfb.org/blogs/congress-could-end-government-shutdown-drama-once-and-all
• U.S. Government Accountability Office. “Defense Budget: Effects of Continuing Resolutions on Selected Activities and Programs Critical to DOD’s National Security Mission.” GAO-26-107065 (reissued Feb. 4, 2026). https://www.gao.gov/products/gao-26-107065
• CBS News. “The 2025 U.S. government shutdown, by the numbers.” CBS News, November 2025. https://www.cbsnews.com/news/2025-government-shutdown-by-numbers/
Congress.gov. “H.R.5870 — Prevent Government Shutdowns Act, 119th Congress (2025–2026).” Library of Congress. https://www.congress.gov/bill/119th-congress/house-bill/5870
Sen. James Lankford. “Lankford, Hassan Team Up to End Government Shutdowns and Hold Congress Accountable.” Press release. https://www.lankford.senate.gov/news/press-releases/lankford-hassan-team-up-to-end-government-shutdowns-and-hold-congress-accountable/
Sen. James Lankford. “The Prevent Government Shutdowns Act of 2025 — Automatic Continuing Resolution (One-Pager).” September 2025. https://www.lankford.senate.gov/wp-content/uploads/2025/09/PGSA-2025-One-Pager-.pdf
NPR. “The longest government shutdown in U.S. history is over. Here’s what you need to know.” NPR, November 15, 2025. https://www.npr.org/2025/11/15/nx-s1-5609367/trump-government-shutdown-what-to-know-longest
U.S. Senate Committee on Appropriations. “Secretary of Defense, Top Pentagon Leadership Sound Alarm That a Year-long CR Would Jeopardize Our National Defense.” Press release. https://www.appropriations.senate.gov/news/majority/new-secretary-of-defense-top-pentagon-leadership-sound-alarm-that-a-year-long-cr-would-jeopardize-our-national-defense
Center for Strategic and International Studies. “What a Government Shutdown Would Mean for Defense Funding in FY 2026.” CSIS Analysis. https://www.csis.org/analysis/what-government-shutdown-would-mean-defense-funding-fy-2026