Champions · For the people who carry the message

Built so that Louisianans don't lose Medicaid for the wrong reasons.

This page is for the people who will champion this work in their communities. State legislators, county officials, advocacy directors, faith leaders, and the policy nonprofits that hold the line for Medicaid beneficiaries.

The technical depth lives at /platform and /safeguards. This is the human story, told through illustrative scenarios built from synthetic test personas. Every fact about the requirement cites the Louisiana Department of Health or a dated public source.

For

State legislators, county officials, advocacy directors, faith leaders, healthcare-policy nonprofits

Length

A 10-minute read. A two-minute scan.

Brief

A four-page version is downloadable at the close.

01 · What is changing

Most Louisiana members are exempt. The risk is losing coverage for paperwork.

Louisiana starts on January 1, 2027.

The requirement starts with new applicants and members renewing from January 1, 2027. Members renewing in January were mailed renewal packets with the new materials in November 2026. Members aged 19 to 64 without an exclusion need 80 hours a month of work, volunteering or a work program, or $580 a month in earnings, or half-time school.

Source: Louisiana Department of Health, Medicaid work requirements page; Informational Bulletin 26-19.

About 297,000 members affected. Most members are exempt.

LDH expects about 297,000 members to be affected, and expects a significant share of them to be medically frail. LDH publishes 13 exclusions, including medically frail, substance use treatment, caregivers, and release from incarceration in the last three months.

Source: LDH fact sheet, January 2026; LDH Medicaid work requirements page.

Not answering can close coverage, even for eligible people.

LDH’s own guidance is direct: “Failure to respond to requests from Louisiana Medicaid could result in health coverage closure, even if the member is still eligible.” Members have 30 days to respond to a notice.

Source: LDH Medicaid work requirements page; LDH verification form, November 2026.

The state decides. Health plans cannot.

The Louisiana Department of Health makes eligibility decisions. Federal rules bar states from delegating compliance decisions to Medicaid health plans. Civistara calculates status from the evidence and routes it to state staff; the state agency decides.

Source: Georgetown CCF explainer of the federal interim final rule, July 2026.

Arkansas already showed what happens when tracking fails.

In the first seven months of Arkansas’s Medicaid work requirement, more than 18,000 people lost coverage, about 1 in 4 of those subject to it. Many who were disenrolled “only found out when they tried to seek medical care or fill a prescription at a pharmacy.” The Urban Institute’s lessons include more community-based outreach and simpler ways to report.

Civistara Compliance is built to help eligible people keep their coverage: exclusions on file, deadlines in view, and notices in their own language.

Source: Urban Institute, Lessons from Launching Medicaid Work Requirements in Arkansas, October 2019.

02 · What the platform does

Eight commitments, built into the platform.

Each row pairs a design commitment with what it means for a member. Each cites the public Architecture Decisions Record or statute behind it. Civistara calculates status from the evidence and routes it to state staff; the state agency decides.

  1. 01

    No closure before the deadline.

    Moving a case toward closure before the response deadline throws an exception in code, not only a policy warning. ADR-006.

    A case cannot be pushed toward closure early because a deadline was mishandled. The workflow refuses the step, and the state agency makes the decision.

  2. 02

    Every step, in order.

    A 15-state noncompliance procedure with notice, cure, hearing and appeal branches. A case moves only along defined transitions, so no step can be skipped. ADR-006; 42 U.S.C. § 1396a(xx)(6).

    Before a closure recommendation reaches state staff, the record shows notice, the response window, caseworker review and an alternative-eligibility check.

  3. 03

    In progress: a pause while a person waits for a placement.

    Cure periods pause while a person waits for a volunteer placement. This is in progress: the pause is recorded today, and applying it automatically is still being built. ADR-007. Informed by Gresham v. Azar, 950 F.3d 93; Stewart v. Azar, 366 F. Supp. 3d 125.

    A member in a rural parish whose nearest placement has a waitlist should not be counted down for a gap on the state’s side.

  4. 04

    15 languages, including Spanish and Vietnamese.

    Onboarding, status, exclusion requests, and in-app guidance in 15 languages. Right-to-left text rendering for Arabic, Urdu, and Persian. /app §2.

    A Vietnamese-speaking grandmother in New Orleans East can see her status, her deadlines and what to do next in Vietnamese, instead of guessing at an English form.

  5. 05

    Exclusions on file, in plain view.

    Members can request an exclusion with supporting documents, and state staff see it with the case. A staff-assisted path for providers is in development. Louisiana’s 13 exclusions are LDH’s list. /for-providers; ADR-005.

    A pregnant member, a medically frail member, a caregiver of a person with a disability, a former foster youth, a Native American eligible for Indian Health Service: an exclusion on file is visible to the state staff who decide.

  6. 06

    No AI denials, ever.

    The status calculation has no AI input path. CivicAI is read-only by design. ADR-008.

    No Louisianan's coverage is denied by a model that the platform cannot explain to a fair-hearing officer.

  7. 07

    An audit trail built for review.

    Audit and ledger records are written as new rows, and the database rejects changes or deletion. Integrity is enforced at the storage layer, not the policy layer. ADR-001; ADR-002.

    Years later, at a fair hearing, the history is still there. The member can see what happened to their case.

  8. 08

    Offline mode for the audience the legacy systems forgot.

    Offline-first: an encrypted read cache, queued changes, and automatic sync on reconnect. /app §3.

    A member on a rural bus route or in a dead zone can still submit what they did; it syncs when the signal returns.

03 · Illustrative scenarios

Eight scenarios the platform is built for.

Illustrative scenarios built from the synthetic personas we test against. These are not real people, and no real organization is named. The first four are detailed below; the remaining four expand.

Scenario 01 · Volunteer hours · New Orleans

Patricia Ann Decuir.

Patricia volunteers at a community organization in New Orleans. The organization confirms her attendance through the partner attestation portal, and the confirmation is attached to her record as evidence. Civistara calculates her status from that evidence and routes it to state staff; the state agency decides.

Each hour Patricia logs is timestamped and written to an append-only record; when she chooses location check-in, the location is recorded too. Years from now, at a fair hearing or a record review, the history is still there as it was recorded.

Patricia is the everyday case: when the infrastructure does its job, it is invisible to her and clear to the person reviewing her record.

Read the architectural commitments behind Patricia's case at/decisions/append-only-decision-ledgerand/decisions/phased-noncompliance-procedure.

Scenario 02 · Rural waitlist · Louisiana

Travis Wayne Fontenot.

Travis lives in a rural parish. His nearest participating community partner is far away and has a waitlist. The wait is not his fault.

A pause in the cure period while a person waits for a volunteer placement is in progress: the waitlist pause is recorded today, and applying it automatically is still being built. Whether a pause applies is the state’s policy decision.

The design is informed by federal court decisions on earlier Medicaid work-requirement waivers: Gresham v. Azar, 950 F.3d 93 (D.C. Cir. 2020) and Stewart v. Azar, 366 F. Supp. 3d 125 (D.D.C. 2019). Both courts faulted approvals that failed to consider the effect on coverage.

Read the architectural record at/decisions/capacity-shortage-tolling.

Scenario 03 · Exclusion · American Indian or Alaska Native

James Allen Dardar.

James is an enrolled member of a federally recognized tribe and is eligible for Indian Health Service care. LDH lists Native Americans and Alaska Natives eligible for Indian Health Service among the people who are exempt.

With the exclusion on file and its supporting documents attached, state staff see it with his case. The state agency decides.

The same path applies to every exclusion on LDH’s list.

Read the architectural record at/decisions/closed-set-actions.

Scenario 04 · Recent release · Louisiana

Darius Wayne Celestin.

Darius came home six weeks ago. LDH lists people released from incarceration within the last three months among those who are exempt, so his record shows the exclusion and the date it ends.

Read the architectural commitment at/decisions/phased-noncompliance-procedure.

Scenarios 05 · 08 · Select any name to expand

Four more.

Each remaining scenario maps to a different champion’s audience: faith leaders, senior advocates, disability-rights advocates, and health-equity advocates. Select any name to read the full case.

  • Scenario 05 · Faith-based volunteer · New Orleans

    Reginald Wayne Batiste.

    Volunteer hours through a faith-based organization. AI can speed up approvals only; it never denies.

    Reginald volunteers at his parish food pantry. The faith-based organization confirms his hours through the partner attestation portal, and clear cases can move quickly to state staff.

    AI cannot deny anyone’s coverage. CivicAI, the member-facing assistant, is read-only and cannot change any compliance status. Faith leaders can speak with confidence: no algorithm takes coverage away, and state staff make the decision.

    Read the architectural record at/decisions/ai-auto-approve-only.

  • Scenario 06 · Senior with delegated access · Louisiana

    Ethel Mae Treme.

    Age 74 and exempt by age. Her daughter helps with the account, and her actions are recorded under her own name.

    Ethel is 74; LDH lists people aged 65 or older among those who are exempt. Her daughter helps manage the mobile account, and the platform is designed to record her daughter’s actions under the daughter’s own name.

    The platform does not assume tech fluency. A family member who supports her can help, with the same accountability.

    Accessibility commitments live across/appand the WCAG 2.1 AA scope on/safeguards.

  • Scenario 07 · Exclusion · Disability

    David Anthony Arceneaux.

    Exempt as a person who is blind or disabled. The exclusion is on file with his case.

    LDH lists people who are blind or disabled among those who are exempt. David’s exclusion is recorded with its supporting documents.

    State staff see the exclusion with his case, and the state agency decides. LDH says it will use information the state already has, such as Social Security records, to check whether members meet the requirements.

    Read the architectural record at/decisions/closed-set-actions.

  • Scenario 08 · Returning after a closure

    Jerome Duval Landry.

    Coverage closed before; back now. His case runs through the same steps as anyone else’s.

    Jerome’s coverage was closed before. He is back. The earlier history and his new record are both on the ledger, intact.

    The workflow treats every member’s case the same way, regardless of history: the same steps, the same response window, the same caseworker review and alternative-eligibility check. Prior history does not become a hidden rule that weights the current case.

    Read the architectural records at/decisions/append-only-decision-ledgerand/decisions/phased-noncompliance-procedure.

04 · For your community

Your constituents. Your congregation. A Vietnamese-speaking grandmother who is not sure what the renewal letter means. A veteran whose nearest volunteer placement has a waitlist. A cousin who came home last month and needs his medication tomorrow. A mother whose daughter helps with her account. These are the people who can lose coverage for paperwork reasons when the infrastructure fails, and the people this platform is built to help keep it.

05 · The discipline

Five rules the platform holds itself to.

  1. Every claim traces.

    Every design claim on this page cites a public Architecture Decisions Record or a statute. Every fact about the requirement cites the Louisiana Department of Health or a published source with a date. No "studies show" language. No imagined percentages. No invented outcomes.

  2. AI cannot deny benefits.

    The status calculation has no AI input path. CivicAI, the member-facing assistant, is read-only and cannot change any compliance status. AI may only speed up clear approvals. The state agency decides.

  3. The audit trail is built for review.

    Audit and ledger records are written as new rows, and row-level database triggers reject changes or deletion. Integrity is enforced at the storage layer, not by an honor code, so the history is there for a fair-hearing review years later.

  4. Illustrative scenarios, clearly labeled.

    The scenarios on this page are built from synthetic test personas and say so. Photography, when it ships, will be documentary photography of real Louisianans with releases. Until then, no stock photography and no AI-generated faces.

  5. Scenarios are test cases, not testimonials.

    Every scenario maps to a synthetic persona in the catalog the platform’s engineers test against. None is a real person, and none is quoted.

The full Architecture Decisions Record collection is at/decisions.

06 · Bring this to your community

We will come to your town hall.

If you want to bring this to your community, get in touch. We will come to your town hall, your parish council, your advocacy convening, your faith-leader gathering. We will also send the four-page brief, distilled from this page, that you can hand to a colleague, a mayor, or a constituent.

A four-page document. Print-ready. No form, no gating, no follow-up sales loop.