On Jan. 14, 2026, House leaders moved H.R. 7006 from floor setup to final passage in a single sequence of recorded votes. The day started with a narrow procedural win, included two failed amendment attempts, and ended with broad bipartisan passage. For readers tracking how appropriations bills actually move, this is a useful case: the amendment coalition was narrow, but the final coalition was much wider.

213-210
Rule vote passed (House Roll Call 25)
341-79
Final passage passed (House Roll Call 28)
2
Amendments failed before final vote

What H.R. 7006 does in plain English

H.R. 7006 is an appropriations vehicle for fiscal year 2026 that covers Financial Services, General Government, and State Department-related funding lanes. In plain terms, it is a funding bill, not a policy-only resolution. That matters because appropriations votes often build broader final coalitions even when interim amendments split the chamber.

The official bill page and text are published on Congress.gov, where readers can review version history and language directly: bill page and bill text.

The four-vote sequence in one floor window

Step 1: Rule adoption. The House first adopted H.Res. 992 in Roll Call 25 by 213-210. The rule set terms for floor consideration of H.R. 7006. According to the House Clerk record, this was a near-perfect party-line procedural vote, with Republicans voting yes and Democrats voting no, plus eight not voting.

Step 2: Roy amendment vote. In Roll Call 26, an amendment by Rep. Chip Roy (R-TX) failed 163-257 (with one present), showing support but not enough to reframe the underlying package.

Step 3: Crane amendment vote. In Roll Call 27, an amendment by Rep. Eli Crane (R-AZ) failed 127-291, an even wider rejection margin.

Step 4: Final passage. The chamber then voted on final passage in Roll Call 28, passing H.R. 7006 by 341-79.

Why final passage was broader than amendment support

The final vote coalition was bipartisan. House Clerk totals for Roll Call 28 show Republicans at 188 yea / 22 nay, Democrats at 153 yea / 57 nay, and 11 not voting overall. That mix can happen on appropriations when members who disagree with some provisions still back moving a funding package forward.

Put differently, the House rejected narrower amendment pathways, then accepted the broader bill framework. The data point for accountability readers is not just “passed,” but how it passed: after failed attempts to alter it and with substantial cross-party support in the closing vote.

What happened next and why H.R. 7148 appears in timelines

GovTrack’s timeline for H.R. 7006 notes that later “final bill” activity appears on a related vehicle, H.R. 7148. This is a process point, not a contradiction. Congress often uses related legislative vehicles as negotiations evolve across chambers.

The key takeaway for this article remains the House floor record on Jan. 14: one rule vote, two failed amendments, one successful final passage vote, all source-linkable to official roll-call pages.

How to verify every number yourself

If you want to replicate this breakdown, start with the four Congress.gov roll calls (25 through 28), then compare against the House Clerk vote pages for line-by-line party and member totals. Finally, use the bill page and text page to confirm scope and status.

This is the core CVT method on vote explainers: keep the narrative plain-English, keep the math transparent, and link every key number directly to an auditable source page.

H.R. 7006 vote math at a glance

VoteQuestionResultCongress.gov Link
Roll Call 25Rule (H.Res. 992)Passed 213-210View
Roll Call 26Roy AmendmentFailed 163-257View
Roll Call 27Crane AmendmentFailed 127-291View
Roll Call 28Final PassagePassed 341-79View

Why this sequence matters for public accountability

Vote explainers are most useful when they separate procedural leverage from final policy coalitions. In this case, the gap between the 213-210 rule vote and the 341-79 final vote tells readers something concrete: a bill can begin on a narrow partisan track, then end with broad support once amendment fights conclude.

It also shows why looking only at one tally can mislead. If someone saw only the rule vote, they might describe this as strictly partisan. If someone saw only final passage, they might miss the failed efforts to rewrite the measure first. The full sequence gives a more accurate picture of how members positioned themselves at each step.

For constituents, this is actionable data. You can check whether your representative supported the rule, supported or opposed specific amendments, and then compare that to their final vote on passage. The House Clerk pages list each member vote, while the linked Congress.gov roll calls provide the canonical roll-call references used throughout this article.

As this bill moved forward, the related-vehicle note tied to H.R. 7148 is another reminder that legislative pathways can shift after initial passage. Tracking that shift with source links, rather than assumptions, helps readers follow what changed, when it changed, and where the final legal text was ultimately advanced.