From the recipient’s perspective, the navigation ecosystem appears as fragmentation rather than integrated support. Someone needing help with multi-employer verification does not care whether their navigator operates through a faith community, CBO, CISE microenterprise, or future DAO. They need someone who understands their situation, can help gather documentation from multiple sources, and will still answer calls next month when verification processes change. The organizational taxonomy matters to policymakers and funders. It barely registers for the 18.5 million people the system is supposed to serve. What they experience instead is a church volunteer who helped their cousin but does not attend their church, a CBO with three-week wait for appointments, a neighbor charging twenty dollars they do not have this week, and a state hotline disconnecting after forty minutes on hold.
The central reality: the ecosystem described across seven preceding articles remains largely theoretical. The coordination infrastructure connecting faith volunteers to CBOs to CISE providers to professional CHWs barely exists outside policy imagination. Regional backbone organizations that could facilitate handoffs do not exist in most communities. Shared technology enabling seamless information exchange has not been built. Quality assurance mechanisms distinguishing competent from incompetent providers remain undeveloped. The coordination problem nobody owns creates predictable failures where people fall through gaps between organizational silos, receive conflicting guidance from different providers, or simply give up after encountering too many barriers navigating the navigation system itself.
The View From Inside: Keisha’s Experience#
Keisha is a thirty-four-year-old home health aide in mid-sized Ohio city working twenty-eight hours weekly for home care agency, picking up another twelve hours through gig platform, and providing unpaid care for her mother with early-stage dementia. Her total qualifying hours should exceed eighty monthly, but proving this requires documentation from three sources: her agency employer, the gig platform, and attestation for caregiver hours potentially qualifying for exemption instead of counting as work.
The fragmentation she encounters reflects how loosely coupled systems actually operate. The faith volunteer who helped her cousin does not know the CBO case manager. The CISE provider has no relationship with the state hotline. The competency matrix assumes matching infrastructure that does not exist. The ecosystem remains theoretical while Keisha’s coverage depends on navigating it successfully.
She tries the church volunteer who helped her cousin. They attend different congregations. The volunteer refers her to her own church, where nobody knows the work requirement verification system yet. She calls the CBO everyone recommends, waits three weeks for appointment, then discovers the navigator left the organization and her case was not transferred. She contacts the CISE provider recommended by neighbor, who charges twenty dollars monthly she does not have until next payday. She calls state hotline, waits forty minutes on hold, gets disconnected. Each pathway presents its own barriers and none connect seamlessly.
The Coordination Infrastructure Nobody Built#
Warm handoffs between providers when cases exceed their competency require coordination infrastructure that barely exists. A faith volunteer recognizes medical complexity and wants to refer to CISE provider with healthcare background. But the volunteer has no warm contact at any CISE provider. She tells the person to find their own provider. The person searches online, finds conflicting information, gets overwhelmed, and gives up. The handoff fails through nobody’s fault.
Who builds this connective tissue? Not state Medicaid agencies, which design eligibility systems but rarely invest in navigation coordination. Not MCOs, which contract with specific vendors rather than convening ecosystem-wide infrastructure. Not individual congregations, CBOs, or CISE providers, which lack resources and authority to coordinate beyond immediate networks. Not foundations, which fund programs but not permanent infrastructure connecting programs to each other.
Regional backbone organizations could fill this coordination role by maintaining relationships across faith communities, CBOs, and independent providers, knowing which navigator has expertise in multi-employer verification or speaks Somali or understands IDD exemptions, operating shared case management systems enabling handoffs without starting documentation over, and coordinating training ensuring consistent competency across organizational boundaries.
Such backbone organizations exist in some communities for other purposes through collective impact initiatives, community health improvement partnerships, and United Way coordination structures. But extending these models to work requirement navigation requires investment nobody has committed and authority nobody possesses. States could mandate and fund regional coordination but face implementation timelines precluding building new infrastructure. MCOs could require coordination among contracted navigators but have no leverage over faith volunteers or independent CISE providers.
Technology Layer and Platform Economics#
The ecosystem needs technology layer providing provider directories searchable by competency and geography, client portals enabling secure information exchange with navigators, verification tracking showing submission status and next steps, payment processing for CISE providers and fee-for-service models, outcome reporting aggregating performance across providers, and handoff facilitation connecting clients to new providers when cases transition.
Building this technology requires substantial investment. A regional platform serving 100,000 expansion adults might need $2-3 million development cost plus $400,000-600,000 annual operations. Who pays? State Medicaid agencies view this as MCO responsibility. MCOs view it as state infrastructure investment. CBOs lack capital for platform development. CISE providers cannot collectively fund shared systems. The investment gap leaves ecosystem operating through disconnected point solutions and informal processes.
Platform economics favor monopolistic consolidation, but navigation ecosystem needs competitive plurality. If one platform dominates, it controls access to clients and dictates terms to providers. If many platforms compete, fragmentation undermines network effects and interoperability. The challenge is building shared infrastructure that enables competition while preventing fragmentation.
Public utility approaches could establish state-funded platforms available to all providers regardless of organizational type. But states have not built such infrastructure and implementation timelines may preclude it. Private platforms create proprietary systems advantaging their organizational sponsors. Open-source approaches lack sustained funding for maintenance and evolution.
Accountability in Distributed Systems#
When no single entity controls the ecosystem, who is accountable for quality, equity, and outcomes? If someone receives poor navigation advice leading to inappropriate coverage loss, who bears responsibility? The volunteer who provided inaccurate information? The CBO that failed to train volunteers adequately? The state that approved volunteer participation? The MCO that should have provided navigation directly?
Distributed accountability creates gaps where harm occurs without clear responsibility. Traditional models assume hierarchical organizations can be held accountable for their employees’ actions. Distributed models involve independent actors making autonomous decisions. The volunteer made good faith effort with incomplete knowledge. The CISE provider exceeded their competency but had no clear boundary guidance. The system failed without individual culpability.
Quality assurance mechanisms for distributed systems require different approaches than hierarchical oversight. Transparent outcome reporting across all providers regardless of organizational type, accessible complaint processes enabling clients to report problems, insurance requirements protecting clients from negligent advice, and clear scope of practice guidelines helping providers recognize capability limits all contribute to quality in distributed systems.
But who enforces these mechanisms? Who investigates complaints? Who determines whether CISE provider exceeded appropriate scope? Who ensures insurance requirements are actually met? The infrastructure for distributed quality assurance barely exists.
Realistic Capacity Estimates#
Verification assistance for someone with straightforward single-employer documentation might take fifteen minutes monthly. Assistance for someone like Keisha with three sources might take ninety minutes. If each volunteer or CISE provider can sustainably help twenty people monthly, reaching 13 million people requires 650,000 active helpers. Where do they come from?
The honest answer is that verification assistance will remain undersupplied relative to need. Some people will get help through faith communities, peer networks, CISE providers, or professional navigators. Some people will manage on their own despite burden. Some people will fail verification and lose coverage despite doing everything required because documentation did not happen correctly. The ecosystem improves outcomes compared to leaving everyone alone. It does not solve the fundamental capacity problem.
Bottom Line#
The navigation ecosystem described across this series provides theoretical framework for understanding different organizational contributions and coordination requirements. But theory remains far from practice. The infrastructure connecting faith volunteers to CBOs to CISE providers to professional CHWs barely exists. Regional backbone organizations that could facilitate coordination do not exist in most communities. Technology platforms enabling matching and handoffs have not been built. Quality assurance mechanisms for distributed providers remain undeveloped. The coordination problem nobody owns creates predictable failures where people fall through gaps, receive conflicting guidance, or give up after encountering too many barriers. Realistic assessment acknowledges that implementation will feature substantial fragmentation, capacity shortfalls, and coverage losses from system failures rather than individual non-compliance. States should invest in coordination infrastructure while accepting that ecosystem development requires time implementation timelines do not provide.