Artificial Intelligence Policy Tracker

AI compliance obligations

Practical requirements extracted from policy instruments, with the source article, the actors they bind, evidence examples and original framework mappings. Legal requirements are marked; everything else is voluntary guidance.

Results

40 of 117 obligations match · page 2 of 2 · Download these as CSV

Legal requirement Transparency and disclosure California (United States)

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

California SB 53 · Business and Professions Code Section 22757.12 (as added by SB 53)

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.

Verified (a factual check against the official source, not a legal review) Applies from 1 Jan 2026
Legal requirement Transparency and disclosure Texas (United States)

Government agencies must disclose to consumers that they are interacting with an AI system

Texas Responsible AI Governance Act (TRAIGA) · Business and Commerce Code Section 551.051

A governmental agency that makes an AI system available to interact with consumers must disclose to each consumer, before or at the time of the interaction, that they are interacting with an AI system. The disclosure is owed even where the AI nature of the interaction would be obvious, must be clear and conspicuous, written in plain language and may not use a dark pattern; a hyperlink to the disclosure is acceptable for online services.

Verified (a factual check against the official source, not a legal review) Applies from 1 Jan 2026
Legal requirement Transparency and disclosure European Union

Providers of generative AI must mark synthetic output as artificially generated in a machine-readable way

EU AI Act · Article 50(2)

Providers of AI systems, including general-purpose AI systems, that generate synthetic audio, image, video or text must ensure the output is marked in a machine-readable format and detectable as artificially generated or manipulated. The technical solution must be effective, interoperable, robust and reliable as far as the state of the art allows, taking account of content type and cost. Systems that only perform assistive editing or do not substantially alter the input, and law-authorised criminal-detection uses, are outside the duty.

Verified (a factual check against the official source, not a legal review) Applies from 2 Aug 2026
Legal requirement Vendor and supply-chain governance European Union

Providers of high-risk AI must have written agreements with suppliers of components, tools and services

EU AI Act · Article 25(4)

A provider of a high-risk AI system and any third party that supplies AI systems, tools, services, components or processes used in or integrated into it must set out, in a written agreement, the information, capabilities, technical access and other assistance needed for the provider to meet its obligations, based on the generally acknowledged state of the art. Suppliers of free and open-source tools and components other than general-purpose AI models are outside this duty. The AI Office may publish voluntary model terms.

Verified (a factual check against the official source, not a legal review) Applies from 2 Dec 2027
Voluntary guidance Governance and accountability India

Adopt the guiding principles and risk-based governance (voluntary)

India AI Governance Guidelines · Guiding principles and recommendations sections

The guidelines encourage organisations to embed principles such as fairness, accountability, safety and transparency, to classify and mitigate risks proportionately, and to participate in voluntary frameworks and incident reporting.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance Governance and accountability United States

Establish AI governance policies, roles and accountability (Govern)

NIST AI RMF · GOVERN function

Govern covers policies and procedures for AI risk, roles and responsibilities, workforce diversity and training, organisational culture, stakeholder engagement, and third-party risk management. It is the cross-cutting function that supports the other three.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance Governance and accountability Australia

Establish accountability processes and a risk-management process (guardrails 1 and 2)

Australian Voluntary AI Safety Standard · Guardrails 1 and 2

Guardrail 1 asks organisations to set up accountability processes including governance, internal capability and a strategy for regulatory compliance; guardrail 2 asks for a risk-management process to identify and mitigate risks across the AI lifecycle.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance Governance and accountability Singapore

Establish internal governance structures and measures for AI

Singapore Model AI Governance Framework · Second edition, Part on internal governance structures and measures

Organisations should adapt existing governance to AI: clear roles and responsibilities, board and senior management oversight, risk-management and internal controls, and staff training.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance Impact assessment United States

Map context, intended use and potential impacts (Map)

NIST AI RMF · MAP function

Map establishes the context: intended purposes, users, deployment settings, legal requirements, risk categorisation, benefits and costs, and impacts on individuals, groups, communities and society.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance AI risk management United Kingdom

Ensure AI systems are safe, secure and robust throughout their lifecycle

UK AI regulation framework · Principle 1, Part 3

Regulators are asked to ensure AI systems function in a robust, secure and safe way, with risks continually identified, assessed and managed. In practice this is enforced through existing safety, security and data-protection law rather than a new duty.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance AI risk management United States

Prioritise, respond to and monitor AI risks (Manage)

NIST AI RMF · MANAGE function

Manage allocates resources to mapped and measured risks, plans responses including decommissioning, manages third-party risks, and documents post-deployment monitoring, incident response and communication.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance Safety testing and evaluation United States

Measure and test trustworthiness characteristics (Measure)

NIST AI RMF · MEASURE function

Measure covers selecting metrics and test methods, evaluating validity, safety, security, resilience, explainability, privacy, fairness and bias, and monitoring these over time, including through independent review and red-teaming for generative AI.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance Transparency and disclosure Singapore

Report incidents and mark AI-generated content (generative AI framework)

Singapore Model AI Governance Framework · Generative AI framework, dimensions on incident reporting and content provenance

The generative-AI framework recommends incident-reporting channels and processes for AI harms, and content provenance measures such as digital watermarking and cryptographic provenance so that users can identify AI-generated content.

Source-linked (a factual check against the official source, not a legal review)

Frequently asked questions

What is an obligation on this site?

A single practical requirement pulled out of an instrument and stated on its own: keep a risk management system, log incidents, document training data, provide human oversight, and so on. Each one cites the article or section it comes from so you can check it against the source.

Does a voluntary obligation have legal force?

No, and every obligation is labelled either a legal requirement or voluntary guidance. Voluntary items still matter in practice, because procurement questionnaires and auditors ask about them, but only the binding ones carry legal consequence.

How do I find the obligations that apply to my organisation?

Filter by jurisdiction, category, actor, sector or use case. The applicability check asks a short set of questions and returns the duties that may reach you. It is an educational screen, not a legal determination, and it says so.

Why do some instruments have no obligations listed?

Because nobody has broken them out yet. Most instruments are recorded at summary level first; obligations are added jurisdiction by jurisdiction. The coverage and open-gaps pages publish exactly what is missing rather than hiding it.