Administrative Architecture on Syam Adusumilli

Work Requirements Article 7A

Sun, 15 Feb 2026 00:00:00 +0000

The Exemption Architecture
#

How rulemaking choices determine who gets protected

State regulators writing exemption rules for December 2026 face a philosophical question disguised as an administrative task. Every decision about who qualifies for exemptions, what documentation proves eligibility, and how long protections last reveals assumptions about human capacity, bureaucratic trust, and the purpose of safety nets. These choices determine whether Medicaid work requirements function as employment promotion or coverage restriction.

Summary: Work Requirements Article 7A

Sun, 15 Feb 2026 00:00:00 +0000

States designing medical exemptions face a choice that reveals more about regulatory philosophy than clinical reality. They can require specialist attestation, restricting exemptions to people who can access and afford specialty care, or accept primary care provider documentation accessible to most Medicaid populations. That single decision determines who maintains coverage independent of any underlying medical condition. Multiply it by hundreds of similar granular choices across exemption categories, documentation standards, processing timelines, and automation investments, and the cumulative effect rivals statutory eligibility rules in shaping who keeps Medicaid. States have roughly eight months between OB3 passage and December 2026 implementation to make these choices, most before their full implications can be understood.

Work Requirements Article 7B

Sun, 15 Feb 2026 00:00:00 +0000

The Verification Architecture
#

How states choose between trusting systems and trusting people

Work requirements mean nothing without verification mechanisms proving compliance. States must decide who submits verification, what documentation suffices, how frequently reporting occurs, and what happens when verification systems fail. These choices determine whether requirements function as employment promotion or become documentation traps creating coverage loss despite work. The fundamental tension is between distributed authority reducing individual burden and centralized control maintaining state oversight.

Summary: Work Requirements Article 7B

Sun, 15 Feb 2026 00:00:00 +0000

Arkansas in 2018 required monthly individual reporting through a web portal. Georgia in 2025 emphasizes quarterly automated data matching with employer payroll systems. Both enforce 80-hour monthly work requirements. The coverage outcomes diverge dramatically: Arkansas lost 25% of expansion enrollment while Georgia maintained stability. The difference is verification architecture, the regulatory infrastructure determining who submits proof of compliance, what documentation counts, and what happens when systems fail. States designing these systems for December 2026 implementation face a binary choice about where to place the burden of proof, and that choice determines coverage outcomes more than any employment policy.

Work Requirements Article 7C

Sun, 15 Feb 2026 00:00:00 +0000

The Coordination Architecture
#

When timing decisions determine who maintains coverage

Exemption rules and verification systems mean nothing without coordination mechanisms determining when people face requirements, how long they have to respond, what happens during transitions, and how multiple systems synchronize. These timing choices create the difference between orderly implementation where people have realistic opportunities to comply and chaotic rollout where procedural failures cascade into coverage losses.

Summary: Work Requirements Article 7C

Sun, 15 Feb 2026 00:00:00 +0000

When SNAP redetermination occurs in March, TANF in June, Medicaid eligibility renewal in September, and work requirements verify monthly, someone managing all four programs faces 15 separate compliance deadlines annually instead of four, multiplying documentation burden by nearly 400 percent. Coordination architecture, the regulatory infrastructure governing when people face requirements, how long they have to respond, what happens during transitions, and how multiple systems synchronize, determines whether work requirements create orderly compliance opportunities or chaotic procedural cascades that produce coverage loss through timing failures rather than work failures. States have eight months to build these coordination systems, and the choices they make about synchronization, grace periods, appeals, and error correction will shape coverage outcomes as powerfully as the substantive requirements themselves.

Work Requirements Article 7D

Sun, 15 Feb 2026 00:00:00 +0000

The Delegation Architecture
#

Legal frameworks enabling participation without creating liability traps

States cannot directly verify work or determine exemptions for 18.5 million people. Administrative capacity doesn’t exist to review employer payroll records, assess medical exemptions, verify educational enrollment, or confirm volunteer hours for millions of individuals monthly. Success requires delegating submission authority to employers, healthcare providers, educational institutions, managed care organizations, and community partners who interact with expansion adults through normal business and service relationships.

Summary: Work Requirements Article 7D

Sun, 15 Feb 2026 00:00:00 +0000

Employers fear liability for coverage loss if they report hours incorrectly. Providers worry about malpractice exposure from exemption determinations. Educational institutions question whether FERPA permits sharing enrollment data. Managed care organizations seek clarity about whether coordination assistance creates responsibility for coverage outcomes. Community organizations resist facilitating applications if doing so creates legal obligations they lack capacity to fulfill. Each of these concerns, left unresolved, prevents participation in the distributed verification and exemption systems that work requirements demand. States cannot directly verify work or determine exemptions for 18.5 million people. The administrative capacity simply does not exist. Success requires delegation to third parties, but delegation requires legal infrastructure that enables participation without creating liability traps.

Article 7E: Tribal Sovereignty and IHS Coordination

Sun, 15 Feb 2026 00:00:00 +0000

Tribal populations present unique rulemaking challenges that transcend the special population framework, demanding policy architecture that states cannot design unilaterally

Sarah Whitehorse has directed Montana’s Medicaid program for six years. She knows her enrollment numbers intimately: 96,000 expansion adults, distributed across a state larger than all of New England combined. But as she prepares for work requirement implementation, one statistic dominates her planning: 18 percent of those expansion adults are Native American, most residing on or near one of Montana’s seven reservations.

Summary: Article 7E: Tribal Sovereignty and IHS Coordination

Sun, 15 Feb 2026 00:00:00 +0000

Reservation unemployment rates frequently range from 40 to 80 percent. Subsistence hunting, fishing, and gathering provide economic value without generating employer pay stubs. Tribal governments exercise data sovereignty that prevents state agencies from unilaterally accessing employment or health records. Verification systems designed around formal employment cannot capture Indigenous economic realities, and state administrative systems cannot operate on tribal lands without negotiated consent. These are not implementation complications to be solved within existing frameworks. They are structural incompatibilities between work requirement architecture and the legal, economic, and cultural realities of tribal communities, requiring distinct policy approaches grounded in the government-to-government relationship between sovereign nations.

Article 7F: Consolidated Rulemaking Decision Matrix

Sun, 15 Feb 2026 00:00:00 +0000

State regulators implementing work requirements face hundreds of granular policy decisions across exemption design, verification architecture, coordination timing, delegation authority, and tribal sovereignty. Each decision interacts with others; choices made in exemption categories ripple through verification processes, coordination timelines, and delegation structures. This consolidated matrix synthesizes all rulemaking choices from the Series 7 handbooks while cross-referencing accommodation requirements for the sixteen special populations analyzed in Series 11 and Article 4D.

Summary: Article 7F: Consolidated Rulemaking Decision Matrix

Sun, 15 Feb 2026 00:00:00 +0000

States implementing work requirements face not a single policy decision but hundreds of granular choices across exemption design, verification architecture, coordination timing, delegation authority, and tribal sovereignty. Each decision interacts with others in ways that are difficult to anticipate: exemption category choices ripple through verification processes, coordination timelines shape who can access exemptions before deadlines pass, and delegation frameworks determine whether third parties participate in verification at all. This decision matrix synthesizes the rulemaking choices from Series 7 articles and handbooks (7A through 7E) while cross-referencing accommodation requirements for the sixteen vulnerable populations analyzed in Series 11 and Article 4D, creating a consolidated framework that reveals both the scope of required decisions and the interdependencies between them.

Series 7 Synthesis: When Administrative Architecture Becomes Policy

Sun, 15 Feb 2026 00:00:00 +0000

Medicaid work requirements depend on regulatory infrastructure that does not exist. States have eight months to design exemption categories, build verification systems, establish coordination timelines, create delegation frameworks, and negotiate tribal sovereignty agreements. The ten articles in this series demonstrate that these are not technical implementation details but fundamental policy choices determining who maintains coverage independent of employment status or work effort.

The regulatory architecture question is ultimately about trust and burden distribution. States trusting people create verification support infrastructure minimizing individual burden and exemption processes assuming legitimate barriers. States skeptical of compliance create individual responsibility systems expecting people to navigate complexity without support and exemption gatekeeping assuming most applications represent work avoidance. These philosophical orientations pervade hundreds of granular regulatory choices about documentation requirements, processing timelines, grace periods, automation investment, and safe harbor protections.

Summary: Series 7 Synthesis: When Administrative Architecture Becomes Policy

Sun, 15 Feb 2026 00:00:00 +0000

States have eight months to design exemption categories, build verification systems, establish coordination timelines, create delegation frameworks, and negotiate tribal sovereignty agreements. The ten articles in Series 7 demonstrate that these are not technical implementation details but fundamental policy choices determining who maintains Medicaid coverage independent of employment status or work effort. The regulatory architecture question is ultimately about trust and burden distribution: states trusting people create verification support infrastructure and exemption processes assuming legitimate barriers, while states skeptical of compliance create individual responsibility systems and gatekeeping mechanisms assuming work avoidance. These philosophical orientations pervade hundreds of granular regulatory choices whose cumulative effect rivals statutory eligibility rules in shaping coverage outcomes for 18.5 million expansion adults.

Work Requirements Article 7A

Sun, 15 Feb 2026 00:00:00 +0000

Complete guide to exemption policy choices for state regulators

State regulators writing exemption rules for December 2026 implementation face hundreds of specific decisions. This handbook provides decision frameworks, implementation requirements, and recommended approaches for each exemption category and edge case.

Design Principles Framework
#

Four principles should guide all exemption rulemaking:

Presumptive access: When in doubt, presume people qualify and verify later through audits rather than creating documentation barriers upfront.

Work Requirements Article 7B

Sun, 15 Feb 2026 00:00:00 +0000

Complete guide to work verification policy choices for state regulators

Work requirements mean nothing without verification systems. States must decide how employers report hours, how individuals document work, what activities qualify, and how to handle edge cases. These decisions determine whether verification creates 40-50% administrative efficiency gains through automation or becomes a paperwork nightmare driving coverage losses.

Core Verification Architecture Decision
#

The fundamental choice: Distributed submission authority versus centralized individual reporting.

Work Requirements Article 7C

Sun, 15 Feb 2026 00:00:00 +0000

Operational coordination requirements for successful implementation

Exemption and verification rules mean nothing without coordination systems determining when people face requirements, how long they have to respond, what happens during transitions, and who provides support. These coordination choices determine whether implementation is orderly or chaotic.

Redetermination Scheduling: The Fundamental Choice
#

Expansion adults face semi-annual redetermination starting January 2027 (six months after December 2026 work requirement implementation). States must decide whether everyone faces redetermination simultaneously or staggered across the year.

Work Requirements Article 7D

Sun, 15 Feb 2026 00:00:00 +0000

Legal architecture for third-party verification and exemption support

States cannot directly verify work or determine exemptions for 18.5 million people. Success requires delegating submission authority to employers, providers, educational institutions, managed care organizations, and community partners. But delegation creates legal questions: What authority can states delegate? Who bears liability when delegated entities make errors? What protections incentivize participation?

This article provides the legal and operational framework for delegation systems that enable third-party verification while protecting all parties from unreasonable liability exposure.

Administrative Architecture on Syam Adusumilli

Work Requirements Article 7A

The Exemption Architecture #

Summary: Work Requirements Article 7A

Work Requirements Article 7B

The Verification Architecture #

Summary: Work Requirements Article 7B

Work Requirements Article 7C

The Coordination Architecture #

Summary: Work Requirements Article 7C

Work Requirements Article 7D

The Delegation Architecture #

Summary: Work Requirements Article 7D

Article 7E: Tribal Sovereignty and IHS Coordination

Summary: Article 7E: Tribal Sovereignty and IHS Coordination

Article 7F: Consolidated Rulemaking Decision Matrix

Summary: Article 7F: Consolidated Rulemaking Decision Matrix

Series 7 Synthesis: When Administrative Architecture Becomes Policy

Summary: Series 7 Synthesis: When Administrative Architecture Becomes Policy

Work Requirements Article 7A

Design Principles Framework #

Work Requirements Article 7B

Core Verification Architecture Decision #

Work Requirements Article 7C

Redetermination Scheduling: The Fundamental Choice #

Work Requirements Article 7D

The Exemption Architecture
#

The Verification Architecture
#

The Coordination Architecture
#

The Delegation Architecture
#

Design Principles Framework
#

Core Verification Architecture Decision
#

Redetermination Scheduling: The Fundamental Choice
#