SB36 amends section 301 of the Congressional Budget Act of 1974 by adding two separate points of order. The first forbids Senate consideration of any measure that would reduce benefits under Medicare (title XVIII) or Social Security (title II), and the second forbids measures whose budgetary math relies on reducing Medicare outlays or increasing Medicare-related revenues to pay for unrelated provisions.
Both points of order can be waived only by a two-thirds affirmative vote.
The bill changes how the Senate enforces budget protections: it creates a procedural roadblock that raises the bar for legislation that trims benefits or repurposes Medicare savings. For legislative strategists, budget offices, and compliance teams, the bill alters what counts as an acceptable offset and makes CBO scoring central to blocking or allowing measures that affect Medicare finances.
At a Glance
What It Does
The bill inserts two new subsections into 2 U.S.C. 632 that (1) make it out of order to consider any Senate measure that would reduce Medicare or Social Security benefits, and (2) make it out of order to consider measures that use decreases in Medicare outlays or increases in Medicare revenues as offsets for non-Medicare provisions, with both rules waivable only by a two-thirds vote.
Who It Affects
The change directly affects Senators and Senate floor procedure, the Congressional Budget Office (which the bill names as the determiner of budgetary effects), and any legislation that proposes benefit reductions or uses Medicare savings as pay-fors—especially budget and finance committees, health policy drafters, and agencies implementing Medicare.
Why It Matters
The bill elevates program-level protections into enforceable Senate budget points of order, shifting the leverage in negotiations over deficit reduction and health-policy trade-offs. It makes CBO scoring of Medicare effects a procedural trigger and narrows permissible budget offsets, altering how drafters structure cost-saving provisions.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB36 writes two procedural guardrails into the Congressional Budget Act. The first is categorical: if a bill, amendment, motion, or conference report would reduce benefits under Medicare (title XVIII) or Social Security (title II), the measure is not in order on the Senate floor.
The second guardrail targets how sponsors finance new measures: if the Congressional Budget Office finds that a proposal’s total budgetary effects rely on decreasing Medicare outlays or increasing Medicare-related revenues to pay for portions of the measure that are not aimed at carrying out Medicare, then that proposal is likewise out of order.
Both points of order extend to the full range of floor actions—the underlying bill, amendments, motions, and conference reports—and both can be waived only by an affirmative two-thirds vote of duly chosen and sworn Senators. The second point of order adds a further procedural detail: sustaining an appeal of the Chair’s ruling on that point of order also requires a two-thirds vote, making it harder to overturn the Chair when the CBO’s score is used as the factual basis for the point of order.Practically, the bill places CBO scoring at the center of parliamentary enforcement.
Sponsors who plan to rely on Medicare savings as offsets will face an upfront procedural hurdle: if CBO attributes the offset to Medicare savings and those savings are not for carrying out Medicare itself, the point of order can remove the measure from consideration unless proponents can marshal a two-thirds majority. That shifts bargaining power on the floor and changes drafting incentives—legislators may avoid explicit Medicare offsets, seek different scoring treatments, or try to craft offsets that CBO will not attribute to Medicare.
The Five Things You Need to Know
Section 2 adds subsection (j) to 2 U.S.C. 632, making it out of order to consider any Senate measure that would reduce benefits under Medicare (title XVIII) or Social Security (title II).
Section 2 requires a two-thirds affirmative Senate vote to waive or suspend the point of order created by subsection (j).
Section 3 adds subsection (k) to 2 U.S.C. 632, barring consideration of measures whose CBO-determined budgetary effects use decreased Medicare outlays or increased Medicare revenues to offset costs of provisions not intended to carry out Medicare.
The subsection (k) point of order also can be waived only by a two-thirds affirmative vote, and an appeal of the Chair’s ruling on that point requires a two-thirds vote to sustain the appeal.
Both new points of order apply to bills, resolutions, amendments, motions, and conference reports and place the Congressional Budget Office’s scoring at the procedural trigger point.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title: Protect Our Seniors Act
This section names the statute the Protect Our Seniors Act. It has no substantive effect on procedure but provides the bill’s official citation for references in other documents and codification.
Absolute point of order against benefit reductions
This provision creates a categorical Senate point of order: any measure that would reduce Medicare or Social Security benefits is not in order. It covers the substantive benefit reductions themselves and extends to all floor vehicles—amendments, motions, and conference reports. The practical implication is that proposals that explicitly cut beneficiary payments, eligibility, or indexed benefits will be blocked procedurally unless two-thirds of the Senate vote to waive the point of order. That moves protection for benefit levels from political negotiation into a parliamentary enforcement tool.
Point of order against using Medicare savings as offsets
This provision bars consideration of measures for which the Congressional Budget Office determines that the total budgetary effects rely on decreasing Medicare outlays or increasing Medicare-related revenue to offset costs of provisions not for carrying out Medicare. In short, sponsors cannot lawfully use projected Medicare savings as pay-fors for unrelated programs if CBO attributes those savings to Medicare. The text ties the procedural trigger to CBO’s determination and builds in a two-thirds threshold to waive or to sustain an appeal of the Chair’s ruling, making reliance on CBO scoring an enforceable floor obstacle and heightening the stakes of how savings are documented and described in legislative text.
This bill is one of many.
Codify tracks hundreds of bills on Healthcare across all five countries.
Explore Healthcare in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Medicare and Social Security beneficiaries — The point of order protects benefit levels by making explicit cuts procedurally out of order unless two-thirds of the Senate agrees to waive the rule.
- Senior advocacy organizations — Groups that lobby to preserve benefits gain an additional procedural mechanism they can invoke when opposing legislation that would reduce benefits or repurpose Medicare savings.
- Senators who prioritize program-level protections — Lawmakers who want to shield beneficiaries obtain leverage on the floor because a supermajority will be needed to pass measures that cut benefits or rely on Medicare offsets.
Who Bears the Cost
- Senators seeking to enact deficit-reduction or reallocation plans that rely on Medicare savings — The point of order limits a common class of offsets and raises the vote threshold for such strategies, reducing legislative flexibility.
- Legislative drafters and budget offices (including CBO) — Bill drafters will need to anticipate and avoid CBO attributions that trigger the point of order, increasing complexity; CBO’s scoring decisions become central and more contested.
- Committees and agencies proposing structural Medicare changes — Proposals that alter payment models, eligibility rules, or benefit design but are intended to reallocate savings could be procedurally blocked even if sponsors argue the savings are for broader health-system reforms.
Key Issues
The Core Tension
The central tension is between locking in beneficiary protections via hard parliamentary rules and preserving the Senate’s flexibility to use program savings—including from Medicare—to pay for other priorities or to pursue structural reforms; protecting benefits makes some fiscally consequential policy routes effectively off-limits unless a supermajority agrees.
SB36 converts program-protection goals into procedural constraints, and that conversion raises several operational questions. First, the bill makes CBO scoring the factual predicate for the subsection (k) point of order; disputes about CBO methodology or attribution—what counts as a Medicare outlay decrease versus savings tied to a broader health reform—are likely to produce repeated Chair rulings and appeals.
The bill requires two-thirds to sustain an appeal under subsection (k), which ratchets up the political cost of contesting CBO’s judgment but does not resolve technical disagreements about scoring boundaries.
Second, the phrase that bars offsets unless they are “for the purpose of carrying out those programs” creates interpretive ambiguity. Does investing Medicare savings in a targeted program that reduces long-term Medicare demand qualify?
Could sponsors re-label offsets to avoid CBO attribution? Those are practical drafting and enforcement problems that the bill does not resolve, and they could incentivize sponsors to design more opaque financing structures.
Finally, the high waiver threshold protects beneficiaries but also limits the Senate’s ability to pursue deficit reduction through programmatic savings or to implement structural reforms that may reduce outlays while improving system efficiency; the bill thus creates a trade-off between program stability and fiscal maneuverability.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.