Blended Rate Integrated Funding Pilots: How to Combine Per-Member Payments and Activity Funding Without Losing Clinical Control

Integrated pilots often struggle with a basic tension: prevention needs stable funding, but acute response and short-term stabilization require flexible capacity. Blended-rate funding pilots address this by combining a per-member payment (to fund proactive work) with activity-based components (to fund episodic intensity). The model only works when clinical control is preserved—meaning eligibility, authorizations, and variance management are operationally disciplined and auditable.

This article supports Integrated Funding Pilots and aligns measurement and assurance expectations with Using Data for Commissioning & Oversight.

What blended-rate pilots are designed to solve

Pure fee-for-service can discourage prevention because it rewards activity rather than stability. Pure per-member payments can create anxiety about under-service and can fail when acuity spikes. A blended approach funds a baseline “care management and navigation” function while allowing defined activity payments for high-intensity episodes, clinically justified visits, or time-limited stabilization packages.

Where blended-rate pilots typically fail

Blended pilots fail when definitions are unclear: what is included in the baseline, what triggers activity payments, and who authorizes transitions between levels. They also fail when partners cannot explain day-to-day decision-making—leading to disputes, inconsistent practice, and audit exposure. The goal is not simply payment innovation; it is operational clarity.

Operational Example 1: Eligibility and level-of-service authorization workflows

What happens in day-to-day delivery

The pilot establishes a daily authorization workflow. Intake staff confirm eligibility criteria and assign an initial service level using a standardized assessment and supporting evidence. A clinical lead reviews and approves service level decisions within defined timeframes, documenting rationale and expected duration. If needs escalate, frontline staff submit an “upgrade request” with objective triggers (deterioration indicators, repeated unplanned contacts, safeguarding concerns). Approvals are logged in a register that supports audit and variance review.

Why the practice exists (failure mode it addresses)

This exists to prevent the failure mode where blended funding becomes discretionary and inconsistent—where some teams “upgrade” quickly and others avoid upgrades to protect budgets, creating inequitable access and unpredictable cost patterns.

What goes wrong if it is absent

Without structured authorization, escalation decisions are informal and uneven. Some individuals receive too little support until crisis, while others receive prolonged high-intensity activity without clinical justification. Over time, funders see uncontrolled variance, and frontline trust deteriorates because rules feel arbitrary.

What observable outcome it produces

A disciplined authorization workflow produces consistent service levels, clearer escalation timing, and defensible documentation of medical necessity and risk management. It also creates measurable stabilization indicators such as fewer unplanned contacts and improved follow-up timeliness.

Operational Example 2: Baseline package definitions and “what’s included” controls

What happens in day-to-day delivery

The pilot defines a baseline package (for example, proactive outreach, care planning, coordination with primary care, benefits navigation, and routine monitoring). Teams use standardized templates so baseline activity is visible without converting into billable encounters. Supervisors review weekly caseload dashboards to confirm baseline services are delivered consistently and that activity billing is reserved for defined episode criteria. Training reinforces boundaries: staff learn what belongs in baseline versus what triggers episodic payments.

Why the practice exists (failure mode it addresses)

This addresses the breakdown where baseline payments become “invisible work” and partners cannot evidence what the per-member dollars purchased. Without clarity, activity billing can inflate because teams try to make work visible through billable claims.

What goes wrong if it is absent

Funders see baseline payments as duplicative or non-value-adding because the operational record is thin. Meanwhile, activity billing grows as teams attempt to prove delivery, undermining the intended balance and increasing the risk of billing disputes or compliance concerns.

What observable outcome it produces

Clear baseline definitions produce consistent delivery of prevention work, reliable caseload management, and a stable operational record. Funders can see what was delivered, at what intensity, and how it contributed to reduced escalation.

Operational Example 3: Variance management, stop-loss triggers, and corrective action

What happens in day-to-day delivery

The pilot runs a monthly variance cycle. Finance and operational teams review cost and utilization variance by cohort, geography, and service level. Stop-loss triggers are pre-defined (e.g., exceptionally high-cost episodes or repeated escalations) and activate structured case review and system learning. Corrective actions may include revising authorization criteria, adding supervision capacity, or changing escalation pathways. All decisions are documented, assigned owners, and re-tested in the next cycle.

Why the practice exists (failure mode it addresses)

This exists to prevent “silent drift” where activity payments expand over time, baseline work erodes, and the model becomes neither preventive nor controlled.

What goes wrong if it is absent

Without variance management, partners only discover the funding imbalance late, often during reconciliation. Trust breaks down, and the pilot becomes politically vulnerable because it cannot explain why costs shifted or why outcomes did not improve as expected.

What observable outcome it produces

Strong variance control produces predictable performance, earlier identification of systemic bottlenecks, and documented learning that supports scale. It also provides a clear audit trail showing active stewardship of public funds.

What funders explicitly expect to see

Expectation 1: Medical necessity and documentation integrity. Funders and oversight bodies expect clear eligibility rules, authorization records, and evidence that activity payments reflect clinically justified intensity, not financial incentives.

Expectation 2: Demonstrable service integrity and equitable access. Commissioners expect assurance that blended funding does not create under-service for complex people, with monitoring of escalation timeliness, complaints, and safety signals across groups.

Why blended-rate pilots can scale when designed properly

Blended-rate pilots work when they create stable prevention capacity while preserving clinical control over episodic intensity. The success test is operational: can the pilot show consistent baseline delivery, disciplined escalation authorizations, and active variance management that keeps the model safe, equitable, and auditable?