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

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

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

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.