From Pilot to Scale: Governing Value-Based Payment as a System, Not a Contract

Value-based payment (VBP) is often treated as a contract feature rather than a system that requires active governance. Pilots may show early promise, but without defined accountability, escalation routes, and learning loops, performance degrades as scale increases. This article explains how commissioners can govern VBP as an operating system rather than a static agreement. For related insight, see Using Data for Commissioning & Oversight and Board Governance & Accountability.

Why value-based payment fails at scale

Scaling VBP increases variability: providers differ in maturity, data quality, workforce stability, and local conditions. Without clear governance, commissioners respond reactively—adding measures, tightening thresholds, or issuing corrective actions that undermine the original intent of the model.

Successful systems treat VBP as a managed environment with explicit roles, escalation points, and review cycles.

Two governance expectations for scaled VBP

Expectation 1: Clear accountability for performance interpretation

Oversight bodies expect commissioners to demonstrate who interprets performance, how disputes are resolved, and how learning is fed back into contract refinement.

Expectation 2: Proportionate response to performance variation

Not all underperformance indicates failure. Regulators increasingly expect graduated responses—support, remediation, and only then sanction—based on risk and impact.

Operational example 1: A tiered performance governance framework

What happens in day-to-day delivery: Performance is reviewed monthly against defined thresholds. Minor deviation triggers provider self-correction plans; sustained deviation prompts joint improvement reviews; severe or safety-related failure escalates to formal action. Roles are clearly assigned across commissioning, quality, and finance teams.

Why the practice exists (failure mode it addresses): Binary pass/fail responses discourage transparency. This practice exists to encourage early disclosure and improvement.

What goes wrong if it is absent: Providers hide problems until they are unmanageable, leading to crisis intervention rather than prevention.

What observable outcome it produces: Tiered governance results in earlier intervention and fewer contract failures. Evidence includes reduced emergency escalations and documented improvement cycles.

Operational example 2: Structured dispute resolution and learning loops

What happens in day-to-day delivery: Contracts include a formal performance query process with timelines, evidence standards, and decision logs. Outcomes of disputes are reviewed quarterly to identify design flaws or clarification needs.

Why the practice exists (failure mode it addresses): Unresolved disputes erode trust and distort behavior. This practice exists to separate genuine delivery issues from design weaknesses.

What goes wrong if it is absent: Disputes become political or adversarial, undermining collaboration and data integrity.

What observable outcome it produces: Learning loops improve contract clarity and reduce repeat disputes. Evidence includes declining query volumes and documented specification refinements.

Operational example 3: Adaptive target setting over time

What happens in day-to-day delivery: Targets are reviewed annually using trend data, service maturity indicators, and external benchmarks. Adjustments are documented and communicated transparently to providers before implementation.

Why the practice exists (failure mode it addresses): Static targets lose relevance as systems improve or conditions change. This practice exists to keep incentives meaningful and fair.

What goes wrong if it is absent: Targets become either unattainable or irrelevant, leading to disengagement or gaming.

What observable outcome it produces: Adaptive targets sustain engagement and continuous improvement. Evidence includes stable participation and consistent outcome gains over time.

Closing: govern value-based payment like critical infrastructure

At scale, value-based payment is not a policy experiment—it is infrastructure. Treating it as such protects people, providers, and public value while allowing outcomes-led funding to mature responsibly.