Performance-based contracting is often promoted as a solution to quality and cost pressure, but poorly designed measures can distort delivery rather than improve it. This article sits within Contract Management and Provider Performance and connects directly to Intake, Eligibility, and Triage Operating Models, because performance incentives shape how providers manage demand at the front door. The focus here is how to design performance-based contracts that control delivery risk rather than encouraging superficial compliance.
Why many performance measures fail to improve outcomes
Performance measures fail when they are easy to count but hard to act on. Metrics such as volume delivered or average response times often hide risk and reward behavior that undermines safety or equity. Providers respond rationally to incentives, even when those incentives conflict with service-user outcomes.
Oversight bodies increasingly scrutinize whether measures reflect real control. Auditors and commissioners ask: if this metric moves, what changes operationally? If the answer is unclear, the measure is unlikely to withstand challenge.
Design measures that align with workflow and decision-making
Effective performance measures are anchored to workflow steps where decisions occur: triage, scheduling, supervision, and escalation. Measures should distinguish between risk tiers and focus attention where harm is most likely. This makes performance-based contracting a control system rather than a scoreboard.
Operational example 1: Risk-weighted response time measures
What happens in day-to-day delivery
Instead of a single average response-time target, the contract defines separate thresholds for urgent, standard, and low-risk referrals. Dashboards highlight breaches by category. When urgent thresholds are breached, providers must implement immediate mitigation and notify commissioners.
Why the practice exists (failure mode it addresses)
The failure mode is acceptable averages masking dangerous delays for high-risk cases. Risk-weighting exists to align performance focus with harm potential.
What goes wrong if it is absent
Providers meet headline targets while urgent cases wait too long. Complaints and adverse events expose the gap between reported performance and lived experience.
What observable outcome it produces
Risk-weighted measures produce faster access for urgent cases and clearer accountability for delays.
Incentives that do not destabilize delivery
Financial incentives should reinforce stability, not volatility. Sudden payment shifts tied to short-term variance can create cash shocks that worsen performance. Many commissioners now favor blended models: base payments for stability with targeted incentives tied to sustained improvement.
Operational example 2: Blended incentive models that protect continuity
What happens in day-to-day delivery
The contract maintains a stable base payment while linking a smaller incentive to sustained performance over multiple periods. Providers track trends rather than single-month spikes, and commissioners review improvement trajectories rather than isolated breaches.
Why the practice exists (failure mode it addresses)
The failure mode is volatility-driven behavior. Blended incentives exist to reward real improvement without encouraging gaming or risk avoidance.
What goes wrong if it is absent
Providers chase short-term metrics, deprioritize complex cases, or reduce access to protect scores.
What observable outcome it produces
Blended incentives produce steadier performance, better access equity, and more predictable financial management.
Assurance and escalation in performance-based contracts
Performance-based contracts must include clear escalation logic: when performance triggers discussion, corrective action, or contractual remedies. Without this, incentives lack credibility and commissioners struggle to demonstrate control.
Operational example 3: Escalation pathways that reinforce performance credibility
What happens in day-to-day delivery
Contracts define explicit escalation thresholds tied to performance measures. Breaches trigger structured reviews, action plans, and follow-up audits. Escalation decisions are documented and proportionate.
Why the practice exists (failure mode it addresses)
The failure mode is inconsistent enforcement. Escalation pathways exist to protect fairness and defensibility.
What goes wrong if it is absent
Performance incentives lose credibility, and commissioners resort to ad hoc intervention.
What observable outcome it produces
Clear escalation produces consistent responses, stronger assurance, and defensible performance narratives.
Performance-based contracting succeeds when measures control delivery rather than distort it. By grounding metrics in workflow, weighting for risk, and pairing incentives with credible escalation, commissioners and providers can improve outcomes without undermining system stability.