The technology for tracking hours, verifying activities, and calculating compliance exists and works reliably. The challenge facing states as they prepare for December 2026 is not technical but architectural: designing verification systems that balance program integrity, administrative burden minimization, and prevention of systematic harm to vulnerable populations. These goals conflict, and every design choice privileges one at the expense of others. Arkansas demonstrated the cost of getting this wrong, losing 18,000 people from coverage in seven months with no measurable employment increase, as research found only an estimated 3-4% of those subject to requirements were genuinely non-compliant while 25% lost coverage. Georgia spent between $86.9 million and nearly $100 million while enrolling far below projections. Both built technical infrastructure. Neither designed verification architecture for the populations it would serve.
The article’s central distinction is between systems designed to catch non-compliance and systems designed to prevent it. Traditional monthly reporting with uploaded documentation, the model Arkansas used, says “prove you met requirements last month.” An always-on verification architecture says “here’s where you stand right now.” The first optimizes for enforcement efficiency through batch processing, clear deadlines, and standardized documentation. The second optimizes for member success through immediate feedback, proactive intervention when someone falls behind, and flexible pathways to demonstrate compliance.
Always-on verification works through a distributed submission network. Instead of requiring every individual to submit documentation through government portals, the model distributes submission authority to the networks where work happens. Employers credential as verified submitters through a simple process: verify business identity, complete a brief training, receive credentials. A small business owner can then submit employee hours through a mobile application in thirty seconds. Community organizations follow similar credentialing for volunteer hours. Family members can credential as verifiers for caregiving relationships. The critical design principle is ruthless minimalism in data collection: who performed the activity, how many hours, what type, what date. No document uploads, no explanatory notes, no complex menus.
Supporting documentation stays with submitters unless randomly selected for strategic audit. This inverts the traditional verification burden. Instead of everyone providing everything upfront, most people provide minimal information verified only if flagged by risk-based algorithms. The trade-off is direct: minimalist submission with strategic auditing accepts higher theoretical fraud risk in exchange for lower administrative burden and reduced systematic exclusion of people who are compliant but documentation-challenged.
The article extends verification architecture to include opportunity discovery. The same system that tracks compliance hours can identify when someone falls behind and surface geographically proximate qualifying activities, available shifts from employers who need workers, volunteer opportunities at organizations that need help, training programs with open enrollment. This transforms verification from a measurement function into a support function, though it raises legitimate concerns about whether state-directed activity matching constitutes facilitation or coercion.
Ohio’s approach illustrates recognition logic in practice: data-matching two-thirds of their population through existing wage databases and exempting them from active reporting. The system looked for work, found it, and removed burden. This contrasts with compliance logic, where states assume non-compliance until proven otherwise each month.
For state Medicaid directors facing the December 2026 deadline, the article presents a clear strategic framework. Build technology for the most common cases through automated integration, which removes burden for over 60% of the population. Design human pathways for the 20-30% with complex employment patterns that technology cannot capture. Create graceful failure modes including automatic grace periods, presumptive eligibility during system outages, and alternative submission methods. Invest in feedback mechanisms through monthly convenings with navigators and frontline workers who surface problems faster than any monitoring dashboard.
The verification systems built over the coming months will operationalize the reciprocal social contract for 18.5 million people. Whether those systems treat people as participants to be supported or subjects to be policed depends on choices states are making now.