Is this vendor's outcome pricing actually qualified, or just attractive?

The outcome is defined in operative contract language, not in a schedule of intent, and the definition includes the exclusion cases.

Evidence required — Draft outcome definition clause with worked examples of included and excluded events.

Outcomes are classified as hard or soft. Soft outcomes are not priced per unit.

Evidence required — Outcome taxonomy with classification rationale per outcome type.

Partial completion is addressed. The treatment of an outcome that is begun and abandoned, or handed to a human mid-process, is specified.

Evidence required — Partial-completion schedule.

The reversal window is defined. An outcome that reverses within the window is not billable, or is subject to clawback.

Evidence required — Reversal definition, window length, and clawback mechanism.

The definition cannot be unilaterally amended by the vendor, including by change to model, prompt, routing logic or classification threshold.

Evidence required — Change control clause covering the measurement path, not only the service.

Where multiple outcome types are priced, the routing of a case between types is determined by rules the client can inspect.

Evidence required — Routing rule set and inspection mechanism.

A measurement and verification plan exists, identifying the data source of record for every payment-relevant quantity.

Evidence required — M&V plan. The absence of a plan at qualification stage is the most common cause of subsequent dispute.

The source of record for the outcome count sits in client-controlled or jointly controlled infrastructure.

Evidence required — System architecture showing telemetry path and control boundary.

Raw event data, not aggregated summaries, is retained for a period exceeding the dispute limitation period.

Evidence required — Retention schedule and storage location.

The client holds an unrestricted audit right over raw event data, exercisable without notice and without vendor mediation.

Evidence required — Audit clause.

Measurement uncertainty is quantified, with a stated tolerance and confidence level, following established practice in performance contracting.

Evidence required — Uncertainty analysis. Energy performance contracting convention is a tolerance at a stated confidence level agreed before signature.

Where contract value warrants it, an independent verifier is appointed, with its remit, funding and reporting line defined.

Evidence required — Verifier appointment terms.

Reconciliation between vendor invoice and client-side count is a defined monthly process with a variance tolerance and an escalation trigger.

Evidence required — Reconciliation procedure.

A pre-deployment baseline has been measured over a period sufficient to capture seasonality and demand cycles.

Evidence required — Baseline dataset with period, coverage and known gaps.

The baseline adjustment method is specified: how the baseline is normalised for changes in volume, case mix, product, policy, channel and organisational structure.

Evidence required — Normalisation methodology. Comparison against an adjusted baseline rather than raw historical data is standard practice.

Confounding contributors to the outcome are enumerated, and the attribution method between them is agreed.

Evidence required — Attribution note listing concurrent initiatives affecting the same metric.

The lag between vendor action and observable outcome is shorter than the contract review cycle.

Evidence required — Lag analysis. Where the lag exceeds the cycle, an intermediate controllable outcome is substituted.

No other supplier is separately remunerated for a contribution to the same outcome without a defined split.

Evidence required — Register of concurrent outcome-linked agreements.

The caseload is segmented by tractability using observable characteristics available at intake.

Evidence required — Segmentation model with within-segment variance analysis.

Within-segment variance in outcome probability has been tested and is materially lower than between-segment variance.

Evidence required — Statistical analysis. Segmentation that fails this test incentivises selective effort within segments.

Unit pricing differs by segment, or a progressive rate applies as the vendor works deeper into the caseload.

Evidence required — Price schedule by segment.

Minimum service levels apply to the least tractable segment and are separately enforceable.

Evidence required — Service level schedule for the residual cohort.

The distribution of vendor-handled against escalated cases is monitored by segment, with a threshold that triggers review.

Evidence required — Monitoring specification.

The whole-population cost per case, including the cost of handling escalated residual, is the reported measure. Cost per vendor-resolved outcome is not used as the headline.

Evidence required — Cost model covering the full population.

Data quality in the systems the vendor will depend on has been profiled, with defect rates quantified.

Evidence required — Data quality assessment.

Responsibility for data quality is allocated, and the consequence of client-side data defects on the payment mechanism is specified.

Evidence required — Data responsibility schedule and relief-event clause.

Interface availability targets for client systems are committed, with vendor relief where they are not met.

Evidence required — Interface SLA and relief mechanism.

Volume forecasts are provided with a stated confidence interval, and the interval has been stress-tested against historical variance rather than against a nominal percentage.

Evidence required — Volume forecast and sensitivity analysis. Historical failures in outcome contracting have followed from testing a nominal variance against actual variance an order of magnitude larger.

Upstream process changes that would materially alter outcome difficulty are subject to notification and repricing.

Evidence required — Change notification clause.

The client retains sufficient internal capability to evaluate vendor performance independently for the contract term.

Evidence required — Retained capability plan with named roles.

The payment mechanism includes a fixed component sized to the vendor committed fixed cost, protecting against volume collapse.

Evidence required — Payment mechanism schedule.

A cap or collar limits total outcome expenditure in any period. Successful deployment increases spend under this model.

Evidence required — Collar terms.

Budget authority for the variable component has been confirmed, including the mechanism for in-year variation.

Evidence required — Finance confirmation.

A retention or clawback element is linked to sustained performance measured after a stabilisation period.

Evidence required — Retention terms.

The vendor cost-to-serve per outcome has been modelled, including inference cost at the high percentile of case complexity, and a sustainable rate demonstrated.

Evidence required — Cost model. Inference is a variable cost of goods sold and scales with case difficulty while the fee does not.

The treatment of the outcome fee as variable consideration under the applicable revenue standard has been considered by both parties.

Evidence required — Accounting position note.

Rate review provisions address movement in the vendor input cost base in both directions.

Evidence required — Rate review clause.

Audited financial statements have been reviewed, and funded runway exceeds the contract term.

Evidence required — Financial statements and funding position.

The vendor has delivered a comparable outcome-linked engagement to completion. Reference sites are contactable.

Evidence required — Reference list with contract structure, not only logo list.

The vendor delivery capability is distinguishable from a repackaging of a third-party model with limited proprietary contribution.

Evidence required — Technical due diligence record.

Vendor dependency on upstream model providers is disclosed, including the consequence of a provider price change or capability withdrawal.

Evidence required — Supply chain disclosure.

Financial security is in place, proportionate to the client transition cost on vendor failure.

Evidence required — Guarantee, bond or escrowed retention.

Concentration exposure across the client estate has been assessed, and no single vendor holds an unmanaged position in more than one critical process.

Evidence required — Vendor concentration register.

Non-delegable duties affected by the scope have been identified and are recorded in Part E.

Evidence required — Legal analysis of statutory and licence obligations.

Regulatory notification, approval or consultation requirements for the arrangement have been discharged or scheduled.

Evidence required — Regulatory engagement record.

Liability for a defective outcome is separated from the payment mechanism. Non-payment is not the sole remedy.

Evidence required — Liability and indemnity provisions.

Personal data flows, cross-border transfers and processor obligations have been assessed and documented.

Evidence required — Data protection impact assessment.

Record-keeping meets the evidential standard the client would need to satisfy a regulator or an inquiry into an individual decision.

Evidence required — Record specification and retention terms.

Procurement route is confirmed as lawful for the structure proposed, including treatment of the variable payment element.

Evidence required — Procurement advice.

Configuration, prompts, tool definitions, routing rules and evaluation datasets are contractually portable in a documented format.

Evidence required — Portability schedule with format specification.

Portability is tested during the term at a defined frequency, not asserted at exit.

Evidence required — Portability test schedule.

A step-in right operates on insolvency, sustained failure or regulatory direction.

Evidence required — Step-in clause.

Transition assistance obligations extend beyond expiry and survive termination for cause.

Evidence required — Exit management schedule.

The term includes break points tied to performance thresholds, preserving contestability at re-tender.

Evidence required — Term and break structure.

Operational knowledge accumulated during the term is contractually the client property, including learned configuration and case handling patterns.

Evidence required — Intellectual property and data rights schedule.