Skip to content

Sunset Clause Review

Standing-rule review — instantiates Deadweight Loss Reduction

Attaches an expiry to a rule, fee, or control so it must periodically re-earn its keep — a scheduled re-test of whether the original purpose still justifies the value it costs, with lapse as the default.

Many of the most expensive distortions are not mistakes; they are survivals — rules, fees, and controls that made sense when enacted and were simply never revisited as the world moved on. Nobody defends them, but nobody has to: they persist by default, and the burden of dislodging them falls on whoever notices, which is nobody. Sunset Clause Review flips that default. It attaches an expiry to a standing rule so that continuation is conditional and scheduled: at each sunset the rule must be affirmatively re-justified — is the original purpose still live, does this body still hold the authority, does the benefit still exceed the value the rule destroys — or it lapses. Its defining move, separating it from its siblings, is that it operates on an existing, long-standing rule and shifts the burden of proof onto its defenders on a recurring clock, with lapse or revision as the default outcome. It is a backward-looking, repeating audit — not a forward experiment on a new lighter rule (Regulatory Simplification Pilot).

Example

Decades ago a state enacted certificate-of-need (CON) rules: a hospital must prove an unmet "need" to a board before adding beds, imaging machines, or a new facility. The original purpose was real — curb duplicative capacity and the cost-shifting it caused. But the rule now often does something else: it lets incumbents block competitors by contesting their "need," slowing new capacity and access while the original cost-control rationale has weakened. Nobody has repealed it because repeal requires effort and a champion; persistence requires neither.

A sunset clause changes that arithmetic. The CON regime is set to expire every few years unless the legislature affirmatively renews it, and the review supplies the test it must pass: is the duplicative-capacity rationale still the binding concern? Does the board still have a legitimate mandate to adjudicate need? Does the access and competition the rule costs still come in under the cost-control it delivers? If defenders can make that case, the rule renews, perhaps adjusted. If they can't, it lapses on schedule — no repeal campaign required, because the default is expiry.[1] The mechanism doesn't decide the rule is bad; it forces the rule to prove, on a clock, that it is still good.

How it works

  • Attach an expiry to the standing rule. Give the rule, fee, or control a defined end date so it terminates unless renewed — converting silent persistence into scheduled re-justification.
  • Set the re-justification test. At each sunset, require an affirmative case: the original purpose is still live, the authority still holds, and the benefit still exceeds the value destroyed.
  • Default to lapse or revision. Make the null outcome expiry or adjustment, not continuation, so the burden of proof rests on the rule's defenders rather than on whoever wants it gone.
  • Renew, revise, or retire. Based on the re-justification, extend the rule as-is, adjust it to current conditions, or let it lapse — a genuine three-way decision, not a rubber stamp.

Tuning parameters

  • Sunset interval — how often the rule must re-earn its keep. Short intervals catch stale rules fast but flood the calendar and invite fatigue; long intervals let distortions run for years between tests.
  • Renewal burden — how demanding the re-justification is, from a pro-forma vote to a full evidentiary case. A high bar genuinely tests the rule but risks letting a still-useful rule lapse for want of a champion; a low bar becomes an automatic rubber stamp.
  • Default outcome — whether expiry means clean lapse, reversion to a prior rule, or a forced revision. Clean lapse maximizes pressure but can create a gap; forced revision keeps a safeguard while removing its distorting drift.
  • Scope of the clause — whether the sunset covers a whole regime or only its most questionable provisions. Broad clauses guard against systemic ossification; narrow ones target the specific components most likely to have outlived their purpose.

When it helps, and when it misleads

Its strength is structural: it fixes the asymmetry that lets bad rules survive good ones. Because persistence normally costs nothing and repeal costs a campaign, distortions accumulate; a sunset makes continuation the thing that must be earned, so rules that have quietly stopped justifying themselves fall away on schedule without anyone having to mount a fight.

Its failure modes come from the renewal ritual going hollow in either direction. If renewal becomes a rubber stamp, the sunset is theater — the rule persists exactly as before, now with a certificate of review. If the default gap is dangerous, a genuinely necessary safeguard can lapse because its defenders were distracted or outmaneuvered at the wrong moment, which is a way of running the mechanism backwards: using "it sunset" to kill a rule someone wanted gone regardless of merit. The discipline is to make the renewal test evidentiary rather than ceremonial, to choose a default (clean lapse vs. forced revision) that matches how costly a coverage gap would be, and to keep the review focused on whether the purpose still holds rather than on whichever side is better organized on renewal day.

How it implements the components

Sunset Clause Review realizes the standing-rule-audit subset of the archetype's machinery:

  • rollback_or_adjustment_rule — the expiry is a built-in path to revise, pause, or reverse the rule: at sunset it renews, adjusts, or lapses rather than persisting untouched.
  • legitimacy_and_authority_review — the re-justification test asks whether the original purpose is still live and whether this body still holds the mandate, the check a lapsed rule fails.
  • pilot_or_sunset_path — the scheduled expiry itself, converting silent persistence into recurring, affirmative re-justification with lapse as the default.

It does NOT run a forward, monitored experiment on a proposed lighter rule (implementation_boundary, monitoring_and_rebound_check on a live slice) — that is the Regulatory Simplification Pilot; it does not weigh the welfare ledger (cost_benefit_assessment_frame, sensitivity_analysis) — that is the Cost–Benefit Assessment Protocol; and it does not map the wedge or size the surplus (distortion_map, surplus_estimate), which the Distortion-Reduction Review supplies.

References

[1] A sunset provision is a clause that automatically terminates a law, rule, or agency on a set date unless it is affirmatively renewed — a standard legislative device precisely for forcing periodic re-justification of standing rules. Its defining feature is that it makes expiry the default and continuation the thing that must be earned, which is what corrects the persistence asymmetry this mechanism targets. ↩