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

59 of 117 obligations match · page 3 of 3 · Download these as CSV

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

Operators of high-impact AI should assess its impact on fundamental rights before use

AI Basic Act · Article 35

An AI business operator that provides high-impact AI, or a product or service using it, is to make efforts to assess in advance the impact the AI may have on people's fundamental rights. The provision is drafted as an endeavour duty rather than a hard requirement, but public bodies procuring high-impact AI are directed to give preference to products that have undergone such an assessment, and the ministry may set assessment methods.

Verified (a factual check against the official source, not a legal review) Applies from 22 Jan 2026
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 Transparency and disclosure United Kingdom

Provide appropriate transparency and explainability

UK AI regulation framework · Principle 2, Part 3

Organisations should communicate when and how AI is used and provide explanations proportionate to the risk, so that people can understand decisions affecting them. For personal data, UK GDPR transparency and automated decision-making rights make this binding in practice.

Source-linked (a factual check against the official source, not a legal review)
Voluntary guidance Vendor and supply-chain governance Australia

Provide contestability, supply-chain transparency and records (guardrails 7 to 9)

Australian Voluntary AI Safety Standard · Guardrails 7, 8 and 9

Establish processes for people impacted by AI to challenge use or outcomes; be transparent with other organisations across the AI supply chain about data, models and systems; and keep and maintain records to allow third parties to assess compliance.

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.