Codify — Article

California AB 631 requires shelters to report intake and outcome data publicly

Creates a statutory transparency requirement for animal shelters and encourages rescue groups to publish standardized intake, outcome, and source data.

The Brief

AB 631 adds Section 32004 to the California Food and Agricultural Code to push animal shelters toward greater public transparency. The bill directs shelters to collect basic intake and outcome information and to make those records available to the public for a multi-year period.

The measure couples required reporting by shelters with nonbinding encouragements targeted at rescue groups and at making data available in a machine-friendly spreadsheet format. For professionals evaluating shelter operations, contracting, or policy interventions, the bill creates a new baseline of publicly accessible operational data.

At a Glance

What It Does

The bill obligates animal shelters to record intake counts (separated into dogs, cats, and other animals), intake sources, and final outcomes, and to maintain that information for public access. It specifies public access methods and retention rules rather than creating criminal penalties for noncompliance.

Who It Affects

Public and private animal control agencies, humane societies, and shelters that receive animals; rescue groups that place or sell previously owned animals are encouraged — but not required — to follow the same reporting practice. Local governments that contract for animal care will also see operational effects.

Why It Matters

By producing consistent, public-facing operational data, the bill aims to support data-driven decisions on pet overpopulation, resource allocation, and performance benchmarking. It also forces shelters to confront recordkeeping and publication practices they may currently handle inconsistently.

More articles like this one.

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

Unsubscribe anytime.

What This Bill Actually Does

AB 631 inserts a new Section 32004 into the Food and Agricultural Code to create a basic public-records regime for animal-shelter operations. The statute defines the covered shelter universe by reference to existing law and gives a separate, broad definition of “rescue group” that includes both for-profit and nonprofit entities involved in placing animals.

That definitional structure determines who the reporting obligations apply to and who the bill nudges toward voluntary compliance.

The bill specifies the data elements shelters must collect: total intakes disaggregated into dogs, cats, and a residual “other” category; the source of each intake (for example stray, owner surrender, or transfer); and the final outcome for each animal (including returned to owner, adopted, transferred, euthanized, died in care, or dead on arrival). The statute requires shelters to update those records at least quarterly and to retain public access for a rolling five-year period.On publication, the bill takes a pragmatic approach.

If a shelter operates a website, it must post the data there and keep the posted records accessible for at least five years; shelters that lack a website must still make the records available on request for the same retention period. Separately, the text encourages shelters and rescue groups with local care contracts to provide the information in a downloadable spreadsheet format (for example CSV or TSV) compatible with widely used spreadsheet applications at the time of posting.AB 631 relies on encouragement rather than enforcement in two places: it does not impose mandatory reporting on rescue groups, and it frames downloadable, machine-readable publication as recommended rather than required.

That design produces a mix of binding duties for shelters and voluntary best practices for partners, which matters for how consistent and comparable the resulting data will be across jurisdictions and organizations.

The Five Things You Need to Know

1

Section 32004 requires shelters to record intake counts split into three categories: dogs, cats, and other animals.

2

Shelters must record intake sources (e.g.

3

stray, owner-surrendered, transferred) with separation by animal category.

4

Outcomes to be tracked include returned to owner, adopted, transferred, euthanized, died in care, and dead on arrival.

5

Shelters must update the required information at least quarterly and keep it publicly accessible for at least five years.

6

The bill encourages (but does not require) rescue groups to collect the same data and recommends downloadable spreadsheet formats (CSV/TSV) for data sharing.

Section-by-Section Breakdown

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

Section 32004(a)

Definitions for covered shelters and rescue groups

This subsection ties “animal shelter” to an existing definition in Section 30503.5 and separately defines “rescue group” to include for-profit and nonprofit entities involved in placing animals previously owned by someone other than the breeder. The scope matters because statutory obligations apply directly to shelters, while rescue groups are placed in a nonbinding, encouraged category; ambiguous language in the draft may require administrative clarification about borderline entities.

Section 32004(b)

Required data elements: intake, source, and outcomes

Subsection (b) lists the discrete data points shelters must collect — intake counts by dogs/cats/other, intake sources separated by category, and outcome categories for every animal. For compliance officers, this creates a minimal schema shelters must implement in their record systems; it also sets the floor for any future standardization work but leaves significant detail (e.g., how to code transfers or mixed-source events) unspecified.

Section 32004(c)

Update cadence and public access/retention rules

This subsection requires quarterly updates and mandates that posted data remain publicly accessible for at least five years. It differentiates between shelters with websites — which must post the information online — and shelters without websites — which must make the data available upon request. Practically, that creates two publication tracks and raises questions about discoverability and proactive disclosure for smaller organizations.

2 more sections
Section 32004(d)

Voluntary compliance language for rescue groups

The bill expressly encourages rescue groups to follow the same collection and publication practices but stops short of making them mandatory. That approach mirrors other transparency statutes that first target agencies under government purview while asking private partners to voluntarily align their reporting to improve comparability.

Section 32004(e)

Recommendation for machine-readable formats

The statute encourages shelters and rescue groups with local contracts to provide data in downloadable spreadsheet formats such as CSV or TSV compatible with widely used spreadsheet software. This is a policy nudge toward machine-readability that eases analysis, but because it is framed as encouragement rather than a requirement, adoption will vary and interoperability problems may persist without implementing guidance or templates.

At scale

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

  • Local policymakers and public health planners — gain a new, consistent source of operational data to inform funding, spay/neuter programs, and shelter capacity decisions.
  • Animal-welfare researchers and advocates — receive more accessible inputs for tracking trends in intake sources and outcomes, enabling evidence-based advocacy and program evaluation.
  • Prospective adopters and the general public — get improved transparency about shelter performance and animal flow, which can build trust and support adoption efforts.
  • Larger shelters and municipal animal-control agencies — can benchmark performance and identify operational inefficiencies against peers using comparable public data.

Who Bears the Cost

  • Small and private shelters without existing record-keeping systems — face administrative and potentially IT costs to capture, disaggregate, and post data quarterly.
  • Local governments that contract shelter services — may incur oversight and contract-renegotiation costs to ensure contractors comply with the new reporting expectations.
  • Rescue groups that elect to align with the encouragement — will absorb voluntary data collection and formatting burdens without statutory relief or funding.
  • County animal-control staff — could see higher operational workload to produce public-facing exports, respond to public requests where no website exists, and maintain five-year archives.

Key Issues

The Core Tension

The bill balances public-interest transparency against administrative burden and data-privacy concerns: it requires shelters to disclose standardized operational data to improve oversight and policy-making, but it stops short of imposing the same obligations on rescue groups or providing funding or technical standards — leaving a trade-off between faster enactment with limited costs and the risk of producing inconsistent, hard-to-use data.

AB 631 sets a useful baseline for transparency but leaves important implementation choices unresolved. The bill specifies categories and a retention period but not a detailed data standard or a controlled vocabulary for intake sources and outcomes.

That will hamper comparability across jurisdictions unless the responsible agencies or a stakeholders’ consortium publish templates or guidance. The statute also creates two distinct publication tracks — proactive posting for shelters with websites and on-request access for those without — which may perpetuate discoverability and accessibility gaps for smaller organizations.

Another practical tension is the law’s mix of mandates and encouragements. Shelters face clear obligations, while rescue groups are only encouraged to participate and the machine-readable requirement is framed as nonbinding.

That split risks producing partial datasets that look systematic on paper but are incomplete in practice. The bill also does not establish enforcement mechanisms, funding, or technical assistance, so compliance will likely depend on local priorities and resource availability.

Lastly, the statutory text contains formatting and definitional irregularities that could create interpretive disputes about which entities qualify as rescue groups and how to treat complex intake events, such as multi-animal surrenders or owner surrenders later reclaimed by transfer partners.

Try it yourself.

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