> For the complete documentation index, see [llms.txt](https://www.headlesslaw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.headlesslaw.com/ai-act/articles/96.md).

# Article 96 — Guidelines from the Commission on the implementation of this Regulation

*In force · Consolidated version of 27 July 2026 · Checked against EUR-Lex on 30 Sep 2026 ·* [*Official source*](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02024R1689-20260727)

1. The Commission shall develop guidelines on the practical implementation of this Regulation, and in particular on:

   **(a)** the application of the requirements and obligations referred to in [Articles 8](/ai-act/articles/8.md) to 15 and in [Articles 25](/ai-act/articles/25.md) and [26](/ai-act/articles/26.md);

   **(b)** the prohibited practices referred to in [Article 5](/ai-act/articles/5.md);

   **(c)** the practical implementation of the provisions related to [substantial modification](https://www.headlesslaw.com/definitions/ai-act/substantial-modification);

   **(d)** the practical implementation of transparency obligations laid down in [Article 50](/ai-act/articles/50.md);

   **(e)** detailed information on the relationship of this Regulation with the Union harmonisation legislation listed in Annex I, as well as with other relevant Union law, including as regards consistency in their enforcement;

   **(f)** the application of the definition of an [AI system](https://www.headlesslaw.com/definitions/ai-act/ai-system) as set out in [Article 3](/ai-act/articles/3.md), point (1);

   **(g)** the practical implementation of [Article 8(2)](/ai-act/articles/8.md), [Article 9(10)](/ai-act/articles/9.md) and [Article 17(3)](/ai-act/articles/17.md) in accordance with the principle of complementarity and proportionality, with a view to ensuring consistency, avoiding duplication and minimising additional burdens when complying with the requirements of this Regulation and the requirements of the Union harmonisation legislation listed in Section A of Annex I; such guidelines shall be published by 1 August 2027.

   When issuing such guidelines, the Commission shall involve the Board and pay particular attention to the needs of SMEs, including start-ups, and SMCs, of local public authorities and of the sectors most likely to be affected by this Regulation.

   The guidelines referred to in the first subparagraph of this paragraph shall take due account of the generally acknowledged state of the art on AI, as well as of relevant harmonised standards and common specifications that are referred to in [Articles 40](/ai-act/articles/40.md) and [41](/ai-act/articles/41.md), or of those harmonised standards or technical specifications that are set out pursuant to Union harmonisation law.
2. At the request of the Member States or the [AI Office](https://www.headlesslaw.com/definitions/ai-act/ai-office), or on its own initiative, the Commission shall update guidelines previously adopted when deemed necessary.

***

[Chapter X — Codes of conduct and guidelines](/ai-act/chapters/x.md) · [← Article 95](/ai-act/articles/95.md) · [Article 97 →](/ai-act/articles/97.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.headlesslaw.com/ai-act/articles/96.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.