Value-based payment (VBP) in HCBS fails for predictable reasons: measures are poorly chosen, incentives are sized in ways that distort behavior, and oversight relies on dashboards that donât match service reality. Done well, VBP can fund the work that prevents breakdownâtimely follow-up, supervision discipline, and proactive risk managementâwhile improving outcomes people actually feel. This article sets out design rules that keep incentives aligned with safe, equitable delivery. For related system context, see Funding, Rates & Payment Models and Quality Assurance, Oversight & Accountability.
Start with a hard truth: HCBS outcomes are not all âbuyableâ
HCBS is delivered across messy real-world conditions: unstable housing, caregiver strain, behavioral risk, and multi-agency interfaces. VBP works when it targets outcomes that are (a) meaningfully influenceable by the providerâs day-to-day practice and (b) measurable with a defensible audit trail. If you set incentives on outcomes that are largely driven by housing shortages, ED admission policy, or inadequate clinical capacity, you create a contract that rewards selection and documentationânot better support.
Early VBP designs should prioritize reliability outcomes that reflect service integrity: timeliness, continuity, missed-visit recovery, care plan execution, incident learning cycles, and member-reported experience that can be validated. As data maturity improves, VBP can widen into shared-accountability outcomes (e.g., avoidable escalation) with clear attribution rules.
Two oversight expectations every VBP design must satisfy
Expectation 1: VBP must include guardrails that protect access and rights
Oversight bodies increasingly expect explicit protections against risk selection and under-service. In HCBS, the biggest danger is that a provider can improve âoutcomesâ by avoiding complexity, reducing authorized hours informally, or discouraging referrals. A defensible VBP design includes minimum access standards, service-delivery integrity checks, and protections for least-restrictive practice.
Expectation 2: Incentives must be auditable and resistant to gaming
If a measure can be improved by coding behavior, documentation drift, or redefining exceptions, it will be. Oversight expectations now include reconciliation routines: how the commissioner validates performance, how exceptions are approved, and how data sources match real service records.
How to size incentives without breaking the service
Incentives should be meaningful but not dominant. If VBP upside/downside is larger than the providerâs operating margin, you create instability and defensive behavior. A common defensible approach is: keep base rates as the primary revenue engine, use a modest VBP layer for reliability outcomes, and introduce larger shared-savings elements only when attribution rules and data integrity are proven.
Also separate âearnedâ performance from âpaperâ performance. If outcomes improve but missed visits rise or staffing ratios collapse, the design is paying the wrong behavior.
Operational example 1: A reliability-focused VBP layer that improves timeliness and visit completion
What happens in day-to-day delivery: The commissioner sets two or three operational measures: (1) time from authorization to first successful contact, (2) visit completion rate, and (3) missed-visit recovery within a defined window. Providers configure a daily exception report from scheduling/EVV (where used), supervisors run a morning huddle to assign recovery actions, and care coordinators receive an alert when repeated misses indicate rising risk. Performance is reported monthly with a short record-sample appendix showing time-stamped recovery actions.
Why the practice exists (failure mode it addresses): Many VBP models jump straight to broad utilization outcomes without fixing basic service reliability. This practice exists to prevent a situation where âoutcomesâ are pursued while the service itself remains inconsistent, driving preventable escalation and dissatisfaction.
What goes wrong if it is absent: Providers focus on documentation and reporting rather than operational control. Missed visits become normalized, families experience instability, and commissioners respond with more monitoring instead of funding the workflow discipline that prevents failure.
What observable outcome it produces: Reliability VBP produces measurable improvements: faster service starts, fewer missed visits, better continuity, and lower complaint volume about cancellations. Evidence includes exception logs, supervisor sign-offs, and trend charts showing reduced repeated misses for high-risk members.
Operational example 2: Guardrails that prevent risk selection and under-service
What happens in day-to-day delivery: The contract includes an access integrity bundle: minimum referral acceptance standards by acuity tier, transparent rejection reasons, and a âno deteriorationâ rule that flags reductions in delivered hours without documented care plan changes. Providers submit monthly referral logs and a short variance report for any reductions in delivered support. Commissioners audit a sample of cases to confirm that service intensity changes are clinically and person-centered justified, not financially motivated.
Why the practice exists (failure mode it addresses): Without guardrails, VBP creates incentives to avoid complex people or quietly reduce service. This practice exists to prevent âsuccessâ being achieved through selection rather than better support.
What goes wrong if it is absent: Networks hollow out for high-acuity cases. People with the greatest needs face longer waits, higher staff churn, and greater risk of crisis because providers protect performance metrics by narrowing intake.
What observable outcome it produces: Guardrails preserve equitable access while still allowing performance incentives. Evidence includes stable acceptance rates for higher-acuity cohorts, fewer unexplained service reductions, and clearer documentation of care plan-driven changes.
Operational example 3: A shared-savings design that funds prevention work, not denial behavior
What happens in day-to-day delivery: The commissioner selects a narrow, attributable event set (e.g., repeated crisis episodes requiring emergency response) and establishes baseline rates with clear exclusions and attribution. Providers implement a prevention bundle: weekly high-risk review, same-day escalation protocol, and mandatory post-incident debrief with updated risk controls in the support plan. Savings are shared only if service integrity indicators remain strong (visit completion, supervision cadence, incident reporting timeliness), preventing savings from being achieved by under-delivery.
Why the practice exists (failure mode it addresses): Shared savings can backfire if providers reduce service intensity to cut cost. This practice exists to prevent âsavingsâ being generated by reducing support rather than reducing avoidable escalation through better practice.
What goes wrong if it is absent: Providers avoid risk, reduce authorizations informally, or delay escalation support to keep costs down. Over time, crises become more severe, family confidence drops, and commissioners face reputational risk because the contract rewarded the wrong behaviors.
What observable outcome it produces: A prevention-funded shared-savings model produces fewer repeat crises and stronger governance signals. Evidence includes documented high-risk reviews, incident debrief logs, updated care plans, and stable access indicators alongside reduced escalation recurrence.
Closing: pay for the behaviors that make outcomes possible
In HCBS, outcomes improve when services become reliable, supervision becomes real, and risk is managed proactivelyânot when providers become better at reporting. A defensible VBP design starts small, protects access and rights, verifies delivery integrity, and only then expands into bigger outcome and savings structures.