> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/30.md). # Art. 30 — Notification procedure 1. Notifying authorities may notify only [conformity assessment](https://headlesslaw.com/definitions/ai-act/conformity-assessment/) bodies which have satisfied the requirements laid down in [Article 31](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/31.md). 2. Notifying authorities shall notify the Commission and the other Member States, using the electronic notification tool developed and managed by the Commission, of each [conformity assessment body](https://headlesslaw.com/definitions/ai-act/conformity-assessment-body/) referred to in paragraph 1. 3. The notification referred to in paragraph 2 of this Article shall include full details of the conformity assessment activities, the conformity assessment module or modules, the types of AI systems concerned, and the relevant attestation of competence. Where a notification is not based on an accreditation certificate as referred to in [Article 29(2)](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/29.md), the [notifying authority](https://headlesslaw.com/definitions/ai-act/notifying-authority/) shall provide the Commission and the other Member States with documentary evidence which attests to the competence of the conformity assessment body and to the arrangements in place to ensure that that body will be monitored regularly and will continue to satisfy the requirements laid down in [Article 31](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/31.md). 4. The conformity assessment body concerned may perform the activities of a [notified body](https://headlesslaw.com/definitions/ai-act/notified-body/) only where no objections are raised by the Commission or the other Member States within two weeks of a notification by a notifying authority where it includes an accreditation certificate referred to in [Article 29(2)](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/29.md), or within two months of a notification by the notifying authority where it includes documentary evidence referred to in [Article 29(3)](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/29.md). 5. Where objections are raised, the Commission shall, without delay, enter into consultations with the relevant Member States and the conformity assessment body. In view thereof, the Commission shall decide whether the authorisation is justified. The Commission shall address its decision to the Member State concerned and to the relevant conformity assessment body. --- # 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.mica.wtf/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/30.md?ask=&goal= ``` `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.