Article 55(2)
CurrentConditional timingDemonstrate Alternative Adequate Compliance for Systemic-Risk GPAI Where Codes or Standards Are Not Used
Applies to GPAI Provider; Systemic-Risk GPAI not relying on approved code or harmonised standard.
- Actors
- GPAI Provider
- AI class
- GPAI with Systemic Risk
- Themes
- Risk & Assurance
Tracker Networks Guidance
Where the provider does not adhere to an approved code of practice or comply with an applicable European harmonised standard, demonstrate alternative adequate means of compliance for Commission assessment.
Official text
2. Providers of general-purpose AI models with systemic risk may rely on codes of practice within the meaning of Article 56 to demonstrate compliance with the obligations set out in paragraph 1 of this Article, until a harmonised standard is published. Compliance with European harmonised standards grants providers the presumption of conformity to the extent that those standards cover those obligations. Providers of general-purpose AI models with systemic risks who do not adhere to an approved code of practice or do not comply with a European harmonised standard shall demonstrate alternative adequate means of compliance for assessment by the Commission.
Timing depends on the system
- 2 Aug 2025 — GPAI model placed on the market on or after 2025-08-02
- 2 Aug 2027 — GPAI model placed on the market before 2025-08-02
Suggested controls
Regulatory Information and Cooperation Process
Respond to reasoned regulator requests with controlled, complete and retrievable compliance information and logs.
GPAI Systemic Risk Management
Identify, assess, monitor and mitigate systemic risks arising from development, market placement and use of systemic-risk GPAI models.
Related risks
Regulatory Cooperation Failure
The organisation may be unable to provide complete, timely and understandable information, records or cooperation to competent authorities.
Unmanaged GPAI Systemic Risk
A systemic-risk GPAI model may create material Union-level risks that are not adequately evaluated, identified, monitored or mitigated.
_BestMeetsRequirements_Mid-Market_MeetsRequirements.svg)
_BestSupport_Enterprise_QualityOfSupport.svg)
_BestSupport_Mid-Market_QualityOfSupport.svg)
_BestSupport_QualityOfSupport.svg)
_BestUsability_Mid-Market_Total.svg)
_EasiestAdmin_EaseOfAdmin.svg)
_EasiestAdmin_Enterprise_EaseOfAdmin.svg)
_EasiestAdmin_Mid-Market_EaseOfAdmin.svg)
_EasiestSetup_EaseOfSetup.svg)
_EasiestSetup_Mid-Market_EaseOfSetup.svg)
_EasiestToDoBusinessWith_EaseOfDoingBusinessWith.svg)
_EasiestToDoBusinessWith_Enterprise_EaseOfDoingBusinessWith.svg)
_EasiestToDoBusinessWith_Mid-Market_EaseOfDoingBusinessWith.svg)
_EasiestToUse_Enterprise_EaseOfUse.svg)
_EasiestToUse_Mid-Market_EaseOfUse.svg)
_FastestImplementation_Mid-Market_GoLiveTime.svg)
_HighPerformer_Enterprise_HighPerformer.svg)
_HighPerformer_HighPerformer.svg)
_HighPerformer_Mid-Market_HighPerformer.svg)
_HighestUserAdoption_Mid-Market_Adoption.svg)
_MostImplementable_Mid-Market_Total.svg)
_UsersMostLikelyToRecommend_Mid-Market_Nps.svg)