Integrated funding pilots promise âwhole-personâ delivery, but the practical challenge is simple: different funding streams carry different eligibility rules, documentation standards, and audit risk. Blended and braided approaches can reduce fragmentation only if dollars, decision rights, and accountability are designed to withstand scrutiny.
This article sits within Integrated Funding Pilots and links directly to how systems prove impact through Using Data for Commissioning & Oversight.
Blended vs. braided: what the distinction means operationally
In a braided approach, multiple funding sources remain distinct while being coordinated into a single delivery model. Services are âstitched togetherâ using rules-based allocation so each claim or cost can be traced back to the correct payer. In a blended approach, dollars are pooled (where legally permissible) under a single governance framework, with agreed rules for what can be purchased and how performance is measured.
Most pilots use a hybrid: braided rules for high-risk categories (clinical services, eligibility-dependent benefits) and blended purchasing for shared infrastructure (care coordination, navigation, community health worker capacity, data platforms). The more dollars move into a pooled structure, the more the pilot must invest in audit trails, decision logs, and quality gates.
What integrated funding pilots are trying to fix
Integrated funding designs typically target three system failure patterns:
- Cost shifting: agencies avoid paying for upstream support, pushing individuals into higher-cost settings funded elsewhere.
- Eligibility whiplash: individuals move between programs, losing access to support and creating repeated re-intakes and re-assessments.
- Unowned outcomes: each funder measures activity in its lane, while no one is accountable for end-to-end stability.
Funders will back integration only when a pilot can prove it is not simply moving cost and risk across agencies. That proof comes from governance design, operational controls, and defensible data.
Operational Example 1: A pooled âstability budgetâ for high-risk cohorts
What happens in day-to-day delivery
A pilot defines a cohort (for example: frequent ED users with housing instability) and assigns a pooled stability budget managed by a joint funding board. A care manager and finance analyst review each proposed non-traditional spend (transport, short-term lodging, medically tailored meals, phone access) against an agreed rulebook. Approvals are logged in a shared platform, tied to the care plan, and tagged to the cohort and intended outcome. Monthly reconciliations compare spend categories, utilization trends, and exceptions.
Why the practice exists (failure mode it addresses)
This practice is designed to prevent a common breakdown: frontline teams identify upstream needs, but no single payer can authorize flexible spending, so the system defaults to avoidable emergency and inpatient use.
What goes wrong if it is absent
Without an authorized pooled mechanism, teams either do nothing (leading to predictable escalation) or they spend informally without defensible documentation. Informal spending creates audit exposure, inconsistent equity, and disputes between agencies about who should have paid.
What observable outcome it produces
When done well, the pilot produces an auditable trail showing why flexible spend was used, what it replaced, and what changed. Outcomes include reduced repeat ED presentations, fewer no-shows, improved engagement, and documented exceptions reviewed and resolved through governance.
Operational Example 2: Braided billing rules for multi-agency teams
What happens in day-to-day delivery
A multi-agency team (behavioral health clinician, CHW, care manager, housing navigator) works from a single care plan but bills under braided rules. The team uses standardized encounter templates that capture time, service type, eligibility basis, and supervision. A weekly utilization huddle reviews questionable encounters, corrects coding, and escalates repeat issues to a compliance lead. A âsource-of-fundsâ ledger tags each unit of activity to the correct stream, with clear boundaries on what cannot be billed.
Why the practice exists (failure mode it addresses)
Integrated delivery often fails when the billing model cannot match the operational reality. Teams either under-document (losing reimbursement) or over-bill (creating compliance risk). Braided rules keep funding lawful while still enabling coordinated work.
What goes wrong if it is absent
Without braided controls, programs drift into inconsistent practices: staff bill differently for the same work, duplicate claims occur, and payers challenge costs. Over time, the pilot loses credibility because finance and compliance cannot reliably explain where money went.
What observable outcome it produces
The model produces clean audit outcomes: consistent documentation, reduced denials, fewer post-payment recoveries, and stable delivery capacity. Operationally, teams spend less time reworking claims and more time on care coordination that actually changes outcomes.
Operational Example 3: Joint outcomes governance with âno wrong doorâ accountability
What happens in day-to-day delivery
A joint outcomes board agrees a small set of shared measures (e.g., avoidable acute use, housing stability, engagement, follow-up timeliness). Each agency contributes data through a defined pipeline, with clear refresh cycles and validation rules. Monthly performance reviews look at cohort-level outcomes, not agency activity. When performance deteriorates, the board commissions a root-cause review and assigns actions with named owners, deadlines, and follow-up checks.
Why the practice exists (failure mode it addresses)
This practice prevents the âunowned outcomesâ pattern where each funder reports success in isolation while the personâs overall stability does not improve.
What goes wrong if it is absent
Without joint outcomes governance, partners revert to siloed incentives. One agency tightens criteria to reduce cost, another absorbs the fallout, and the individual cycles through services. The pilot becomes politically fragile because it cannot demonstrate shared impact.
What observable outcome it produces
Strong governance produces measurable improvements that can be defended publicly: improved follow-up, fewer crisis escalations, reduced duplication, and documented corrective actions. The audit trail shows decisions, actions, and whether those actions changed performance over time.
What funders and oversight bodies explicitly expect to see
Expectation 1: Clear eligibility and âpayer of last resortâ logic. Funders expect written rules that define who qualifies, what can be purchased, and how costs are assigned when multiple programs could pay. This includes exception handling, dispute resolution, and periodic testing to prevent drift.
Expectation 2: Audit-ready documentation and separation of duties. Integrated pilots must show who approved spend, who delivered services, who validated claims, and who reviewed exceptions. Oversight bodies look for role clarity, supervision, fraud and waste controls, and a defined cadence of internal audit.
Design guardrails that make pilots defensible
High-performing pilots build in: a rules-based spend framework; documented decision rights; routine reconciliations; quality gates that prevent âchasing savingsâ at the expense of safety; and a measurement plan that combines utilization, experience, equity, and stability indicators. These guardrails do not slow innovationâthey make it fundable.
Integrated funding is not a slogan. It is a controlled operating system. When governance is explicit and documentation is reliable, pilots can scale without collapsing under audit risk or interagency conflict.