AB 520 directs the State Controller to build and maintain a publicly accessible online portal that consolidates information about state spending on homelessness and mental health. The portal must surface program‑level allocations alongside per‑fiscal‑year totals so users can see where money flows within those policy areas.
For professionals tracking service networks, grants, or fiscal oversight, the bill creates a single place to find distribution amounts, appropriation figures, and basic program contacts — information that is often scattered across departments and budget documents. That centralization is intended to support accountability, program planning, and easier comparisons across years and programs.
At a Glance
What It Does
The bill compels the Controller, working with the Department of Health Care Services and the California Interagency Council on Homelessness, to publish and maintain a searchable portal that lists per‑fiscal‑year funding totals and itemized program allocations for homelessness and mental‑health programs. Each program entry must include basic descriptive data, amounts distributed versus appropriated, contact information, and active/inactive status.
Who It Affects
Directly affects the State Controller’s Office, DHCS, and the California Interagency Council on Homelessness; state departments that administer homelessness or mental‑health programs must supply the data; local service providers, policy shops, auditors, and advocates will be primary users of the portal.
Why It Matters
Centralizing distribution and appropriation data can shorten research and oversight cycles and expose funding trends across multiple years. It also creates new operational duties for the Controller and source agencies to standardize, reconcile, and publish consistent fiscal data.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 520 requires the Controller to assemble fiscal data about state spending on homelessness and mental health into a single, searchable web portal. The bill separates the two policy domains but applies the same data architecture to each: annual totals for the current fiscal year plus a ten‑year history, and an itemized list of programs that received Controller‑distributed funds in the current year.
For each program the portal must show the program name and administering department, a short statement of the program’s objective, the dollar amount the Controller distributed that year, the amount appropriated to the program that year, a liaison’s email and phone number, and the program’s activation or inactivation date where applicable.
The statute mandates collaboration: the Controller develops and maintains the portal in coordination with the Department of Health Care Services and the California Interagency Council on Homelessness, and those three entities must each provide a prominent link to the portal on their websites. The bill asks for visibility into year‑to‑year changes by requiring that differences in funding levels between fiscal years be made apparent, which implies some form of comparative presentation or visualization rather than raw tables alone.Operationally, the Controller will rely on department‑level reporting to populate the portal.
That creates a need for standardized reporting formats, reconciliation between appropriated and distributed figures, and an intake process for contact information and activation dates. The statute does not specify update frequency, validation procedures, or enforcement mechanisms, so the design choices and data quality controls will fall to the implementing agencies during build‑out and maintenance.
Because the requirement focuses on funds distributed by the Controller’s Office, the portal will reflect distribution events rather than every possible state commitment, contract, or local allocation tied to homelessness or mental‑health policy.
The Five Things You Need to Know
Deadline: The Controller must have the portal developed, published, and maintained by January 1, 2027.
Ten‑year view: The portal must display total Controller‑distributed funding for each of the previous ten fiscal years alongside the current fiscal year for both homelessness and mental‑health spending.
Required fields: Each program entry must include program name, administering department, program objective, amount distributed by the Controller that fiscal year, amount appropriated that fiscal year, a liaison’s email and phone number, and activation/inactivation dates if applicable.
Scope of amounts: The statute ties reporting to funds distributed by the Controller’s Office rather than to every appropriation or contractual commitment the state makes.
Visibility links: The Controller, DHCS, and the California Interagency Council on Homelessness must each publish a readily available link to the portal on their public websites.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Homelessness — per‑year totals and trend visibility
This provision requires the Controller to list the total amount distributed for homelessness programs for the current fiscal year and the preceding ten fiscal years, and to make inter‑year differences apparent. Practically, that means the portal must present longitudinal totals and some comparative display (summary table, percentage change, or chart). For analysts, this is the primary mechanism for spotting funding trends or year‑over‑year shifts in Controller distributions related to homelessness.
Homelessness — searchable, itemized program listings
The statute mandates a searchable, itemized roster of all programs that received Controller distributions for homelessness in the current fiscal year, and enumerates six specific data fields (program name and administering agency; mission; amount distributed; amount appropriated; liaison email/phone; active/inactive dates). That combination of descriptive and fiscal fields forces departments to provide both contextual and numeric data, which enables filtering by department, mission, amount, or status.
Mental health — per‑year totals and trend visibility
Mirroring the homelessness totals requirement, this subsection obligates the Controller to publish distributed funding totals for mental‑health programs for the current fiscal year plus the previous ten years and to highlight differences between years. Because it applies the same temporal window as the homelessness totals, users can compare long‑run trajectories across the two policy areas, though the bill does not require integrated cross‑domain analytics.
Mental health — searchable, itemized program listings
This mirrors the itemized listing mandate for homelessness but for mental‑health recipients. Departments must supply the same six categories of information for each program that received Controller distributions in the current fiscal year. The uniformity of required fields across (a)(2) and (b)(2) simplifies portal design but transfers the burden of consistent reporting formats to source agencies.
Interagency cooperation and public access
The Controller must develop the portal in collaboration with DHCS and the California Interagency Council on Homelessness, and those three entities are required to post direct links on their websites. This section creates an explicit accountability loop: the portal is the Controller’s product, but DHCS and the Council share responsibility for discoverability. It also implies coordination on metadata, update cadence, and outreach to program administrators who supply the underlying data.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government 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
- State budget and policy analysts — get a centralized source of Controller‑distributed totals and program allocations, shortening time to compile cross‑departmental spending snapshots and supporting audits or trend analysis.
- Local service providers and nonprofits — can more easily identify which state programs fund their services, locate program liaisons, and monitor changes in distribution levels that affect contract planning.
- Advocates and researchers — receive a consistent dataset to test hypotheses about funding allocation, to prioritize advocacy efforts, and to correlate fiscal inputs with service gaps.
Who Bears the Cost
- State Controller’s Office — must design, build, host, secure, and maintain the portal; reconcile incoming data from departments; and present comparative visualizations, creating IT and staffing costs.
- Department program administrators (state agencies) — must compile standardized records for every program that received Controller distributions, including liaison contacts and activation dates; smaller programs may need administrative support to comply.
- California Interagency Council on Homelessness and DHCS — required to coordinate with the Controller and post portal links, which implies time and resources for integration, QA, and outreach.
Key Issues
The Core Tension
The central trade‑off is transparency versus administrative accuracy and cost: making distribution‑level fiscal data public quickly aids accountability and planning, but doing so reliably requires sustained investment in data collection, reconciliation, and quality control; exposing raw dollar flows without standardized context can mislead users or create false impressions about program effectiveness.
Several implementation questions could meaningfully affect the portal’s usefulness. First, the statute ties reporting to amounts distributed by the Controller’s Office; it does not capture other relevant fiscal flows such as department internal transfers, memoranda of understanding, contractual commitments not yet distributed, or locally administered federal funds.
Users could misread the portal as a complete accounting of state investment unless metadata clarifies the scope.
Second, the bill prescribes specific data fields but leaves out operational details that determine data quality: how frequently departments must report updates, the data format and validation rules, mechanisms for correcting errors, and whether distributed and appropriated amounts will be reconciled to a common accounting standard. Those choices affect comparability across agencies and years and will drive implementation costs.
Finally, publishing contact emails and phone numbers and activation/inactivation dates raises privacy and accuracy risks—especially for programs administered at a substate level—so the implementing agencies must balance transparency with data hygiene and security considerations.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.