Outcome-based commissioning becomes distorted when contracts compare people with radically different starting points as though they were the same case. In Medicaid HCBS and LTSS, one individual may begin with stable housing, family support, and moderate needs, while another arrives after repeated crisis episodes, service distrust, medication breakdown, and housing instability. If both are judged only on the same final endpoint, providers who accept the hardest referrals can look weaker even when they are doing stronger work. That is why better contract design in outcome-based commissioning and pay-for-performance must be paired with realistic cost versus outcomes analysis that reflects acuity, baseline position, and staged improvement rather than simplistic league-table comparisons.
For provider executives, Medicaid plans, county commissioners, and bid teams, the practical challenge is designing a fair way to judge progress. The contract must reward meaningful change without weakening accountability. The strongest answer is to measure baselines carefully, define what “distance traveled” looks like in practice, and connect that evidence to outcomes that can still stand up under audit and procurement scrutiny.
Why baseline-blind outcome contracts create the wrong incentives
When contracts ignore baseline position, they quietly encourage providers to prefer easier cases. That is not always explicit cherry-picking, but the effect is similar. Services become financially safer when they work with people who are already closer to the contractual endpoint. This is particularly damaging in community services, where the people with the greatest system risk are often the ones furthest from quick measurable success.
State Medicaid agencies, managed care organizations, and county oversight teams increasingly expect providers to show who they started with, how risk and capability were assessed, and what type of progress was realistically achievable over a defined period. They also increasingly expect commissioners to distinguish between early stabilization, medium-term improvement, and final outcome achievement when setting performance expectations.
Operational example 1: Behavioral health support judged through stabilization before crisis reduction
What happens in day-to-day delivery
In a strong behavioral health HCBS pathway, staff begin by establishing a documented baseline across contact reliability, symptom instability, medication adherence, crisis history, housing security, and family or social support. This baseline is not just recorded once and forgotten. It is used in weekly case review to judge whether the service is first achieving engagement, then routine participation, then measurable stability. Staff record kept appointments, successful outreach, medication follow-through, reduction in chaotic contact patterns, and the person’s ability to tolerate a predictable support schedule before judging whether urgent crisis use falls.
Why the practice exists
This approach exists because one of the most common failure modes in outcome contracts is expecting crisis reduction before the service has even secured engagement. A person who has repeatedly disengaged from treatment may need several weeks of trust-building and routine formation before it is reasonable to expect fewer crisis presentations. The baseline protects that reality and stops commissioners from interpreting early-stage work as underperformance.
What goes wrong if it is absent
Without a structured baseline and distance-traveled logic, providers working with higher-need people appear weak next to services handling lower-risk cases. Teams may then avoid the hardest referrals, concentrate on easier participants, or overstate progress to protect performance ratings. Commissioners lose sight of who is genuinely reducing risk and who is simply serving people who were already easier to stabilize.
What observable outcome it produces
The observable outcome is a more credible performance trail. Commissioners can see that engagement improved, routines became more stable, and crisis dependence reduced in sequence. The provider can evidence that measurable progress occurred even before the final endpoint matured, making contract decisions fairer and more transparent.
Operational example 2: Housing-related support measured through tenancy risk reduction, not just tenancy presence
What happens in day-to-day delivery
In housing stabilization work, providers begin by documenting the individual’s initial tenancy status, arrears level, warning notices, conflict triggers, benefit disruption, and prior homelessness history. Frontline staff then record whether rent issues are resolved, landlord contact is stabilized, household routines improve, and tenancy breaches reduce. Supervisors review these indicators at defined intervals and use them to decide whether the person has moved from immediate housing fragility to short-term stabilization and then to sustained community tenure.
Why the practice exists
This practice exists because another common failure mode is treating “still housed” as the only meaningful outcome. For many higher-risk individuals, the more significant early achievement is not simply tenancy presence but reduced eviction risk, fewer breaches, and better household reliability. Those changes are often what make longer-term tenancy possible and are essential to fair outcome assessment.
What goes wrong if it is absent
If contracts only reward a final tenancy endpoint, services that accept people already near stability are advantaged over those managing active eviction, chaotic arrears, or severe housing-linked risk. Providers may become more cautious about whom they accept, and commissioners may accidentally fund access bias rather than effective support.
What observable outcome it produces
The observable outcome is more defensible evidence of progress in high-risk housing cohorts. Providers can show reduced tenancy warnings, improved rent compliance, better landlord engagement, and then stronger community tenure. Commissioners get a clearer view of whether the service genuinely changed the trajectory rather than simply inheriting easier cases.
Operational example 3: Reablement judged by functional distance traveled, not one uniform endpoint
What happens in day-to-day delivery
In a good reablement service, staff define baseline function task by task: transfers, washing, dressing, meals, medication prompting, mobility, and tolerance for routine. The team then records how much assistance is needed at the start, how that changes over time, and whether support can safely step down. Weekly reviews compare progress against the original baseline and document whether gains are sustained when direct input is reduced. Supervisors use that evidence to distinguish limited but meaningful progress from full independence.
Why the practice exists
This exists because a major failure mode in pay-for-performance is binary thinking. If the only recognized success is “independent at discharge,” the contract ignores substantial progress made by people with higher complexity who may never reach that full endpoint within the same timeframe as lower-acuity individuals.
What goes wrong if it is absent
Without functional baseline logic, providers may feel pressured to overclaim independence, discharge too early, or avoid more complex people who need a longer or more nuanced pathway. Commissioners then lose confidence in the data because the contract’s expectations were unrealistic from the start.
What observable outcome it produces
The observable outcome is a more honest picture of functional change. Providers can show reduced assistance levels, improved task participation, and sustainable step-down decisions. Commissioners can see whether the reablement service delivered real value even where the final endpoint was partial rather than absolute independence.
What commissioners and funders should explicitly require
Two expectations matter here. First, commissioners should require a documented baseline framework that captures acuity, functional status, and risk at entry rather than relying on broad referral descriptions. Second, they should require outcome logic that recognizes staged progress and distance traveled alongside final endpoints. Both expectations are increasingly important in Medicaid and county contracting because they protect equity, reduce gaming, and make provider performance easier to interpret accurately.
Designing fairer contracts without weakening accountability
Using baselines and distance traveled does not mean lowering standards. It means applying standards intelligently. Providers should still be challenged on poor practice, weak engagement, and unexplained lack of progress. But they should not be penalized simply for accepting more complex referrals than their peers.
The strongest outcome-based contracts reward real change from the actual starting point. When commissioners design performance frameworks this way, higher-need populations are served more fairly, providers are less exposed to distorted incentives, and contract data becomes much more useful for oversight, procurement, and long-term system learning.