Report critical safety incidents to the Office of Emergency Services

Practical action

Define critical-safety-incident criteria and an escalation path with the statutory clock.

Who does it apply to?

Frontier developers.

Actors

Provider / developerGeneral-purpose AI model provider

Sectors

Cross-sector / all sectors

Use cases

Generative AI and foundation models

Applies from: 1 January 2026

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.

• satisfiesProcessIncident coordinator · continuous
  AI incident management and regulatory reporting

  Serves 14 recorded duties · evidence: AI incident response playbook, AI incident record, Incident report to an authority

  Critical-safety-incident criteria and escalation to the state office within the statutory time.

• 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

  Defines the incident types the framework is meant to prevent.

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.

• AI Incident Response Playbook and Log

  Procedure · DOCX and XLSX · v3

• NIST AI RMF ↔ EU AI Act ↔ ISO/IEC 42001 Crosswalk

  Crosswalk · XLSX · v3

• AI Audit Evidence Tracker

  Register · XLSX · v1

• AI Post-Market Monitoring Plan

  Procedure · DOCX and XLSX · v2

All 6 templates that cover it →

What evidence would a reviewer expect?

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 →

Frequently asked questions

Cite this record

AIPolicyTracker (2026). “Report critical safety incidents to the Office of Emergency Services (California SB 53)” [AIPT-OBL-0080, verified 26 September 2026 by Bhaskar Bhatt]. https://aipolicytracker.org/id/AIPT-OBL-0080 (accessed 27 October 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0080: 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.

@misc{aipolicytracker2026_reportcriticalsafetyinci,
  author       = {{AIPolicyTracker}},
  title        = {{Report critical safety incidents to the Office of Emergency Services (California SB 53)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/us-california-sb-53-critical-safety-incident-reporting}},
  url          = {https://aipolicytracker.org/obligations/us-california-sb-53-critical-safety-incident-reporting},
  urldate      = {2026-10-27},
  note         = {Data licensed CC BY 4.0. Accessed 27 October 2026}
}

Change history

Similar obligations in other instruments

• Report serious incidents to market surveillance authorities — EU AI Act, European Union
• Providers must take corrective action and inform the supply chain about non-conforming high-risk AI — EU AI Act, European Union
• Providers of systemic-risk GPAI models must track and report serious incidents to the AI Office — EU AI Act, European Union
• Implement reasonable security safeguards and notify breaches — India DPDP Act, India
• Developers must notify the Attorney General and deployers of discovered algorithmic discrimination — Colorado AI Act, Colorado (United States)
• Deployers must notify the Attorney General of discovered algorithmic discrimination — Colorado AI Act, Colorado (United States)