Akshay DineshWhen a public program adds a work requirement, the rule is usually described in simple terms: people must work, look for work, attend school, volunteer, or join an approved activity to keep receiving benefits. In practice, the economics is less simple. A work requirement changes not only what people are expected to do, but also how eligibility is checked, how often paperwork must be filed, what counts as proof, and who loses help because of missed forms or confusing rules.
That is why work requirements are often debated in programs such as Medicaid and the Supplemental Nutrition Assistance Program, better known as SNAP. Supporters see them as a way to connect public benefits with employment and reduce spending on people who could work but do not. Critics argue that many affected adults already work, have unstable hours, care for family members, face health limits, or lose coverage because of reporting problems rather than a real refusal to work. A useful way to understand the issue is to look at incentives, administrative burden, and tradeoffs together.
What a work requirement actually requires
A work requirement is a condition attached to eligibility. Instead of qualifying only through income, age, family status, disability status, or another program rule, a person may also have to show a certain amount of work or approved activity. The common benchmark in recent U.S. policy is 80 hours per month, which is roughly 20 hours per week.
Medicaid and SNAP use different legal structures, but the basic idea is similar. In June 2026, the Centers for Medicare and Medicaid Services described a Medicaid community engagement rule for certain non-pregnant adults ages 19 to 64 who are not enrolled in Medicare and are covered through specified adult Medicaid groups. Qualifying activities can include employment, education, community service, or other approved activities. SNAP has long had separate rules for many able-bodied adults without dependents, often called ABAWDs, who can face a three-month time limit unless they meet work or training rules or qualify for an exemption.
The word work can therefore be misleading if it sounds like only a payroll job counts. Programs may count paid work, job training, school, volunteering, work programs, or a combination. Some people may also be exempt because of pregnancy, disability, caregiving, age, medical limitations, or other conditions. The hard part is not only writing those categories down. The hard part is proving, checking, and updating them for millions of people whose work hours, health, family responsibilities, and paperwork access can change from month to month.
The incentive idea behind the rule
The economic argument for work requirements begins with incentives. If benefits are available with no employment condition, some policymakers worry that the program may reduce the pressure to work or search for work. A requirement tries to make benefits conditional on labor-force attachment, training, or community participation. In theory, that can encourage more people to work, keep people connected to job services, and reassure taxpayers that assistance is aimed at people who are making an effort or facing a recognized barrier.
That logic is easiest to picture when someone is fully able to work, has available jobs nearby, understands the rules, and can document every hour without trouble. For that person, a work requirement may act like a nudge. It says the benefit continues if the person stays connected to work or an approved pathway toward work.
Real households are often messier. Many low-income workers have changing schedules, seasonal jobs, gig work, short shifts, transportation problems, child-care gaps, or health appointments that interrupt work hours. A person might work 90 hours one month, 65 the next, and 100 the month after that. Another person may have a job but no easy way to upload pay stubs, answer mail quickly, or correct a mistake before a deadline. The incentive effect and the paperwork effect can point in different directions.
That distinction matters because losing benefits is not the same thing as getting a better job. If someone loses food assistance or health coverage because they missed a reporting step, the program may spend less money, but the person has not necessarily become more employed. The rule has changed measured enrollment, not automatically changed the labor market.
Administrative burden can decide who keeps help
Administrative burden is the cost of dealing with a rule. It includes forms, phone calls, online portals, proof documents, office visits, deadlines, notices, appeals, and confusion about what counts. These costs are not always visible in a program budget, but they strongly shape what happens.
Work requirements tend to create several layers of burden. First, the program must identify who is subject to the rule and who is exempt. Then it must tell people what they need to do. Then it must collect proof, check that proof, process exceptions, handle errors, and repeat the process on a schedule. States and local agencies need computer systems, call-center staff, caseworkers, training, notices, translations, and appeal procedures. Enrollees need stable addresses, internet access or phone access, time, documents, and enough understanding to avoid accidental noncompliance.
The Arkansas Medicaid work-requirement experience in 2018 became a major reference point because coverage losses were large and quick. KFF has reported that more than 18,000 people lost coverage while the policy was in effect, with many losses tied to reporting and documentation problems. That example does not prove every work requirement will work the same way, but it shows why the mechanics of reporting can matter as much as the formal rule.
Administrative burden also changes the meaning of an exemption. A rule may say that people with certain health conditions, caregiving responsibilities, or other barriers do not have to meet the work standard. But if an exempt person must find the right form, submit it correctly, renew it often, and respond to notices on time, the exemption is only as useful as the process around it. A poorly designed exemption can exist on paper while still failing people in practice.
Why Medicaid and SNAP raise different concerns
Medicaid and SNAP both support basic needs, but they do not work the same way. Medicaid is health coverage. Losing it can mean losing access to prescriptions, doctor visits, mental health care, chronic-disease management, or preventive care. If a person becomes sicker after losing coverage, working may become harder, not easier. That is one reason health-policy researchers pay close attention to whether Medicaid work requirements actually increase employment or mainly reduce coverage.
SNAP is food assistance. Its work rules are often discussed through the ABAWD time limit, which can restrict benefits after three months in a three-year period for certain adults who do not meet work or training requirements and do not qualify for an exemption. SNAP benefits are usually modest, but they can be central to a household food budget. Losing them can shift costs to food banks, relatives, local charities, or unpaid household tradeoffs such as skipping meals or buying cheaper, less nutritious food.
The overlap between programs can also be important. A low-income adult may interact with Medicaid, SNAP, housing assistance, unemployment insurance, tax credits, and child-care programs at the same time. Each program can have its own definitions, reporting schedule, online system, and exemptions. A rule designed program by program may feel much heavier when a household must manage all of them together.
There is also a local labor-market question. A work requirement assumes that qualifying work or training is realistically available. In places with weak public transportation, few entry-level jobs, seasonal employment, or limited training slots, the requirement may be harder to satisfy even for people who are trying. A rule that looks uniform at the federal level can land differently in rural counties, small towns, suburbs, and large cities.
The tradeoff between savings, access, and trust
Work requirements can reduce government spending if fewer people receive benefits. The Congressional Budget Office often analyzes such policies by estimating both budget savings and coverage or enrollment effects. But a lower enrollment number can mean several different things. It may mean fewer ineligible people are receiving help. It may mean eligible people were discouraged or confused. It may mean people found work and no longer needed benefits. Or it may mean people who still needed help lost it because they could not navigate the process.
That is why policy design matters. A work requirement with clear notices, automatic data matching, broad exemptions, easy reporting, good language access, and quick error correction will not behave the same way as one with confusing mail, limited online access, strict deadlines, and narrow exemptions. The same 80-hour rule can produce very different outcomes depending on implementation.
Trust is part of the economics, too. People are more likely to comply with a rule they understand and believe is fair. Agencies are more likely to administer a rule well if they have enough time, money, staffing, and reliable data systems. Employers may be pulled into the process if workers need schedule records or verification letters. Health clinics, food banks, legal-aid groups, and community organizations may also absorb extra demand when people lose benefits or need help fixing paperwork problems.
A balanced evaluation should ask more than whether a rule sounds strict or generous. It should ask who is subject to it, what activities count, how exemptions are handled, how often reporting is required, what happens after a mistake, how much administration costs, and whether employment actually rises. A program can be too loose, but it can also be so difficult to navigate that it fails people it was meant to serve.
How to read work-requirement debates carefully
Strong claims about work requirements often leave out a key distinction: the difference between eligibility policy and labor-market policy. If the goal is to help people work, then job availability, wages, transportation, child care, health, training quality, and employer flexibility matter. If the main tool is benefit termination, the policy may reduce enrollment faster than it increases employment.
It also helps to notice whether a debate is about people who are truly not working, people whose work hours are unstable, or people who are exempt but must prove it. Those groups are not the same. A cleaner policy conversation separates them instead of treating every person affected by the rule as though they face the same choices.
The most practical question is not simply whether work should matter. Work already matters deeply in household income, health insurance, taxes, retirement benefits, and daily stability. The better question is how a public program should recognize work without punishing people for poverty, unstable schedules, illness, caregiving, weak local job markets, or paperwork obstacles. That question is harder, but it is also more honest.
Work requirements sit at the intersection of economics and administration. They are about incentives, but they are also about forms. They are about public budgets, but they are also about grocery carts, prescriptions, bus schedules, and missed notices. Any serious evaluation has to follow the rule all the way from the policy document to the person trying to keep life steady while meeting it.
Add comment