Milestone-based integrated funding pilots are attractive to commissioners who want clearer accountability than fee-for-service and more operational control than fully capitated models. Instead of paying for units of service, the pilot releases payments when participants reach verified milestones: stabilization, engagement, care plan completion, housing steps, or sustained follow-up. The operational risk is that milestones become targets that distort frontline behavior—creating “checklist care,” selective enrollment, or documentation inflation. Well-designed milestone pilots build verification into day-to-day work so progress is real, evidenced, and safe.
This article supports Integrated Funding Pilots and complements measurement and assurance approaches in Using Data for Commissioning & Oversight.
What milestone-based funding is trying to solve
Many integrated programs struggle to demonstrate value because activity counts don’t show whether people are safer, more stable, or using fewer crisis services. Milestone funding attempts to align payments with meaningful progress—while still allowing multidisciplinary teams to choose the best pathway for each person. In practice, this only works when the milestones reflect real-world trajectories (including relapse and re-engagement) and when verification is operationally feasible.
Design principles that keep milestones from becoming perverse incentives
Milestones must be measurable without being simplistic. They should reward engagement and stabilization processes that reduce avoidable ED use and crises, but not punish complexity. Strong pilots include: (1) clear definitions and acceptable evidence, (2) a verification workflow that is independent of the delivering team, and (3) safeguards so providers are not incentivized to avoid high-need individuals.
Operational Example 1: Milestone definitions embedded into daily documentation workflows
What happens in day-to-day delivery
The pilot publishes a milestone library with definitions, minimum evidence requirements, and “edge case” guidance. In the case management platform, each participant has a milestone tracker. Frontline staff document normal care activities (outreach, assessments, follow-ups), and the system prompts for specific evidence when a milestone is approached—for example, a completed crisis plan, medication reconciliation confirmation, or verified connection to a primary care appointment. Supervisors review milestone readiness during weekly case conferences, ensuring evidence is present before submission.
Why the practice exists (failure mode it addresses)
This prevents the common breakdown where milestones are interpreted differently by different teams, creating inconsistent submissions and disputes during payment review.
What goes wrong if it is absent
Staff use informal judgment to declare milestones achieved. Evidence is patchy, submissions are rejected, and teams respond by either over-documenting everything (wasting capacity) or “learning the game” (documenting to the milestone rather than to the person’s needs).
What observable outcome it produces
Embedded milestone workflows produce consistent evidence, fewer payment disputes, and clearer clinical accountability because the pathway to “milestone met” is transparent and auditable.
Operational Example 2: Independent verification and sampling audits that do not overload operations
What happens in day-to-day delivery
The pilot uses a two-tier verification model. For high-value milestones, an independent reviewer validates evidence against the milestone definition before payment is released. For lower-value milestones, the pilot uses statistical sampling with post-payment audits. A verification team maintains a checklist, logs reasons for rejection, and shares monthly learning with providers. Importantly, verification is time-boxed (e.g., five business days) so cash flow is predictable, and providers know what “good evidence” looks like.
Why the practice exists (failure mode it addresses)
This addresses the risk that milestone payments become either ungoverned (creating fraud/audit exposure) or over-governed (creating delays and administrative burden that defeat the point of integration).
What goes wrong if it is absent
Without independent verification, trust collapses when performance looks “too good.” Without proportional audits, verification becomes a bottleneck, payments stall, and providers shift capacity away from outreach and engagement toward paperwork.
What observable outcome it produces
Proportionate verification produces reliable payment cycles, a defensible audit trail, and continuous improvement because rejection themes become operational training inputs.
Operational Example 3: Equity safeguards to prevent cherry-picking and access barriers
What happens in day-to-day delivery
The pilot establishes an access and equity protocol: minimum acceptance rates for high-need cohorts, required “no wrong door” triage behaviors, and a risk-adjusted milestone approach for complex cases. Intake teams use a standardized acuity tool, and the program reports enrollment and milestone achievement by subpopulation (e.g., homelessness, serious mental illness, high utilizers). A governance group reviews whether milestone design is inadvertently excluding people with unstable contact details, language barriers, or high trauma histories. If inequities emerge, milestones are refined and additional supports are commissioned.
Why the practice exists (failure mode it addresses)
This prevents the failure mode where milestone funding creates incentives to enroll people most likely to achieve milestones quickly, rather than those with the highest need.
What goes wrong if it is absent
Programs subtly shift intake thresholds, stop chasing hard-to-reach individuals, or deprioritize complex participants who require longer engagement. Apparent performance improves while system-level need worsens, increasing crisis use and inequity.
What observable outcome it produces
Equity safeguards produce more representative enrollment, stable engagement for complex cohorts, and evidence that milestone performance reflects real improvement rather than selection effects.
What funders explicitly expect to see
Expectation 1: Verifiable evidence for payment release. Funders expect each milestone to have a clear definition, acceptable proof, and a documented verification decision path that can withstand audit.
Expectation 2: Controls against gaming and exclusion. Commissioners and oversight bodies expect safeguards that prevent cherry-picking, documentation inflation, and inappropriate milestone shortcuts that reduce safety or access.
Making milestone funding operationally honest
Milestone pilots succeed when verification is built into real work rather than bolted on. The goal is not perfect measurement—it is credible progress that can be defended, learned from, and improved over time without undermining frontline care.