Skip to content
Lex Machina Review logoLex Machina Review
Menu

Regulation

Where the SAVE America Act Senate Vote Stands Now

As of Aug. 1, 2026, the SAVE America Act has not passed the Senate, and no Senate passage vote is scheduled. The current status check is against the congress.gov pages for H.R. 7296 and S. 3752 and the Senate roll-call page, last checked Aug. 1, 2026.[1][2][3]

The latest Senate roll calls listed for July 29-30 are not SAVE passage votes. They concern S.Res. 817, S.J.Res. 181, and S.J.Res. 199, which is why a late-July Senate vote reference should not be rewritten as “the Senate voted on SAVE” unless the roll call actually identifies a SAVE vehicle or amendment.[3]

Bill document stalled in a Senate chamber with paths toward a 60-vote gate and a gavel-sealed procedural door
Status questionVerified answer as of Aug. 1, 2026
Has the SAVE America Act passed the Senate?No.
Is a Senate passage vote scheduled?No scheduled passage vote appears on the verified status sources checked for this record.
Did the House pass the current House vehicle?Yes. H.R. 7296 passed the House 218-213 on Feb. 11, 2026.
Did the Senate take any procedural action?Yes. A motion to proceed was recorded 51-48 on March 17, 2026.
What are the live paths?An NDAA attachment route with a 60-vote problem, and a reconciliation route blocked by the Byrd Rule ruling.

What has actually happened

The current House vehicle, H.R. 7296, passed the House 218-213 on Feb. 11, 2026. The Senate companion is S. 3752. Those are the two congress.gov pages to use for the present 2026 status record, not a press-release shorthand or an older bill number carried forward by commentary.[1][2]

The Senate did record a procedural step: a motion to proceed passed 51-48 on March 17, 2026, with Sen. Lisa Murkowski joining Democrats in opposition. That was not final passage. It did not enact the bill, and it did not show a 60-vote path for cloture.[3]

The bill then failed to advance before the March 27 recess, and Campaign Legal Center described the measure as stalled in the Senate by April 21.[4]

The harder record for headline writers is the amendment track. SAVE amendments failed 48-50 in spring 2026, including in reports tied to the late-night reconciliation debate and later blocking efforts. Four Republicans — Murkowski, Mitch McConnell, Susan Collins, and Thom Tillis — joined Democrats against the measure in that setting, so the amendment did not even reach a simple majority, much less a filibuster-proof threshold.[5][6]

That is the difference between “the Senate voted on a SAVE amendment” and “the Senate passed SAVE.” The first may be true for particular roll calls or amendment attempts. The second is not true as of this status check.

Why a 53-47 Senate majority has not produced passage

Republican control of the Senate does not answer the vote-status question by itself. A 53-47 majority can organize the chamber and pass some measures by simple majority, but ordinary Senate legislation usually faces a 60-vote cloture barrier if opponents do not consent to move forward. SAVE is sitting in that procedural gap.

That gap is not theoretical here. Senate Majority Leader John Thune was reported saying the votes were “not even close,” while coverage of President Trump’s pressure campaign described the same 60-vote problem facing Senate Republicans.[7][8]

The failed 48-50 amendment votes are the cleaner procedural warning sign. If an amendment cannot hold 50 votes in a setting designed to test party support, then the phrase “blocked by the filibuster” is incomplete. The immediate problem is not only that opponents can demand 60. It is also that the recorded SAVE amendment votes available in this record did not show 50 supporters in that vehicle.[5][6]

The political calendar makes that math more visible, but it does not change the vote count. Reporting tied the fight to pressure before the Aug. 7 recess, and Florida Gov. Ron DeSantis publicly put pre-recess odds at “basically zero.” Senate Minority Leader Chuck Schumer was also reported calling the bill “dead on arrival” and pointing to repeated failed attempts; that is a political assessment, not an official Senate disposition.[7][9]

The two remaining routes

Diagram showing an NDAA route blocked by a 60-vote gate and a reconciliation route sealed by a Byrd Rule ruling

The remaining fight is procedural. One path tries to attach SAVE to a larger must-pass or high-pressure vehicle. The other tries to use reconciliation, where a simple majority is normally more attractive but Senate budget rules decide what belongs in the package.

NDAA attachment

The NDAA path is the more visible live vehicle because the House acted on it in July. The House attached SAVE-related language to the NDAA route on July 15 by a 217-209 vote, and then passed the annual defense bill on July 22 by 216-212.[10][11]

That House action does not solve the Senate problem. The Senate NDAA version failed to advance 50-46 on July 14, and any Senate-side package carrying SAVE still runs into the same cloture question unless the chamber’s consent structure changes.[3]

So the NDAA route should be described as an attachment route, not as Senate passage of SAVE. It can become important quickly if Senate negotiators revive the defense vehicle, but the verified status on Aug. 1 remains no Senate passage vote for SAVE.

Reconciliation

Reconciliation is attractive because it can avoid the usual 60-vote cloture requirement for qualifying budget provisions. SAVE’s problem is that the parliamentarian’s Byrd Rule ruling was reported as blocking that route, and Trump responded by calling for the parliamentarian’s ouster.[7][8]

The House Administration Committee deadline of Sept. 11 keeps reconciliation on the calendar as a place to watch, but the deadline does not erase the ruling. Unless the Senate finds a different procedural theory, changes the vehicle, or overrules the advice in some fashion, reconciliation remains a blocked route for SAVE rather than a pending simple-majority vote.[10]

Why bill numbers are causing bad status sentences

Some confusion comes from reusing “SAVE Act” or “SAVE America Act” as a label across different vehicles. Older references may point to a 2025 House vote: a legislative-history compilation lists H.R. 22 passing the House 220-208 on April 10, 2025.[12]

That history explains why readers may see different identifiers in search results, but it does not update the current Senate status. For the Aug. 1, 2026 check, the operative congress.gov pages are H.R. 7296 and S. 3752. If a memo, alert, or headline cites another identifier, the safe move is to verify whether it is discussing an older vehicle, a companion bill, an amendment, or a different procedural attempt.[1][2]

How to state the status without overclaiming

  • Defensible: “The House passed H.R. 7296, but the Senate has not passed the SAVE America Act as of Aug. 1, 2026.”
  • Defensible: “The Senate took a procedural vote on March 17, 2026, but that was a motion to proceed, not final passage.”
  • Defensible: “SAVE amendments failed 48-50 in spring 2026, showing the measure lacked even a simple majority in that amendment setting.”
  • Too broad: “The Senate passed SAVE.”
  • Too broad without a vehicle: “SAVE was blocked” or “SAVE is dead.” Those phrases need the chamber, vote type, vehicle, and date.

The bill is politically charged because it would require documentary proof of U.S. citizenship for voter registration in federal elections, but this record is not the place to resolve the policy dispute. The procedural status is narrower and more useful: no Senate passage, no scheduled passage vote, and two difficult routes left on the board.[1][2][3]

What to check next

The next status changes would come from Senate NDAA movement, a renewed SAVE amendment, reconciliation action after the House Administration deadline, or a new Senate roll call before or after the Aug. 7 recess. Until one of those appears in the primary record, the answer remains: the SAVE America Act has not passed the Senate, and no Senate passage vote is scheduled.[3][7][10]

This is an election-administration legislative tracker, not AI legislation. For adjacent governance context, see the site’s Senate 60-vote procedure record and the voter-roll verification reliability record; those companion issues should not be folded into this Senate vote status unless a new SAVE vehicle actually raises them in the legislative text.

References

  1. H.R.7296 - 119th Congress (2025-2026): SAVE America Act - Congress.gov
  2. S.3752 - 119th Congress (2025-2026): SAVE America Act - Congress.gov
  3. Votes - United States Senate
  4. Victory for Voters: SAVE America Act Fails in Senate - Campaign Legal Center
  5. Kennedy forces SAVE Act vote during late-night reconciliation bill debate - Senator John Kennedy
  6. WATCH: Padilla Leads Charge to Successfully Block Another SAVE America Act Push - Senator Alex Padilla
  7. Trump demands Senate cancel August break until it passes the SAVE America Act - PBS NewsHour / Associated Press
  8. Trump SAVE America Act Congress voting restriction bill: What to know - NBC News
  9. DeSantis doubts SAVE Act passage - The Hill
  10. House Passes SAVE Act Anti-Voting Measures in Budget Reconciliation, Stock Trading Bills - Democracy Docket
  11. House Annual Defense Spending Bill SAVE America Act Iran War - TIME
  12. Safeguard American Voter Eligibility Act - Wikipedia

Operationalizing workflow

No workflow has been explicitly linked to this obligation yet. See Workflows generally.

Illustrative cases

← Back to Regulation

Report a correction or tip

Spotted an outdated figure, a misstated fact, or a ruling this regulation entry should reflect? Public comments are disabled for this content given the professional cost of a misreported case outcome, penalty amount, or rule text — use the structured correction channel instead.

Report a correction or tip for this record →
Blogarama - Blog Directory