AIPolicyTracker

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

Context fileUnder California SB 53, Business and Professions Code Section 22757.12 (as added by SB 53)

Source-linked Open official source

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 13 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.

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
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

Cite this record

AIPolicyTracker (2026). “Frontier developers must publish a transparency report before deploying a new frontier model (California SB 53)”. https://aipolicytracker.org/obligations/us-california-sb-53-transparency-report (accessed 24 September 2026). Data licensed CC BY 4.0.

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.

Similar obligations in other instruments

Informational only, not legal advice. Verify every claim against the linked official sources and consult qualified counsel before acting.