Approach · Multi-stakeholder workflow

One hour. Six surfaces. One record.

This is an illustrative scenario built from the synthetic personas we test against. Patricia Ann Decuir volunteers at a community organization in New Orleans. She also works part time. Her hours move through six stakeholder surfaces before they become a row in the state's audit ledger: her phone, the volunteer organization's attestation portal, her employer's payroll system, the caseworker review queue, the health plan's outreach dashboard, and the state reviewer's console.

This page walks the workflow stakeholder by stakeholder. The audience is the state Chief Technology Officer, the Managed Care Organization compliance lead, and the procurement officer who needs to evaluate how cleanly compliance data moves between actors. The architectural guarantees from /platform and the beneficiary protections from /safeguards are how this workflow holds together; this page shows what each actor does inside it.

Stakeholder breadth
6stakeholder surfaces · one shared ledger across them
Response window
30days to respond to a notice · tracked on every open case
Procedural depth
7sequenced steps before a closure recommendation can reach state staff
Audit posture
1append-only audit record · every actor's action chained to it

Updated

Chapter 01 · Beneficiary

Patricia Ann Decuir.

Patricia volunteers at a community organization in New Orleans. She also works part time at a coffee shop near the Tulane campus. Most weeks, the volunteer hours plus the part-time hours combine cleanly to satisfy her community engagement requirement.

One month her hours come up short: the bus is late, and she misses a volunteer shift. When the state sends a notice, it also arrives in her Civistara app, and the 30-day response window begins. The timeline below shows what happens next.

Mechanism · Beneficiary surface
Surface
Civistara mobile app · iOS and Android · 15 languages
Daily use
Status at a glance · in-app hour log · optional location check-in at a registered site · exclusion requests · notices
When something goes wrong
Notice arrives in-app with timestamped delivery receipt · 30-day response countdown · 4-tier urgency · status visible on every screen
Standard
Designed to WCAG 2.1 AA · 22 screens reviewed, on-device testing of 5 in progress · on-device encryption with device-only keys
What happens next

The response window.

Six narrative phases summarize the seven sequenced steps the workflow records before a closure recommendation can reach state staff. The workflow cannot skip or reorder them, and the state agency makes the decision.

  1. 1
    Notice received

    The state’s notice also arrives in the Civistara app, with the response window, fair-hearing rights, and reapplication information. Day 1.

  2. 02
    Cure period begins

    A 30-day window opens. The member can respond any time during the window. In progress: cure periods pause while a person waits for a volunteer placement.

  3. 03
    Cure submission

    Hours, an exclusion on file, employer attestation, or a status change. Patricia submits her volunteer organization’s attestation on day 11.

    Patricia is here
  4. 04
    Case-worker review

    Authorized staff only. The case-worker review exit is role-gated. No path through the procedure lets an unauthorized actor advance the case.

  5. 05
    Alternative-eligibility check

    Recorded before a closure recommendation can go forward. Outcomes: eligible on another basis, eligible for another program, or no alternative. Each outcome is a documented branch for state staff.

  6. 30
    Recovery, or hearing notice and appeal pathway

    Day 30, branch endpoint. Members who resolve the notice exit here. Those who do not receive a hearing notice and the appeal pathway specified in 42 U.S.C. § 1396a(xx)(6).

Chapter 02 · Community partner

The volunteer coordinator.

The coordinator runs the volunteer program where Patricia logs hours. They confirm her attendance, validate the work performed, and attest her hours through the partner attestation portal. The confirmation is attached to her record as evidence for state staff.

The coordinator also manages the organization’s capacity and waitlist. In progress: cure periods pause while a person waits for a volunteer placement. The design is informed by federal court decisions on earlier Medicaid work-requirement waivers, including Gresham v. Azar, 950 F.3d 93 (D.C. Cir. 2020) and Stewart v. Azar, 366 F. Supp. 3d 125 (D.D.C. 2019). Site accessibility metadata (ADA, transit, parking) lets beneficiaries filter for sites they can physically reach.

Some states may elect a self-certification regime within the data-first hierarchy that H.R. 1 §71119 permits, where the partner-attestation pathway becomes optional rather than required. The platform's data model already accommodates self-reported submissions; credit-gating logic is configurable per state. Program-integrity options for the state in that variant include signed attestations, random-sample quality review, risk-based review of anomaly flags, and cross-checks against the wage data the state already holds. See /for-states. Implementation detail under NDA.

Mechanism · Community-partner surface
Surface
Civistara partner attestation portal
Marketplace
Capacity management · waitlist · matching by interest · faith-based and community-based partner registry
Attestation
Volunteer confirmation attached to the member’s record as evidence for state staff
Accessibility metadata
ADA-accessible · public transit nearby · parking available · so beneficiaries can filter for sites they can physically reach
Chapter 03 · Caseworker

The case-worker review.

A state caseworker reviews Patricia’s response. Civistara calculates status from the evidence and routes it to state staff; the state agency decides. The review step is role-gated: only authorized state staff (caseworker, supervisor, or state administrator) can advance the case.

The caseworker also records the alternative-eligibility check before a closure recommendation can go forward. If the state later restores coverage, the restoration is recorded as a new event with a reason and timestamp, and the original record stays on the append-only ledger. See /safeguards for the full set of beneficiary protections this chapter exercises.

Mechanism · Caseworker surface
Surface
Civistara caseworker console
Authority
Role-gated state review · exclusions on file shown with the case · alternative-eligibility check required before a closure recommendation
Reversal pathway
State-approved restoration recorded with reason · original record preserved · append-only
Audit
Staff actions timestamped and role-attributed · ready for fair-hearing review · cross-referenced with /safeguards
Chapter 04 · Employer

Patricia's employer.

Patricia’s part-time employer at the coffee shop submits her hour attestations through the employer portal. Employer attestations record signer identity, time, IP and device.

This chapter shows the work pathway alongside Patricia’s volunteer pathway. When employer-reported hours and beneficiary-reported hours diverge, the discrepancy surfaces for case-worker review with a formal dispute path. The employer cannot directly affect compliance status; attestations feed verified-only credit gates rather than auto-credited credits.

Mechanism · Employer surface
Surface
Civistara employer attestation portal
Verification
Employer attestations record signer identity, time, IP and device
Discrepancy handling
Employer-reported vs. beneficiary-reported hour mismatches surface for case-worker review · formal dispute path
Authority
Employer cannot directly affect compliance status · attestations feed verified-only credit gates
Chapter 05 · Health plan (outreach)

The care-management lead.

A Managed Care Organization care-management lead sees which of the plan’s members may need help before a deadline. Federal rules bar states from delegating compliance decisions to health plans, so the plan’s view is for outreach, not decisions. In progress: signed webhooks to push status, exclusion, and appeal events into the plan’s care-management system.

Tenant boundaries are checked before data is returned, and PHI reads are audited. The plan can reach out before the response window closes, turning what could be a coverage loss into a care touchpoint.

Mechanism · Health-plan surface
Surface
Civistara health plan console
Outreach
Members who may need help before a deadline · scoped to the plan’s own members · no compliance decisions
Integration
In progress · signed webhooks into the plan's care-management system
Cross-tenant safety
Member access boundary checked before data is returned · PHI reads audited
Chapter 06 · State reviewer

The review, three years later.

Three years later, a reviewer pulls Patricia’s record. Maybe CMS asked for a sample. The append-only ledger and versioned rules are built so the procedural history can be reconstructed: what evidence arrived, which rule version applied, and what state staff decided.

Notices delivered in the app carry a timestamped receipt. Transitions are role-attributed. Appeal timelines are tamper-evident and hash-chained, verifiable on demand. Cross-link to /platform for the design principles behind this record.

Mechanism · State reviewer surface
Surface
Civistara state console
Reconstruction
Append-only audit ledger · hash-chained appeal events · versioned rules for reconstruction
Standards reference
Cross-link to /platform for the five design principles
Reviewability
In-app notices receipt-logged · transitions role-attributed · state decisions recorded with the evidence behind them

Briefing

Walk it with us.

Briefings include a walkthrough of the stakeholder consoles with synthetic data, a scenario using your state’s rules, and a review of what is built today and what is in development against your requirements.

Detailed product roadmap and source-citation evidence available under NDA.

Schedule a briefing