Fiscal commentary, graduate seminars, and committee staff rooms return to a single comparison, sequestration against pay-as-you-go, as if the two terms named rival instruments built for the same job. Students meet the pair in textbooks, staff meet the pair in drafting sessions, and commentators meet the pair whenever a deficit debate turns from promises to enforcement. The comparison sounds tidy, and the tidiness misleads. Sequestration names a remedy, an automatic cancellation of budgetary resources that follows a measured breach of a fiscal rule. Pay-as-you-go names a rule, a requirement that legislated changes to mandatory spending and revenues not increase the deficit. Placing a remedy beside a rule produces confident verdicts about toughness that the statutes do not support, because the severity of a cancellation says nothing about the standard the cancellation serves, the moment the breach gets measured, or the accounts the cancellation reaches. The architecture that joined the pair appears in the guide to the Budget Enforcement Act, the statute that first paired discretionary spending caps with the pay-as-you-go scorecard and placed the same remedy behind each instrument.

The confusion matters because enforcement history reads differently once rule and remedy stand apart. A cancellation that enforced fixed deficit targets belongs to a different design from a cancellation that enforced an appropriations cap, and both differ from a cancellation that was supposed to enforce a cumulative scorecard. The Gramm-Rudman-Hollings guide traces the first sequester design, in which the remedy stood behind deficit targets that Congress set in 1985 and revised in 1987 after the Supreme Court decision in Bowsher v. Synar moved the trigger determination to the Office of Management and Budget. Against that history, cap sequesters were ordered and executed, while a pay-as-you-go sequester was never carried out under either statutory regime, because Congress excluded, shifted, or zeroed scorecard debits before an order could issue. A reader who treats the remedy as the rule misses that record entirely. A reader who separates the two can ask the question that decides the comparison, whether the accounts exposed to cancellation are the accounts controlled by the decision the rule polices.

A Rule and a Remedy, Not Two Rules

Comparison fails at the first step when the objects compared belong to different categories. Sequestration and pay-as-you-go are routinely placed side by side as if each named a competing standard of fiscal discipline, a competing test that enacted law either passed or failed, or a competing philosophy of deficit control. That placement contains a category error. One term names a remedy that operates after a breach has been measured. The other term names a rule that defines the breach in the first place. A remedy answers a question about consequence, namely what happens to budgetary resources after a standard has been violated. A rule answers a question about obligation, namely what enacted law was required to achieve.

Sequestration, in the statutory sense, is an automatic cancellation of budgetary resources ordered by the President on calculations prepared by the Office of Management and Budget. The authority for the cancellation rests in the Balanced Budget and Emergency Deficit Control Act of 1985, as amended, classified at 2 U.S.C. 900 to 907d. The Congressional Research Service and the Congressional Budget Office both describe the mechanism in those operational terms, as a cancellation that takes effect through an order rather than through a new statute repealing earlier law. The order follows a determination that a defined limit has been exceeded or that a defined scorecard balance has moved into debit. The cancellation then reduces the resources available in affected accounts by a calculated amount.

Pay-as-you-go, by contrast, names a rule about the content of legislation itself. The rule requires that legislated changes to mandatory spending and to revenues, considered together as enacted law records them, not increase the deficit. The requirement was first imposed by the Budget Enforcement Act of 1990, enacted as Title XIII of the Omnibus Budget Reconciliation Act of 1990, Public Law 101-508. That statutory regime expired on September 30, 2002, together with the discretionary spending caps that the same act had established. The requirement returned in statutory form through the Statutory Pay-As-You-Go Act of 2010, Public Law 111-139, signed on February 12, 2010. The Office of Management and Budget maintains the official scorecards under section 4(d) of the 2010 act and issues an annual pay-as-you-go report shortly after a session of Congress ends.

Across four decades, one remedy enforced three different rules. The first rule consisted of fixed deficit targets established under the framework associated with Gramm-Rudman-Hollings in the Balanced Budget and Emergency Deficit Control Act of 1985 and revised in 1987. The second rule consisted of discretionary spending caps, first imposed by the Budget Enforcement Act of 1990, extended in 1993 and in 1997, allowed to expire in 2002, and later replaced by a new cap regime under the Budget Control Act of 2011, Public Law 112-25. The third rule was the pay-as-you-go scorecard requirement, created by the Budget Enforcement Act of 1990 and restored by the Statutory Pay-As-You-Go Act of 2010. The same word, sequester, described the cancellation that followed a breach in each setting, even though the standard breached, the decisions policed, and the accounts exposed differed in each setting. Calling an action a sequester therefore says nothing, without further specification, about which rule the action enforces.

Confusion persists in part because fame attaches unevenly to the parts of the enforcement system. The remedy has a distinctive and memorable name, a visible date on which an order takes effect, and a set of percentage reductions that translate readily into headlines about programs losing resources. The first sequester under the Gramm-Rudman-Hollings framework, in the amount of 11.7 billion dollars by an order effective March 1, 1986, gave the mechanism an early public identity. The sequester order of March 1, 2013, under the Budget Control Act, in the amount of 85.3 billion dollars, renewed that identity for a later generation of budget debate. Public memory therefore retains the sanction and forgets the standard, and later discussion asks whether sequestration worked without specifying whether the underlying test concerned a deficit target, an appropriations cap, or the cumulative effect of mandatory spending and revenue legislation.

Commentary compounds the confusion by treating the sanction as if the sanction were the standard. A debate framed as a choice between sequestration and pay-as-you-go in fact compares a punishment with one of several rules that the punishment has served. The comparison also distorts evaluation of severity. A harsh remedy attached to a narrow rule may bind lightly in practice, because the rule reaches few decisions or because the accounts available for cancellation bear little relation to the decisions that created a breach. A milder remedy attached to a well aligned rule may bind firmly, because the actors who make a decision also control the accounts that bear the consequence. Judging the remedy alone, without identifying the rule and without tracing the accounts exposed to the remedy, produces a verdict about a label rather than about an enforcement design.

Is sequestration a rule or a remedy?

Sequestration is a remedy, not a rule. A rule states what enacted law must achieve, while sequestration is the automatic cancellation of budgetary resources ordered after a rule has been breached. The cancellation enforces the rule without changing the rule itself or rewriting the underlying legislation that produced a deficit effect.

The direct answer carries a practical consequence for reading any enforcement episode. Identification of an episode requires three separate findings, stated in order. The first finding names the rule, whether a fixed deficit target, a discretionary cap for a defined category, or the pay-as-you-go requirement recorded on the scorecards. The second finding names the measurement, whether an appropriations total exceeded a cap for a single year or whether the cumulative effect of enacted legislation produced a debit at the end of a session of Congress. The third finding names the remedy, the presidential order canceling budgetary resources in nonexempt accounts by the percentage required to eliminate the measured excess or debit, subject to statutory exemptions and special rules.

Precise vocabulary sustains that structure, and the terms of art in federal budget enforcement each carry a defined operational meaning. Budgetary resources means the authority and amounts available to an account for obligation and expenditure, including new budget authority, unobligated balances carried from earlier periods, and other resources that statute makes available for a federal program or activity. A cancellation of budgetary resources reduces what an account may commit or spend. The reduction operates on availability rather than on the statutory language that created a program. An agency administering an affected account receives less room to obligate funds than the account otherwise would have held.

Direct spending, also called mandatory spending, means spending that flows from authorizing legislation and entitlement authority rather than from an annual appropriations act. Social Security benefits, Medicare payments, and other payments governed by eligibility rules and benefit formulas in permanent law fall within the category, as do other mandatory accounts that the Congressional Budget Office distinguishes from discretionary programs in budget presentations. The distinction matters for pay-as-you-go because the rule applies to legislated changes in direct spending and in revenues. A statute that expanded eligibility for a mandatory program or that altered a benefit formula changed direct spending, and the estimated effect entered the pay-as-you-go calculation. A statute that changed a tax rate or a revenue provision likewise entered the calculation.

Discretionary appropriations means budget authority provided in annual appropriations acts, together with the spending that follows from that authority, for programs whose funding Congress sets through the yearly appropriations process. Defense operations funded through annual acts, along with a wide range of domestic agency activities funded in the same manner, illustrate the category. The distinction between direct spending and discretionary appropriations explains why two kinds of sequester developed under the same statutory roof. A cap sequester policed discretionary appropriations against a cap for a defined category in a single year, measured when the appropriations cycle closed. A pay-as-you-go sequester policed enacted changes to direct spending and revenues, measured cumulatively at the end of a session.

A scorecard is the official ledger on which the Office of Management and Budget records the budgetary effects of enacted legislation for pay-as-you-go purposes. The Statutory Pay-As-You-Go Act of 2010 maintains two scorecards, a five-year scorecard and a ten-year scorecard, each accumulating the estimated effects of measures enacted during a session and carried under the statutory accounting rules. The Congressional Budget Office supplies cost estimates during consideration of legislation, and the Office of Management and Budget maintains the official scorecards that govern enforcement after enactment under section 4(d) of the 2010 act. The annual report issued shortly after a session ends states the balances that determine whether enforcement follows. The scorecard is a cumulative official record, built measure by measure across a session, against which the rule is tested once the session closes.

A debit is a negative balance on a scorecard, meaning that the cumulative recorded effect of enacted legislation increased the deficit over the scorecard period after offsets recorded on the same scorecard receive credit. If either scorecard shows a debit when the session-end accounting occurs, the statute directs the enforcement sequence that ends, absent intervening congressional action, in a presidential sequestration order under the Balanced Budget and Emergency Deficit Control Act. A debit is not itself a cut, a tax, or a program change. A debit is a finding that the rule has been breached by a stated amount, and the amount of the debit sets the amount that a subsequent cancellation must eliminate from nonexempt mandatory accounts if the order issues.

A uniform percentage reduction is the arithmetic device by which a sequestration order converts a total dollar amount into cancellations across the accounts exposed to the order. The Office of Management and Budget calculates the percentage that, applied uniformly to the budgetary resources of nonexempt accounts within the base available for cancellation, eliminates the required amount. Each exposed account then loses the same percentage of available resources, regardless of the size of the account, the merits of the program, or the relation of the account to the legislation that produced a breach. Special rules in section 256 of the Balanced Budget and Emergency Deficit Control Act, classified at 2 U.S.C. 906, cap Medicare benefit payment reductions at 4 percent under a statutory pay-as-you-go order and at 2 percent under the joint committee sequester that began on March 1, 2013. When a capped category absorbs less than a uniform share, the remaining nonexempt accounts absorb a recomputed and higher percentage.

The operation of the remedy also requires a plain statement of limits. A sequester cancels budgetary resources in accounts. A sequester does not repeal the legislation that created a deficit effect, and a sequester does not amend that legislation. A statute that expanded a mandatory program remains in law after an order issues, with eligibility rules and benefit formulas intact as enacted, even as the resources available in nonexempt accounts stand reduced by the cancellation. The order addresses the recorded consequence of enacted law by reducing resources elsewhere within the statutory base, rather than by rewriting the enacted law that produced the recorded effect. A sequester also does not claw back benefits already paid. Payments lawfully made before the cancellation remain paid, and the cancellation falls on resources available for cancellation at the time the order takes effect.

Institutional responsibility for the remedy reinforces the same point. Determination of whether a breach occurred and calculation of the required cancellation rest with the Office of Management and Budget, and the President issues the order on the basis of those calculations. The arrangement reflects a constitutional repair enacted after Bowsher v. Synar, in which the Supreme Court held in 1986 that the Comptroller General could not perform the trigger determination assigned under the original 1985 framework. The 1987 repair, Public Law 100-119, moved the determination to the Office of Management and Budget within the executive branch. The Congressional Budget Office estimates effects and reports on balances, and the Congressional Research Service explains the framework, while the executive calculation and the presidential order execute the remedy.

Exemptions define the ground on which the remedy can operate, and the ground has always been narrower than the mandatory budget as a whole. Section 255 of the Balanced Budget and Emergency Deficit Control Act, classified at 2 U.S.C. 905, lists programs and activities exempt from sequestration. Social Security benefits and Tier I railroad retirement stand exempt, net interest stands exempt, refundable tax credits stand exempt, and all programs administered by the Department of Veterans Affairs stand exempt under the controlling version of section 255(b) as the 2010 act left that provision, even though the 1985 original had exempted only veterans compensation and pensions. The Congressional Research Service, in In Focus IF11332, recorded that three quarters of all mandatory spending stood exempt from the mandatory sequester. The exemption structure means that a uniform percentage must be drawn from a base representing only a fraction of mandatory spending.

Trigger and target complete the opening framework. A cap sequester is triggered by appropriations exceeding a category cap in a single year, and the resulting cancellation falls within the category that breached, so that the appropriators who made the decisions policed by the cap confront a consequence inside the field of those decisions. A pay-as-you-go sequester is triggered by the cumulative budgetary effect of all enacted legislation recorded on the five-year and ten-year scorecards, measured at the end of a session of Congress, and the resulting cancellation falls on nonexempt mandatory accounts across the government, regardless of which legislation created the debit. The distance between decision and consequence, built into the design of the pay-as-you-go remedy, stands in sharp contrast to the shorter distance inside a category under a cap sequester.

Language discipline follows from the factual structure. References to sequestration should name the remedy and, where precision matters, the rule enforced in the episode under discussion. References to pay-as-you-go should name the rule and should reserve language of cancellation for the separate event that follows a session-end debit if an order issues. The Congressional Budget Office record through the end of the 2019 session showed that no sequestration had ever been triggered under the Statutory Pay-As-You-Go Act of 2010, even though the rule operated during drafting, during scoring, and during session-end accounting across the decade after enactment in 2010. A rule may therefore operate with real force while the remedy attached to the rule never executes, because Congress acted before an order issued through exclusions from the scorecards, through emergency designations under section 4(g) of the 2010 act, through shifts of recorded debits, and through statutory reductions of scorecard tallies to zero.

The evaluative standard for the comparison emerges from the structure described across the preceding paragraphs, and the standard can be stated as a namable claim for the enforcement design as a whole: “Align the cut with the decision.” Alignment means that the accounts exposed to cancellation are the accounts controlled by the decision that a rule polices, so that the actors whose choices create a breach also govern the field on which the consequence falls. Under a cap the cancellation fell inside the breached category, while under pay-as-you-go a cancellation, if ordered, spreads across an unrelated and heavily exempt mandatory base. Severity alone cannot distinguish strong enforcement from weak enforcement under that contrast, because a severe cancellation aimed at accounts disconnected from a decision gives the decision makers little direct reason to alter the decision. Alignment, rather than severity, determines whether a fiscal rule binds in practice, and the remainder of the comparison tests the historical record, the exemption structure, the Medicare caps, and the repeated congressional waivers against that single deciding factor.

One Remedy, Three Rules

A cancellation of budgetary resources can look deceptively simple from a distance. An order issues, accounts lose authority they had held, and spending capacity falls by a stated amount across a defined set of programs. The instrument retained a recognizable form across four decades because the form was never the hard part. Deciding what counted as a breach, who made the determination, when measurement occurred, and which accounts absorbed the loss required a rule, and the rule changed completely three times while the remedy carried its name and its mechanics from one regime into the next.

The legal home was the Balanced Budget and Emergency Deficit Control Act of 1985, classified at sections 900 to 907d of title 2 of the United States Code. Across these regimes, sequestration remained an automatic cancellation of budgetary resources rather than a rescission debated account by account. Automatic did not mean unmeasured or unconditional. A determination had to establish that a condition set by statute had been crossed, a calculation had to translate that crossing into a reduction amount, and an order had to apply the reduction to nonexempt accounts under formulas and special rules. The recurring order was the consequence, not the policy choice itself, and separating consequence from condition is the only way to follow the history without treating unlike episodes as repetitions of a single experiment.

The first rule asked the broadest question a budget process can ask. It asked whether the federal deficit itself had stayed within a ceiling fixed in statute for that year. No inquiry into a particular appropriations bill, tax provision, or mandatory spending law could substitute for that aggregate test, and no favorable result in one corner of the budget could cure an unfavorable total. The second rule narrowed the question sharply. It asked whether appropriations for a defined category had exceeded a cap for that category, and separately whether legislation enacted during a session had worsened the deficit on a scorecard recording its effects. The third arrangement, built in 2011, returned to caps while adding a trigger tied to the failure of a joint committee process, so that an order could follow from the collapse of a negotiated path Congress had established for itself.

That variation matters because a remedy acquires meaning from the discipline attached to it. A cut imposed for exceeding a deficit ceiling speaks to the whole fiscal stance of the government in a year when revenues, mandatory spending, appropriations, economic conditions, and prior law all contributed to the result. A cut imposed inside a single appropriations category speaks narrowly to the committees that wrote the bills in that category. A cut recorded against a scorecard speaks to legislated changes alone, excluding much of what moved the deficit for reasons outside the bills under review. The regimes did not share a theory of responsibility, and the history from 1985 through the extensions enacted in 2019 is largely a history of Congress revising that theory while keeping the cancellation device in reserve.

What rules has sequestration enforced?

Sequestration has enforced fixed deficit targets under Gramm-Rudman-Hollings, discretionary spending caps under the Budget Enforcement Act of 1990 and the Budget Control Act of 2011, and the pay-as-you-go scorecard requirement under both the 1990 act and the Statutory Pay-As-You-Go Act of 2010.

The first regime began with the statute commonly called Gramm-Rudman-Hollings, enacted as Public Law 99-177 and signed on December 12, 1985. The measure reached the President attached to an increase in the debt limit, a pairing that placed deficit control beside the borrowing authority required to finance obligations the government had already incurred. The statute wrote fixed maximum deficit amounts into law and set those amounts declining over a sequence of years. Each year carried its own ceiling, each ceiling sat below the one before it, and the remedy waited behind the figures if the measured deficit exceeded the amount allowed.

The opening measurement produced the first order under the act. That order, effective March 1, 1986, canceled 11.7 billion dollars in budgetary resources. Because the order took effect partway through the fiscal year, the reductions were prorated over seven twelfths of the year, compressing into the remaining months an adjustment that a full year order would have spread across twelve. Proration did more than change arithmetic. Automatic cancellation had moved from statutory description to executed order, at a scale visible across the government and under a rule that measured the deficit as a whole rather than any single bill or category.

A constitutional defect then interrupted the original design. In Bowsher v. Synar, cited as 478 U.S. 714 and decided in 1986, the Supreme Court found fault with the arrangement that placed the decisive determination in the Comptroller General. The problem concerned the officer assigned to execute the law and the constitutional position that officer occupied, rather than the existence of deficit targets as a legislative choice. Congress could set maximum amounts and prescribe a consequence for exceeding them, but the determination that set the consequence in motion had to rest with an officer whose role survived the separation of powers objection identified by the Court. The distinction preserved the remedy while disabling its first trigger mechanism.

Congress supplied that home in the 1987 repair, enacted as Public Law 100-119, which moved the determination to the Office of Management and Budget. The shift placed the calculation inside the executive branch office that stood at the center of budget formulation and execution, and it answered the defect identified in Bowsher v. Synar without abandoning fixed targets as the governing rule. The repair also formed part of a broader revision of the targets themselves. The amounts that had appeared fixed in the 1985 text were amended, and that amendment carried a lesson that recurred throughout the four decades. A legislature that writes a ceiling into statute retains the power to rewrite the ceiling by statute, and an automatic remedy behind an amendable target disciplines only for as long as the target holds.

In the event, the targets were amended and never met. The rule measured an outcome that no single actor controlled and that many forces outside the annual legislative process could move. When the outcome and the ceiling diverged, Congress faced a choice between accepting cancellations dictated by formula and revising the standard that produced them. Revision proved the chosen course, and once the standard moved, the remedy behind it lost the certainty offered as its chief virtue. The 1986 order had demonstrated that resources could be canceled, prorated, and applied under an enacted formula. The failure lay in the fit between a total outcome, influenced by the economy and by laws enacted across many years, and a fixed number that Congress had committed to in advance and then declined to defend.

The Budget Enforcement Act of 1990 replaced that theory with a more segmented one. Enacted as Title XIII of the Omnibus Budget Reconciliation Act of 1990, Public Law 101-508, the act divided enforcement into parts that corresponded more closely to the decisions that produced them. Discretionary spending, which Congress controls through annual appropriations, received caps. Legislated changes to mandatory spending and revenues, which Congress controls through authorizing and tax legislation, received the first pay-as-you-go rule and its scorecard. The cancellation remedy stood behind both parts, but the breach in each part was defined separately and the consequence in each part was located separately.

Under the 1990 act, discretionary caps were set within walled categories. A wall meant that room unused under one ceiling could not legitimate an excess under another, and an excess in one category did not draw its correction from accounts in a category that had stayed within its limit. If appropriations breached a category cap, a sequester was confined to the breaching category. Appropriators who wrote bills above a ceiling faced reductions in the same field of spending where the excess had occurred, while categories that had respected their ceilings were insulated from paying for a breach they had not committed. Measurement followed the appropriations cycle for a single year, and the question closed on whether the enacted total for that category had crossed the enacted cap for that category.

The record of the new cap regime included a small order that demonstrated the precision in practice. A cap sequester was ordered for fiscal 1991 to close a 395 million dollar breach in the international category. The amount stood in sharp contrast to the 11.7 billion dollars canceled in 1986, and the contrast was informative rather than embarrassing to the design. A breach measured within one walled category produced a correction sized to that category and to that category alone. The remedy had become narrower in that application, not because the formula had grown gentler but because the rule had grown narrower. Grouping the 1991 order and the 1986 order together under a single label, without naming the rule behind each, would miss the transformation the 1990 act accomplished.

Beside the caps, the 1990 act erected the scorecard for legislation. The pay-as-you-go requirement asked whether enacted changes to mandatory spending and revenues, taken together, increased the deficit over the periods the scorecard recorded. Discretionary appropriations were policed by the caps and stayed outside that test, because they already had a ceiling of their own. If the combined effect of enacted mandatory and revenue legislation produced a debit, the remedy waited behind that recorded result, measured at the end of a session of Congress rather than at the close of an appropriations cycle. Legislation accumulates across a session in separate measures passed at separate moments, and only a cumulative record could state whether the session as a whole had honored the requirement that new commitments and new tax reductions pay for themselves.

The 1990 settlement endured through extensions enacted in 1993 and in 1997 before reaching its statutory end. The caps and the pay-as-you-go rule expired on September 30, 2002. With the ceilings gone and the scorecard requirement gone, the remedy lost the rules that had given it work under that settlement, and a statute signed on December 2, 2002, Public Law 107-312, set the pay-as-you-go balances to zero as the regime ended, a closing entry whose fuller treatment belongs elsewhere in the comparison. Deficit targets had given way to caps and a scorecard, the replacement rules had operated for more than a decade through two extensions, and then both lapsed together at the end of fiscal 2002.

The Budget Control Act of 2011, enacted as Public Law 112-25, created a new cap regime for discretionary spending. The caps again supplied annual ceilings that appropriations were required to respect, and the cancellation remedy again stood behind a breach. Both regimes recognized that annual appropriations lend themselves to annual ceilings, both measured the breach within the discretionary field, and both assigned the consequence to the field where the excess occurred. The resemblance ended at the most consequential feature of the 2011 act, because the statute added a second and quite different path to an order, one that did not depend on appropriators exceeding a cap in the ordinary course of a session.

That second path ran through a joint committee. The Budget Control Act established a process under which a joint committee was charged with producing further deficit reduction, and failure of that process to deliver the contemplated result armed a sequester of its own. The trigger therefore recorded an institutional failure rather than a category breach. No single appropriations bill had to cross a ceiling, and no scorecard of enacted mandatory and revenue legislation had to close with a debit, for the prescribed cancellations to proceed. The statute converted the absence of an agreement into the event that measurement recognized. Deficit targets had judged an outcome. Caps had judged a category total. The joint committee trigger judged whether a procedure created by the same statute had succeeded, and it attached a predetermined cancellation to a negative answer.

The order that followed gave the 2011 regime a scale and a composition unlike either predecessor episode. On March 1, 2013, a sequester of 85.3 billion dollars issued under the Budget Control Act framework. The Government Accountability Office recorded in 2014 that the amount fell to 80.5 billion dollars after the fiscal 2013 appropriations act. A single episode can pass through an order, an adjustment, and a revised total without becoming two separate sequesters, and the Government Accountability Office account supplies the authority for the revised figure. Reductions within the episode fell across defense discretionary spending at 7.8 percent, nondefense discretionary spending at 5.0 percent, and Medicare at 2 percent, the capped rate for Medicare benefit payments under the joint committee sequester. An order born of a failed governmentwide bargain was never designed to confine itself to one appropriations category, and its incidence matched the breadth of the failure it answered.

Later legislation then tested the durability of the 2011 ceilings. The caps were raised by the Bipartisan Budget Acts of 2013, 2015, 2018, and 2019. The pattern recalled the amended deficit targets of the Gramm-Rudman-Hollings period in one respect and differed in another. It recalled the earlier period because a statutory ceiling again proved amendable by the institution that had enacted it, and the remedy again waited behind a line that moved. It differed because the caps retained their category structure and their measurement discipline for whatever ceiling stood in law in a given year.

The mandatory side of the Budget Control Act followed a longer timetable. Mandatory sequestration arising under the act was repeatedly extended, and under the Bipartisan Budget Act of 2019 the extension ran through fiscal 2029. Extension in that form carried consequences beyond the period in which the joint committee trigger had fired, so that the order of March 1, 2013 became not a single year correction but the opening of a prolonged schedule of reductions in nonexempt mandatory accounts. Medicare reductions within that schedule remained subject to the 2 percent cap for benefit payments under the Budget Control Act sequester, a ceiling distinct from the 4 percent ceiling that applied to Medicare under a statutory pay-as-you-go order, and keeping the two ceilings apart is essential to reading the period accurately. The Statutory Pay-As-You-Go Act of 2010, signed on February 12, 2010, had restored the scorecard rule in statutory form a year before the Budget Control Act was enacted, and its remedy shared a name with the 2013 order while answering to an entirely different trigger, a different measurement date, and a different distribution of the resulting cuts.

Viewed across the full span from 1985 to the extensions enacted in 2019, the sequence resolves into three rules wearing one remedy. Fixed deficit targets came first, survived a constitutional repair that moved their determination from the Comptroller General to the Office of Management and Budget, and ended in amendment without attainment. Discretionary caps came second, walled by category, paired with a scorecard for legislated changes, extended in 1993 and 1997, and expired on September 30, 2002. A new cap regime came third in 2011, joined to a joint committee trigger that produced the 85.3 billion dollar order of March 1, 2013, later recorded at 80.5 billion dollars, followed by four enacted raisings of the caps and an extension of mandatory sequestration through fiscal 2029. At every stage the cancellation itself remained recognizable. Resources were withdrawn automatically, by formula, from accounts the statute had not exempted, once a prescribed determination had been made. Nothing else remained constant. The quantity measured, the moment of measurement, the office responsible, the actors whose decisions were judged, and the accounts that paid all changed as Congress moved the same instrument from rule to rule, and any account of enforcement that names the remedy without naming its rule has described the weapon and omitted the law that aimed it.

Two Triggers: The Single Year and the Session

Every enforcement system has a moment at which a rule stops being a statement of intent and becomes a finding of fact. For the fiscal rules built around sequestration, that moment is the trigger, and the design of the trigger determines almost everything else about how the rule behaves. A trigger defines what gets measured, who does the measuring, when the measurement occurs, and which decisions are held responsible for the result. Two rules that share the same remedy can therefore operate in entirely different ways, because the path that leads to the remedy differs at each of those points. The discretionary spending caps audit one stream of decisions, the annual appropriations for a single fiscal year, against a fixed numerical limit for that year. The pay-as-you-go requirement audits a different object altogether, the accumulated budgetary record of legislation enacted across a session of Congress, recorded on scorecards that carry effects forward from one session into the next. The order that follows a breach looks the same in each case, an automatic cancellation of budgetary resources, but the finding that produces the order rests on a different measurement, taken at a different time, by a different route.

The cap trigger begins with the character of a discretionary spending cap itself. A cap is an annual limit on budget authority, set in law for a defined category of spending for a defined fiscal year. It governs the amount of budget authority that appropriations acts may provide within the category for that year, and compliance is therefore a comparison between two numbers that belong to the same year and the same category. One number is the ceiling written into statute. The other number is the total that the appropriations process actually enacted under that ceiling. Because both numbers are fixed once the appropriations cycle for the year has closed, the comparison can be made cleanly and finally, with no projection and no estimate of effects in later years. The question is narrow and factual, whether the enacted appropriations for the category exceeded the limit that governed them.

The Office of Management and Budget performs that measurement after the appropriations cycle for a fiscal year closes. The timing follows from the nature of the object being measured. A single appropriations act, taken alone, does not establish compliance or breach, because the category total depends on the full set of acts that provide budget authority within the category for the year. Only when the cycle has run its course can the totals be added and set against the cap. The final report for the year therefore serves as the measuring instrument, and the breach, if one exists, is certified against a completed record rather than against a partial tally or a forecast. The Congressional Research Service has described this architecture as one in which the enforcement measurement waits for the decisions it polices to be complete. Appropriators act during the cycle with knowledge of the ceiling, and the measurement that follows examines the finished product of that work, year by year, category by category.

A breach found in that measurement has a confined consequence, and the confinement is part of the trigger design. If appropriations in one category exceed the cap for that category, a sequestration order is required within days of the final report, and the order is confined to the category that breached. The cancellation falls on the accounts inside the limit that was exceeded, at a uniform rate calculated to eliminate the excess. A breach in one category does not authorize reductions in another category that stayed within its own limit, and a compliant year in one category does not offset an excess in another. The trigger, the finding, and the remedy all refer to the same bounded object, a single category in a single year. That boundedness gives the cap trigger its precision. The measurement identifies not only that a rule was broken but also where it was broken, and the remedy follows the finding to that location and no other.

Under the Budget Control Act of 2011, the same architecture ran with categories defined by function, a defense category and a nondefense category, each with its own statutory limit for each fiscal year. The structure of the trigger did not change when the categories changed. Compliance was measured year by year, after the appropriations for the year were complete, and a breach in either function required an order confined to that function. The 2011 act also carried statutory cap adjustments for designated categories of spending, and those adjustments refine the comparison without altering its character. Spending designated for overseas contingency operations, for example, sat outside the caps, so amounts provided under that designation did not count against the limits and could not by themselves produce a breach. The measured object was therefore not all discretionary budget authority enacted in a year, but the budget authority that the statute assigned to the capped categories, after designated amounts outside the caps had been set aside.

The annual character of the cap trigger also governs how a breach ages. A cap applies to a fiscal year, the measurement follows the close of that year’s appropriations cycle, and the resulting order addresses that year’s excess. The finding does not accumulate. A category that complied in one year carries no credit into the next year, and a category that breached in one year does not add its excess to the limit of the next. Each year begins with a fresh ceiling and ends with a fresh measurement, so the trigger operates as a repeating audit of a repeating decision. That rhythm, annual decisions tested by annual measurement, is the first half of the contrast, and it holds across both cap regimes, the Budget Enforcement Act caps that ran through 2002 and the Budget Control Act caps enacted in 2011.

The second half of the contrast has a longer history, because the institution that pulls the trigger was itself redesigned after a constitutional challenge. The original 1985 design of the Balanced Budget and Emergency Deficit Control Act assigned the trigger determination to the Comptroller General, the head of the Government Accountability Office, an officer situated within the legislative branch. In Bowsher v. Synar, 478 U.S. 714 (1986), the Supreme Court held that arrangement unconstitutional, on the ground that an officer answerable to Congress could not exercise the executive function of determining that an order must issue. The repair enacted in 1987 moved the determination to the Office of Management and Budget, an executive agency within the Executive Office of the President. That single change explains why an executive agency certifies breaches of rules that Congress wrote for itself. The limits and scorecard requirements remained statutory, but the act of finding a breach and setting the remedy in motion passed to the executive branch, where it remained through the regimes that followed.

The pay-as-you-go trigger measures something fundamentally different, and the difference begins at the moment a law is enacted rather than at the close of an appropriations cycle. Under the Statutory Pay-As-You-Go Act of 2010, every enacted law that affects mandatory spending or revenues is scored for its budgetary effects. The scoring attaches to legislation itself, measure by measure, as enactments accumulate. A tax provision that reduces revenues enters the record. A mandatory spending provision that increases outlays enters the record. A provision that reduces mandatory spending or raises revenues enters the record as an offsetting credit. The trigger therefore does not wait for a single category of decisions in a single process. It collects the effects of decisions made across every subject that touches mandatory spending or the revenue laws, and it holds those effects in a running account until the account is read.

The Office of Management and Budget maintains that running account on two scorecards, the five-year scorecard and the ten-year scorecard, under section 4(d) of the Statutory Pay-As-You-Go Act of 2010. Each enacted law’s budgetary effects are recorded on both scorecards, spread across the years the effects are estimated to cover, so the same enactment appears in two different spans of measurement at once. The dual structure matters because a law can look balanced across one span and unbalanced across the other. Provisions with effects concentrated in early years weigh differently on a five-year tally than on a ten-year tally, and provisions whose costs grow in later years register more heavily on the longer scorecard. The trigger reads both tallies, and a net debit on either one is enough. The design reflects the purpose of the rule, which is concerned not with a single year’s appropriations total but with whether legislated changes, taken together, worsen the deficit across the periods over which their effects unfold.

The annual pay-as-you-go report issues shortly after a session of Congress ends, and that report is the measuring instrument for the session. If either scorecard shows a net debit balance for the budget year, the President must issue a sequestration order against nonexempt mandatory spending. The sequence deserves attention because it separates the roles that the cap process combines. The Office of Management and Budget records the effects, maintains the scorecards, and reports the balances. The finding of a debit balance then obliges the President to issue the order. The remedy, as with the caps, is an automatic cancellation of budgetary resources, but the object canceled bears no necessary relationship to the legislation that created the debit, a distinction that belongs to the analysis of targets rather than triggers. For the trigger itself, the essential point is object and timing. The measured object is a cumulative balance, the residue of many enactments, and the moment of measurement is the end of a session.

What triggers a sequestration order?

A sequestration order is triggered when the Office of Management and Budget finds a breach: either appropriations for a fiscal year exceeding a discretionary cap in one category, or a net debit on either statutory PAYGO scorecard for the budget year at the end of a session of Congress.

The residue metaphor is exact, because the scorecards do not reset with each session in the way that caps reset with each year. Effects recorded in an earlier session remain on the scorecards and are carried forward, so a law enacted in one session can contribute to a debit balance read at the end of a later session. The trigger at the end of any given session therefore audits more than that session’s work. It audits the accumulated balance, which includes the recorded effects of laws passed in earlier sessions whose consequences were entered on the scorecards and held there. A session that enacted nothing with budgetary effects could face a debit balance inherited from the standing record, and a session that enacted offsetting savings could reduce a balance created by predecessors. The unit of account is not the session, and it is not the year. The unit of account is the scorecard itself, a continuing ledger that sessions add to and subtract from but do not own individually.

That ledger quality separates the two triggers at the level of responsibility as well as arithmetic. The cap trigger examines a decision stream that a defined set of actors controls within a defined period. Appropriations for a fiscal year are the work of the appropriations process for that year, the measurement follows immediately, and the finding names the category and the year in which the excess occurred. The pay-as-you-go trigger examines an accumulation that no single committee, session, or enactment controls. Tax legislation and mandatory spending legislation originate in different committees and move on different schedules. By the time the annual report reads the balance, the debits on it may trace to several enactments across several sessions, each scored at enactment and carried forward. The finding names a balance, not a decision. It establishes that the accumulated record is in debit for the budget year, without assigning the debit proportionally to the measures that produced it.

Timing sharpens the same contrast. The cap measurement follows the close of the appropriations cycle for the fiscal year under examination, and the required order follows within days of the final report, so the distance between the last decision in the audited stream and the enforcement finding is short. The pay-as-you-go measurement waits for the end of a session of Congress, which can fall many months after some of the enactments recorded during that session became law, and the balances it reads may include effects first recorded in sessions that ended earlier still. The appropriations trigger is therefore retrospective over a short and closed interval, one fiscal year’s enactments measured as that year is completed. The scorecard trigger is retrospective over an open and layered interval, in which the reading date is fixed by the congressional calendar while the contents being read accumulated over a longer period. A legislator voting on a mandatory spending bill early in a session acted without knowing the final balance that the full record, combined with carried balances, would produce when the report issued after adjournment.

The institutional paths differ in parallel with the timing. In the cap process, the Office of Management and Budget measures enacted appropriations against the statutory ceilings, and that measurement produces the finding from which the order follows. In the pay-as-you-go process, the same office maintains the scorecards as a standing record across sessions and issues the annual report after a session ends, and the obligation to issue the order falls on the President when a scorecard shows a debit for the budget year. After the 1987 repair that followed Bowsher v. Synar, both paths run through the executive branch, a legacy of the constitutional ruling. Yet the functions performed along those paths are not the same function performed twice. One is an audit of a completed annual process against a ceiling. The other is the custodianship of a continuing ledger, followed by a report that converts a ledger balance into a legal obligation.

The measured objects differ most of all, and that difference explains why the two triggers generate different kinds of pressure before either one fires. A cap is a bright numerical line attached to decisions that appropriators make in full knowledge of the line, and the closeness of appropriations to the cap can be tracked as the cycle proceeds, so a looming breach is visible to the actors who can prevent it by reducing amounts within the category. The scorecard balance, by contrast, is an aggregation of scored effects from enacted law, and prevention operates at a different point. Offsets must be written into legislation before enactment, or effects must be excluded or shifted by statute, because once an effect is recorded the balance moves only when another recorded effect moves it back. The Congressional Research Service and the Office of Management and Budget describe enforcement that begins from opposite ends of the legislative sequence. The caps test a total after a process concludes. The scorecard test accumulates entries from the moment each law is enacted and reads the total when a session concludes.

Set side by side, the two triggers share exactly one element, the remedy waiting at the end of each path. A cap breach produces a sequestration order confined to the breached category, calculated against a single year’s appropriations. A scorecard debit produces a sequestration order against nonexempt mandatory spending, calculated against a balance accumulated across enactments and sessions. Everything upstream of the order diverges. One trigger audits a single decision stream at the moment it closes, measured against a ceiling fixed for that year and that category. The other trigger audits the accumulated residue of every law enacted across an entire session, together with recorded effects carried forward from earlier sessions, and reads that residue on two scorecards spanning five years and ten years. The single year and the session are not two names for the same interval. They are two different theories of what a fiscal rule should examine, one fixed on a recurring annual process, the other fixed on the cumulative consequences of legislation whenever those consequences were enacted.

Where the Cut Falls

Two enforcement orders can carry the same legal name and produce opposite patterns of incidence. Sequestration describes an automatic cancellation of budgetary resources after a fiscal rule has been breached, but that description leaves open the decisive question of target. A remedy may fall on the accounts that produced the breach, on a defined half of the budget paired with another half, or on whatever accounts a statute has left exposed after exemptions have removed most of the budget from reach. Each design distributes pain differently and creates a different feedback loop for the legislators whose votes caused the breach. The comparison between cap enforcement and pay-as-you-go enforcement turns on that axis more than on any difference in arithmetic, because the arithmetic of a shortfall can be identical while the location of the reduction changes who learns from the event and who pays for it.

A cap sequester begins and ends inside a boundary drawn in advance. Discretionary caps under the Budget Enforcement Act divided appropriations into categories, and a breach of a category cap was closed by canceling resources within that same category. The category was the legal container within which appropriations had been provided and against which the Office of Management and Budget measured the completed appropriations cycle. If the total recorded for the category exceeded the cap, the excess defined the amount to be eliminated, and the accounts inside the category supplied the resources to be canceled. Accounts outside the boundary were not reached merely because resources existed there. Incidence followed membership in the breached category.

The fiscal 1991 order under the Budget Enforcement Act gives that principle a concrete scale. A sequestration order for fiscal 1991 closed a breach of 395 million dollars in the international category. The amount was small in relation to total federal spending, and the size was not accidental. The cut landed only where the overspending occurred, so the order had to recover only the amount by which that one category had passed its ceiling. A breach in a single category did not become an occasion for reducing unrelated domestic accounts, defense accounts, or mandatory programs that had played no part in the appropriations total. The narrowness of the base and the narrowness of the breach matched each other, which is why a genuine cap breach could produce an order measured in hundreds of millions rather than in tens of billions.

Other cap regimes divided the budget more coarsely, and incidence followed the coarser division just as faithfully. Under Gramm-Rudman-Hollings, which enforced fixed deficit targets, and under the Budget Control Act of 2011, which imposed a newer set of discretionary caps and then a further sequester after the joint committee process failed, the reduction was split between defense and nondefense. Within each side of that split, a uniform percentage reduction applied. The first Gramm-Rudman-Hollings order, effective March 1, 1986, canceled 11.7 billion dollars. The Budget Control Act order of March 1, 2013 canceled 85.3 billion dollars, with reductions of 7.8 percent for defense discretionary accounts and 5.0 percent for nondefense discretionary accounts, before the fiscal 2013 appropriations act brought the total down to 80.5 billion dollars, as the Government Accountability Office reported in 2014. The percentages differed between the two sides because the split assigned separate amounts to each side, but within a side the reduction did not select favored accounts for protection. The structure of the limit and the structure of the remedy were the same structure, expressed first as a ceiling and then as a percentage.

That correspondence between limit and remedy matters because of who writes the legislation on each side of the event. Appropriations bills are written by appropriators, operating through the appropriations process, within allocations that translate a cap into amounts for individual bills and accounts. When the finished bills exceed a cap, the accounts funded by those bills take the cut. The decision and the consequence therefore sit in the same hands, in the institutional sense that the process creating the breach and the process bearing the remedy are the same process. An appropriations subcommittee that pressed an account above the level the category could sustain knew the statutory neighborhood in which any resulting cancellation would fall. The feedback was imperfect, since a uniform percentage reached accounts that had grown modestly as well as accounts that had grown aggressively, yet the feedback stayed inside the community of decision makers who had produced the excess.

The pay-as-you-go design was built in the opposite direction. Under the Budget Enforcement Act version and under the Statutory Pay-As-You-Go Act of 2010, a debit arose from the cumulative budgetary effect of enacted legislation affecting mandatory spending and revenues, recorded by the Office of Management and Budget on five-year and ten-year scorecards and measured at the end of a session of Congress. The act that created the debit might be a tax statute that reduced revenues. It might be an authorizing statute that expanded a benefit, altered an eligibility rule, or changed a payment formula. The committees that drafted such legislation often controlled no mandatory accounts directly in the sense that appropriators control discretionary accounts, and some of the most consequential debits came from revenue provisions that corresponded to no spending account at all. A tax reduction widens the deficit from the revenue side, and the scorecard records that effect, but no appropriations category exists in which the resulting remedy can naturally land. The statute therefore had to find its remedy somewhere else, and somewhere else meant the pool of nonexempt mandatory accounts that the Balanced Budget and Emergency Deficit Control Act left available for cancellation.

Who bears the cost of a sequestration?

A cap sequestration is borne by the appropriations accounts inside the category that exceeded its cap, while a PAYGO sequestration is borne by nonexempt mandatory accounts across the government, including farm supports and Medicare payments, regardless of which legislation created the recorded debit on the scorecard.

That separation between cause and cost is the defining feature of a scorecard sequester. The remedy cancels resources in whatever nonexempt mandatory accounts exist, from farm supports to federal retirement administration to Medicare provider payments. Most of the accounts in that pool had no connection to the law that created the debit. A statute adjusting tax rates could leave a debit to be recovered from agricultural payments. An authorizing law expanding one program could leave a debit to be recovered in part from the administration of another program whose beneficiaries, eligibility rules, and payment structure the enacting committees had not touched. The connection between the law and the loss is purely accounting in character. Both appear in the same statutory ledger, first as a debit recorded against the scorecard and then as cancellations drawn from the exposed base, but accounting connection is not programmatic connection. Exposure, rather than responsibility, determined placement in the path of the remedy.

Because the target is a residual pool rather than a chosen set of accounts, a scorecard sequester cannot be aimed. The order does not revisit the legislation that created the debit and reduce its benefits, narrow its eligibility, restore its revenue loss, or suspend its effective date. The enacted law remains intact, with its provisions operating as Congress wrote them, while the cancellation reaches sideways into unrelated accounts. Nor does the order weigh the exposed accounts against one another by need, performance, or relation to the policy that caused the shortfall. Apart from statutory exemptions and special rules, the mechanism applies a uniform percentage to the available base, recomputed to produce the amount the scorecard requires. Aiming would require a judgment about which policy should give ground, and the automatic remedy exists precisely to avoid a further discretionary judgment after the rule has been breached. The price of that automatic character is blindness to connection.

Exemptions decide how concentrated that blindness becomes. Section 255 of the Balanced Budget and Emergency Deficit Control Act, classified at 2 U.S.C. 905, exempted Social Security benefits and Tier I railroad retirement benefits from sequestration. As the version of section 255 in force under the 2010 act provided, all programs administered by the Department of Veterans Affairs were also exempt, a broader protection than the 1985 original, which had exempted only veterans compensation and pensions. Net interest was exempt. Refundable tax credits were exempt. The Congressional Research Service, in In Focus IF11332, recorded that three quarters of all mandatory spending was exempt from the mandatory sequester, a share that included Social Security, veterans programs, net interest, refundable income tax credits, civilian and military retirement, federal-aid highways, unemployment compensation, and low-income programs including Medicaid, the Children’s Health Insurance Program, Supplemental Security Income, the Supplemental Nutrition Assistance Program, and Temporary Assistance for Needy Families. Taken together, the exemptions left only a small fraction of mandatory spending available to absorb a scorecard debit of any size.

A small base changes the character of the remedy even before any order issues. If the exposed accounts are few relative to the spending that the rule governs, a modest debit translates into a noticeable percentage reduction for those accounts, and a large debit translates into a percentage that the exposed programs may be unable to absorb without severe disruption to payments Congress had separately directed. The burden does not spread across mandatory spending in proportion to size, because three quarters of that spending sits outside the reach of the order. The burden concentrates. An account representing a minor share of mandatory spending can face a reduction out of all proportion to its place in the budget simply because neighboring accounts of far greater size hold statutory protection. Incidence becomes an accident of drafting history, reflecting which programs obtained exemptions in 1985, which protections later statutes broadened, and which programs were left exposed when the list settled. Exposure bears no systematic relation to the legislation whose effects the sequester exists to offset.

Medicare illustrates how a special rule can sharpen that concentration rather than relieve it. Under the special rules of section 256, classified at 2 U.S.C. 906, reductions in Medicare benefit payments under a statutory pay-as-you-go sequestration order are capped at 4 percent. That 4 percent ceiling must be kept distinct from the separate 2 percent cap that applied to Medicare benefit payments under the Budget Control Act joint committee sequester that began on March 1, 2013. The two percentages belong to two different orders enforcing two different rules, and merging them misstates both regimes. When the uniform percentage needed to clear the debit exceeds 4 percent, Medicare pays at the capped rate and stops there, and the remainder is recovered from the other nonexempt accounts at a recomputed, higher percentage. Protection for the largest exposed program therefore deepens the cut for every smaller exposed program. The total must still be produced, the capped account contributes less than the uniform rate would have taken, and arithmetic assigns the difference to whatever remains exposed.

The same structure lets a committee create an enormous debit while the accounts governed by its own legislation sit exempt or untouched. A revenue measure can reduce receipts by an amount that dwarfs the exposed mandatory base without placing any account under the drafting committee’s jurisdiction at risk, because revenue provisions have no accounts to cancel. An authorizing measure can expand a program that section 255 protects, record a substantial cost on the scorecard, and leave the recovery to fall on farm supports, administrative accounts, Medicare providers operating under the 4 percent ceiling, and the other members of the residual pool. The remainder of the recovery is exported to constituencies that received nothing from the legislation. Exporting the cost weakens the signal that the scorecard was supposed to send at the moment of drafting, because the legislators weighing a costly provision could know that the statutory remedy, if ever allowed to operate, would collect most of the bill from programs outside the bargain being struck.

Appropriations enforcement sends the opposite signal, and the contrast explains why the location of the cut matters for behavior as well as for fairness. An appropriator weighing a bill against a cap confronts a remedy that will return to the appropriations accounts as a class. Yet the community that drafted the bills and the community that administered the reduced accounts overlapped heavily, and the political complaints generated by the reductions arrived at the same committees that had written the appropriations. Under a scorecard regime, complaints about a canceled farm payment or a reduced provider payment arrive as consequences of a ledger, but the legislative act that filled the ledger may have been a tax bill or an authorization considered in a different committee room, under a different coalition, for reasons unrelated to the programs absorbing the loss. Traceability fades with each step between enactment and remedy, and faded traceability makes the remedy easier to disown and harder to use as a guide for the next drafting decision.

The limits of a sequester define the target question from another direction, because a cancellation reaches only a specific kind of budgetary resource and leaves several large elements of the deficit untouched by design. A sequester does not reduce net interest. Interest on the federal debt is exempt under section 255, so the cost of borrowing already undertaken continues regardless of the size of an order. A sequester also does not cancel obligations already incurred for exempt programs. Benefits and payments that an exempt program owes under its governing statute remain obligations of the government, outside the cancellation, however large the scorecard debit grows. For the programs listed in section 255, the exemption removes the obligation itself from the remedy, so a sequester can run alongside undiminished payment streams that account for most of mandatory spending. What remains reachable is budgetary resources in nonexempt accounts, the authority to incur obligations and make payments that the order cancels before that authority is exercised.

That distinction between budgetary resources and outlays governs how a sequester appears in the deficit during its first year. A cancellation reduces budget authority, meaning the permission an account holds to enter obligations that will result in spending. Outlays, the payments that actually leave the Treasury and enter the deficit calculation, follow obligations according to the rhythm of each program. Cancelling a dollar of budget authority therefore does not cancel a dollar of outlays in the same year in every account. The first-year outlay effect of an order is smaller than its budget authority effect because a portion of the canceled authority would not have converted into payments until later years, and obligations already validly incurred before the order follow their own payment schedules. The remedy was designed to cancel resources, and the lag between resources and outlays is a property of how federal spending moves from enacted authority through obligation to payment.

Viewed along the target axis, the two applications of one remedy describe two different theories of enforcement. Cap enforcement locates the loss where the excess was recorded, narrowly in the fiscal 1991 international category, more broadly across a defense or nondefense side under Gramm-Rudman-Hollings and the Budget Control Act, but always within a boundary that the breached rule itself had drawn. The appropriations process that exceeded the boundary absorbed the correction, and the correction carried information back to the participants who had exceeded it. Pay-as-you-go enforcement locates the loss in a residual pool defined by exemptions, a pool dominated by accident of statutory protection, capped at 4 percent for Medicare under a statutory order, and largely disconnected from the tax and authorizing legislation whose cumulative effects filled the scorecard. Farm supports and Medicare provider payments stand in that pool not because the programs caused a debit but because earlier Congresses left the accounts exposed while shielding three quarters of mandatory spending. The place where the cancellation lands decides whether the order reads as a correction delivered to the decision that failed or as a levy collected from bystanders whom the statute happened to leave within reach.

The Exemption Problem

The pay-as-you-go rule was policed by a remedy that could reach only a minority of the spending it governed. A pay-as-you-go sequester operated under a different geometry. The debit that triggered the order arose from the cumulative budgetary effect of enacted legislation, recorded by the Office of Management and Budget on five-year and ten-year scorecards and measured at the end of a session of Congress. The cancellation that answered the debit fell on nonexempt mandatory accounts across the government, regardless of which legislation had created the debit and regardless of whether an account ordered to absorb a reduction had contributed to the recorded shortfall. Before any percentage was calculated, the statute removed most mandatory spending from the field of action altogether. The exemptions in section 255 of the Balanced Budget and Emergency Deficit Control Act therefore determined the size of the base, the size of the base determined the percentage any given debit would require, and the required percentage determined whether the order could ever be issued in practice.

Section 255, codified at 2 U.S.C. 905, performed that determination by category rather than by a general standard. The provision did not ask whether a program was large, whether a program was growing, or whether a program had been altered by the legislation that produced a scorecard debit. The provision listed programs and categories of payment that sequestration could not touch. Each exemption protected a named commitment on its own terms, for reasons that made sense at the level of the individual program, and the aggregate effect emerged from accumulation rather than from a single decision about how much of the budget enforcement should be able to reach. No provision of section 255 stated a target share of mandatory spending to remain available for cancellation. The statute fixed a set of protected categories in 1985 and amended that set in later enactments, most consequentially in the Statutory Pay-As-You-Go Act of 2010, while spending inside the protected categories moved according to law and economic conditions that the exemption list did not govern.

Social Security benefits stood at the head of the protected categories, joined by Tier I railroad retirement benefits. The pairing reflected the treatment of the two programs as earned retirement income in payment rather than as ordinary mandatory outlays available for automatic reduction. Social Security was the largest single component of mandatory spending in the decades governed by the 1990 and 2010 versions of the rule, so exempting Social Security benefits alone removed a very large share of the mandatory total from the base before any other exemption was counted. The railroad retirement exemption operated on the same principle at a smaller scale, protecting the tier of benefits that corresponded most closely to Social Security within a separate retirement system for a single industry. Every dollar of benefit payment placed beyond the reach of an order was a dollar that could not contribute to closing a scorecard debit, and the remaining base began as a fraction of the whole rather than as the whole minus a margin.

Programs administered by the Department of Veterans Affairs occupied a broader protected position under the text as amended in 2010 than the position the original 1985 enactment had given them. The Balanced Budget and Emergency Deficit Control Act as enacted in 1985 exempted veterans’ compensation and pensions, the benefit payments owed to veterans for service-connected disability and to eligible survivors and low-income wartime veterans. Programs administered by the department beyond those benefit categories did not receive the same complete protection under the original listing. The Statutory Pay-As-You-Go Act of 2010, signed on February 12, 2010, produced a version of section 255 under which all programs administered by the Department of Veterans Affairs were exempt. The Congressional Research Service recorded that reading as the controlling one, with the 2010 act version of section 255(b) governing the question. A Government Accountability Office legal opinion reinforced the result, resolving a conflict between section 255 and the special rules in section 256 in favor of the exemption. Neither the amendment nor the legal opinion involved a calculation of how much sequestration base the broader exemption surrendered.

Net interest and refundable tax credits completed a structure that protected the financial obligations of the government and a class of payments delivered through the tax code. Net interest, the cost of servicing debt already incurred, was exempt because a sequestration order could not reduce the obligation itself. Interest owed on outstanding Treasury securities arose from borrowing decisions already made, and canceling budgetary resources assigned to interest payment would not have reduced the amount owed. Exclusion of net interest followed from the nature of the payment rather than from a judgment about the size of the federal debt, and the exclusion removed another substantial component of mandatory spending from the base. Refundable tax credits stood on different ground. The refundable portion of a credit produced payments to taxpayers in excess of tax liability, functioning as spending administered through the revenue system, and section 255 exempted those payments. A channel through which Congress delivered substantial assistance to low-income households therefore sat outside the remedy, even when legislation affecting the tax code contributed to a scorecard debit on the revenue side.

Why is so much spending exempt from sequestration?

Most mandatory spending pays benefits already in payment, interest on debt already incurred, or subsistence support for low-income households. Congress exempted those categories in section 255 because cutting them automatically would break commitments, raise borrowing costs, or remove basic support without a deliberate vote on the underlying programs themselves.

The Congressional Research Service, in In Focus IF11332, measured the accumulated result of the section 255 list and recorded that three quarters of all mandatory spending was exempt from the mandatory sequester. A sequestration order enforcing a scorecard debit did not draw on mandatory spending as a whole. The order drew on the quarter of mandatory spending that the exemption list had left available, and within that quarter the order encountered the special treatment of Medicare under section 256, which limited the contribution of the largest program remaining in the base. Three quarters is not a marginal carve-out at the edge of a budget, and a remedy confined to the remaining quarter operated on a base whose relationship to the scale of legislated deficit effects was weak from the start. The aggregate rested on the combined weight of retirement benefits, health programs for low-income households, veterans’ programs, interest, and the other protected categories acting together.

The exempt categories named by the Congressional Research Service included the principal low-income and social insurance programs of the federal government. Medicaid, the health coverage program for low-income individuals that the federal government and the states financed jointly, was exempt. The Children’s Health Insurance Program, which extended health coverage to children in families with incomes above the Medicaid threshold, was exempt. Supplemental Security Income, which paid cash assistance to aged, blind, and disabled individuals with limited income and resources, was exempt. The Supplemental Nutrition Assistance Program, which provided food assistance to low-income households, was exempt. Temporary Assistance for Needy Families, the block grant program that replaced Aid to Families with Dependent Children in 1996 and funded cash assistance and related services, was exempt. Unemployment compensation, which replaced a portion of wages for workers who lost employment, was exempt. Civilian and military retirement, which paid earned pensions to former federal employees and former members of the armed forces, was exempt. Federal-aid highways, a mandatory spending category that supported the surface transportation system, was exempt.

Those exemptions reflected judgments that automatic cancellation was the wrong instrument for the programs in question. Medicaid and the Children’s Health Insurance Program delivered health coverage to populations whose eligibility rested on low income, and a uniform percentage reduction would have reduced payments within programs whose costs followed the health needs of enrolled individuals rather than a fixed annual allotment. Supplemental Security Income and Temporary Assistance for Needy Families delivered cash assistance at levels tied to subsistence, and the Supplemental Nutrition Assistance Program delivered food assistance on the same basis. A reduction of a few percentage points in a subsistence benefit represented a direct reduction in the income or food purchasing power of households with the least capacity to replace the loss from other resources. The exemption of those programs recorded a deliberate preference for protecting basic support over preserving the breadth of the sequestration base.

Medicare occupied a position unlike any other program in the enforcement structure, because Medicare was neither exempt under section 255 nor exposed to the full uniform percentage that a sequestration order applied to other nonexempt accounts. The special rules of section 256, codified at 2 U.S.C. 906, governed the treatment of Medicare and placed a ceiling on the reduction in Medicare benefit payments under a sequestration order. One judgment treated Medicare as too central to the federal budget for complete exemption, since exempting the second great health and retirement program alongside Social Security would have shrunk the available base toward practical insignificance. The other judgment treated Medicare benefit payments as unsuited to an uncapped automatic reduction, since payments governed by statutory payment systems would transmit a large uniform cut directly into the financing of care for elderly and disabled beneficiaries. Medicare stayed in the base and contributed to closing a debit, at a rate the statute capped below whatever uniform percentage the arithmetic of the order otherwise produced.

The ceiling on Medicare reductions took two distinct values under two distinct legal authorities, and keeping the two values separate was essential to the comparison between the enforcement regimes. Under the joint committee sequester created by the Budget Control Act of 2011, the sequester that began with the order of March 1, 2013, reductions in Medicare benefit payments were capped at 2 percent. That 2 percent figure belonged to the enforcement regime of the 2011 act, and the figure appeared in the March 1, 2013 order alongside reductions of 7.8 percent in defense discretionary accounts and 5.0 percent in nondefense discretionary accounts. Under a sequestration order issued to enforce the Statutory Pay-As-You-Go Act of 2010, by contrast, reductions in Medicare benefit payments were capped at 4 percent under the special rules of section 256. That 4 percent figure belonged to the scorecard remedy, the enforcement path that followed a debit recorded by the Office of Management and Budget at the end of a session. Merging the two figures into a single general statement about Medicare and sequestration erased the distinction between the regimes and misstated both. The cap that applied depended on the rule being enforced, and the identity of the triggering rule determined the treatment of the largest program left in the mandatory base.

The cap on Medicare, at either value, interacted with the exemption structure to concentrate a pay-as-you-go sequester on the accounts least able to spread the burden. When the uniform percentage required to close a debit exceeded the Medicare ceiling, Medicare paid at the ceiling rather than at the uniform percentage, and the shortfall between the amount the uniform percentage would have collected from Medicare and the amount the ceiling allowed did not disappear. The statute recomputed the percentage for the remaining nonexempt accounts, raising the rate applied to every other account in the base so that the total cancellation still equaled the debit. Medicare was large relative to the rest of the nonexempt mandatory base, so holding Medicare below the uniform percentage shifted a substantial amount of required savings onto a comparatively small set of programs. The concentration compounded at larger debits, because the Medicare ceiling fixed the contribution of the largest remaining program while the residual accounts carried the entire increase. A mechanism described in general terms as a uniform percentage reduction therefore produced a steeply nonuniform result, with the deepest percentage cuts falling on the smallest and least protected corner of the mandatory budget.

The arithmetic that followed from the exemption list and the Medicare ceiling explained, at the level of mechanism, why no pay-as-you-go sequester was ever allowed to occur under either the 1990 regime or the 2010 regime. The base was roughly one quarter of mandatory spending before the Medicare ceiling limited the contribution of the largest program inside that quarter. A tax measure or a health measure of the scale Congress enacted in the decades after 1990 could record scorecard effects that were large in absolute terms, measured across five-year and ten-year scorecards, without any single provision approaching the size of the exempt programs. Collecting such a debit from the residual base required a percentage reduction far above the single digit rates associated with the Budget Control Act sequester of 2013. At moderate debits the recomputed percentage on nonexempt accounts reached levels that would have eliminated substantial shares of the affected programs in a single order. At larger debits the required percentage approached or exceeded the total resources the base contained, so that even canceling every available dollar in the nonexempt accounts would not have closed the recorded debit. A remedy that demands confiscatory reductions from a narrow set of accounts, or that cannot satisfy the recorded amount by any reduction the base can yield, presents an outcome that cannot be executed as written.

That record requires no recourse to explanations based on motive, cowardice, or hypocrisy. The consistent refusal, across Congresses controlled by different parties and across two separate statutory versions of the pay-as-you-go rule, to permit a scorecard sequester followed from the structure of the remedy rather than from a failure of nerve that recurred by coincidence over three decades. A legislature facing a cancellation concentrated by exemption and recomputation on a residual base faced a situation in which allowing the order to issue meant imposing reductions whose distribution bore no relationship to the legislation that created the debit and whose depth bore no relationship to the capacity of the affected accounts. The exemption problem determined the enforcement outcome in advance for any debit of significant size, by ensuring that the remedy attached to the rule was the one element of the regime that no Congress, examining the actual distribution of the cuts, would permit to operate.

None of that analysis converts the exemptions themselves into errors of drafting or evidence of bad faith in 1985, 1990, or 2010. The exemptions recorded deliberate policy choices, made openly in statutory text, about categories of federal payment that automatic cancellation should not reach. Protecting Social Security benefits and railroad retirement benefits protected the retirement income of beneficiaries who had contributed during working lives and who depended on payments already in course. Protecting net interest protected the credit of the government itself, on which the cost of all federal borrowing depended. Protecting subsistence programs protected households whose margin between assistance and destitution was the benefit itself. Protecting veterans’ programs, first in the form of compensation and pensions and after 2010 in department-wide form, protected obligations incurred through military service. Protecting refundable credits protected a delivery channel for assistance to low-income working households. The flaw in enforcement arose not from any one of those choices but from the decision to attach a serious enforcement remedy to a base that the combined choices had reduced to a residual, without adjusting either the remedy or the rule to the base that remained.

The result was a rule whose stated consequence could not be the consequence that governed behavior. Legislators drafting a measure subject to the scorecard requirement knew, from the structure of section 255 and section 256 and from the record of both regimes through the end of the 2019 session, that a resulting debit would not in practice produce a sequestration order of the kind the statute described. The knowledge did eliminate the credibility of the threatened cancellation as a proportional response to a large debit, because proportionality was exactly what the exemption architecture destroyed. A small debit might have produced a manageable percentage on the residual base, while a large debit, the kind that mattered most for the deficit path the rule existed to protect, produced a percentage that no order could carry out. Enforcement that functions only for violations too small to matter, and that collapses for violations large enough to matter, inverts the logic of a fiscal rule. The exemption problem was the mechanism of that inversion, written into sections 255 and 256 in plain statutory language, measurable in the Congressional Research Service figure of three quarters of mandatory spending beyond reach, and visible in the unbroken record of scorecard sequesters described in law and never carried out in fact.

The Waiver Record and the Case for the Rule

Across two separate statutory regimes, no PAYGO sequestration order was ever carried out. The remedy existed on paper in both eras. The scorecards existed, the accounting existed, and the authority for the President to issue an order under the Balanced Budget and Emergency Deficit Control Act existed. Debits that would have supported such an order were recorded in amounts that dwarfed the base available to absorb them. Each time a debit accumulated to a level that would have required an order, Congress acted first, through legislation, and removed the condition that would have triggered the order. The pattern repeated across different Congresses, different presidents, and different fiscal conditions. A single waiver might reflect the politics of a single session. A record without exception, extending across the full life of the first regime and through the end of the 2019 session under the second, reflects something about the mechanism itself.

The first regime ran to a defined end. The Budget Enforcement Act of 1990, enacted as Title XIII of the Omnibus Budget Reconciliation Act of 1990, paired discretionary spending caps with the scorecard requirement, and both elements expired on September 30, 2002. Legislated changes to mandatory spending and revenues were recorded and scored, and the Office of Management and Budget maintained the accounting that would have determined whether an order was required. No order under the pay-as-you-go side of that system was carried out. The closing act of the regime made the outcome explicit. Legislation signed on December 2, 2002, enacted as Public Law 107-312, set the PAYGO balances to zero. With the balances at zero, no debit remained from which a fiscal 2003 sequester could have been calculated, and no such sequester could occur as the caps and the scorecard expired together. The statute addressed the scorecard itself, the only channel through which the debits could have produced a cancellation of budgetary resources.

The second regime repeated the record of the first. The Statutory Pay-As-You-Go Act of 2010, signed on February 12, 2010, restored the scorecard requirement in statutory form after an interval in which the rule had operated only as a rule of the House and the Senate. Under the restored statute, the Office of Management and Budget maintained five-year and ten-year scorecards under section 4(d) of the act and prepared the annual report, issued shortly after a session ended, that would show whether a debit stood on either scorecard. A debit shown in that report would have required an order. The Congressional Budget Office record is that sequestration has never been triggered under the Statutory Pay-As-You-Go Act of 2010. Through the end of the 2019 session, major legislation with large recorded effects passed repeatedly, and in each instance in which a debit of consequence accumulated, a statutory provision prevented that debit from surviving to the point at which an order would have been required.

The techniques by which Congress prevented a debit from surviving differ in form while converging on a single effect. None involved defiance of the statute. Each operated through legislation, enacted and signed into law, and each changed the legal status of a recorded effect so that the scorecard no longer carried the debit that the underlying legislation had created. The rule was never violated while left standing. The rule was instead adjusted, measure by measure, by the same lawmaking authority that had created the rule, using forms of words that became standardized through repetition. Statutes from the 2010s carried that language so regularly that the language acquired the character of boilerplate, and that regularity matters, because boilerplate is evidence of planning rather than evidence of neglect.

How does Congress stop a PAYGO sequestration?

Congress stops a PAYGO sequestration by enacting another statute before the order issues. That statute directs the Office of Management and Budget to exclude specified effects from the scorecards, designates them as emergencies, shifts a debit beyond the budget year, or reduces the recorded balances to zero.

The first technique is an instruction carried in the text of a statute itself. A law whose budgetary effects would otherwise be recorded may direct the Office of Management and Budget to exclude those effects from the scorecards. When such a direction is enacted, the effects are not recorded, no debit arises from that law, and no later corrective action is needed. The direction operates at the moment of enactment and disposes of the enforcement question before the accounting begins. The decision about whether a measure counts against the rule is thus made inside the measure, by the same majority that enacts the measure. No separate vote on enforcement is required, and no official outside the legislative process holds a veto over the exclusion.

The second technique reaches the same result through a designation the 2010 act itself supplies. Section 4(g) of the Statutory Pay-As-You-Go Act addresses provisions designated as emergency requirements, and budgetary effects carrying that designation are excluded from the scorecards, with the same excluding effect as a direct instruction. The designation differs in one respect that matters to defenders of the system. The designation invokes a category the statute recognizes and frames the exclusion as a response to circumstances rather than as a refusal to count costs. A Congress using the designation states, in the text of the law, that the provisions answer an urgent need whose costs should not be governed by the ordinary offset requirement. Mechanically, the accomplishment is identical to a direct instruction. The designated effects do not enter the balances, and the annual report records no amount from that law requiring cancellation.

The third technique operates on timing rather than on inclusion, and the Bipartisan Budget Act of 2018, enacted as Public Law 115-123, supplies the largest illustration. The Tax Cuts and Jobs Act of 2017 had produced scorecard debits that the nonexempt mandatory base could not have absorbed, with the debit recorded on the ten-year scorecard running to roughly 1.5 trillion dollars as scored at enactment, a figure attributed to the Congressional Budget Office. Left standing, a debit of that scale would have required an order demanding a uniform percentage reduction across the small fraction of mandatory spending that the exemption structure leaves reachable, with Medicare reductions capped at 4 percent under the special rules governing a statutory PAYGO order. The act of 2018 shifted the scorecard debits recorded for the tax legislation of 2017 out of the budget year. The shift did not deny the recorded effects or repeal any provision of the tax law. The shift relocated the debit beyond the point at which the order would have been calculated, and a relocated debit, like an excluded effect, produces no order.

The fourth technique is the most comprehensive, and the Bipartisan Budget Act of 2019, enacted as Public Law 116-37 and signed on August 2, 2019, supplies the illustration. That act included language reducing the scorecard tallies to zero, a treatment the Congressional Research Service recorded in reporting on Medicare and budget sequestration. Zeroing differs from exclusion and from shifting in scope. An exclusion addresses the effects of a particular law, and a shift addresses the placement of a particular debit. A reduction of the tallies to zero addresses the accumulated record as a whole, clearing whatever debits stand on the scorecards regardless of which enactments produced them. The technique repeats the closing act of the first regime, when Public Law 107-312 set the balances to zero in December 2002. After a zeroing provision is enacted, the historical record of what legislation cost remains available in estimates and reports, but the enforcement record, the only record the remedy reads, stands empty.

Set against that record of avoidance, the cap side of the same enforcement statute shows that sequestration was executed when the rule being enforced was a spending cap or a deficit target. The first sequester under the Gramm-Rudman-Hollings deficit targets took effect on March 1, 1986, canceling 11.7 billion dollars in budgetary resources, prorated across the remaining seven twelfths of that fiscal year. A cap sequester was ordered for fiscal 1991 under the Budget Enforcement Act regime to close a breach of 395 million dollars in the international category. The sequester that began on March 1, 2013, under the Budget Control Act of 2011, canceled 85.3 billion dollars, with reductions of 7.8 percent in defense discretionary accounts, 5.0 percent in nondefense discretionary accounts, and 2 percent in Medicare benefit payments under the cap that governed that order, before fiscal 2013 appropriations legislation brought the total to 80.5 billion dollars, as the Government Accountability Office recorded in 2014. Orders of that kind issued and took effect. The failure of the pay-as-you-go remedy to execute was therefore not a failure of the remedy as an instrument. The instrument worked when pointed at a different rule.

The cap record also contains a form of non-enforcement, and precision about the difference matters. Congress raised the Budget Control Act caps repeatedly, through the Bipartisan Budget Acts of 2013, 2015, 2018, and 2019. Raising a cap changes the rule prospectively. A higher cap states, in advance, that a larger amount is permitted, and appropriations enacted under the higher cap comply with the rule as revised. No recorded violation is erased, because no violation occurs under the revised limit. The pay-as-you-go techniques operate differently. Exclusions, emergency designations, shifts, and zeroing provisions act on effects that legislation has already produced under a rule left formally unchanged. The recorded debit is removed after the fact, or prevented from being recorded, while the statement of the rule, that legislated changes should not increase the deficit, remains unamended. One practice revises the standard before performance is measured. The other practice revises the measurement after performance has occurred.

That distinction frames the harder question, which is whether a rule that has never produced the stated remedy deserves to be counted as a working rule at all. The strongest answer available to defenders of pay-as-you-go rejects the premise that the remedy is the rule. On the counter-reading, stated at full strength, the order was always the backstop rather than the mechanism, a penalty held in reserve whose principal function was to shape behavior early enough that the penalty would never be needed. Judged by execution of the backstop, the rule failed completely. Judged by influence over legislation before enactment, the rule operated continuously in both eras, and the waiver record itself supplies part of the evidence. A rule that nobody planned around would not need to be waived. Bill text across the 2010s routinely carried scorecard treatment language precisely because drafters planned around the rule and treated the disposition of the effects as part of the legislative design.

The operation before enactment has concrete content beyond the fact of waivers. A scorecard requirement obliges the sponsors of a measure that spends through mandatory programs or reduces revenues to confront the recorded cost in a form that survives debate over the measure itself. Offsets must be identified, drafted in statutory language, and scored while a measure is being written, when the composition of the measure remains open to change. Provisions were altered during drafting to reduce recorded costs, and proposals that could not carry the recorded costs faced an obstacle that proposals without fiscal effects did not face. None of that activity appears in a count of sequestration orders. All of that activity is attributable to a recorded accounting with a stated consequence attached, because without the accounting, the cost of a measure would remain a debating point rather than a balance carried forward from session to session. The scorecard gave fiscal effects a memory.

The waiver process itself, on the counter-reading, imposes a cost that silent non-enforcement would not impose. Waiving the recorded effect of a law requires an explicit provision in an enacted statute, written into a text that members vote on, passed by both chambers, and presented to the President for signature. The position taken is therefore recorded and public, attributable to identifiable majorities in identifiable votes, rather than a product of silent inaction. Escape required legislation, the most visible act the institution performs, and analysts who track the scorecards, including the Congressional Budget Office and the Congressional Research Service, could identify each exclusion and each zeroing provision by citation because each one existed as law. Visibility does not equal restraint, and the counter-reading does not claim that visibility prevented the waivers.

The experience of the 1990s gives the counter-reading historical weight. The first regime operated during an era of deficit reduction, in which large deficit reduction laws in 1990 and 1993, spending restraint under the caps, and a growing economy moved the federal budget from persistent deficit toward surplus by the end of the decade. The enforcement system did not author the improvement, which was produced by substantive decisions in the reconciliation laws, by economic conditions, and by revenue growth. The enforcement system preserved gains that other forces produced. A guard is not the author of the thing guarded, yet a guard performs real work when pressure to spend accumulated gains, or to give the gains away in unoffset tax reductions, arrives continuously. Each proposal to breach the caps or to enact unoffset legislation had to overcome the scorecard and find offsets or waiver language. Some proposals were modified under that pressure and some were abandoned.

Two organized positions organize the debate over what the waiver record means, and each deserves statement with attribution. The Committee for a Responsible Federal Budget has argued the discipline case across both eras. On that case, a fiscal rule earns standing by binding when binding is uncomfortable, and a rule that yields whenever a large debit accumulates teaches every future Congress that large debits are precisely the ones that will be excused. The pattern of exclusion and zeroing therefore erodes the rule as a precedent, converting an announced requirement into a default that applies to small measures while exempting the largest measures, whose fiscal effects matter most. Emergency designations illustrate the erosion in the clearest form, because a designation available for any provision a majority chooses to label urgent supplies a standing route around the scorecard. Credibility, once spent through repeated waivers, cannot be restored by reenacting the same words, which is why the discipline case treats each waiver as a cost imposed on every later attempt at restraint, with erosion of the rule as the central harm.

The Center on Budget and Policy Priorities has argued the flexibility case with equal consistency, on the ground that a fiscal rule cannot be designed as if all years were alike. Emergencies and recessions are the stated ground for flexibility. In a recession, revenues fall and mandatory spending rises through the operation of existing law, and legislation responding to the emergency will record large debits at exactly the moment when requiring offsets would force contractionary choices. A rule without an emergency route would either break in a crisis, damaging the credibility the discipline case prizes, or hold at a substantive cost no majority would accept. On the flexibility case, the section 4(g) designation and explicit statutory exclusion are parts of the design, safety valves that allow the rule to govern ordinary legislation in ordinary years while releasing the constraint when the conditions that justify release are present and publicly stated. The test, on that reading, is not whether waivers occur but whether waivers require justification stated in law and whether offsets govern the run of legislation that carries no emergency claim.

The two cases agree on more than advocacy emphasizes. Both treat the scorecard as valuable, and both treat explicit statutory treatment as superior to silent evasion. Both accept that the order under pay-as-you-go never executed and, given an exemption structure that leaves three quarters of mandatory spending beyond reach and caps Medicare reductions at 4 percent under a statutory PAYGO order, could not have executed at the scale of the largest recorded debits without producing reductions in a narrow set of accounts unrelated to the legislation creating the debits. The disagreement is over the inference to draw from a record of universal waiver. The discipline case infers a rule eroded toward irrelevance, in which the cost of obtaining an exception fell with each repetition until the exception became the expectation. The flexibility case infers a rule performing a different function than the remedy suggests, screening and shaping legislation before enactment. Between those inferences stands the comparison built across this article, in which cap sequesters executed repeatedly and raised caps were revised prospectively, while scorecard debits were erased after the fact. The comparison poses the design question on which any verdict must rest. What property makes one mechanism bind and the other bend?

The Rule and Remedy Table

The comparison compresses into three rows because one remedy served three rules, and each row pairs a rule with the trigger that measured a breach, the accounts that absorbed the cancellation, and the exemptions that bounded the remedy before any percentage was calculated. Reading across a row shows the full enforcement design at a glance, and reading down the final column shows why the designs diverged in practice even though the cancellation at the end of each path carried the same name.

Mechanism	What it constrains	What triggers it	Which accounts are reduced	What is exempt	Whether it has ever operated
The deficit targets of 1985 to 1987 (Gramm-Rudman-Hollings)	The federal deficit as a whole, against fixed maximum amounts set in statute	A measured deficit above the fixed amount allowed for the year	Budgetary resources across the government under the order, divided between defense and nondefense	Programs and payments listed in section 255, including Social Security benefits and net interest	Yes. An order effective March 1, 1986 canceled 11.7 billion dollars, prorated over seven twelfths of the year
The discretionary caps (Budget Enforcement Act of 1990 and Budget Control Act of 2011)	Annual appropriations within a defined category, against a cap set in statute for that category and year	Appropriations exceeding a category cap in a single year, measured when the appropriations cycle closes	Accounts inside the category that breached, at a uniform percentage calculated to eliminate the excess	Accounts outside the breached category, together with programs exempt under section 255	Yes. A fiscal 1991 order closed a 395 million dollar breach in the international category, and an order on March 1, 2013 canceled 85.3 billion dollars
The pay-as-you-go scorecard (Budget Enforcement Act of 1990 and the Statutory Pay-As-You-Go Act of 2010)	Legislated changes to mandatory spending and revenues, recorded cumulatively on five-year and ten-year scorecards	A net debit on either scorecard, measured at the end of a session of Congress	Nonexempt mandatory accounts across the government, regardless of which legislation created the debit	Three quarters of mandatory spending under section 255, including Social Security, veterans programs, net interest, refundable tax credits, and low-income programs	No. Congress excluded, shifted, or set to zero the recorded debits before any order issued under either regime

Verdict: Why Sequestration Binds and PAYGO Bends

The verdict turns on mechanism design alone, and mechanism design yields a clear answer. Sequestration binds when the rule behind the order aligns the cancellation with the decision that produced the breach, and the pay-as-you-go scorecard bends because that alignment is absent from the design. Alignment is the deciding factor. An enforcement mechanism works when the accounts it cuts are the accounts controlled by the decision the mechanism polices. That condition holds for discretionary spending caps, whose breach is measured inside a defined category and whose remedy falls inside the same category. That condition fails for the pay-as-you-go scorecard, whose breach is recorded from legislation affecting mandatory spending and revenues across the whole government and whose remedy falls on a residual pool of nonexempt mandatory accounts with no necessary connection to the legislation recorded. Severity does not decide the question. A remedy of unlimited harshness aimed at the wrong accounts gives the actors who created a debit no direct exposure to the consequence, and a remedy of modest size aimed at the right accounts confronts decision makers with a cost inside the field governed by the decision.

The cap record demonstrates the condition in operation. Appropriators write appropriations bills against a known ceiling for a defined category in a single year, the Office of Management and Budget measures the completed cycle against that ceiling, and a breach produces a cancellation confined to the category that exceeded the limit. The fiscal 1991 order that closed a breach of 395 million dollars in the international category shows the design at its most precise, a correction sized to one category and delivered to that category alone. The Budget Control Act guide traces the largest sequester actually carried out, the order of March 1, 2013 that canceled 85.3 billion dollars before later appropriations legislation brought the total to 80.5 billion dollars. In each episode the actors whose choices created the excess administered or funded the accounts that absorbed the reduction, and complaints about the reduction returned to the process that had produced the breach.

The scorecard record demonstrates the opposite condition with equal clarity. A debit arises from the cumulative effect of enacted legislation, and the legislation responsible might be a revenue measure with no spending accounts of its own, an authorization expanding a program that section 255 exempts, or a measure drafted by committees that control no mandatory accounts directly. The remedy then draws on the quarter of mandatory spending that the exemption structure in section 255 leaves reachable, a base amounting to the one quarter of mandatory spending left reachable after the exemptions the Congressional Research Service recorded in In Focus IF11332, with Medicare benefit payments inside that base capped at 4 percent under a statutory pay-as-you-go order. Recomputation pushes the remaining accounts to a higher percentage whenever Medicare pays at the capped rate, so the percentage required grows steeply as a debit grows, and at the scale of the largest recorded debits the base cannot yield the amount the scorecard demands. Congress responded to that arithmetic in every instance, through exclusions from the scorecards, emergency designations under section 4(g) of the 2010 act, shifts of recorded debits, and reductions of the scorecard tallies to zero. A remedy that cannot execute at the scale of the violations that matter most carries no credible threat during drafting, and credibility at scale is the property the verdict measures.

The counter-reading deserves full weight before the verdict rests, because the scorecard produced real effects through a different channel. Pay-as-you-go discipline operates before enactment, during drafting, when offsets must be identified, written into statutory language, and scored while the composition of a measure remains open to change. Measures were altered during drafting to reduce recorded costs, and waiver of a recorded effect required an explicit provision in an enacted statute, leaving a public and attributable record. The Committee for a Responsible Federal Budget has argued that repeated waivers erode a rule by teaching later Congresses that large debits are the debits most likely to be excused, while the Center on Budget and Policy Priorities has argued that emergency routes belong in the design because a rule without a release for recessions and emergencies would either break in a crisis or impose costs no majority would accept. Neither position establishes the sequester behind the scorecard as a credible enforcement device, and the verdict concerns the device. Pay-as-you-go as a rule shaped legislation. Pay-as-you-go sequestration as a remedy never operated, under either the 1990 regime or the 2010 regime, and the exemption and recomputation structure explains that record without recourse to motive.

A fiscal rule binds when the consequence of breaching the rule lands on the field controlled by the actors who decide whether to breach, at a scale the exposed accounts can actually absorb, under a measurement those actors can track while decisions remain open. The claim that organizes the entire comparison can be stated in one sentence: “Align the cut with the decision.” Where alignment holds, a modest remedy binds. Where alignment fails, no increase in stated severity repairs the design, because severity multiplied across disconnected accounts produces an order that the institution charged with issuing the order will act to prevent.

What to Study First

A student beginning the subject gains the most from the distinction between rule and remedy, studied before any episode. The distinction explains why one remedy could serve deficit targets, discretionary caps, and a scorecard across four decades, and why a verdict about sequestration that omits the rule enforced describes a label rather than a design. After the distinction, the two triggers deserve attention, the single year measured at the close of an appropriations cycle and the session measured through cumulative scorecards, followed by the exemption structure in section 255 and the special rules in section 256. A student who masters that sequence can read any enforcement episode by naming the rule, the measurement, and the accounts exposed, in that order.

A staffer drafting or scoring legislation needs the operational layer first. Scorecard mechanics govern daily work: the Office of Management and Budget maintains the five-year and ten-year scorecards under section 4(d) of the 2010 act, effects are recorded at enactment, emergency designations under section 4(g) exclude designated effects, and statutory language can exclude, shift, or zero a recorded debit. The two Medicare ceilings require exact handling in any draft or memorandum, 2 percent for benefit payments under the Budget Control Act sequester and 4 percent under a statutory pay-as-you-go order, because merging the figures misstates both regimes. Exemption checking against section 255 belongs in the same routine, since the reach of any order depends on the protected categories before any percentage is calculated.

A researcher gains the most from the primary record and the measurement sources. The Congressional Research Service recorded the exemption share in In Focus IF11332 at three quarters of mandatory spending, the Congressional Budget Office record establishes that sequestration was never triggered under the Statutory Pay-As-You-Go Act of 2010, and the Government Accountability Office account from 2014 fixes the revised total of the March 1, 2013 order at 80.5 billion dollars. Statutory text at 2 U.S.C. 900 to 907d supplies the controlling definitions, and the budget process reform impact article assembles the record of what the successive regimes achieved across the period. A journalist covering a proposed order serves readers best by naming the rule behind the remedy in the first reference, verifying the percentage for each category against the order itself, and reporting exemptions as part of the story rather than as background. For readers deciding where the comparison sits inside the wider series, the series study guide maps the surrounding statutes and the order in which the guides build on one another.

The study path that holds the material together runs from distinction to trigger to target to record, and a durable notebook matters more than speed along that path. A reader working through the regimes in sequence can keep your statute notes, citations, and case chronologies together free on VaultBook, and a reader testing command of the surrounding material can practice and revise US government and civics material on ReportMedic.

The design lesson extends to any fiscal rule a legislature might write. Exemptions are not decoration around an enforcement mechanism; exemptions set the base, the base sets the percentage, and the percentage decides whether an order can execute at the scale of the violations the rule exists to prevent. A rule drafted without counting the protected share invites the waiver record that both pay-as-you-go regimes produced. A rule drafted with the cut aligned to the decision, measured close to the decision, and sized to accounts the decision makers control gives the remedy a chance to operate as written, which is the only test an enforcement design can pass.

Frequently Asked Questions

Q: What is the difference between sequestration and PAYGO?

Sequestration and pay-as-you-go occupy different positions in the enforcement system. Pay-as-you-go is a rule about the content of legislation, requiring that enacted changes to mandatory spending and revenues, taken together, not increase the deficit. The requirement was created by the Budget Enforcement Act of 1990 and restored by the Statutory Pay-As-You-Go Act of 2010, with effects recorded on five-year and ten-year scorecards maintained by the Office of Management and Budget. Sequestration is a remedy, an automatic cancellation of budgetary resources ordered after a rule has been breached. The same remedy also enforced fixed deficit targets and discretionary spending caps, so naming the remedy alone never identifies the rule in an episode.

Q: Is sequestration a rule or a remedy?

Sequestration is a remedy. A rule states what enacted law must achieve, such as a deficit target, an appropriations cap for a defined category, or a scorecard balance that shows no debit. Sequestration states none of those standards. Sequestration is the consequence that follows a measured breach, an order by the President, based on calculations by the Office of Management and Budget, canceling budgetary resources in nonexempt accounts by the percentage required to eliminate the excess or the debit. The cancellation enforces the rule without changing the rule itself, and the remedy does not amend or repeal the legislation that produced the measured breach.

Q: What programs are exempt from sequestration?

Section 255 of the Balanced Budget and Emergency Deficit Control Act, classified at 2 U.S.C. 905, lists the exempt programs and payments. Social Security benefits and Tier I railroad retirement are exempt. All programs administered by the Department of Veterans Affairs are exempt under the version of section 255(b) left in force by the 2010 act, a broader protection than the 1985 original, which covered veterans compensation and pensions. Net interest is exempt, and refundable tax credits are exempt. The Congressional Research Service, in In Focus IF11332, recorded that three quarters of all mandatory spending was exempt, including Medicaid, the Children’s Health Insurance Program, Supplemental Security Income, the Supplemental Nutrition Assistance Program, Temporary Assistance for Needy Families, unemployment compensation, civilian and military retirement, and federal-aid highways.

Q: Why has a PAYGO sequestration never happened?

A pay-as-you-go sequestration never happened because Congress acted before an order could issue in every instance across both regimes. Statutes directed the Office of Management and Budget to exclude a measure’s effects from the scorecards, emergency designations under section 4(g) of the 2010 act excluded other effects, the Bipartisan Budget Act of 2018 shifted recorded debits arising from the tax legislation of 2017 out of the budget year, and the Bipartisan Budget Act of 2019 reduced the scorecard tallies to zero. The closing act of the first regime followed the same pattern, when Public Law 107-312 set the pay-as-you-go balances to zero in December 2002. The exemption structure supplied the underlying reason, because the reachable base was too small to absorb large debits.

Q: Does sequestration cut Medicare?

Sequestration reaches Medicare, but a statutory ceiling limits the reduction, and the ceiling differs by regime. Under the joint committee sequester created by the Budget Control Act of 2011, the sequester that began on March 1, 2013, reductions in Medicare benefit payments were capped at 2 percent. Under a sequestration order issued to enforce the Statutory Pay-As-You-Go Act of 2010, reductions in Medicare benefit payments are capped at 4 percent under the special rules of section 256, classified at 2 U.S.C. 906. The two figures belong to two different orders enforcing two different rules. When the uniform percentage required by an order exceeds the Medicare ceiling, Medicare pays at the capped rate and the remaining nonexempt accounts absorb a recomputed, higher percentage.

Q: Which works better, caps or PAYGO sequestration?

Caps work better as an enforcement design, and the deciding factor is alignment. A cap is measured inside a defined category for a single year, and a breach produces a cancellation inside the same category, so the appropriators whose decisions created the excess administer the accounts that absorb the consequence. A pay-as-you-go sequester is measured from the cumulative effect of legislation across the government and falls on nonexempt mandatory accounts regardless of which legislation created the debit. Cap sequesters were ordered and executed, including the fiscal 1991 order and the order of March 1, 2013. A pay-as-you-go sequester was never carried out under either regime. Alignment, rather than severity, explains the difference in the record.

Q: Do sequestration cuts fall evenly?

Sequestration cuts do not fall evenly across the budget. The arithmetic begins with a uniform percentage applied to the budgetary resources of nonexempt accounts inside the base an order can reach, and exemptions remove most of the budget from that base before the percentage is calculated. Under section 255, three quarters of mandatory spending stood exempt from the mandatory sequester, so the entire reduction concentrates on the remaining quarter. Special rules then break uniformity inside the base itself. Medicare benefit payments pay at a capped rate below the uniform percentage, and the remaining accounts absorb a recomputed, higher percentage. Orders divided between defense and nondefense assign separate amounts to each side, producing different percentages on each side of the split.

Q: Which should a student study first, sequestration or PAYGO?

A student gains the most by studying the distinction first and the remedy second, before either regime is read in detail. Sequestration supplies the shared vocabulary, budgetary resources, cancellation, uniform percentage, exemptions, and the order itself, and that vocabulary appears in every episode from the deficit targets of the 1980s onward. Pay-as-you-go then becomes readable as one rule among three that the remedy enforced, with a trigger based on cumulative scorecards rather than a single year appropriations total. Studying the scorecard first, without the remedy in place, leaves the central puzzle of the subject unexplained, why a rule with a stated consequence operated for decades while the consequence never executed under either statutory regime.

Q: What is a PAYGO scorecard?

A pay-as-you-go scorecard is the official ledger on which the Office of Management and Budget records the budgetary effects of enacted legislation affecting mandatory spending and revenues. The Statutory Pay-As-You-Go Act of 2010 maintains two scorecards under section 4(d), a five-year scorecard and a ten-year scorecard, and each enacted law is recorded on both, spread across the years the effects are estimated to cover. Debits and offsetting credits accumulate measure by measure across a session and carry forward into later sessions. The annual report issued shortly after a session ends states the balances. A net debit on either scorecard for the budget year is the finding that obliges the President to issue a sequestration order, absent intervening congressional action.

Q: What happens when discretionary spending caps are breached?

A cap breach produces a confined and rapid consequence. The Office of Management and Budget measures the completed appropriations cycle for a fiscal year against the cap for the category, and a finding that appropriations exceeded the cap requires a sequestration order within days of the final report. The order is confined to the category that breached, and accounts inside that category lose budgetary resources at a uniform percentage calculated to eliminate the excess. A breach in one category does not authorize reductions in another category that stayed within the limit. The fiscal 1991 order illustrates the precision of the design, closing a breach of 395 million dollars in the international category from accounts inside that category alone.

Q: Does a sequester cancel the law that caused the deficit?

A sequester does not cancel, repeal, or amend the law that caused a deficit effect. The order cancels budgetary resources in nonexempt accounts, reducing the authority available for obligation and expenditure in those accounts. The statute that expanded a mandatory program or reduced revenues remains in law, with eligibility rules, benefit formulas, and tax provisions operating as enacted. Payments lawfully made before an order takes effect remain paid. The remedy therefore addresses the recorded consequence of enacted law by reducing resources elsewhere inside the statutory base, rather than by rewriting the enacted law that produced the recorded effect. That separation between the law enforced against and the accounts reduced explains why a revenue measure can create a debit that spending accounts must answer for.

Q: Who calculates whether a sequestration is required?

The Office of Management and Budget performs the calculation, and the President issues the order on the basis of that calculation. The arrangement reflects a constitutional repair. The original 1985 design assigned the trigger determination to the Comptroller General, and the Supreme Court held in Bowsher v. Synar, 478 U.S. 714 (1986), that an officer answerable to Congress could not exercise that executive function. The repair enacted in 1987, Public Law 100-119, moved the determination to the Office of Management and Budget, where the function remained through the regimes that followed. The Congressional Budget Office estimates the effects of legislation and reports on balances, and the Congressional Research Service explains the framework, while the executive calculation and the presidential order execute the remedy.

Q: What does an emergency designation do under PAYGO?

An emergency designation removes the designated effects of a measure from the pay-as-you-go scorecards. Section 4(g) of the Statutory Pay-As-You-Go Act of 2010 addresses provisions designated as emergency requirements, and budgetary effects carrying that designation are excluded from the five-year and ten-year balances, with the same effect as a direct statutory instruction to exclude a measure. Because the effects never enter the balances, no debit arises from the designated provisions and no order can follow from that measure. Flexibility arguments, of the kind the Center on Budget and Policy Priorities advances, treat the designation as an intended safety valve for recessions and emergencies, stated openly in statutory text. Discipline arguments, of the kind the Committee for a Responsible Federal Budget advances, treat routine designation as a route around the scorecard, available whenever a majority chooses to apply the label.

Q: Why is Medicare treated differently from other programs in a sequester?

Medicare occupies a middle position that no other large program occupies. Medicare is not exempt under section 255, so Medicare benefit payments remain inside the base available for cancellation and contribute to closing a debit or an excess. Medicare is also not exposed to the full uniform percentage that an order applies to other nonexempt accounts, because the special rules of section 256, classified at 2 U.S.C. 906, cap the reduction in benefit payments. One judgment treated Medicare as too central to the federal budget for complete exemption alongside Social Security. Another judgment treated benefit payments governed by statutory payment systems as unsuited to an uncapped automatic reduction. The capped contribution then shifts additional percentage onto every other account in the base through recomputation.

Q: What does alignment mean for a fiscal rule?

Alignment means that the accounts exposed to cancellation are the accounts controlled by the decision that a fiscal rule polices. Under a discretionary cap, the cancellation falls inside the category that breached, so appropriators confront a consequence inside the field of the appropriations decisions under review. Under the pay-as-you-go scorecard, the cancellation falls on nonexempt mandatory accounts across the government, regardless of which legislation created the debit, so the consequence lands outside the field of the drafting decisions under review. Alignment determines whether the actors who can prevent a breach bear the cost of a breach. Severity cannot substitute for alignment, because a severe cancellation aimed at disconnected accounts gives decision makers little direct reason to alter the decision that created the debit.

Q: How large a debit could a PAYGO sequester actually remove?

A pay-as-you-go sequester could remove only a debit that the nonexempt mandatory base could yield, and that base is small. Section 255 exemptions leave roughly one quarter of mandatory spending reachable, and the special rules cap the contribution of Medicare, the largest program inside that quarter, at 4 percent of benefit payments under a statutory order. A modest debit translates into a noticeable percentage on the exposed accounts. A large debit demands a percentage beyond what the base can absorb, and at the largest recorded scale the arithmetic fails entirely. The debit recorded for the tax legislation of 2017 ran to roughly 1.5 trillion dollars on the ten-year scorecard as scored at enactment, a figure attributed to the Congressional Budget Office, and legislation in 2018 shifted that debit out of the budget year rather than allow an order.

Q: Are defense and nondefense spending cut at the same percentage in a sequester?

Defense and nondefense spending are not necessarily cut at the same percentage. Orders built on a divided structure assign a separate dollar amount to each side of the split, and the percentage for each side follows from the amount assigned and the base available on that side. The order of March 1, 2013 under the Budget Control Act illustrates the pattern, with reductions of 7.8 percent for defense discretionary accounts and 5.0 percent for nondefense discretionary accounts, alongside Medicare benefit payments at the capped rate of 2 percent. Within a side, the reduction applies at a uniform percentage to the exposed accounts. Across the split, the percentages differ because the statute assigned different amounts to each side rather than a single rate to the whole order.

Q: Can Congress waive a sequestration after an order has issued?

The record through the end of the 2019 session contains no pay-as-you-go order to waive after issuance, because Congress acted before issuance in every instance, through exclusions, emergency designations, shifts of recorded debits, and reductions of the scorecard tallies to zero. The mechanism of waiver in that record is preventive legislation aimed at the scorecard, the only channel through which a debit can produce an order. The cap record shows a different relationship between legislation and an executed order. The order of March 1, 2013 canceled 85.3 billion dollars, and fiscal 2013 appropriations legislation enacted after the order brought the total to 80.5 billion dollars, as the Government Accountability Office recorded in 2014. Later statutes also raised the Budget Control Act caps through the Bipartisan Budget Acts of 2013, 2015, 2018, and 2019, revising the rule prospectively rather than erasing a recorded breach.

Q: What does budgetary resources mean when an order cancels them?

Budgetary resources means the authority and amounts available to an account for obligation and expenditure. The category includes new budget authority, unobligated balances carried from earlier periods, and other resources that statute makes available for a federal program or activity. A cancellation of budgetary resources reduces what an account may commit or spend. The reduction operates on availability rather than on the statutory language that created a program, so an affected agency administers the same program with less room to obligate funds than the account otherwise would have held. A cancellation also differs from a reduction in outlays during the first year, because payments follow obligations according to the rhythm of each program, and obligations already validly incurred before an order follow established payment schedules.

Q: Where can a reader verify how a specific sequestration order was calculated?

Verification begins with the executive record, because the Office of Management and Budget performs the calculation behind every order. For a pay-as-you-go question, the annual report issued shortly after a session ends states the five-year and ten-year scorecard balances that determine whether an order is required, and the office maintains those scorecards under section 4(d) of the 2010 act. For an executed order, the order itself and the accompanying reports state the amounts and percentages by category. Independent accounts then test the executive figures. The Government Accountability Office recorded the revised total of the March 1, 2013 order at 80.5 billion dollars in 2014, and the Congressional Budget Office and the Congressional Research Service publish estimates and explanations that allow a reader to trace a stated percentage back to the base and the exemptions that produced the rate.