With only a handful of legislative days left before the five-week August recess, Congress is trying to move an unusually heavy load of defense, spending, and reform legislation through a House with almost no margin for error (Federal News Network, July 2026). Below is a bill-by-bill vote outlook for the four measures policy professionals should be watching most closely, followed by a synthesis of what this week’s dynamics signal for the fall.
A note on evidence: where formal whip counts exist, we cite them. Where they don’t — which is most of the time, because leadership whip sheets are not public — we reason from the hard numbers we do have: committee votes, procedural (rule) votes, and recorded floor margins. Those are the most reliable proxies available, and we flag the uncertainty accordingly.
National Defense Authorization Act for Fiscal Year 2027 (H.R. 8800 / S. 4784)
One-sentence plain-English summary: The NDAA is the annual bill that authorizes roughly $1.15 trillion in defense policy and spending — setting personnel levels, weapons programs, and Pentagon reforms for the year (Strickland, June 5, 2026).
Current stage: Stalled mid-process in both chambers. The House began floor consideration under a structured rule (H. Res. 1438) on July 21 but left the bill as “unfinished business” with amendment votes postponed (H.R. 8800, 119th Congress). In the Senate, cloture on the motion to proceed failed 50–46 on July 14 ([legislation research summary]).
Expected vote margin and whip-count reasoning
House: narrowly passable, but not yet locked. The bill cleared the House Armed Services Committee 44–12, but that margin masks trouble — normally only “one or two” committee Democrats oppose the NDAA, and this year nearly half the panel’s Democrats voted no (Strickland, June 5, 2026). That erosion of the traditional bipartisan floor coalition matters because Republican leadership tried to merge the NDAA with the SAVE Act (a national voter-ID measure), which “didn’t go over well with the conservative wing of the party” and left the bill “stuck in suspended animation” (Federal News Network, July 2026). The companion rule (H. Res. 1438) passed only 214–211, confirming that leadership has essentially no cushion on defense-adjacent procedural votes (H. Res. 1438, 119th Congress).
Senate: currently short of 60. The July 14 cloture vote failed 50–46 — ten votes short of the 60 needed to proceed ([legislation research summary]). A later motion to proceed was entered July 20, but no successful renewed cloture vote had occurred as of this writing.
Key swing votes
- Sen. Tammy Duckworth (D-IL): Publicly committed to vote no unless her amendment halting further funding for offensive operations against Iran is included, calling it unacceptable to authorize “$1.14 trillion in defense spending… for Donald Trump to continue his illegal and disastrous war” (Duckworth, July 14, 2026). What could move her: inclusion of her Iran war-powers amendment. Senate Republicans blocked it in committee, so this is a live obstacle.
- Senate Democrats as a bloc are the pivotal group for cloture — with the bill 10 votes short, roughly that many Democratic (or Democratic-caucusing) votes must be found, almost certainly through amendment concessions on Iran ([legislation research summary]).
- House conservatives opposed to the SAVE Act merger are the corresponding House pressure point (Federal News Network, July 2026).
The unusual defense-hawk/anti-war split cuts across party lines this year: Rep. Seth Moulton (D-MA) sought to cut $150 billion from the topline, saying “I’m not going to hand them a blank check to fund reckless unilateral wars of choice,” while Ranking Member Adam Smith (D-WA) targeted funding for Trump-class battleships — both defeated by GOP defense hawks (Strickland, June 5, 2026).
Timing and what could delay it
The House had H.R. 8800 on the July 21 floor agenda but did not finish it (H.R. 8800, 119th Congress). The binding constraint is the calendar: only about eight legislative days remained before recess when both chambers returned (Federal News Network, July 2026). The most likely delay triggers are (1) the unresolved SAVE Act merger fight in the House and (2) the failed Senate cloture path, compounded by uncertainty over the separate $67 billion Iran supplemental and Sen. McConnell’s hospitalization, which affects the subcommittee that moves Pentagon money (Federal News Network, July 2026).
Scenario planning
- Scenario A — House finishes, Senate slips (most likely): The House completes amendments and passes on a near-party-line vote, but the Senate cannot rebuild a 60-vote cloture coalition before recess. Conference and final passage push into the fall. For contractors: continued planning uncertainty, especially for programs the administration routed through reconciliation rather than the base bill (see below).
- Scenario B — Amendment-driven deal: Senate leadership accepts an Iran-related amendment to win back Duckworth and enough Democrats to clear cloture. For stakeholders: watch the amendment text closely — Iran operational funding, munitions replenishment, and right-to-repair provisions (backed by Reps. Goodlander and Harrigan, a “big blow to defense industry giants”) are all in play (Strickland, June 5, 2026).
- Scenario C — Full stall: Both chambers leave without resolution. Given the 66-year unbroken streak of NDAA enactment via regular order (Cramer, June 11, 2026), a total failure is unlikely, but a delayed fall timeline is very plausible.
Continuing Appropriations Act, 2027 (H.R. 9770)
One-sentence plain-English summary: A “clean” short-term stopgap that keeps the government funded at current levels through December 4, 2026, avoiding a September 30 shutdown (House Appropriations Committee, July 17, 2026).
Current stage: Already passed the House on July 21, 220–205 (Roll no. 272), and is now awaiting Senate action (H.R. 9770, 119th Congress).
Expected vote margin and whip-count reasoning (House — actual)
The House passed the CR 220–205 (H.R. 9770, 119th Congress). That is a workable but tight majority, and it broke from precedent in a telling way: Democratic leaders privately signaled opposition to a clean stopgap they would traditionally support. Minority Leader Hakeem Jeffries “expressed strong opposition” at a leadership meeting, and the No. 3 House Democrat, Rep. Pete Aguilar, said publicly, “I’ll be voting ‘no.’ And if any members ask, I would encourage them to do the same” (Politico, July 21, 2026). The near-party-line margin means Republicans carried this largely on their own.
The real fight is now the Senate
This is where the vote outlook turns negative. The bill “is highly unlikely to get the 60 votes needed for passage in the Senate” (NBC News live coverage, July 21, 2026 — as reported in the aggregated coverage). Majority Leader John Thune committed to holding a vote but cautioned it “doesn’t have all the provisions the White House requested,” and notably left the door open to using budget reconciliation to fund the government “in the event that… the wheels come off on a CR.”
Key swing votes
- Senate Democrats are the pivotal bloc: with 60 votes required and the House product passed on a party-line basis, roughly seven or more Democrats would need to cross over. Given Jeffries’s and Aguilar’s posture in the House, that cooperation is in doubt (Politico, July 21, 2026).
- Sen. John Thune (R-SD) is the procedural pivot — his choice between pressing the CR and pivoting to reconciliation will shape the endgame.
Timing and what could delay it
The House deliberately moved early — Chairman Tom Cole framed the July timing as “acting before a funding lapse crisis, not in response to it,” explicitly to get it done before the August district work period (Cole floor remarks, H.R. 9770). The genuine deadline is September 30 (House Appropriations Committee, July 17, 2026). The delay risk is not the calendar — it’s the Senate’s 60-vote wall.
Scenario planning
- Scenario A — Senate stalls the House CR (most likely near-term): The CR fails to reach 60 votes, and the funding fight carries into September. For stakeholders: the early-July House action means there is a long runway, so near-term shutdown odds are low, but the fall fight is merely deferred, not resolved.
- Scenario B — Reconciliation pivot: Thune uses budget reconciliation (51 votes) as a funding vehicle if the CR collapses (Politico/NBC coverage, July 21, 2026). This would be a significant procedural escalation. For stakeholders: a partisan funding mechanism changes what riders and program levels are achievable and removes Democratic leverage.
- Scenario C — Bipartisan Senate deal: The Senate amends the CR to add White House-requested provisions and sends it back, compressing the House-Senate “ping-pong” into the fall calendar ([legislation research summary]).
FY2027 Budget Resolution — "Reconciliation 3.0" (H. Con. Res. 113)
One-sentence plain-English summary: A budget resolution that unlocks a party-line “reconciliation” package — this year aimed at roughly $60 billion in additional defense funding, intelligence programs, farm provisions, and (contested) voter-ID grants — that can pass the Senate with 51 votes instead of 60 (Federal News Network, July 2026; H. Con. Res. 113, 119th Congress).
Current stage: Reported from the House Budget Committee and placed on the Union Calendar; the enabling rule (H. Res. 1438) was adopted July 21, with the resolution itself set for a House floor vote on or around July 22 (H. Con. Res. 113, 119th Congress; Politico, July 21, 2026).
Expected vote margin and whip-count reasoning
Razor-thin. The enabling rule passed just 214–211 (H. Res. 1438, 119th Congress), and the research indicates the budget resolution itself passed the House on July 22 by roughly 216–214 — an extraordinarily narrow, near-party-line margin ([legislation research summary]). Speaker Johnson “cannot lose more than a tiny handful of Republicans,” and with Democrats uniformly opposed, every defection counts (Politico, July 21, 2026).
The whip environment is genuinely shaky. One government-affairs firm noted that authorizing chairmen — including Ways and Means Chairman Jason Smith and T&I Chairman Sam Graves — “have publicly stated they aren’t involved or don’t think it’s a good idea,” and that leadership was “whipping vulnerable Rs, several of whom have told us directly they aren’t enthusiastic” (Elevate Government Affairs).
Key swing votes
- Rep. Warren Davidson (R-OH): Committed no because the resolution “lacks offsets to reduce the deficit impact of the new spending” (Politico, July 21, 2026). What could move him: addition of spending offsets.
- Rep. Chip Roy (R-TX): Expressed uncertainty over the same lack of offsets, though some reporting suggested he might ultimately back the rule and resolution (Politico, July 21, 2026). What could move him: fiscal guarantees or the promise of a “more sweeping” partisan bill in the fall, which Speaker Johnson and OMB Director Russ Vought were dangling (Politico, July 21, 2026).
Timing and what could delay it — including the Senate problem
Even if the House cleared it July 22, the Senate is the graveyard risk. Sens. Mitch McConnell and Susan Collins have both been “skeptical that 3.0 will actually move forward,” and the Senate has shown “little, to none, to perhaps negative interest” (Federal News Network, July 2026; Elevate Government Affairs). The Byrd Rule is a substantive constraint: policy provisions like the SAVE Act’s voter-ID language could hit “a buzzsaw” with the Senate parliamentarian, and even proponents admit they’re unlikely to get the whole package through (Federal News Network, July 2026).
Scenario planning
- Scenario A — House passes, Senate ignores (most likely): The House adopts the resolution on a bare margin, but the Senate declines to take it up or slow-walks it (Federal News Network, July 2026). For defense contractors: this is the critical risk. Roughly $350 billion of the FY27 defense request — including 53 of 85 requested F-35s, a space-based AMTI system, and Golden Dome components — was routed through reconciliation, not the base budget (Government Executive, July 8, 2026). If 3.0 stalls, those programs “would have to be slowed or reduced in scope in the near-term.”
- Scenario B — Offset-driven amendment: Leadership adds offsets to win Davidson and reassure Roy, passing a modified resolution. For stakeholders: the composition of offsets (potential safety-net cuts have been floated) becomes the story (Larson, April 30, 2026).
- Scenario C — Full stall: The reconciliation timetable slips past recess, compressing committee drafting into the fall and jeopardizing the whole vehicle ([legislation research summary]).
Stock Trading Ban — STOCK Act 2.0 (H.R. 3779) and the More Likely Vehicle (H.R. 7008)
One-sentence plain-English summary: These bills would restrict or ban members of Congress (and, in some versions, their families and other senior officials) from trading individual stocks while in office (H.R. 3779, 119th Congress).
Current stage — an important distinction: H.R. 3779 (STOCK Act 2.0), sponsored by Rep. Dave Min, remains at the introduction/committee-referral stage with no markup, no rule, and no scheduled floor vote (H.R. 3779, 119th Congress). The bill actually positioned for a floor vote is a different, milder measure — the Stop Insider Trading Act (H.R. 7008) — which was reported from the House Administration Committee 7–4 and set up for floor consideration under H. Res. 1438 (Carey, January 14, 2026; H. Res. 1438, 119th Congress). Policy professionals tracking “the stock trading ban” should watch H.R. 7008, not H.R. 3779.
Expected vote margin and whip-count reasoning
Highly uncertain; enactment odds low. No formal whip count exists. The most concrete data points are the 7–4 party-line committee vote on H.R. 7008 (Carey, January 14, 2026) and prediction-market pricing that assigns just an 8.5% chance of any ban clearing both chambers and the White House before 2027 (Polymarket). The broader bipartisan alternative — the Restore Trust in Congress Act — had 126 cosponsors but its discharge petition stalled at 82 signatures, well short of the 218 needed (Gillibrand, January 15, 2026; Roll Call, March 31, 2026).
The core problem is a split among reformers, not simple opposition. Democrats view the GOP-backed H.R. 7008 as insufficient because it lets members keep stocks they already own, while the competing bipartisan bill requires divestiture (Politico, July 15, 2026). One reform advocate argued Democratic leadership “decided to blow that up” by expanding their version to cover the President and VP — a poison pill for Republicans (Roll Call, March 31, 2026).
Key swing votes
- Reps. Ed Case (D-HI) and Josh Riley (D-NY): The only two Democrats cosponsoring the GOP-backed H.R. 7008 (Politico, July 15, 2026). Their willingness to break from leadership’s preferred divestiture approach makes them the bellwethers for any bipartisan floor coalition.
- Rep. Anna Paulina Luna (R-FL): The chief agitator, threatening continued “pressure and pain” on leadership and a discharge petition; she says she was promised a Q1 2026 floor vote that never materialized (Roll Call, March 31, 2026).
- Speaker Mike Johnson (R-LA): The ultimate gatekeeper — he has said he’d bring a ban to the floor with “solid support” but has also warned it could deter qualified candidates (Time, 2026).
Timing and what could delay it
GOP leaders eyed a possible H.R. 7008 vote as soon as the week of July 20, potentially bundled with the reconciliation framework during “fly-out week” (Politico, July 15, 2026). But this is the fourth reported deadline to slip — a Q1 promise already came and went (Roll Call, March 31, 2026). Even if the House acts, the Senate “is not expected to take up the bill,” and Majority Leader Thune has doubted he’ll bring it to the floor (Politico, July 15, 2026; Time, 2026).
Scenario planning
- Scenario A — Messaging vote, no enactment (most likely): The House passes the milder H.R. 7008 as a pre-recess messaging win, but it dies in the Senate (Politico, July 15, 2026). For stakeholders: watch the scope. H.R. 7008 only bans new purchases and requires advance notice of sales — a far lighter compliance lift than the divestiture-based bills (Carey, January 14, 2026).
- Scenario B — Continued stall (very plausible): No floor vote before recess, consistent with the 8.5% market-implied enactment odds (Polymarket).
- Scenario C — Discharge breakthrough (low probability): Luna’s pressure campaign forces a broader bill to the floor. This would be the version with real teeth — divestiture requirements, family coverage, and (in the STOCK Act 2.0 formulation) coverage of the Fed, judiciary, and executive branch (H.R. 3779, 119th Congress; Fitzpatrick, June 26, 2026). For compliance and wealth-management professionals advising officials, this is the low-probability/high-impact tail risk to model.
What This Week Signals for the Fall
The through-line is a House majority governing on the thinnest possible margins, and a Senate 60-vote wall that neuters most of what the House produces. The 214–211 rule vote, the ~216–214 budget resolution, and the 220–205 CR all tell the same story: Republican leadership can pass party-line priorities in the House with essentially zero cushion, but almost nothing here has a credible Senate path before recess (H. Res. 1438; H.R. 9770; Politico, July 21, 2026).
The scenarios most policy professionals should prepare for now:
- A deferred, high-stakes fall funding fight. The CR’s likely Senate stall — and Thune’s openness to a reconciliation-based funding pivot — means the September 30 deadline fight is merely postponed, and could arrive in a more partisan form than usual (Politico/NBC, July 21, 2026). Government-facing clients should not treat the early House CR as “problem solved.”
- Defense procurement in limbo. The single most consequential private-sector risk is the fate of Reconciliation 3.0, because ~$350 billion in defense priorities — F-35s, Golden Dome, munitions replenishment, space programs — was deliberately parked there rather than in the base NDAA or appropriations (Government Executive, July 8, 2026). With the Senate cool to 3.0 and the base NDAA itself stalled, defense contractors and their advisors should model near-term program slowdowns as a realistic base case, not a worst case.
- Iran as the swing variable across defense bills. Duckworth’s NDAA ultimatum, the separate $67 billion Iran supplemental, and Democratic opposition to funding “a war Congress did not authorize” are interlocking (Duckworth, July 14, 2026; Government Executive, July 8, 2026). How the Iran question resolves will shape the NDAA endgame and the appetite for defense reconciliation.
- Stock trading reform: prepare for optics, not enactment. The 8.5% market-implied odds and the reformers’ own infighting suggest the most likely outcome is a messaging vote or continued stall (Polymarket; Roll Call, March 31, 2026). Compliance teams should track H.R. 7008’s lighter “no-new-purchases-plus-notice” model as the realistic near-term standard, while keeping the divestiture-based bills on the watch list as a tail risk.
The recommendation for policy professionals: anchor your fall planning to the Senate constraints, not the House votes. House passage this week is largely a statement of Republican intent; the operative question for every one of these four bills is whether leadership can find 60 Senate votes (NDAA, CR) or hold 51 through the Byrd Rule gauntlet (Reconciliation 3.0). On current evidence, the base case for all four is delay or partisan workaround rather than clean bipartisan enactment before recess — and clients exposed to defense procurement should treat the reconciliation stall scenario as the one most worth hedging against today.
About Statt
Statt is an end-to-end AI workflow platform for public policy, government affairs, and regulatory teams, built on a proprietary policy-native dataset of 100M+ indexed documents across U.S. federal, all 50 states, the EU, and 100+ global markets. A dedicated forward-deployed engineer builds Statt around each customer’s own workflows, templates, and data, delivering relevant work products and integrations that give teams a 360-degree view of global regulation and legislation.