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

55 of 117 obligations match · page 2 of 3 · Download these as CSV

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 Quality management system European Union

Operate a quality management system

EU AI Act · Article 17

Providers of high-risk AI systems must put in place a documented quality management system covering regulatory-compliance strategy, design and development procedures, testing and validation, technical specifications and standards, data management, the risk-management system, post-market monitoring, incident reporting, communication with authorities, record keeping, resource management and an accountability framework.

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

Deployers must implement a risk management policy and programme

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

Deployers of high-risk AI must implement a risk-management policy and programme governing deployment, specifying principles, processes and personnel used to identify, document and mitigate known or reasonably foreseeable risks of algorithmic discrimination, and reasonable in light of recognised frameworks such as the NIST AI RMF or ISO/IEC 42001.

Pending review (a factual check against the official source, not a legal review)
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 Colorado (United States)

Developers must document high-risk systems and disclose known risks

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

Developers must make available to deployers a general statement of intended uses, documentation of known or reasonably foreseeable risks of algorithmic discrimination, training-data summaries, limitations, performance evaluation and mitigation measures, and information needed for deployer impact assessments, and must publish a public statement describing their high-risk systems and how they manage discrimination risks.

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

Draw up technical documentation before placing a high-risk system on the market

EU AI Act · Article 11 and Annex IV

Technical documentation must be drawn up before a high-risk system is placed on the market or put into service and kept up to date. It must demonstrate compliance with the Section 2 requirements and contain at least the elements in Annex IV, including a general description, development process, monitoring and control, risk-management description, and the applied standards. SMEs may use a simplified form provided by the Commission.

Pending review (a factual check against the official source, not a legal review) Applies from 2 Dec 2027
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 New York (United States)

Employers and employment agencies must notify candidates and employees before an automated tool is used

NYC Local Law 144 (automated employment decision tools) · NYC Administrative Code Section 20-871(b)(1) and (b)(2); 6 RCNY Section 5-303

Candidates and employees who reside in New York City must be told, at least ten business days before an automated employment decision tool is used to assess them, that such a tool will be used in the hiring or promotion decision, and which job qualifications and characteristics the tool will assess. The DCWP rules allow the notice to be given on the careers page, in the job posting, or by mail or email, and require that it reach the person before the tool is applied.

Verified (a factual check against the official source, not a legal review) Applies from 5 Jul 2023
Legal requirement Transparency and disclosure New York (United States)

Employers and employment agencies must publish a summary of the bias audit results

NYC Local Law 144 (automated employment decision tools) · NYC Administrative Code Section 20-871(a)(2); 6 RCNY Section 5-302

Before using an automated employment decision tool, the employer or employment agency must make a summary of the most recent bias audit results and the distribution date of the tool publicly available on the employment section of its website. Under the DCWP rules the summary states the audit date, the data source and type, the number of applicants or candidates in each category, and the selection or scoring rates and impact ratios, and must remain posted for at least six months after the tool was last used.

Verified (a factual check against the official source, not a legal review) Applies from 5 Jul 2023
Legal requirement Transparency and disclosure European Union

Employers must inform workers and their representatives before using high-risk AI at work

EU AI Act · Article 26(7)

Before putting a high-risk AI system into service or using it at the workplace, a deployer that is an employer must tell the workers' representatives and the affected workers that they will be subject to the system. The information is given following the procedures and rules on informing workers and their representatives under Union and national law and practice, which may include works-council consultation.

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)

Notify consumers and explain adverse consequential decisions

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

Before a high-risk system makes a consequential decision, deployers must notify the consumer that AI is used, describe its purpose and nature, and provide contact and opt-out information where applicable. After an adverse decision they must state the principal reasons, the data used and its sources, and offer an opportunity to correct data and to appeal for human review where feasible.

Pending review (a factual check against the official source, not a legal review)
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
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)

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.