Exemption Screening

Work Requirement Exemptions Identified From Data Your Agency Already Holds

Amorphic HHS 360 resolves constituent identity across agency systems, screens records against the exemption categories the state’s own data can support, and assembles the evidence behind each apparent match for a caseworker to determine. The policy rules stay separate from the data, so when requirements change, the update is quick to make and easy to trace.

Your data. Your AWS account. Your rules. Auditable from day one.

The Data Exists. The Infrastructure to Use It Doesn’t.

The state owns the data. It asks the person to prove it anyway.

A policy changes. Every file gets manually reprocessed.

Across states, a large share of people lose benefits for procedural reasons: missed paperwork, failed reverification, or administrative mismatch, not because they stopped qualifying.

In New Hampshire’s 2019 work requirement, the state cleared far more people from labor data it already held than managed to self-report their hours. The data to spare someone the paperwork chase usually exists inside the agency.

One Foundation. Three Steps That Stay Separate by Design.

In the eligibility systems we have seen, three things that need to be separate are usually tangled together. Keeping them distinct is what makes the system adaptable when requirements change.

Infographic: One foundation, three steps that stay separate by design. The foundation: work requirement verification runs on Amorphic HHS 360, which ingests, cleans, standardizes and quality-checks source system data into governed, reusable datasets before any record is matched. Step 1, Entity Resolution: are these the same person? The matching engine resolves records across agency systems, deterministic first, then probabilistic, routing low-confidence matches to a person for review. Step 2, Master Data Management: which source do we trust? Survivorship rules produce authoritative master records with full lineage back to every source. Step 3, The Rules Engine: who appears to qualify for an exemption? Exemption rules are human-readable, configurable and auditable; when policy changes, you update the rules and re-run. When federal rules change, you re-run the policy, not the whole pipeline. Every screening result carries its audit trail: which record was read, which rule version was applied, what the output was, and when.

The Burden of Proof Shifts From the Person to the System.

Before and after infographic. Before: the individual proves facts the state already holds; different departments pay separately for the same third-party verification; the burden falls on the person who can least carry it. After: the process starts from data the agency already holds; the platform surfaces exemptions the state already has evidence for; most records resolve from agency data, so staff focus on genuine edge cases. Exemption categories a state can screen from its own records include parents and caregivers of dependents, former foster youth, veterans rated 100 percent disabled by the VA, and people who are pregnant or postpartum.
Buy Third-Party Data Last.

Buy Third-Party Data Last.

Agencies pay third-party vendors to verify facts the state already holds, and pay more than once: different departments buy the same verification, separately, for the same person. Third-party data has a role, but it belongs at the end of the process. Start with what the agency already owns, and outside lookups become the exception, bought only for what the agency genuinely does not have.

Proven on Real State Data, Now in Delivery.

Cloudwick is delivering SNAP work requirement verification for a state health and human services agency under a signed agreement, with agency data flowing since August 2026.

Proof points: 99.93 percent match and rule accuracy on real state data; three months from deployment to first run; scaling statewide. Medicaid work requirement screening extends the same rules engine and foundation and adds Medicaid claims data; it is not yet in delivery.

The Agency Determines. The Platform Identifies and Assembles.

The agency determines eligibility and exemptions. The platform identifies who appears to qualify and assembles the supporting evidence. Federal law sets that division (42 CFR 431.10(c)(2)), so no vendor’s system makes the call. Every screening output and rule version is logged so the state can show how a result was assembled if a determination is appealed.

The Foundation Built for HR1 Carries Every Program That Follows.

Diagram: the foundation of entity resolution, master records and a rules engine feeds every program that follows: cross-agency data sharing, care coordination, Medicaid community engagement and program analytics. Because policy rules stay separate from the data, the matching logic, rule sets and screening outputs built for HR1 carry forward to every use case that follows.

Wherever You Are With HR1, This Works With What You Have.

Many states are already down the road on HR1. Some of those approaches are costly to run, hard to change when rules shift, and dependent on outside data vendors. This foundation can sit underneath what you have already built, automate more of it, lean on the data you already own, and hold up the next time policy shifts.

Cloudwick deploys into the agency’s own AWS account. You own the data, the encryption keys, and the access controls.