Where do we start?
Identify what the tool does and whether you are assessing an AI system, a reusable model or simpler software. Check inference, autonomy, outputs and the effect on people or the environment.
Work through five checks to find the duties that apply to your AI.
Identify the tool, test exclusions, confirm your role, check risk categories and save the decision.
Start with the tool's intended use. The checks below separate system risk categories from the rules for general-purpose AI models. Record the relevant application date after you identify each duty.
An AI system infers how to produce outputs from inputs, for explicit or implicit objectives. It operates with some autonomy, may adapt after deployment, and produces predictions, content, recommendations or decisions that can influence physical or digital environments.
Software that only executes operations using human-defined rules may fall outside that definition. Recital 12 distinguishes inference from simpler software and basic data processing.
A general-purpose AI (GPAI) model can perform many distinct tasks. The model needs further elements, such as an interface, to form an AI system. Assess the model and any application built with it separately.
Sources (2)
Supports the AI system definition in Article 3(1), Recital 12's distinction from simpler software, and Recital 97's distinction between GPAI models and AI systems.
infers, from the input it receives
Explains the Commission's risk-based categories and notes that GPAI models can become the basis for AI systems in the EU.
risk-based rules for AI developers and deployers
Check Article 2 before assigning duties. Solely scientific research and development has a separate exclusion from pre-market research, testing and development. The pre-market exclusion does not cover real-world testing.
Military, defence and national-security exclusions depend on the exclusive purpose and actual supply or use. Reassess if the system later has a civilian, law-enforcement, public-security or other non-excluded purpose.
Sources (2)
Supports exclusions for military, defence, national-security, and certain scientific research and development contexts, including limits when systems are later used for non-excluded purposes.
military, defence or national security purposes
Commission Q&A confirms that research, development, and prototyping before market release and systems exclusively designed for military, defence, or national security purposes are exempt.
There are certain exemptions to the regulation.
The Act can cover EU and non-EU organisations supplying systems or GPAI models to the EU market, putting systems into service in the EU, or using systems in the EU. Non-EU providers and deployers can also be covered when outputs are used in the EU.
Assign roles per system and activity. You may be a provider when releasing your own tool, a deployer when using a supplier's tool, or a downstream provider when building an AI system with a model.
Sources (3)
Supports Article 2 scope and the operator-role structure used to route provider, deployer, importer, distributor, and GPAI obligations.
placing on the market, putting into service and use
Explains that the framework applies to actors inside and outside the EU that place AI systems or GPAI models on the EU market, put AI systems into service, or use them in the EU.
inside and outside the EU
Supports the check for third-country GPAI model providers appointing an EU authorised representative and maintaining technical documentation access.
appoint an authorised representative
The Commission explains system risk through four labels: unacceptable, high, limited or transparency, and minimal or no risk. The Act assigns duties through specific uses and articles.
Screen prohibited practices first. Then check high-risk status and transparency duties separately: Article 50 can apply to a high-risk system too. A minimal/no-risk conclusion still leaves relevant duties, including Article 4 measures to support AI literacy and other applicable laws.
GPAI models have a separate framework. A model's systemic-risk status is not a fifth system risk category. Using a supplier's model does not by itself make you its model provider.
The new ban concerning specified non-consensual intimate material and child sexual abuse material applies from 2 December 2026. Record it separately from the original Article 5 prohibitions, which already apply.
Sources (4)
Supports the four risk levels, examples of prohibited and high-risk uses, transparency requirements, and GPAI rule overview.
The AI Act defines 4 levels of risk
Primary support for Articles 5, 6, 50, 53, 55, and Annex III classification logic.
High-risk AI systems referred to in Article 6(2)
Supports scope checks for GPAI model providers and the Commission's interpretation of GPAI provider obligations.
scope of the obligations for providers
Supports the new prohibited-practice category, its 2 December 2026 application date, and the revised Annex III and Article 6(1) high-risk application dates.
Keep a record another reviewer can follow: facts, role, classification, legal source, evidence, owner and approval.
For high-risk systems, link the decision to risk management, data governance, documentation, logs, instructions, oversight, testing, conformity, registration, monitoring and incident reporting. For GPAI, link model documentation, integrator information, any required representative mandate and systemic-risk evidence.
Use obligation-specific dates. The 2026 amendment retains 2 August 2026 as the general date, but Chapter III Sections 1-3, except Article 6(5), apply from 2 December 2027 for Annex III systems and 2 August 2028 for Article 6(1) systems. Original prohibitions have applied since 2 February 2025 and GPAI duties since 2 August 2025.
Identify what the tool does and whether you are assessing an AI system, a reusable model or simpler software. Check inference, autonomy, outputs and the effect on people or the environment.
Yes, if Article 6(3) is satisfied: no significant risk of harm and at least one listed task condition. The exception is unavailable for an Annex III system that profiles people. Providers must document the assessment before supply or first use and meet the registration requirement.
Keep the intended use, EU scope facts, exclusions, roles, classification checks, source references, approvals, supporting product records and review triggers.
Sources (3)
Supports evidence for registering high-risk AI systems and certain not-high-risk Article 6(3) classifications in the EU database.
register themselves and their system
Supports measures to develop AI literacy for staff and other persons operating or using AI systems on behalf of providers or deployers, taking account of context and affected persons.
take measures to support the development of AI literacy
Primary support for keeping classification, technical, registration, monitoring, and GPAI documentation tied to the applicable obligation.
documentation of the assessment
Sorena can help you check the facts, identify missing evidence and assign the next actions.
"laying down harmonised rules on artificial intelligence"
"infers, from the input it receives"
"military, defence or national security purposes"
"placing on the market, putting into service and use"
"High-risk AI systems referred to in Article 6(2)"
"documentation of the assessment"
"risk-based rules for AI developers and deployers"
"The AI Act defines 4 levels of risk"
"inside and outside the EU"
"There are certain exemptions to the regulation."
"Before placing on the market"
"register themselves and their system"
"providers established in third countries"
"appoint an authorised representative"
"general-purpose AI models"
"scope of the obligations for providers"
"take measures to support the development of AI literacy"
Clear answers on AI Act scope, risk categories, provider and user duties, general-purpose models, disclosures, rights, assessments and deadlines.
Find the AI Act deadline for your system or model. Check high-risk dates, transparency duties, older-model transitions and the evidence to prepare.
Check who needs an Article 27 fundamental rights impact assessment, what it must contain and how DPIA reuse, notification and registration work.
Collect model documentation, integration information, copyright records and training summaries. Add testing, incident and security records for systemic risk.
Set up high-risk AI monitoring, identify serious incidents and check reporting deadlines, recipients, deployer escalation and corrective action.
Check the AI Act fine tiers, smaller-organisation caps, GPAI provider fines and the facts authorities consider when deciding a penalty.
Check serious-incident harm, preserve evidence and choose the reporting deadline and recipient for high-risk AI systems and systemic-risk GPAI models.
See which AI Act rules apply now and what comes next. Check high-risk dates, older-model transitions and the difference between legal and standards dates.
Compare AI Act legal duties with ISO/IEC 42001 management-system requirements. See which records can be reused and what certification does and does not cover.
Compare AI Act legal duties with the voluntary NIST AI RMF. Map risk records to specific requirements and identify legal steps that need separate evidence.
Choose between provider-run internal control, notified-body assessment and a product-law procedure before release.
Classify an AI tool or model before purchase or release. Check EU scope, prohibited uses, high-risk rules, transparency and GPAI duties.
Check each AI tool, decide which duties apply, and give every action an owner and evidence link.
Some high-risk systems use a provider-run assessment. Others need an authorised independent assessor or a product-law assessment.
Check whether the AI Act applies to your system or model, identify your provider or deployer role, and keep evidence for the decision.
Check GPAI provider duties for documentation, integrator information, copyright and training summaries, plus extra requirements for systemic-risk models.
High-risk providers must meet system requirements before supply. Deployers must use and monitor the system under the provider's instructions.
Check the system's risk controls, data, documentation, logs, instructions, human oversight and testing before release.
Find high-risk AI examples in recruitment, banking, education, healthcare, public services and products. Check Article 6 conditions and exceptions.
Build a compliance plan for each AI tool: your role, the duties that apply, the evidence needed and the person responsible.
Use EN 18286:2026 to organise provider quality-management procedures and keep evidence that they work for each high-risk system.
Build the technical file and provider records for a high-risk AI system, with owners and evidence links for each field.
Check Article 50 chatbot notices, synthetic-output marking, biometric notices, deepfake disclosures and public-interest text exceptions.
Check Article 5 prohibited AI practices, the narrow exceptions, evidence to retain and the new content prohibitions from 2 December 2026.
Check provider, deployer, importer and distributor roles, when changes create provider duties, and how model and system responsibilities differ.
Find the assessment route for high-risk AI, when a notified body is required, and which declaration, CE-marking and registration records you need.
Check whether software counts as AI, how models differ from systems, when embedded AI is high-risk, and which scope and role evidence to keep.
Understand high-risk AI monitoring under Article 72: the provider plan, deployer feedback, logs, corrective action, incidents and change reviews.
See which industry AI uses fall under Annex III, when Article 6(3) can apply, and what providers must document and register.
See what Article 11 and Annex IV require in high-risk AI technical documentation, from system identity and testing to monitoring and retention.
Check general-purpose model duties, systemic-risk classification, open-source conditions, copyright, training summaries, incidents and application dates.
Check AI interaction notices, technical content marking, biometric notices, deepfake and text disclosures, exceptions, accessibility and deadlines.
Check serious-incident outcomes, reporting roles, 15-, 10- and two-day deadlines, authority recipients, corrective action and the separate model route.
Check who needs an Article 27 fundamental rights impact assessment, what it must cover, and how privacy assessments, notification and registration fit.