SB 961 refocuses how California treats college students for CalFresh (SNAP) eligibility. Rather than relying on case-by-case campus program approvals, the bill directs the State Department of Social Services to treat broad categories of public higher-education programs and a set of state-funded student support programs as qualifying ‘‘local educational programs that increase employability’’ to the extent federal law allows, and it creates a streamlined path for other campus programs to seek certification.
The bill also builds a procedural pipeline for targeted outreach: it requires the Student Aid Commission and CDSS to craft a data‑sharing agreement and for the Commission to modify its Grant Delivery System so students who opt in can have limited contact information shared with CDSS, counties, and campus system offices to receive basic‑needs and CalFresh outreach. The policy aims to reduce student food insecurity and increase CalFresh participation, but it pairs expanded access with new data, consent, IT, and county workload implications that agencies will need to operationalize.
At a Glance
What It Does
SB 961 creates a presumption—subject to federal law—that adult education, career technical education, certificate programs, and all degree programs at California public institutions qualify as state-approved local educational programs that increase employability for the CalFresh student exemption. It requires a CSAC–CDSS data‑sharing agreement and changes to CSAC’s Grant Delivery System so students can opt in to limited contact‑info sharing for direct outreach about CalFresh and other basic‑needs services.
Who It Affects
Public higher education systems (California Community Colleges, CSU, UC), the Student Aid Commission, the State Department of Social Services, county human services agencies that administer CalFresh, campus basic‑needs offices, and students enrolled at least half‑time. IT vendors and operators of CalSAWS and the Grant Delivery System will also be engaged.
Why It Matters
If implemented, SB 961 could materially increase outreach to students who are eligible but not enrolled in CalFresh, shifting verification work away from students and toward system coordination. That promises higher uptake of federal benefits and potential campus retention gains, but it also creates new privacy, technical, and county administrative burdens and depends on federal SNAP rules and funding structures.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill rewrites how California treats campus programs for the CalFresh student exemption. Currently, CDSS maintains a list of approved local educational programs that increase employability (LPIEs); students participating in an approved LPIE can qualify for the SNAP student exemption.
SB 961 directs CDSS to issue guidance that, to the extent federal law permits, treats large categories of public higher‑education offerings—adult education, career technical education, certificates, and associate through doctoral degree programs—as state‑approved LPIEs. That change is intended to remove a common paperwork barrier where students and campus staff must prove program approval for the student exemption.
The bill keeps a pathway for campus programs not covered by the presumptive categories: CCC, CSU, and UC campuses may submit certification applications for other campus-based programs and CDSS must determine whether those programs meet the employability standard. CDSS must work with CalSAWS to show general categories of approved programs in caseworker systems, and it will implement these changes through all‑county letters or similar instructions rather than a standard regulatory process.On outreach and enrollment, SB 961 requires CDSS and the California Student Aid Commission to build a data‑sharing agreement that complies with FERPA and state privacy law.
Under that agreement the Commission must amend its Grant Delivery System to flag students who may be CalFresh‑eligible, collect a separate opt‑in consent to share limited contact information, and then provide that information to CDSS. CDSS can in turn share those limited data with the appropriate county human services agency and the systemwide office for the campus so counties and campuses can conduct direct outreach about CalFresh and basic‑needs services.
The bill specifies the contact fields to be shared and limits use of the data to outreach and linkage to resources.SB 961 also builds reporting and implementation guardrails: CDSS must issue the guidance letter and implement the program categories by specified deadlines, work with CalSAWS and report annually (for a defined period) on approved, pending, and denied campus program applications, and require campuses to contact students who opt in beginning in the 2028–29 academic year for CCC and CSU (UC campuses are requested to participate). The statute emphasizes compliance with federal law—for example, where the presumption conflicts with USDA rules, federal constraints will control—so some provisions are explicitly qualified by ‘‘to the extent permitted by federal law.’u
The Five Things You Need to Know
By May 31, 2027 CDSS must issue guidance that, to the extent federal law permits, treats adult education, career technical education, certificate programs, and all degree programs at public institutions as state‑approved local educational programs that increase employability for the CalFresh student exemption.
The Student Aid Commission must amend its Grant Delivery System to identify potentially CalFresh‑eligible students, let those students provide a separate, opt‑in consent for sharing contact information, and then send consented contact records to CDSS.
The student contact information limited to be shared is legal name, email address, ZIP code or county of residence, and telephone number; CDSS may share those data only with the appropriate county human services agency and the campus system office for the purpose of outreach to basic‑needs services and CalFresh.
CDSS will accept certification applications from campus‑based programs not covered by the presumptive categories, determine approvals, and publish annual reports (beginning Sept. 1, 2028 through 2030) disaggregating approved, pending, and denied campus programs by campus and name.
CDSS must implement the program changes via all‑county letters or similar instruction (with the force of regulation) by May 30, 2027, and campuses must begin contacting students who opted in starting in the 2028–29 academic year (CCC and CSU required; UC requested).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
CSAC Grant Delivery System: opt‑in and consent flow
This section requires the California Student Aid Commission to modify its Grant Delivery System after entering the CDSS data‑sharing agreement. Practically, that means the Commission must implement a screening process to identify students who might qualify for CalFresh, present a separate consent mechanism that is distinct from other financial aid consents, and link identified students to campus and off‑campus basic‑needs services. The section narrowly defines the contact fields that may be shared and limits use of the data to basic‑needs outreach—an implementation detail that will drive how the Commission designs consent screens and audit trails.
Duplicative CSAC requirement for other student populations (parity across systems)
This companion provision mirrors Section 69408.5’s requirements for other segments or student groups covered by the Commission’s Grant Delivery System. In practice it ensures both major student‑facing application systems within the Commission follow the same opt‑in, data‑limitation, and linkage procedures so outreach is consistent across program types and campuses.
Guidance, administrative instructions, and standardized verification
The bill tightens CDSS’s instruction set to counties: it must publish and maintain detailed processing guidance that minimizes student burden for verifying CalFresh student exemptions, and includes specific pathways for workstudy, employment self‑certification, and career and technical education students. It directs campuses to distribute standardized verification forms where practicable. This is intended to reduce ad hoc verification requests that delay or deter student enrollment in CalFresh but will require operational changes at county caseworker desks.
Presumption that many public higher‑education programs qualify as LPIEs
The new section creates the central substantive change: CDSS must issue a guidance letter that, subject to federal limitations, designates broad program categories and a list of specified state‑funded student support programs (EOP, EOPS, Guardian Scholars, etc.) as state‑approved local educational programs that increase employability. It also preserves an application route for other campus programs and directs CDSS to integrate category listings into CalSAWS. The instruction to bypass formal rulemaking and use all‑county letters accelerates implementation but reduces formal public notice and comment.
CSAC–CDSS data‑sharing agreement and outreach chain
This section mandates the data‑sharing agreement’s creation and sets clear limits: data must be shared in compliance with FERPA and state privacy law; CDSS may share the limited contact fields only with the ‘appropriate’ county agency and systemwide campus office; and data use is restricted to linking students to basic‑needs resources and CalFresh outreach. It specifies an operational start for campus outreach (2028–29 academic year) and makes CCC and CSU participation mandatory while UC campuses are requested to participate.
Timelines, reporting, and administrative effect
CDSS must issue the guidance letter by a specified date and implement the changes through all‑county letters by May 30, 2027. The department must report annually to legislative higher education and human services committees from Sept. 1, 2028 through 2030 on approved, pending, and denied program applications, and post that data publicly. These deliverables create accountability but also concentrate a number of IT, policy, and training tasks within a compressed timeframe.
This bill is one of many.
Codify tracks hundreds of bills on Social Services across all five countries.
Explore Social Services in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Food‑insecure students enrolled at least half‑time: They get a lower verification barrier to the CalFresh student exemption and direct outreach from campuses and counties, which should increase enrollment and reduce unmet food needs that harm retention and completion.
- Campus basic‑needs and student support offices: Easier identification of students who opt in reduces reliance on students to self‑navigate benefit systems and lets campuses target services and referrals more efficiently.
- Public higher education systems (CCC, CSU, UC): A clearer, statewide approach reduces administrative friction when students seek exemption verification and aligns system offices with county caseworkers, simplifying cross‑system coordination.
- Counties and local economies: Higher CalFresh participation by students channels federal dollars into local economies and can lower uncompensated costs associated with student hunger (e.g., health and emergency services).
- Policy planners and researchers: The reporting requirements and system changes produce disaggregated program data that can inform future policy and measure outreach effectiveness.
Who Bears the Cost
- County human services agencies: Counties will handle increased outreach follow‑ups, eligibility determinations stemming from CSAC referrals, and possibly higher caseloads without a guaranteed funding increase, creating front‑line workload and staffing pressures.
- State agencies (CDSS and CSAC): Both agencies must build, negotiate, and operate a FERPA‑compliant data‑sharing architecture, update IT systems (Grant Delivery System and integration with CalSAWS), and create new operational guidance—work that requires staff time and procurement.
- Colleges and campuses: Campus staff must implement consent collection, perform outreach to opted‑in students, and coordinate with county agencies; smaller campuses with limited basic‑needs capacity will feel these operational costs acutely.
- Privacy/compliance teams and legal counsel: Institutions must design and monitor ‘‘separate and distinct’’ consent flows, FERPA compliance, and data use limitations, increasing legal and technical oversight costs.
- State budget (potentially): The bill acknowledges federal SNAP cost‑sharing changes in federal law; if federal rules raise California’s share of administrative or benefit costs, the state and counties may face fiscal exposure tied to higher take‑up.
Key Issues
The Core Tension
The central tension is between widening access to CalFresh for students (reducing verification friction and enabling proactive outreach) and the legal, technical, and fiscal limits imposed by federal SNAP rules, student privacy law (FERPA), and local administrative capacity—expanding eligibility in principle can increase participation, but it also raises compliance exposure, operational complexity, and costs that are not fully resolved in the bill.
SB 961 trades a case‑by‑case administrative model for a broad categorical approach, but the draft repeatedly qualifies that shift with ‘‘to the extent permitted by federal law.’' That caveat is critical: USDA SNAP rules determine whether a blanket presumption will withstand federal review. If USDA requires program‑level validation or rejects broad categorizations, counties could be left with inconsistent treatment across campuses and programs, and CDSS could face audit and recoupment risk.
The bill attempts to limit data sharing to a small set of contact fields and insists on separate, opt‑in consent, but operationalizing a distinct consent flow inside existing financial‑aid systems is complex. Interfaces, consent storage, audit logs, and FERPA‑aligned processing agreements will need attention; any misstep could expose participants to privacy complaints or regulatory penalties.
The bill also compresses work into administrative channels (all‑county letters and CalSAWS changes) rather than rulemaking, which speeds rollout but reduces stakeholder input and may shift implementation risk to counties and campuses that must interpret guidance. The optional status for UC campuses—requested rather than mandated to conduct outreach—creates a two‑tier implementation that could undermine statewide consistency and complicate county operations when students move between systems.
Finally, while the statute anticipates improved CalFresh take‑up, it does not provide dedicated funding for counties, campuses, or system IT upgrades; absent additional resources, the promised outreach and verification improvements may be limited by staffing, procurement lead times, and legacy systems.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.