Codify — Article

California bill sets seven minimum race and ethnicity categories for state data

AB 1186 would require California state agencies and contractors to use seven baseline race/ethnicity categories, publish detailed subcategories per federal SPD‑15, and provide write‑in options.

The Brief

AB 1186 standardizes race and ethnicity data collection across California state agencies by defining seven minimum categories and directing agencies to collect and publish more detailed subcategories aligned with the federal SPD‑15 standard (as of March 29, 2024). The bill also requires write‑in options, lets the Department of Finance’s Demographic Research Unit (DRU) grant narrow exemptions when administrative burden outweighs public benefit, and sets reporting, oversight, and a compliance deadline.

This matters because the bill would create a uniform baseline for how the state counts and reports racial and ethnic groups — affecting resource allocation, civil‑rights monitoring, public‑health data, and vendor contracts — while raising practical questions about privacy, data comparability, implementation cost, and an unclear drafting point about how many detailed subcategories to publish.

At a Glance

What It Does

The bill requires any state agency, board, or commission that collects race/ethnicity data (directly or by contract) to use seven minimum categories and to collect and publish more granular subcategories consistent with OMB SPD‑15 as of March 29, 2024. It mandates write‑in options, allows an exemption where burden outweighs benefit, and tasks the Chief Statistician and the Demographic Research Unit with oversight and technical assistance.

Who It Affects

State agencies, boards, and commissions that collect demographic data; contractors and commercial vendors who collect data on the state’s behalf; the Department of Finance’s Demographic Research Unit and the Chief Statistician; researchers, civil‑rights groups, and program managers who rely on disaggregated data.

Why It Matters

By locking in a minimum taxonomy and a SPD‑15 reference date, the bill aims to increase comparability and visibility for many groups currently aggregated or overlooked. At the same time it creates new compliance and reporting duties and raises privacy and interoperability issues that agencies and vendors must solve.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

AB 1186 defines seven baseline race and ethnicity categories that state entities must use: American Indian or Alaska Native; Asian; Black or African American; Hispanic or Latino; Middle Eastern or North African; Native Hawaiian or Pacific Islander; and White. The bill then requires agencies to go beyond those top‑level labels by collecting and publishing more detailed subcategories; it ties that requirement to the Office of Management and Budget’s SPD‑15 standard as it stood on March 29, 2024.

For each of the seven categories, agencies must surface the largest detailed groups (the bill’s text contains an apparent drafting inconsistency about whether to publish the top six or top nine detailed categories), and they must offer respondents a free‑text write‑in option both as a general choice and within each top‑level category. Agencies can be excused from these requirements only if the administrative burden demonstrably outweighs the public benefit; the DRU may grant an exemption but only after the responsible agency produces a written, evidence‑based determination.The statute casts a wide net: it covers administrative and survey collections, and explicitly includes third‑party and commercial data collections when those collections are performed for contracts, partnerships, or agreements involving state agencies.

The Chief Statistician of California and the DRU must oversee implementation, provide technical assistance, and track compliance. Agencies must begin reporting annually on progress to the Legislature and the Assembly Committee on Governmental Organization starting January 1, 2027, and must complete implementation no later than January 1, 2029.Finally, AB 1186 requires that collected data be made public consistent with law but treats personally identifying information as confidential and bars state agencies from handing PII to federal agencies unless federal law expressly requires disclosure.

The Five Things You Need to Know

1

The bill defines seven required top‑level race/ethnicity categories that all covered state data collectors must use.

2

For each top‑level category, agencies must collect and publish the largest detailed subgroups consistent with OMB SPD‑15 as of March 29, 2024 — the text ambiguously references either the top six or the top nine detailed categories.

3

The bill requires two write‑in options: a general write‑in for respondents who do not identify with listed options, and a write‑in field within each top‑level category for more specific self‑identification.

4

An exemption is available when an agency shows, in a written determination backed by substantial evidence, that the administrative burden of collecting/publishing a particular category’s details outweighs the anticipated benefit to that population group; the DRU may approve that exemption.

5

Agencies must report annually to the Legislature beginning January 1, 2027, implement the requirements no later than January 1, 2029, and keep personally identifying information confidential, with no disclosure to federal agencies unless federal law expressly requires it.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section (a)

Seven minimum race and ethnicity categories

This provision lists the seven baseline categories state data collectors must use. That definition creates a mandatory taxonomy for any covered state collection and establishes the legal floor for how California will classify respondents in its administrative and survey datasets.

Section (b)(1)–(3)

Obligation to collect and publish detailed subcategories and provide write‑ins

Subsection (b) requires agencies that collect race/ethnicity data to record at least the seven minimum categories and to publish more granular 'detailed categories' tied to SPD‑15 (the federal standard) as of the specified date. It also mandates a write‑in option for respondents who do not see themselves in the listed choices and a write‑in field inside each top‑level category to capture more granular self‑identification. Practically, agencies will need to revise forms (print and online), build or update data dictionaries and code lists, and plan for how to classify and report free‑text responses.

Section (c)

General exemption where burden outweighs benefit

This short clause allows an agency to claim an exemption from the collection/publishing rules if the administrative burden exceeds the expected public benefit. It is a high‑level standard that delegates the specifics of weighing burden and benefit to the implementation regime described next.

3 more sections
Section (d)

DRU review and written, evidence‑based exemption determinations

The bill gives the Demographic Research Unit (within the Department of Finance) the authority to exempt a data collection only after the collecting agency submits a written determination supported by substantial evidence. That imposes a procedural hurdle on exemptions: agencies must document cost, logistical or privacy barriers and show why those barriers eclipse public value before the DRU can relieve them of the requirement.

Sections (e)–(f)

Scope (third‑party/commercial collections) and implementation deadline

AB 1186 explicitly extends its rules to administrative and survey data, including third‑party and commercial collections performed for state contracts, partnerships, and agreements. It requires agencies to comply 'as early as reasonably feasible' but no later than January 1, 2029. That makes vendors and contract managers part of the compliance chain and creates a clear outer deadline for system changes.

Sections (g)–(h) and (i)

Oversight, reporting, public availability, and confidentiality

The Chief Statistician and the DRU are charged with overseeing implementation, tracking progress, and providing technical assistance. Agencies must submit annual reports on compliance and instruments beginning January 1, 2027. Data must be publicly available consistent with law, but personally identifying information is confidential and may not be disclosed to federal agencies unless federal law explicitly requires it, which places a restriction on intergovernmental data sharing.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Civil Rights across all five countries.

Explore Civil Rights 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

  • Specific racial and ethnic subpopulations (for example, MENA communities and disaggregated Asian subgroups): the required minimum categories and mandated detailed subcategories increase visibility in state data and make it easier to identify disparities and target programs.
  • State program planners and public‑health analysts: more consistent, standardized taxonomy across agencies improves comparability and supports evidence‑based allocation of funds and services.
  • Civil‑rights and community advocacy groups: standardized, disaggregated data strengthens monitoring, enforcement, and advocacy by enabling clearer assessments of differential outcomes.
  • Academic and policy researchers: access to richer, standardized demographic fields and published detailed categories enhances the robustness of analyses on inequality and program impact.
  • Vendors and contractors that provide survey and administrative data services: clearer state standards reduce ambiguity about required data elements for state contracts (though they also imply implementation work).

Who Bears the Cost

  • State agencies, boards, and commissions that collect demographic data: they must redesign forms, update IT systems, train staff, and publish new outputs to meet the new taxonomy and reporting requirements.
  • Third‑party contractors and commercial data vendors working for the state: contracts will need scope adjustments and potentially higher fees to support new collection fields, write‑in processing, and reporting obligations.
  • Department of Finance’s Demographic Research Unit and Chief Statistician: the DRU gains review and oversight duties that require staffing, technical review capacity, and a process to evaluate exemption requests.
  • Privacy and compliance teams: increased granularity and free‑text responses raise disclosure risk and data governance workload — small agencies may need external help to address re‑identification risks.
  • Small boards or specialty commissions with limited IT budgets: the 'burden outweighs benefit' exemption is available but requires an evidence‑based written determination, which itself consumes staff time and resources.

Key Issues

The Core Tension

The central dilemma is straightforward: the state needs more granular, standardized race and ethnicity data to identify disparities and allocate resources accurately, but collecting and publishing those details increases administrative cost, burdens less‑resourced agencies and vendors, and raises privacy and comparability challenges that the bill’s procedural tools (exemptions, DRU review, confidentiality rules) only partially resolve.

AB 1186 pursues better demographic visibility by mandating a consistent top‑level taxonomy and requiring publication of detailed subgroups, but that clarity exposes several implementation tensions. The bill links its detailed‑category requirement to SPD‑15 as of a fixed date; that choice promotes short‑term harmonization with a federal standard but risks becoming out of step with future federal revisions unless the law is updated.

The text also contains an editorial ambiguity about whether agencies must publish the top six or the top nine detailed categories; that drafting gap will create confusion for agencies and vendors unless clarified.

The write‑in requirements improve self‑identification but complicate data processing and comparability. Free‑text responses increase the work of coding and recoding into standardized categories, and they raise small‑cell disclosure risks when agencies publish disaggregated tables.

The exemption mechanism — burden must outweigh public benefit and the agency must supply substantial evidence for the DRU to act — is a reasonable check, but it could become a paper‑intensive gatekeeper that advantages better‑resourced agencies. Finally, the law’s bar on disclosing personally identifying information to federal agencies 'unless required by federal law' creates potential conflicts where federal grant or reporting conditions demand data elements that the state prefers to withhold; those conflicts will need contractual and legal reconciliation.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.