Outcome-Based Contract¶
Incentive contract — instantiates Dependency-Capture Exit Design
Pays the provider for durably resolving the need rather than for activity, so profiting from a perpetuated problem stops paying.
When a provider is paid per hour, per ticket, or per visit, they profit from the need recurring — every unsolved problem is next month's invoice, and indispensability is a business model. Outcome-Based Contract rewires that by binding payment to the durable resolution of the need itself rather than to the volume of activity, so the provider only prospers if the problem actually goes away and stays away. Its defining move is realigning the money: it makes a solved, self-sustaining outcome the thing that pays, and it deliberately writes in anti-lock-in terms — data portability, documented handover, a right to a second source — so the buyer is never trapped even while the contract runs. It is a commercial instrument that changes what pays, not a diagnosis of who benefits and not a measurement dashboard.
Example¶
A county has for years paid a contractor a fixed fee per pothole filled to maintain its rural roads. Predictably, road quality never improves: shallow, short-lived patches maximize the count, and a genuinely durable road would end the revenue. The county rebids the work as a performance-based road-maintenance contract. Now the contractor is paid against a road-condition index — measured by an independent surveyor across the network — that must be held above a threshold for the contract term, with penalties when it slips and a bonus for sustained improvement.
The incentive inverts overnight. The contractor now wants to fix the causes of potholes — drainage, base failures — because durable roads mean fewer callouts for the same payment. The contract also requires the contractor to deposit road-survey data and repair records in an open, portable format the county owns, and to support a competing bidder's transition at term's end. When the contract expires, the county is not captive: it has the data, a defined wind-down, and a viable second source ready to bid.
How it works¶
- Pay for the outcome, meter it independently. Payment attaches to a measured state of the need being durably met — a condition index, an uptime, a resolved-and-stayed-resolved rate — assessed by a party the provider does not control.
- Reward durability, penalize recurrence. The terms make a problem that comes back cost the provider, so perpetuating or superficially papering over the need stops being profitable.
- Write in anti-lock-in from the start. Data ownership, portable formats, documented methods, and an explicit right to bring in or switch to a second source are contractual obligations, not favors — keeping an exit ramp open throughout.
- Bound the residual at term. The contract specifies the wind-down: what transition support the provider must give a successor and for how long, so ending the relationship does not resurrect dependence.
Tuning parameters¶
- Outcome metric — narrow proxy (potholes) vs. holistic condition (road-condition index). Broad outcome metrics resist gaming but are costlier to measure and argue over; narrow proxies are cheap and dangerously easy to game.
- Payment-at-risk share — how much of the fee rides on outcomes vs. is guaranteed. A high at-risk share sharpens the incentive but scares off good providers and invites metric-gaming; a low share barely moves behavior.
- Measurement independence — provider self-report vs. independent survey. Independence is what makes the outcome real; self-measurement invites the provider to grade its own homework.
- Anti-lock-in strength — from a vague "cooperate on transition" to hard data-ownership and second-source clauses. Stronger terms preserve the exit but narrow the pool of providers willing to sign.
When it helps, and when it misleads¶
Its strength is that it turns the provider's self-interest toward solving the problem: the party best placed to perpetuate a dependency is paid to dissolve it instead, which is far more robust than policing a provider whose incentives point the other way. Combined with anti-lock-in terms, it keeps the buyer free even during a multi-year engagement.
Its failure mode is the badly-chosen metric, gamed to the letter while the real need rots — the cobra effect[n1], where rewarding a proxy produces exactly the proxy and none of the intent (shallow patches that ace the pothole count, "resolved" tickets that quietly reopen under new numbers). A second misuse is anti-lock-in written so weakly that the provider still owns the data and the tacit method, so "outcome-based" coexists with total capture. The guard is to meter a holistic outcome independently, penalize recurrence explicitly, and make data ownership and a second-source right hard contractual terms rather than aspirations.
How it implements the components¶
durable_resolution_metric— payment is bound to an independently-measured state of the need being met and staying met, making durable resolution the thing that pays.residual_support_boundary— the contract's wind-down terms define what transition support the provider owes a successor and for how long, bounding the residual at term.substitute_or_second_source_path— anti-lock-in clauses (portable data ownership, a right to bring in a competitor) keep a live exit ramp to an alternative provider throughout.
It does not diagnose who benefits from the dependency or why the need persists (role_benefit_and_incentive_map) — that's Independent Needs Assessment; this contract restructures the payoff around an already-defined need rather than mapping the incentive landscape.
Related¶
- Instantiates: Dependency-Capture Exit Design — supplies the commercial realignment that makes solving the need more profitable than perpetuating it.
- Consumes: Dependency-Reduction Scorecard — its durable-resolution measure supplies the outcome the payment is metered against; Second-Source Review — qualifies the alternative the anti-lock-in clause points to.
- Sibling mechanisms: Capability Handoff Checklist · Dependency-Reduction Scorecard · Exit-Readiness Review · Fixed-Term or Sunset Mandate · Independent Needs Assessment · Open Documentation Package · Post-Exit Dependency Audit · Rotation or Term Limit · Second-Source Review
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Outcome-Based Contract operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it pays the provider for durably resolving the need rather than for activity, so profiting from a perpetuated problem stops paying.
Independent corroboration: The frozen evidence defines Outcome-Based Contract as 'Pays the provider for durably resolving the need rather than for activity, so profiting from a perpetuated problem stops paying', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Outcome-Based Contract is most directly rooted in public administration and policy's design of accountable programs, budgets, consultation, and service institutions. The lineage fits its defining practice: Pays the provider for durably resolving the need rather than for activity, so profiting from a perpetuated problem stops paying.
Related originating lineages:
- Economics & Finance — Outcome-Based Contract also draws materially on economics and finance's analysis of scarcity, incentives, tradeoffs, contracts, and option value, which shaped this mechanism rather than merely adopting it as an application.
- Law & Governance — Outcome-Based Contract also draws materially on law and governance's development of rights, duties, procedures, oversight, and legitimate authority, which shaped this mechanism rather than merely adopting it as an application.
Review resolution: Authoritative-source research resolves the primary-origin disagreement in favor of public administration policy. Results-Based Financing — World Bank documents the formative practice or theory represented here. The retained alternate domains identify material co-development or translation, while current applicability is recorded separately as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] The cobra effect — the failure in which an incentive rewards a proxy so literally that people optimize the proxy against the intent, worsening the real outcome. Named for a colonial anecdote in which a bounty on dead cobras led to cobras being bred for the reward; it is the standing hazard of any pay-for-outcome scheme with a gameable metric. ↩