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

19 of 117 obligations match · Download these as CSV

Legal requirement Governance and accountability South Korea

Operators of high-impact AI must prepare user-protection measures and keep records of their safety and trust measures

AI Basic Act · Article 34(1)

Operators of high-impact AI must prepare and implement a plan to protect users, and must prepare and keep documents describing the measures they take to secure the AI's safety and reliability, so that they can be shown to the Ministry of Science and ICT on request. Further items may be added by Presidential Decree, and the ministry may publish guidelines on how to meet these duties.

Verified (a factual check against the official source, not a legal review) Applies from 22 Jan 2026
Legal requirement Incident reporting and handling Colorado (United States)

Deployers must notify the Attorney General of discovered algorithmic discrimination

Colorado AI Act · C.R.S. 6-1-1703(7)

If a deployer discovers that a high-risk AI system it uses has caused algorithmic discrimination, it must send a notice to the Colorado Attorney General within 90 days of the discovery, in the form the Attorney General prescribes, without unreasonable delay.

Pending review (a factual check against the official source, not a legal review)
Legal requirement Incident reporting and handling Colorado (United States)

Developers must notify the Attorney General and deployers of discovered algorithmic discrimination

Colorado AI Act · C.R.S. 6-1-1702(5)

Within 90 days after a developer discovers, through ongoing testing or a credible report from a deployer, that a high-risk AI system it developed has caused or is reasonably likely to have caused algorithmic discrimination, it must disclose this to the Colorado Attorney General and to all known deployers or other developers of the system, without unreasonable delay.

Pending review (a factual check against the official source, not a legal review)
Legal requirement Prohibited practices European Union

Do not deploy or provide AI for prohibited practices

EU AI Act · Article 5

Article 5 bans placing on the market, putting into service or using AI for listed practices, including subliminal or manipulative techniques that cause significant harm, exploitation of vulnerabilities, social scoring by public or private actors leading to detrimental treatment, untargeted scraping of facial images to build recognition databases, emotion recognition in workplaces and education institutions except for medical or safety reasons, biometric categorisation to infer protected characteristics, and real-time remote biometric identification in publicly accessible spaces for law enforcement outside narrow exceptions.

Pending review (a factual check against the official source, not a legal review) Applies from 2 Feb 2025
Legal requirement AI risk management Colorado (United States)

Deployers must use reasonable care to avoid algorithmic discrimination

Colorado AI Act · C.R.S. 6-1-1703(1)

A deployer of a high-risk AI system must use reasonable care to protect consumers from known or reasonably foreseeable risks of algorithmic discrimination. A deployer that runs the required risk-management programme, completes impact assessments, gives consumer notices and makes the required disclosures benefits from a rebuttable presumption of reasonable care; some deployers with fewer than 50 employees are relieved of parts of the programme and assessment duties when they rely on the developer's impact assessment.

Pending review (a factual check against the official source, not a legal review)
Legal requirement AI risk management Colorado (United States)

Developers must use reasonable care to avoid algorithmic discrimination

Colorado AI Act · C.R.S. 6-1-1702(1)

A developer of a high-risk AI system must use reasonable care to protect consumers from any known or reasonably foreseeable risk of algorithmic discrimination arising from the intended and contracted uses of the system. A developer that meets the documentation, public-statement and Attorney General disclosure duties in the rest of section 6-1-1702 benefits from a rebuttable presumption that it used reasonable care.

Pending review (a factual check against the official source, not a legal review)
Legal requirement AI risk management European Union

Establish a risk management system for high-risk AI

EU AI Act · Article 9

Providers of high-risk AI systems must establish, implement, document and maintain a continuous, iterative risk-management system across the system's lifecycle: identifying known and reasonably foreseeable risks to health, safety and fundamental rights, estimating and evaluating risks including from reasonably foreseeable misuse, evaluating post-market data, and adopting targeted risk-management measures, with testing before placing on the market.

Pending review (a factual check against the official source, not a legal review) Applies from 2 Dec 2027
Legal requirement AI risk management South Korea

Operators of high-impact AI must establish and operate a risk management plan

AI Basic Act · Article 34(1)

An AI business operator that provides high-impact AI, or a product or service using it, must establish and operate a plan for managing the risks of that AI. High-impact AI is AI used in areas such as energy, drinking water, health care and medical devices, nuclear safety, biometric analysis for criminal investigation, decisions on recruitment or loans, transport, public services and education, where it may materially affect life, safety or fundamental rights.

Verified (a factual check against the official source, not a legal review) Applies from 22 Jan 2026
Legal requirement Technical documentation European Union

Providers must document and register a conclusion that an Annex III system is not high-risk

EU AI Act · Article 6(4); Article 49(2)

A provider that considers a system listed in Annex III to be outside the high-risk tier because it meets one of the Article 6(3) conditions, such as performing a narrow procedural task or only preparing a human assessment, must write down that assessment before placing the system on the market or putting it into service, register the system in the EU database under Article 49(2), and hand over the assessment on request from a national competent authority.

Verified (a factual check against the official source, not a legal review) Applies from 2 Dec 2027
Legal requirement Transparency and disclosure European Union

Deployers must explain individual decisions taken with high-risk AI on request

EU AI Act · Article 86

A person affected by a decision that a deployer took on the basis of the output of an Annex III high-risk AI system, other than critical-infrastructure systems, which produces legal effects or similarly significantly affects them in a way they consider adverse to their health, safety or fundamental rights, has the right to obtain from the deployer clear and meaningful explanations of the role the system played in the decision and the main elements of the decision. The right does not apply where Union or national law provides an exception.

Verified (a factual check against the official source, not a legal review) Applies from 2 Dec 2027
Legal requirement Transparency and disclosure Colorado (United States)

Deployers must publish a statement about the high-risk AI systems they use

Colorado AI Act · C.R.S. 6-1-1703(5)

A deployer must make available on its website, or in another public way, a clear and readily available statement summarising the types of high-risk AI systems it currently deploys, how it manages known or reasonably foreseeable risks of algorithmic discrimination from those systems, and the nature, source and extent of the information it collects and uses. The statement must be updated periodically.

Pending review (a factual check against the official source, not a legal review)
Legal requirement Transparency and disclosure European Union

Deployers must tell natural persons that a high-risk AI system is used in decisions about them

EU AI Act · Article 26(11)

Deployers of Annex III high-risk AI systems that take decisions about natural persons, or help take them, must inform those persons that they are subject to the system. The notice is separate from any explanation owed under Article 86 and from the worker notice in Article 26(7). In law-enforcement contexts the duty follows the information rules of the Law Enforcement Directive.

Verified (a factual check against the official source, not a legal review) Applies from 2 Dec 2027
Legal requirement Transparency and disclosure Colorado (United States)

Disclose the use of the technology and the principal reasons after an adverse consequential decision

Colorado ADMT law (SB 26-189)

After an adverse consequential decision, the deployer must tell the consumer that automated decision-making technology was used, give the principal reasons for the decision, and explain how to obtain human review.

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

Notify consumers before automated decision-making technology influences a consequential decision

Colorado ADMT law (SB 26-189)

Deployers must tell a consumer, before the decision is made, that automated decision-making technology will be used to make or materially influence a consequential decision about them. The exact content and timing of the notice follow the enrolled bill, which a reviewer must read.

Pending review (a factual check against the official source, not a legal review) Applies from 1 Jan 2027
Legal requirement Transparency and disclosure South Korea

Operators of high-impact AI must be able to explain outputs and the main criteria behind them

AI Basic Act · Article 34(1)

Operators of high-impact AI must put in place measures to explain the AI's final results, the main criteria used to reach them, and an overview of the training data, to the extent that this is technically feasible. The duty targets explainability of the system's decisions to users and affected people rather than full disclosure of the model.

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

Provide deployers with clear instructions for use

EU AI Act · Article 13

High-risk AI systems must be designed so their operation is sufficiently transparent for deployers to interpret output and use it appropriately, and must be accompanied by instructions for use covering the provider's identity, the system's characteristics, capabilities and limitations, performance for the intended purpose and known foreseeable misuse, human-oversight measures, expected lifetime and maintenance.

Pending review (a factual check against the official source, not a legal review) Applies from 2 Dec 2027

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.