Rebound Aware Efficiency Governance¶

Pair efficiency improvements with absolute resource targets, rebound modeling, demand guardrails, and adaptive monitoring so cheaper service does not erase or reverse the intended savings.

Orientation¶

Pair efficiency improvements with absolute resource targets, rebound modeling, demand guardrails, and adaptive monitoring so cheaper service does not erase or reverse the intended savings.

Jevons Paradox is not a claim that efficiency is useless. It is a warning that technical efficiency changes the economic and operational environment around a service. Lower resource input per unit often lowers price, time, latency, effort, or capacity cost; that can make more use feasible and profitable. The intervention is therefore to keep the efficiency gain while governing the demand and scale response so the intended absolute outcome survives.

Problem model¶

Decision-makers optimize resource intensity per unit of service while treating service demand, capacity expansion, substitution, indirect spending, and boundary leakage as exogenous. The efficiency gain lowers effective cost or friction, alters behavior and investment, and can cause total resource use to diverge from the engineering forecast.

The essential distinction is between intensity and scale. If a service uses fewer resource units per transaction but the number or size of transactions grows faster, total use can still rise. The same pattern appears when saved money is spent elsewhere, when released capacity attracts new work, when producers expand supply, or when infrastructure and network effects reshape the market.

Canonical relationship¶

Let r be resource input per unit of useful service and q be service quantity, so total use T = r × q. An efficiency improvement gives r₁ < r₀, but absolute savings require r₁q₁ < r₀q₀. Engineering savings at fixed demand are S_eng = r₀q₀ − r₁q₀; observed savings are S_obs = r₀q₀ − r₁q₁; rebound fraction B = 1 − S_obs/S_eng. B = 1 erases expected savings and B > 1 is backfire.

The formula is a decision aid, not a promise of precise attribution. Direct rebound may be measurable quickly; indirect and system-wide rebound often require ranges, wider boundaries, and longer observation.

Intervention logic¶

Define the useful service, quality, beneficiary set, functional unit, and resource inputs before claiming efficiency.
Set the lifecycle and system boundary and construct a baseline and counterfactual for both service demand and total resource use.
Measure the unit-efficiency gain and identify how it changes effective price, time, convenience, quality, capacity, and investment incentives.
Map direct, indirect, substitution, induced-capacity, producer, and system-wide rebound channels with uncertainty and delay.
Estimate demand response and stress-test low, central, high, delayed, and backfire scenarios.
State an absolute resource target and an explicit rebound tolerance that distinguishes essential access gains from uncontrolled expansion.
Precommit how released money, capacity, infrastructure, or operating margin will be retired, reinvested, rebated, or constrained.
Select legitimate demand guardrails such as caps, quotas, prices, procurement rules, sufficiency bands, or capacity ceilings while protecting an access floor and equity.
Pilot or phase the efficiency intervention where feasible and monitor unit efficiency, service quantity, total use, externalities, substitution, and distribution together.
Expand the measurement boundary and time horizon to test for leakage, induced infrastructure, embodied burdens, and delayed adaptation.
Trigger recalibration when observed rebound or total resource use exits the allowed band, and document the rationale, burden, and affected parties.
Retain the efficiency gain only when the combined design meets the absolute outcome, welfare, safety, access, and legitimacy requirements.

Components¶

Component	Description
Service Output and Functional Unit (Required) ↗	Define the useful service being delivered and the unit against which efficiency, demand, and total resource use will be compared. A technical input unit is not enough. The component must distinguish resource input, useful service, quality, access, and any expansion in the amount or intensity of service consumed.
Baseline and Counterfactual Measure (Required) ↗	Estimate what service demand and total resource use would have been without the efficiency intervention. Reuse the Elasticity-Based Leverage component. The counterfactual must account for secular growth, weather, population, prices, and other changes rather than attributing every post-intervention change to rebound.
Unit-Efficiency Metric (Required) ↗	Measure resource input per unit of useful service while preserving quality and service equivalence. This is the engineering or operational efficiency measure that creates the expected savings. It must not be reported as the final outcome without total-use measurement.
Lifecycle Scope Boundary (Required) ↗	Set the spatial, temporal, organizational, supply-chain, and lifecycle boundary within which resource use and rebound will be counted. Reuse the Externality Internalization component. A narrow boundary can make rebound disappear by exporting it to another category, supplier, geography, user, or time period.
Total Resource-Use Target (Required) ↗	Specify the absolute resource, emissions, material, land, water, energy, or capacity outcome that efficiency is meant to improve. The target converts an intensity goal into an absolute outcome. It may be a cap, declining budget, safe operating band, or bounded service-growth envelope.
Elasticity and Behavior Estimate (Required) ↗	Estimate how lower effective cost, lower friction, greater convenience, or higher performance changes service demand across user groups and time horizons. Reuse the Price Signal Design component. Estimate ranges, thresholds, heterogeneity, and adaptation rather than assuming a single stable elasticity.
Response Path Map (Required) ↗	Map the causal path from efficiency gain through effective price or convenience changes to demand, utilization, substitution, capacity expansion, and total resource use. Reuse the Price Signal Design component. The map should include direct, indirect, induced-investment, and economy-wide response paths where material.
Rebound Channel Map (Required) ↗	Separate direct same-service rebound, cross-category spending rebound, producer response, induced capacity, and broader structural rebound. The channels differ in observability, delay, policy owner, and appropriate control. Combining them into one percentage hides where intervention is possible.
Rebound Budget or Tolerance (Required) ↗	Define how much expected engineering savings may be absorbed by additional service demand before the intervention is judged off target. The tolerance should distinguish acceptable access expansion from uncontrolled backfire and should be stated as a range with uncertainty.
Substitution Path Monitor (Required) ↗	Observe whether users, firms, or systems substitute toward larger, more intensive, or complementary activities that raise total resource use. Reuse the Elasticity-Based Leverage component. Include product-size, mode, time, location, and cross-category substitution where relevant.
Externality Register (Required) ↗	Record resource, environmental, congestion, health, maintenance, and distributional effects that are not reflected in the lower effective price of service. Reuse the Externality Internalization component. Rebound is especially damaging when the induced demand imposes costs outside the buyer or operating unit.
Embodied and Indirect Resource Account (Required) ↗	Include the resource use embodied in the efficient technology, induced infrastructure, complementary goods, maintenance, and spending of saved money when those terms are material. The account prevents an operating-efficiency improvement from appearing beneficial while capital turnover or indirect consumption shifts the burden elsewhere.
Demand Guardrail (Required) ↗	Constrain or reshape demand when expected rebound would breach the absolute resource target. The guardrail can be a cap, quota, price, access rule, service sufficiency band, capacity limit, procurement rule, or another legitimate demand-side control.
Access Floor or Lifeline Rule (Required) ↗	Protect essential service access so rebound control does not deny basic needs or lock in prior inequity. Reuse the Price Signal Design component. Resource ceilings should distinguish luxury expansion from unmet essential demand and provide protected or subsidized minimum access where justified.
Equity Adjustment Guardrail (Required) ↗	Review who receives efficiency savings, who expands consumption, who bears caps or prices, and who absorbs externalized costs. Reuse the Externality Internalization component. A policy can meet an aggregate resource target while distributing burdens or access unfairly.
Efficiency-Dividend Allocation Rule (Required) ↗	Precommit how financial, capacity, or resource savings from efficiency will be retired, reinvested, rebated, or redirected rather than automatically converted into more throughput. The rule makes the post-efficiency disposition of released budget or capacity explicit. Without it, organizational growth pressure often absorbs the savings.
Rebound Trigger and Adjustment Rule (Required) ↗	Specify the observed rebound level, resource trajectory, or boundary leakage that triggers demand-control, pricing, quota, capacity, or program redesign. The trigger should include confidence bands, lag structure, minimum observation windows, and emergency action for clear backfire.
Monitoring and Recalibration Loop (Required) ↗	Update the demand-response model and intervention as actual service, prices, technology, behavior, and total resource use change. Reuse the Elasticity-Based Leverage component. Rebound can emerge slowly through behavior, asset turnover, capacity growth, and market adaptation.
Governance Owner and Authority (Required) ↗	Assign responsibility and legitimate authority for the absolute resource target, rebound monitoring, cross-boundary coordination, and corrective action. Efficiency owners often control only unit performance, while demand, pricing, procurement, capital planning, and externalities sit elsewhere. The owner must span or coordinate those decision rights.
Boundary-Leakage Sensitivity Check (Required) ↗	Test whether the apparent savings persist when the measurement boundary expands across users, categories, suppliers, places, and time horizons. This is the main defense against claiming success through scope selection. Report where the conclusion changes under plausible boundary choices.
Price or Friction Adjustment (Optional) ↗	Restore part of the scarcity signal or behavioral friction removed by the efficiency gain when unbounded demand expansion would violate the absolute target. Reuse the Elasticity-Based Leverage component. It is optional because caps, quotas, capacity rules, procurement limits, and non-price sufficiency measures may be better in some domains.
Use Quota or Use Limit (Optional) ↗	Bound total or per-actor use when a measurable shared resource cannot be protected by efficiency and price signals alone. Reuse the Commons Governance component. Quotas require legitimacy, monitoring, transfer rules, exceptions, and an access floor.
Price Cap or Volatility Guardrail (Optional) ↗	Prevent rebound-control prices from becoming unstable, exploitative, or destructive of essential access. Reuse the Price Signal Design component. It is relevant when dynamic or scarcity pricing is part of the intervention.
Adaptation Cadence (Optional) ↗	Set the schedule for reviewing rebound estimates, resource budgets, distributional effects, and corrective controls. Reuse the Commons Governance component. Review intervals should match behavioral, infrastructure, and market response delays.
Service-Sufficiency Band (Optional) ↗	Define a service range that is enough for the intended outcome, above which additional use receives less priority or stronger resource constraints. This optional component helps distinguish beneficial access expansion from low-value intensity growth without claiming that one service level fits every user or context.

Common mechanisms¶

Elasticity Experiment¶

Estimate how changes in effective price, convenience, speed, or quality alter service demand before scaling the efficiency intervention.

Reuse the indexed Elasticity-Based Leverage mechanism. Use phased, segmented, or natural-experiment designs where randomized tests are impractical.

Control Group Comparison¶

Compare treated and untreated units or periods to separate efficiency-induced rebound from background demand growth.

Reuse the indexed Counterfactual Comparison mechanism and adapt it to total resource use and service-output outcomes.

Full-Cost Accounting¶

Bring external, lifecycle, maintenance, congestion, and downstream resource costs into the efficiency and rebound decision.

Reuse the indexed Externality Internalization mechanism.

Comparative LCA Model¶

Compare embodied, operating, replacement, infrastructure, and end-of-life resource burdens under the efficiency and counterfactual scenarios.

Reuse the indexed Lifecycle Trade-Off Evaluation mechanism where a lifecycle model is material and evidence is available.

Resource Monitoring Dashboard¶

Display unit efficiency, service demand, total resource use, rebound fraction, distributional effects, and budget status together.

Reuse the indexed Commons Governance mechanism. A dashboard that shows only intensity is insufficient.

Demand Response Pricing¶

Adjust effective price by scarcity, total-use trajectory, or system conditions to keep demand inside the resource envelope.

Reuse the indexed Elasticity-Based Leverage mechanism. Protect essential access and monitor substitution and avoidance behavior.

Usage-Based Pricing¶

Tie at least part of payment or internal chargeback to actual use so unit-efficiency gains do not make marginal consumption appear free.

Reuse the indexed Price Signal Design mechanism. It is not appropriate where metering is invasive, inequitable, or administratively disproportionate.

Quota System¶

Allocate bounded use rights when the absolute resource target must hold despite strong or uncertain rebound.

Reuse the indexed Commons Governance mechanism. Include allocation, transfer, exception, enforcement, and review rules.

Cap-and-Trade¶

Place a hard aggregate cap on resource use or emissions while allowing governed exchange of use rights.

Reuse the indexed Commons Governance mechanism. The cap, not trading alone, is what bounds total use.

Price Incentive Adjustment¶

Recalibrate rebates, subsidies, tariffs, or internal prices when efficiency savings create excessive demand expansion.

Reuse the indexed Elasticity-Based Leverage mechanism. Avoid abrupt changes that strand low-income users or undermine trust.

Cost–Benefit Assessment Protocol¶

Compare welfare, access, externality, distributional, and absolute resource outcomes rather than treating lower unit cost as sufficient evidence of success.

Reuse the indexed Deadweight Loss Reduction mechanism with explicit total-use and rebound terms.

Direct and Indirect Rebound Audit¶

Trace same-service demand expansion, cross-category spending, complementary purchases, induced capacity, and supplier responses after an efficiency gain.

New provisional assessment mechanism. It should report channel-specific uncertainty rather than one unsupported headline rebound number.

Rebound Scenario Stress Test¶

Test the intervention under low, central, high, delayed, and structural rebound scenarios before committing to scale.

New provisional mechanism. Include price elasticity, service-quality change, induced investment, boundary leakage, and policy-response delays.

Absolute Resource-Budget Protocol¶

Translate a unit-efficiency project into an enforceable absolute resource budget with allocation, monitoring, exception, and correction rules.

New provisional protocol. It can be implemented through budgets, caps, procurement constraints, capacity ceilings, or equivalent domain-specific controls.

Efficiency-Dividend Lockbox¶

Reserve a defined share of efficiency savings for resource retirement, debt reduction, restoration, or protected public benefit rather than automatic throughput growth.

New provisional institutional mechanism. The lockbox can be financial, capacity-based, material, or operational.

Rebound-Triggered Policy Recalibration¶

Escalate through predefined corrective actions when observed rebound or total use exceeds the allowed band.

New provisional workflow. Corrective actions may include pricing, quotas, capacity limits, procurement changes, service redesign, or withdrawal of incentives.

Essential-Access Rebound Review¶

Distinguish demand growth that closes an unmet-need gap from low-value or externally costly consumption growth before applying controls.

New provisional assessment. It requires affected-party input, an access floor, and explicit evidence rather than moralizing about use.

Service-Output Normalization Dashboard¶

Normalize resource input, service quantity, service quality, utilization, and access so efficiency and total-use changes can be interpreted together.

New provisional dashboard. It should show both per-unit and absolute outcomes and identify changes in the service definition.

Embodied-Resource Payback Test¶

Determine whether the resource cost of replacing or upgrading equipment is repaid within the relevant lifetime after observed rebound.

New provisional assessment. Include premature replacement, induced infrastructure, maintenance, and disposal burdens.

Rebound-Leakage Boundary Review¶

Repeat the outcome calculation across wider category, supply-chain, geographic, and time boundaries to reveal exported or delayed rebound.

New provisional method. The result should state which boundary choices change the decision and which remain robust.

Key parameter dimensions¶

Efficiency gain: percentage change in resource input per equivalent unit of service, including quality changes.
Service-demand elasticity: response to lower monetary price, time, latency, friction, or inconvenience.
Rebound channel: direct use, indirect spending, substitution, producer response, induced capacity, or system-wide change.
Rebound fraction: observed erosion of fixed-demand engineering savings, with uncertainty and lag.
Absolute resource envelope: cap, declining budget, safe operating band, or bounded growth path.
Essential-access floor: protected service level and eligibility conditions before discretionary controls apply.
Boundary width: device, user, facility, portfolio, supply chain, sector, jurisdiction, or economy.
Time horizon: immediate behavior, asset turnover, infrastructure investment, market adaptation, and long-run structure.
Savings disposition: retirement, reserve, reinvestment, rebate, restoration, access expansion, or new throughput.
Control strength: information, friction, price, quota, cap, capacity, procurement, or institutional lockbox.
Uncertainty band: confidence in counterfactual demand, channel attribution, and indirect resource intensity.
Distributional incidence: who gains service and savings, who pays controls, and who bears externalities.

Invariants to preserve¶

Essential service access and a defensible minimum quality floor.
Absolute resource, emissions, or shared-capacity limits relevant to the intervention objective.
Transparent distinction between per-unit efficiency and total resource outcomes.
Safety, reliability, privacy, and operational continuity during metering and control.
Procedural legitimacy, explainability, appeal, and exception handling for demand constraints.
Distributional fairness across users, regions, income groups, workers, and future claimants.
Traceability of released money, capacity, and infrastructure after the efficiency gain.
Boundary and counterfactual consistency sufficient to detect exported or delayed rebound.

Expected outcomes¶

Engineering efficiency gains translate into credible absolute resource or emissions reductions, or into explicitly bounded service expansion.
Direct, indirect, and structural rebound channels become visible before they erase the intended benefit.
Demand controls are activated by evidence and governed thresholds rather than by ad hoc moral judgment.
Released capacity and financial savings are allocated deliberately instead of automatically feeding throughput growth.
Essential access and equity are protected while discretionary or externally costly expansion is constrained.
Decision-makers can distinguish a successful efficiency intervention, acceptable partial rebound, full erosion, and backfire.
The organization learns and recalibrates as behavior, markets, and infrastructure adapt over time.

Decision rules¶

Do not call an intervention resource-saving solely because resource per service unit fell; report the absolute total-use trajectory and counterfactual.
If high-end rebound scenarios erase the target before scale, require a binding demand guardrail or redesign rather than relying on optimistic behavior assumptions.
If observed demand growth closes an evidenced essential-access gap and remains inside the resource envelope, treat it as an intended benefit rather than automatic failure.
If rebound exceeds the tolerance but total use remains inside a safe absolute budget, recalibrate proportionately rather than chasing zero rebound as an end in itself.
If total use exceeds the absolute target, escalate corrective controls even when the engineering efficiency metric is on plan.
If wider-boundary or lifecycle analysis reverses the conclusion, use the wider material boundary or disclose the unresolved uncertainty.
Do not use price controls alone when metering, market power, information, essential access, or substitution makes the response inequitable or unreliable.
Retire, lock, or deliberately allocate released capacity and savings before they are absorbed by default growth pressure.
Review the design when technology, prices, demand elasticity, service quality, infrastructure, or policy authority changes materially.

Tradeoffs¶

Efficiency and access gains versus absolute resource reduction.
Simple, timely measurement versus wider-boundary lifecycle completeness.
Hard caps that guarantee the aggregate outcome versus flexible prices that preserve choice but may miss the target.
Uniform rules versus equity adjustments, lifeline access, and heterogeneous demand response.
Rapid deployment of efficient technology versus time needed to estimate rebound and build governance capacity.
Retiring released capacity versus using it for socially valuable unmet demand.
Local accountability versus system-wide effects that require coordination across organizations and jurisdictions.
Stable long-term rules versus adaptive recalibration as technology, prices, and behavior change.

Failure modes¶

Intensity-only success claim¶

Cause: Only resource per unit is measured while service quantity and total resource use are omitted.

Mitigation: Require paired unit and absolute metrics, a counterfactual, and a total-use target in every approval and review.

Boundary laundering¶

Cause: Rebound is exported to another category, supplier, geography, user, or time horizon outside the chosen scope.

Mitigation: Apply lifecycle scope, indirect-resource accounting, and boundary-leakage sensitivity checks; disclose where conclusions change.

Elasticity optimism¶

Cause: The design assumes weak demand response despite latent demand, quality improvements, network effects, or induced investment.

Mitigation: Use ranges, experiments, high-rebound stress tests, and binding guardrails before scale.

Released-capacity absorption¶

Cause: The organization automatically fills saved budget, staffing, compute, floor space, or infrastructure with new throughput.

Mitigation: Adopt an efficiency-dividend allocation rule or lockbox before the gain is realized.

Price-only control¶

Cause: A price signal is used despite essential needs, weak metering, market power, low responsiveness, or easy avoidance.

Mitigation: Combine prices with access floors, quotas, capacity rules, procurement standards, or non-price sufficiency measures.

Cause: All demand growth is treated as waste, including use that closes unmet essential needs.

Mitigation: Define a service sufficiency band, essential-access review, distributional monitoring, and legitimate exceptions.

Delayed structural backfire¶

Cause: Short pilots miss capacity investment, asset turnover, market entry, infrastructure, or producer responses that occur later.

Mitigation: Use staged follow-up, induced-investment scenarios, long-horizon review, and sector or portfolio caps where warranted.

False causal attribution¶

Cause: Population, weather, income, policy, or unrelated technology changes are mistaken for rebound.

Mitigation: Maintain a credible counterfactual, control groups or matched comparisons, and uncertainty bands.

Efficiency rejection¶

Cause: The existence of possible rebound is used as a reason to abandon beneficial efficiency improvements entirely.

Mitigation: Treat rebound as a design and governance requirement; preserve the efficiency gain while adding outcome controls unless evidence shows net harm.

Unenforceable absolute target¶

Cause: The resource budget is announced without ownership, metering, allocation, authority, or corrective action.

Mitigation: Assign a governance owner, instrument the boundary, define triggers and sanctions or redesign paths, and audit exceptions.

Boundaries and neighbors¶

Distinct from Elasticity-Based Leverage¶

Uses elasticity to find high-leverage price or friction interventions. It does not require an initiating efficiency gain, an engineering-savings counterfactual, rebound-channel accounting, or an absolute resource target.

Distinct from Price Signal Design¶

Designs prices or price-like signals to coordinate behavior. Pricing is only one optional mechanism here; the parent also governs caps, quotas, capacity, savings disposition, lifecycle boundaries, access, and total-use monitoring.

Distinct from Commons Governance¶

Governs shared resources broadly. Rebound-Aware Efficiency Governance is triggered specifically when improved unit efficiency lowers effective service cost and expands demand enough to threaten the absolute outcome.

Distinct from Externality Internalization¶

Brings spillover costs or responsibilities inside the decision boundary. It is an important component, but it does not by itself model engineering savings, demand response, rebound fractions, or released-capacity disposition.

Distinct from Deadweight Loss Reduction¶

Removes avoidable wedges to recover mutually beneficial activity. Its goal can legitimately be more activity, whereas this archetype asks whether an efficiency-driven increase defeats an absolute resource objective.

Distinct from Compounding Control¶

Controls runaway growth or decay in any compounding process. It does not require the specific efficiency → lower effective cost → demand expansion → total resource chain.

Distinct from Cycle Efficiency and Reversibility Assessment¶

Reduces losses within a repeated process relative to an ideal cycle. It does not govern the additional service demand or system expansion made possible by the efficiency gain.

Distinct from Load Leveling / Demand Smoothing¶

Redistributes demand over time to reduce peaks and queues. Total demand may remain unchanged or grow; this archetype governs the absolute quantity after efficiency.

Distinct from Rate Limiting¶

Caps an actor's temporal consumption rate. Rate limits are one possible mechanism and may still allow total use to expand across actors or longer periods.

Distinct from Minimum Effective Intervention¶

Finds the smallest intervention dose that works. It does not distinguish unit resource efficiency from induced service demand and total resource use.

Distinct from Saturation Avoidance¶

Prevents a bounded response channel from receiving useless additional input. Jevons-type rebound can occur far below saturation and is driven by lower effective cost and demand expansion.

Boundary with the ontology parent `rebound_effect`¶

The accepted prime rebound_effect describes compensatory overshoot after a sustained suppressor is removed. Jevons Paradox is cataloged as its child because both involve a counter-response that erodes an expected effect, but the intervention here is not tapering a suppressor. It governs price- and capacity-mediated demand expansion after efficiency improves a service.

Recognized variants¶

Direct Service-Rebound Control¶

Govern the increase in use of the same service after efficiency lowers its effective cost or friction.

Distinctive feature: The rebound occurs primarily through more frequent, longer, larger, or more intensive use of the improved service itself.

Why it remains under the parent: It uses the same functional unit, counterfactual, elasticity estimate, absolute resource target, access floor, demand guardrail, and recalibration logic.

Cross-Category Spending-Rebound Accounting¶

Track and govern the resource burden created when financial savings from efficiency are spent on other goods, services, or investments.

Distinctive feature: The induced resource use occurs outside the improved service through reallocation of saved money, time, capacity, or capital.

Why it remains under the parent: It uses the same counterfactual, lifecycle boundary, externality register, efficiency-dividend rule, total resource target, and leakage review.

System-Wide Efficiency-Backfire Governance¶

Govern structural rebound when efficiency changes prices, capacity, investment, market size, technology adoption, or network structure enough to raise system-wide resource use.

Distinctive feature: The rebound is generated by structural adaptation and scale, not only by an individual user's response to a lower marginal price.

Why it remains under the parent: It retains the same efficiency-to-effective-cost-to-demand causal chain and the same need to bind unit gains to absolute outcomes.

Examples¶

A city pairs more efficient street lighting with a fixed lighting-service plan and total electricity budget so lower cost does not produce uncontrolled fixture growth, brightness escalation, or operating-hour expansion.
A data-center operator measures joules per workload and total portfolio energy, then reserves part of the efficiency dividend and requires new workloads to pass value and carbon gates.
An irrigation program improves delivery efficiency while enforcing a basin-level consumptive-use cap and monitoring expansion of irrigated area and crop water demand.
A fleet adopts more efficient vehicles but evaluates induced travel, vehicle size, route expansion, and total fuel or emissions before claiming savings.
A manufacturer reduces material per product, sets a total material-throughput target, and monitors price-driven sales growth, accelerated replacement, and embodied infrastructure.
An organization automates case handling but locks part of the released staff capacity into backlog reduction, quality, and recovery rather than automatically increasing intake volume.

Extended example¶

A cloud platform deploys a new inference stack that cuts energy per request by 45 percent. At fixed workload, the engineering forecast shows a large energy saving, but the lower cost and latency make new features and high-frequency uses profitable. The platform first defines a stable service unit and quality band, constructs a counterfactual workload forecast, and models direct request growth, larger models, longer context windows, new customers, induced hardware purchases, and the use of saved budget elsewhere. It adopts a portfolio-level energy and carbon budget, a minimum-access tier, workload-value and quota rules, and an efficiency-dividend lockbox that reserves part of the savings for capacity retirement and clean-power procurement. A dashboard reports energy per request, request volume, total energy, service quality, access, embodied hardware burden, and channel-specific rebound. If the rebound fraction or total-use trajectory exits the agreed band, the owner tightens workload admission, revises pricing and quotas, slows capacity expansion, or changes the service design. The efficiency improvement remains valuable, but its success is judged by the combined service, access, and absolute resource outcome rather than by the per-request metric alone.

Non-examples¶

Replacing a motor with a more efficient model and reporting only its rated efficiency.
Applying a generic carbon price without linking it to an efficiency intervention, rebound model, or total-use counterfactual.
Calling all growth after an efficiency project rebound without accounting for population, weather, income, or unrelated demand changes.
Reducing an intervention gradually to avoid withdrawal rebound.
Imposing a usage cap solely because capacity is scarce, with no efficiency-induced demand change.
Expanding essential service access under an independently enforced absolute resource cap and calling the intended expansion a paradox.

Monitoring and review¶

A mature implementation reports at least four linked trajectories: resource per equivalent service unit, service quantity and quality, absolute total resource use, and the counterfactual. It then explains the channel-specific rebound estimate, wider-boundary sensitivity, essential-access effects, distributional incidence, released-capacity disposition, and any corrective action. Review must continue long enough to capture behavioral adaptation, asset turnover, capacity investment, and market response rather than stopping at commissioning.

Review posture¶

This draft should be reviewed for its boundary with Elasticity-Based Leverage, Price Signal Design, Commons Governance, and Externality Internalization. The full archetype is warranted only if the catalog preserves the distinctive initiating event and lifecycle: unit-efficiency improvement changes effective service cost, demand and scale respond, and an absolute resource outcome must be governed. Individual caps, prices, audits, models, standards, and dashboards should remain components or mechanisms.

Common Mechanisms¶

Absolute Resource-Budget Protocol — Converts a per-unit efficiency gain into a binding ceiling on total resource use, with a stated rebound tolerance, so a smaller unit cannot quietly become a larger system.
Cap-and-Trade — Holds total resource use under a hard aggregate cap while letting priced, tradable rights allocate the scarce total — so an efficiency gain frees allowances to trade rather than expanding the pie.
Comparative LCA Model — Models the full physical resource burden — embodied, operating, replacement, end-of-life — of an efficient option against its counterfactual, per unit of service, so a smaller operating footprint isn't bought with a bigger hidden one.
Control Group Comparison — Compares treated units against otherwise-similar untreated ones to recover what total use would have been without the efficiency program — separating the real saving from the rebound and from what would have happened anyway.
Cost–Benefit Assessment Protocol — Weighs a proposed distortion repair on full welfare terms — surplus recovered, who gains and loses, and how robust the case is — instead of accepting 'it costs less' as proof it is better.
Demand Response Pricing — Varies price continuously by time, load, or scarcity so responsive demand moves off the peaks efficiency would let it pile onto — reshaping when the resource is used rather than what it costs on average.
Direct and Indirect Rebound Audit — Traces where an efficiency gain's freed capacity and freed money actually went — same-service demand, cross-category spending, and induced supply — to see how much of the intended saving rebounded.
Efficiency-Dividend Lockbox — A standing fund that ring-fences a defined share of efficiency savings for resource retirement or public benefit, so the dividend cannot be silently reinvested into more throughput.
Elasticity Experiment — Deliberately tests several lever magnitudes, messages, or friction levels on small slices before scaling, to measure how strongly demand rebounds — the elasticity every price and guardrail is tuned against.
Embodied-Resource Payback Test — Checks whether the resource embodied in replacing or upgrading equipment is actually repaid by the in-use savings within the equipment's life — after real-world rebound is counted.
Essential-Access Rebound Review — Sorts post-efficiency demand growth into need-closing use that must be protected and low-value use that controls may target, so rebound controls don't cut off the under-served.
Full-Cost Accounting — Pulls the upstream, downstream, social, and environmental costs an efficiency decision leaves off-ledger back onto it — so the choice is judged on its full resource burden, not just the metered operating bill.
Price Incentive Adjustment — Applies a standing, deliberate change to price — a fee, tax, rebate, or subsidy set where demand will respond — to re-raise the effective cost an efficiency gain quietly lowered.
Quota System — Rations the scarce total into bounded, per-holder use limits — the choice when an absolute target must hold even under strong or uncertain rebound and no price or market can be trusted to protect it.
Rebound Scenario Stress Test — Runs the efficiency intervention through a spread of rebound scenarios — from negligible to full backfire — before scaling, to see whether the intended saving survives the bad cases.
Rebound-Leakage Boundary Review — Re-runs the efficiency outcome at successively wider category, supply-chain, geographic, and time boundaries to expose rebound that was merely exported or delayed past the original accounting line.
Rebound-Triggered Policy Recalibration — A standing monitor-and-escalate loop that fires predefined corrective actions, in order, once observed rebound or total use pushes past the allowed band.
Resource Monitoring Dashboard — Puts unit efficiency, service demand, total resource use, rebound fraction, and budget status on one live view — so the gap between per-unit gains and the stubborn total is impossible to miss.
Service-Output Normalization Dashboard — Puts resource use, service quantity, service quality, utilization, and access on one normalized basis so an efficiency gain can be told apart from simply delivering more service.
Usage-Based Pricing — Ties at least part of what is paid to actual metered use, so an efficiency gain that lowers unit cost never makes marginal consumption feel free — defeating the flat-rate overuse that erases the saving.

Compression statement¶

When resource use per unit falls, the effective price or friction of useful service often falls too. Demand, utilization, substitution, investment, or market scale can then expand enough that total resource use declines less than expected, stays flat, or rises. The intervention therefore treats unit efficiency as one input to an absolute-outcome control loop: define the service and counterfactual, model rebound channels, set a total-use target and tolerated rebound, protect essential access, precommit the disposition of released savings or capacity, apply legitimate demand-side controls, observe actual service and resource trajectories across a defensible boundary, and recalibrate when rebound exceeds the allowed band.

Canonical formula: Let r be resource input per unit of useful service and q be service quantity, so total use T = r × q. An efficiency improvement gives r₁ < r₀, but absolute savings require r₁q₁ < r₀q₀. Engineering savings at fixed demand are S_eng = r₀q₀ − r₁q₀; observed savings are S_obs = r₀q₀ − r₁q₁; rebound fraction B = 1 − S_obs/S_eng. B = 1 erases expected savings and B > 1 is backfire.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (8)

Boundedness: Values remain within limits.
Demand: A schedule relating quantity sought to generalized cost, with slope, elasticity, and substitution structure.
Externality: Spillover effects.
Feedback: Outputs influence inputs.
Jevons Paradox: Improving the efficiency with which a resource is used lowers the effective price of its output, expands demand, and can raise total resource consumption rather than lower it.
Price Elasticity: Sensitivity to price changes.
Resource Management: Allocation of finite assets.
Withdrawal Rebound: A system that adapted to a sustained input by mounting an opposing internal compensation overshoots in the opposite direction when the input is abruptly removed, because the now-unopposed compensation is still pushing against an input that is no longer there.

Also references 24 related abstractions

Allocation: Assign a limited supply across competing claimants under a feasibility constraint, independent of which criterion fills in the rule.
Carrying Capacity: The sustainable load envelope of a system: the maximum demand it can carry indefinitely before sustained operation begins consuming its own substrate and lowering future capacity.
Constraint: Limits possibilities to guide outcomes.
Cost–Benefit Analysis: Evaluate decisions.
Crowding Out: Introducing or expanding one activity inside a finite shared substrate displaces an existing activity that depended on that same substrate.
Diminishing Returns (Law of): Reduced output gains.
Economies of Scale: Cost reduction with scale.
Elasticity: The unit-free ratio of a fractional response to a fractional stimulus.
Equity: Context-sensitive fairness.
Gains from Trade: Mutual benefit exchange.

▸ Show 14 more

Variants¶

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Direct Service-Rebound Control · subtype · recognized