Artificial Intelligence Policy Tracker

Frontier developers must publish a transparency report before deploying a new frontier model

Download: JSON · MarkdownUnder California SB 53, Business and Professions Code Section 22757.12 (as added by SB 53)

Verified against the official source 26 Sep 2026 (a factual check against the official source, not a legal review or legal advice)
What this label means
Verified
— a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
Pending review
— linked to the official source and in the queue for a reviewer to confirm.
Source-linked
— linked to the official source, not yet confirmed by a reviewer.
Verification policy and current standing · a factual check, not legal advice.
No change recorded as of 26 Sep 2026 · official source last checked
On this page 9 sections

In brief

Frontier developers must publish a transparency report before deploying a new frontier model is a legal requirement under the California SB 53 in California (United States) (Business and Professions Code Section 22757.12 (as added by SB 53)). It applies from 1 January 2026. The record carries 2 evidence examples and mappings to 2 frameworks.

Instrument
California SB 53
Nature
Legal requirement
Source reference
Business and Professions Code Section 22757.12 (as added by SB 53)
Applies from
1 January 2026
Who it binds
Provider / developer, General-purpose AI model provider
Evidence examples
2
Framework mappings
NIST AI Risk Management Framework 1.0, ISO/IEC 42001:2023
Controls that meet it
3
Official source
Open official text
Verification
Verified against the official source 26 Sep 2026

What does it require?

Before or at the time a frontier developer deploys a new frontier model, or a substantially modified version, it must publish a transparency report on its website describing the model, its intended uses and restrictions, the release date and modalities, and how to contact the developer. A large frontier developer must add a summary of its catastrophic-risk assessment for the model, the results, any third-party evaluators involved and the steps taken under its frontier AI framework, with trade-secret and security redactions explained.

Practical action

Attach a model-release transparency report to the launch checklist, with a redaction log for withheld details.

Who does it apply to?

Frontier developers above the compute threshold; the catastrophic-risk elements apply to large frontier developers above the revenue threshold.

Applies from:

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

  • satisfiesProcessProduct or model owner · at launch and on material change
    Technical documentation, model cards and instructions for use

    Serves 14 recorded duties · evidence: Technical documentation file, Model card or deployer information pack, Instructions for use

    The model card content the report is built from.

  • supportsPolicyHead of AI safety · annual
    Frontier model safety and security framework

    Serves 9 recorded duties · evidence: Published frontier safety framework, Dangerous-capability evaluation report, Threshold notification to an authority

    Report describes steps taken under the framework.

  • supportsProcessRelease manager · at launch and on material change
    Model release and change-management gate

    Serves 5 recorded duties · evidence: Release or change approval record, Release and change-classification procedure

    Release is gated on the report being published.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

All 10 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Published model transparency reportdocument
Redaction justification logrecord

Framework mappings

Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.

See every California (United States) duty mapped this way →

Framework mappings table
FrameworkReferenceNoteConfidence
NIST AI RMF 1.0GOVERN 4.2, MAP 5.1, MEASURE 2.6Public documentation of intended use and safety evaluation.medium
ISO/IEC 42001:2023Annex A.8.2, A.8.3System documentation and external reporting.medium

Frequently asked questions

Is this a legal requirement?

Yes. It is a legal requirement under California SB 53 (Business and Professions Code Section 22757.12 (as added by SB 53)).

Who must comply with this obligation?

Frontier developers above the compute threshold; the catastrophic-risk elements apply to large frontier developers above the revenue threshold.

When does this obligation apply?

It applies from 1 January 2026.

What evidence shows compliance?

A reviewer would expect: Published model transparency report; Redaction justification log.

Which frameworks map to this obligation?

It is mapped to NIST AI Risk Management Framework 1.0 GOVERN 4.2, MAP 5.1, MEASURE 2.6, ISO/IEC 42001:2023 Annex A.8.2, A.8.3. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

Frontier model safety and security framework; Model release and change-management gate; Technical documentation, model cards and instructions for use.

What should an organisation do in practice?

Attach a model-release transparency report to the launch checklist, with a redaction log for withheld details.

Cite this record

AIPolicyTracker (2026). “Frontier developers must publish a transparency report before deploying a new frontier model (California SB 53)” [AIPT-OBL-0081, verified 26 September 2026 by Bhaskar Bhatt]. https://aipolicytracker.org/id/AIPT-OBL-0081 (accessed 8 November 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0081: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: SB 53 Transparency in Frontier Artificial Intelligence Act, California Legislative Information, https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB53.

BibTeX
@misc{aipolicytracker2026_frontierdevelopersmustpu,
  author       = {{AIPolicyTracker}},
  title        = {{Frontier developers must publish a transparency report before deploying a new frontier model (California SB 53)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/us-california-sb-53-transparency-report}},
  url          = {https://aipolicytracker.org/obligations/us-california-sb-53-transparency-report},
  urldate      = {2026-11-08},
  note         = {Data licensed CC BY 4.0. Accessed 8 November 2026}
}

Change history

No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.

Similar obligations in other instruments

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.