Civic tech: Eligibility

Translating brand-new policy into a Medi-Cal renewal people can finish

New federal work rules, a tight deadline, and requirements that changed every other day. My job was to turn them into clear steps on BenefitsCal.

Role
UX Designer
Timeline
Sept 2024 - Present
Team
State of California, Project Managers, Engineers
Tools
Figma
Overview

BenefitsCal - California Eligibility Portal

BenefitsCal is a portal where Californians can get and manage benefits online. This includes food assistance (CalFresh) formerly food stamps, cash aid (CalWORKs, General Assistance, Cash Assistance Program for Immigrants), and affordable health insurance (Medi-Cal). This includes program status, benefit amount, and other case details.

As a UX designer, I've spent most of my time on BenefitsCal enhancing the site: policy-driven updates, navigation, content clarity, and accessibility. I've led several enhancements end to end, including the Medi-Cal renewal, the CalFresh renewal, and the login experience. This case study focuses on the Medi-Cal renewal.

  • Easier to log into their BenefitsCal account
  • More comprehensible to apply for benefits
  • Manage their account
The problem

A policy no one had implemented before, on a deadline

The HR1 policy introduced new work and community engagement rules for Medi-Cal, along with a way to claim an exemption from them. It had never been done before and was high priority: falling behind would be costly for the state and, worse, could leave Californians who depend on Medi-Cal without coverage. BenefitsCal doesn't determine eligibility. It's the pathway people use to apply and renew, so everything we showed had to follow a policy that was still being written.

How might we turn new, still-changing policy requirements into a renewal experience people can complete online, without having to go to a county office?
  • Requirements and form language changed often, sometimes every other day
  • Content had to stay at a sixth-grade reading level
  • The old form made people repeat the same information over and over
The solution

Clear steps, familiar patterns, no repeated answers

I designed both the exemption questions and the process for reporting work or community engagement, updating existing screens and building new ones. Wherever possible I reused patterns people already knew, and I cut out questions that made them retype information we already had.

Design process

Designing while the policy was still being written

Most of the challenge wasn't any single screen. It was keeping the design in step with constant changes while making sure the online path stayed easier than going in person.

  1. 01

    Field research at county offices

    Visited county offices to see why people renew in person when they could do it online, and where the online experience left gaps we could close.

  2. 02

    Reuse what works

    Adapted the CalFresh work-rules screens (ABAWD) for the Medi-Cal exemption questions. Same structure for a cohesive experience, with options and wording rewritten for Medi-Cal's rules. With the time crunch, there was no reason to rebuild something that already worked.

  3. 03

    Never answer twice

    The old form asked people early on to confirm their information hadn't changed, then made them re-enter it anyway. We replaced that with a background check so it happens automatically instead of being another yes/no question.

  4. 04

    Keep 50+ stakeholders aligned

    Presented designs to groups of 50+ people, including my team, the client, and external stakeholders. Worked through gaps between the old and new form language as requirements shifted.

Final design

The Medi-Cal renewal flow

Updated and new screens covering the HR1 exemption questions and work and community engagement reporting, built on familiar BenefitsCal patterns and written in plain language.

Reflection

What this project taught me

Lessons learned

  • Clear documentation and tidy files are a quiet superpower. Labeled, organized designs mean anyone can pick up where I left off
  • Translating shifting policy language into user-facing steps is as much design work as the screens themselves
  • Under a tight deadline, reusing a proven pattern can be the best design decision

Next steps

  • Stay closer to development after handoff so design intent carries through to the build